GAP & PRO Themes... now open source

[ll00ll00ll00ll]

But it is, in fact, already working for the aforementioned two extensions. Would a simple field for the three core themes only (Wizards, Grey, Brown) be that much of a difference? I mean I get your point of having an elaborate system being an overload, but as far as I know, the other modules are not mutually exclusive - you can load and access all the desktop decal extensions -, so no need for the whole classification. I would probably have one internal field, which stores what mutex type the module is - which right now could either be language font, or theme -, and from each set category you can only load one.

But alas, I don't know how elaborate / complicated can and should the loader be, so it might need way more than just a field in the extension's xml file.

You have officially moved past my pay grade...

[edem]

You have officially moved past my pay grade...

Hah, sorry And I did not mean *you* should be doing it, especially the whole original point was that you retire from maintaining the extension, it just felt like in context to mention here.

[Moon Wizard]

Yes, there was actually a system like that in place at one point, and guess what? It added quite a bit of extra complexity to the launcher and client extension loading code; but no one actually ever used it. Everyone had to agree on the mutex phrase to use, and verify when prerequisites and conflicts would occur. The short answer is this is actually quite a bit more work than just communicating to the users up front and helping them through forums/support.

Regards,
JPG

[dulux-oz]

...but no one actually ever used it...

Ah, this is me being pedantic, but I use it: its in all the DOEs, and documented as such. It's used for a couple of reasons: to allow others to specify in their own Extensions if they don't want to conflict with a given DOE, and because I had an idea at one stage to combine all the DOEs into a DOE-Suite which would need to exclude each individual DOE from loading.

[LordEntrails]

Ah, this is me being pedantic, but I use it: its in all the DOEs, and documented as such. It's used for a couple of reasons: to allow others to specify in their own Extensions if they don't want to conflict with a given DOE, and because I had an idea at one stage to combine all the DOEs into a DOE-Suite which would need to exclude each individual DOE from loading.

Exception to the rule! Don't we say the problem with RPGs is their is always an exception? Just be happy we appreciate you being one of the exceptions!

[dulux-oz]

Exception to the rule! Don't we say the problem with RPGs is their is always an exception?

Oh, so I'm a problem, am I?!

[LordEntrails]

Oh, so I'm a problem, am I?!

Your words I said you were an "exception"

[dulux-oz]

Your words I said you were an "exception"

Oh, so now I'm an "exceptional" problem?!

[LordEntrails]

Oh, so now I'm an "exceptional" problem?!

Well, I had thought about using the word "challenge" instead of problem, so I guess that makes you an "exceptionally challenging problem"? I can think of a few people who wouldn't argue that point

[dulux-oz]

Well, I had thought about using the word "challenge" instead of problem, so I guess that makes you an "exceptionally challenging problem"? I can think of a few people who wouldn't argue that point

Touché