Talk about add-ons and extension development.
9 posts • Page 1 of 1
Hi -- I maintain the addon "search results sort by date not relevance": https://addons.thunderbird.net/en-US/th ... src=search
It's a dead-simple overlay extension that pulls in a .js file to overwrite a single method (FacetContext.initialBuild()) in order to always sort search results by Date by default.
My understanding is that my legacy webextension will no longer work with aurora and beta versions coming down the pipe because legacy webextensions are no longer supported.
Do I further understand correctly that the new API offers no way to adjust these search results? I couldn't find anything documented, but I know basically nothing about all this.
I read in a recent thread here that I might be able to put code in something called "implementation.js" and still make it work. Are there any tutorials or guides about that? And does anyone know how I would reference FacetContext from that file?
Presumably this implementation.js trick is temporary -- where is the proper place to request API additions?
Incidentally, the related bug regarding the search order is here: https://bugzilla.mozilla.org/show_bug.cgi?id=663859 -- if anyone feels inspired to make a patch, a lot of people would be grateful.
I would ask for help on the topicbox site.
Thunderbird addons forum
I don't know how to override a chrome file in a Thunderbird WebExtension without the legacy API. (removed in Thunderbird 74)
Thunderbird WebExtensions APIs
Thunderbird WebExtensions Experiments
http://firefox-source-docs.mozilla.org/ ... xperiments
Here is a simple implementation.js example that I believe works with Thunderbird 74 and later. (doesn't override a chrome file)
PopMailListRecipients 2 Version 1.1
http://github.com/cleidigh/ThunderKdB/t ... ents-2/src
The newer versions use the addressBooks API and compose API, not the implementation.js file.
Thanks! I posted over there.
The question I asked there was: if this "experiments" route works for me, is it going to go away in a few versions as well? I assume that if the "experiment" is brought in to the API it won't, but if no changes are made to the API, is the "experiments" just a kind of temporary sandbox? I'm just trying to figure out if it's worth my time going to school on this or not. Thanks.
I read that experiments should not be seen as a long term solution.
Comment by Magnus
Intent to desupport traditional addons
Other thread over there
Hmm, I guess option C is the only way.
Option A: convert addon to a WebExtension
Option B: convert addon to a WebExtension Experiment
Option C: integrate functionality into core
Thank you morat -- I have come to the same conclusion. I have already figured out how to do the integration; now the real work begins: figuring out how to compile TB, test it, generate a proper patch, and submit it.
I'll see what I can do.
So, did this work out OK for you? (us?)
If you are ever bored, maybe you can help with this:
See also one or more of these:
9 posts • Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest