Changes

Jump to: navigation, search

FlightGear wiki:Village pump

12 bytes added, 14:11, 5 May 2015
Aircraft Page Organization
Here are a few ideas:
* '''Give aircraft a codeword or project name.''' For instance, the Boeing 787 (Dream Project) or Boeing 787 (GPL Project) to distinguish between them. Then list them like that in the index as well. When you both have a --aircraft= A319 and A319-131, what are you going to do when the next person comes around and wants to design an A319? It would make more sense to migrate to a structure of say B787-8-Dream and B787-8-GPL. If you make a piece of software, you're not going to go calling your software 'Conference Manager', with the next person making the similar stuff calling it 'Conference Manager 2', but rather ConferenceTime and and ConferenceMaster. It's easier to do with Naming your work after aircraft but it in the current way gets bloody confusing.
* I imagine that perhaps as a bit of a continuation of the above, '''people try to distinguish between their models by giving them very specific names, such as Boeing 707-338'''. I realize that people want to work on it themselves, but from a broader perspective, how much technical difference is there really between these? The A319 should also work with the corresponding changes as a A320- it is an identical cockpit and much the same fuselage. IMHO, it should have been filed as an A320 instead with only one model, an A319. As for the Boeing, give it a codeword, such as Boeing 707 (Qantas Project). It even makes it more marketable.
70
edits

Navigation menu