So I recently saw that the mod ListGenerator had a list of scenes, which makes at least three programs (two versions of PAMM) which have this built in. Would it be better to have a "scenes" object to clearly delineate this information? We'd still need a list for backwards compatibility, but at least that list could be frozen at the current set of scenes. EDIT: Example for clarity Code: { "author": "wondible", ... "scenes": { "live_game": [ "coui://ui/mods/....css", "coui://ui/mods/....js" ] }, ... }
What we have: Code: { "author": "wondible", ... "live_game": [ "coui://ui/mods/....css", "coui://ui/mods/....js" ], ... }
Does the Windows version at least prompt for program updates, so we could say there is a point at which it is safe to remove the top-level scene names?
If you mean prompt for new versions of PAMM, then yes (as you probably just found out ). As for when to stop supporting the top-level scene names, I plan to keep the current ones in, but not add any more. If we get to a point where none of the older mods use the top-level names anymore, then I'll remove them, but it's not a big deal to keep them there.
I've updated the amdclean template to use scenes as primary and copy them down to the main object during build.
I'm on OS X, which is why I had to ask. I was referring to mod authors removing the keys, since they will only want to maintain one set.