Pithecanthropu
New member
- Joined
- Jan 23, 2009
- Messages
- 31
- Reaction score
- 0
- Points
- 0
I know that, for example, an accounting application might not have a "meshes" folder, but in general is this how shrink-wrapped software is developed? I refer to the way that different types of configurational input are distributed into "config", "meshes", "scenarios" folders and so on. Obviously, I wouldn't expect a project management tool to have a "Flights" folder. But would the overall architecture of the accounting app be similar?
I've noticed that Orbiter add-ons all seem to follow the same directory structure as Orbiter, and they all instruct the user to unpack them in the application root directory. Is this also a typical approach? If I develop something of my own using this general principle, do I need to get permission from Martin to use this design?
I've noticed that Orbiter add-ons all seem to follow the same directory structure as Orbiter, and they all instruct the user to unpack them in the application root directory. Is this also a typical approach? If I develop something of my own using this general principle, do I need to get permission from Martin to use this design?