Closer than yesterday, but not as close as tomorrow.Does this mean we are close to having a new version of Orbiter?!?
Closer than yesterday, but not as close as tomorrow.Does this mean we are close to having a new version of Orbiter?!?
for me, main issue with addons (other than overlapping files) is when addon requires editing one of orbiter's config file.
This is especially annoying with additional base addons - when adding a texture to a base list requires editing base.cfg.
Why not make a special folder for textures used for bases? Then Orbiter could scan it for textures list, instead of scanning config file.
To address these issues, I like Artlav's suggestion - provided the structure could be made backward compatible (doable I think, but more work for Martin).for me, main issue with addons (other than overlapping files) is when addon requires editing one of orbiter's config file.
This is especially annoying with additional base addons - when adding a texture to a base list requires editing base.cfg.
Why not make a special folder for textures used for bases? Then Orbiter could scan it for textures list, instead of scanning config file.
The "Great Filter" of OrbiterQuick_Nick said:If someone has hopes of figuring out Orbiter, they should be able to figure out how to get a compressed file open, especially if given instructions.
I don't think so, as the conventions are simple and documented. Besides, you're pulling out a big chunk of code from the core; no need to add more.I know that some people already use some generic package management system for their addons. Is there any additional functionality required that is not provided by these utilities and that would necessitate a dedicated orbiter package manager?
I like the zip file myself, just open it, dump it into a folder and you're away, reminds me of the old amiga days in a way. More programs should work like this!
I prefer the current method, but I'm open to other methods so long as I can still have multiple copies installed, and it doesn't write to the registry. I like to have one general purpose copy, one for add-on development and testing, and maybe one for say, pure "AMSO-only", etc.
Same here!I'm fine with an installer but only if we also have the option of using a Zip instead too. There's many advantages to Zips for me.