doxygen-improvement (D5252) #7052
Labels
No Label
Closed
Duplicate
Closed
Fixed
Closed
Invalid
Closed
Needs info
Closed
Won't fix
Closed
Works for me
Difficulty
Hard
Difficulty
Medium
Difficulty
Simple
Needed for Beta
Needs Design Input
Needs Info
Pathfinding
Priority
1: Release Blocker
Priority
2: Must Have
Priority
3: Should Have
Priority
4: Nice To Have
Priority
5: If Time Permits
Regression
Theme
AI
Theme
Art & Animation
Theme
Atlas editor
Theme
Build & Packages
Theme
Core engine
Theme
Documentation
Theme
Internationalization & Localization
Theme
Maps
Theme
Multiplayer Lobby
Theme
Music & Sound FX
Theme
Network
Theme
Non-game systems
Theme
Simulation
Theme
UI & Simulation
Theme
UI – Game setup
Theme
UI – In-game
Theme
UI – Miscellaneous
Theme
Website & Forum
Type
Defect
Type
Enhancement
Type
Task
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: 0ad/0ad#7052
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "Cayleb-Ordo/0ad:doxygen-improvement"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I thought ill try the new system with this change, so it wont get lost.
Thanks for the port to here! I will use the opportunity to setup the docs pipeline.
Thanks indeed for the follow up. Unfortunately the friend I asked for the logo update hasn't delivered yet. I suppose the first version will use the logo you found.
Would you be interested in this logo found in the art repo ?
The Logo itself looks good. But then we have to review the current Style i have set. For Example the right one is the current style. The other one could also be used. I personally favor the one with the red header, as the technical docs website uses the same look and feel.
f7812a7c9c
toab93b8e9ab
Hello! I have setup a rough pipeline for generating the docs. I ran it, including the upload to the website.
Can you please adapt your work and rebase it on top of Itms/docs? Then I will set the pipeline to follow your PR instead of my branch.
Thanks for your work.
@ -0,0 +1,104 @@
# 0 A.D. Licensing Details
Can you also delete LICENSE.txt so that this becomes a file move?
@ -0,0 +1,50 @@
FROM debian:trixie-slim
I have reduced this to a dockerfile where only documentation tools are installed. This documentation pipeline should not need building the game. The entity.rng file will be generated in the nightly build.
I removed my ggc13-docs Dockerfile.
@ -0,0 +18,4 @@
# Get current Branch Name to set it as the Project Number.
find_package(Git)
find_package(Subversion)
This pipeline will run on a git checkout, not an SVN checkout, you can remove SVN dependent code.
Alright, ill remove that.
@Itms using debian-latest doesn't seem really reproductible. Not sure it matters much though? Python versions maybe?
debian:bookworm
would not be reproducible either, as that image gets updated regularly (at least on each point version). I'd like this pipeline to use trixie as soon as it's out. The only downside I'd see is if a package changes name or gets deleted between the versions, but that doesn't seem to be the case for the packages used here.ab93b8e9ab
to19e4e1ffa2
19e4e1ffa2
to0928487abf
0928487abf
to6e8f476ef7
6e8f476ef7
toa76c59e4a2
a76c59e4a2
to8bf029ae31
@Itms Anything else needed here ?
Yes, a couple:
trunk.html
tonightly.html
. It is more correct but will break many links.For 2) I would assume only the files in that doxygen folder, since as far as I know source in C++ doesn't have images.
For 3) I'm not sure the name of the html file matters, for https://docs.wildfiregames.com/pyrogenesis/ works ?
For 2) i can say that the docs only need the files located under /source. See CMakeLists.txt Line 59.
But i`d like to add another point. We did not finish the discussion on the style/Logo. This could be done in a later commit, but i think that this will not be touched in a long time after we merge that.
I'm still working with someone for the logo, it will also require approval, so I think we can use the icon Itms provided. I'll make another PR with the updated art. (Will also be a good test for this pipeline) :)
Currently the old logo is configured. If we will change the logo, then we could leave that because with the current style @Itms Logo is kind of invisible :D
Checkout
From your project repository, check out a new branch and test the changes.