Getting Australis add-ons working

[codefisher]

I write a number of add-ons, and I normally try to support as many applications applications as possible. When updating one of my extensions reciently, I started to use Australis becuase it offers better intergration into Firefox and makes it a lot easier with restartless extensions. However this causes issues with, Thunerbird and SeaMonkey and Pale Moon. To fix this I have written a JavaScript module that is now a partial implimention of CustomizableUI.jsm, that if you jump though a few hoops (mainly because of the needs of Thundebird), replaces it.

I was wondering if anyone here might be interested in it. Maybe it could be put into Pale Moon, it might make a few extra extensions start working.
https://github.com/codefisher/mozbutton ... izable.jsm

[squarefractal]

While I'm not an extension dev and Moonchild is the final authority on what goes into the Pale Moon code base -- it seems very interesting indeed

IMO this should get into Pale Moon.

And of course, thank you for your efforts to make your extensions compatible with Pale Moon

[codefisher]

I was looking around the site for a bug tracker, but did not find one. Does one exist for Pale Moon where it might be better to post something like this?

[squarefractal]

https://github.com/MoonchildProductions ... oon/issues

[New Tobin Paradigm]

The problem with this is while you MAY be able to get customizableUI bits working it does not mean that it will fix anything. Not only is customizeableUI not in Pale Moon but also parts of the Australis related support structure in jetpack and jetpack based add-ons.

Simply put we can and will ONLY support add-ons using Firefox 24 level (loosely pre-australis era) technologies.

[Moonchild]

It's a very interesting approach to the problem. I do like the idea!

I think adding a shim like this would be something for extension developers to do if they desire to have their extension work on Pale Moon while keeping their actual Australis-focused code changes small. Pale Moon doesn't have Australis' CustomizableUI, and at the core shouldn't pretend to have it, because that would just cause confusion. Things not working or fully working is clear. Things half-working is a headache I'd rather avoid.

Since it's a small .jsm that they can load as a fallback, I don't really see much of an issue in theory for adding this shim to Australis-focused extensions as a translation layer between the extension's code and the API offered by Pale Moon. So, it could/should be offered as an SDK or library to extension devs instead of asking for it to be included in the core, similar to what is done with feature translation shims for different browsers in web design.

EDIT: If it's expanded further to cover all CUI functions instead of just a handful, then it may be an idea to add this to the core, but as it stands now it seems to only address a few small functions (unless I misunderstood how little is actually exposed to extensions...?). As Tobin said though: it will also not help with Australis JetPack add-ons since that would also need a different Jetpack version - and my guess is that this is what the lion's share is going to be for Australis...

[codefisher]

I am thinking of implementing most of the interface if people are interested in using it. I say most, not all, because some parts are not supposed to be used by outside code (not that it can't be used, just should not). Right now I just have what I need myself, or thought might be the most useful.

If you think it would be best as a shim, would you be willing to mention it on https://addons.palemoon.org/resources/incompatible/ as a work around if I did a complete implementation?

As to the JetPack problem, I just need them start using my SDK instead https://github.com/codefisher/mozbutton_sdk