Hi,
as we all know, legacy XUL add-ons will soon not be supported any more
and those who wish to convert their add-on to a WE Experiment need to
make it restartless first.
So I did just that for ThunderHTMLedit and I enclose the resulting
bootstrap.js file.
Using ExtensionSupport.registerWindowListener() and
MozXULElement.parseXULToFragment() has made this conversion rather easy,
and hadn't the add-on been such a forked mess, the entire process would
have been easy, but I needed to straighten out the initialisation path
to adjust the scripts previously run via the XUL <script> tag.
The add-on is not on Github, but you can get a version from ATN and
inspect it.
Jörg.
Hi Jörg,
would you suggest to use your approach as a "standard suggestion" for
XUL based addons? I would then add this to the update guide on
developer.thunderbird.net.
Thanks for your time and your help,
John
Am 29.10.2019 um 11:28 schrieb Jörg Knobloch:
Hi,
as we all know, legacy XUL add-ons will soon not be supported any more
and those who wish to convert their add-on to a WE Experiment need to
make it restartless first.
So I did just that for ThunderHTMLedit and I enclose the resulting
bootstrap.js file.
Using ExtensionSupport.registerWindowListener() and
MozXULElement.parseXULToFragment() has made this conversion rather
easy, and hadn't the add-on been such a forked mess, the entire
process would have been easy, but I needed to straighten out the
initialisation path to adjust the scripts previously run via the XUL
On 05/11/2019 15:36, John Bieling wrote:
would you suggest to use your approach as a "standard suggestion" for
XUL based addons? I would then add this to the update guide on
developer.thunderbird.net.
Yes, could be good for the ones that only overlay one or very few XUL
elements.