Howto talk:Start core development: Difference between revisions
Jump to navigation
Jump to search
m (moved [[Talk:Howto: Start core development]] to [[Talk:Howto:Start core development]]: Robot: Moved page) |
No edit summary |
||
| Line 20: | Line 20: | ||
* list of FG related people (i.e. developers) | * list of FG related people (i.e. developers) | ||
* gdb, valgrind, gprof, gcov | * gdb, valgrind, gprof, gcov | ||
== Use of "repo" links in wiki pages. == | |||
I'm not sure there's much advantage to using the "repo" link system. It's an abstraction that protects us against something that happens extremely rarely (changing of the main git repositories) at the cost of an obscure macro-like thing in the wiki text. Personally i'm with the Python philosophy of "Explicit is better than implicit" in this case. Apart from anything else, the most likely change to repositories is not a simple move to different location, but a merging of flightgear and simgear into a single repository, for which the repo macro is useless. [[User:Cgdae|Cgdae]] ([[User talk:Cgdae|talk]]) 10:34, 22 November 2020 (EST) | |||
Revision as of 15:35, 22 November 2020
Open questions
- merge requests (post follow-up to mailing list and file review via issue tracker)
Planned improvements
- navigating the source trees (FG + SG)
- FG entry point (bootstrap.cxx)
- the FG main loop
- FG subsystems
- adding new fgcommands
- adding new network protocols
- adding new telnet/props commands
- adding new startup options (options.cxx)
- adding new subsystems
- networking
- scripting
- GUI code
- instruments
- list of FG related projects (URLs, type of software)
- list of FG related websites
- list of FG related people (i.e. developers)
- gdb, valgrind, gprof, gcov
Use of "repo" links in wiki pages.
I'm not sure there's much advantage to using the "repo" link system. It's an abstraction that protects us against something that happens extremely rarely (changing of the main git repositories) at the cost of an obscure macro-like thing in the wiki text. Personally i'm with the Python philosophy of "Explicit is better than implicit" in this case. Apart from anything else, the most likely change to repositories is not a simple move to different location, but a merging of flightgear and simgear into a single repository, for which the repo macro is useless. Cgdae (talk) 10:34, 22 November 2020 (EST)