<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=windows-1252">
</head>
<body smarttemplateinserted="true" text="#000000" bgcolor="#FFFFFF">
<div id="smartTemplate4-template"><img style="margin-top: 1em;
float: right; box-shadow: 1px 1px 2px rgba(20, 20, 20, 0.4);"
moz-do-not-send="false" class="myLogo"
src="cid:part1.F5256512.383D8207@gmail.com" alt="Get
Thunderbird!" height="15" width="94">
</div>
<div id="smartTemplate4-quoteHeader">
<style type="text/css" scoped="">
#newHeaderAG1 b { font-weight:bold; color: #990033; min-width: 4.5em; max-width:none; display:inline-block;}
</style><br>
<blockquote type="cite">bootstrapped add-ons, which will at least
still be supported, can change/access anything overlay add-ons
can, so there is no loss in functionality. Only that it's a bit
more elaborate to do.
</blockquote>
<p>I have done it in my Menu-On-Top Addon, had some problems with
moving my code into multiple jsm modules, but it did support
using a XUL overlay for the preferences so as long as we have
XUL I guess it's only a "bit" more elaborate. My Addons have
25k+ lines of code so there may be some fall-out but I guess we
shall pass that bridge when we come to it. <br>
</p>
<p>
<blockquote type="cite">Patrick B has a patch to simulate it
using JavaScript.
</blockquote>
Sounds great! Will you post some more data for creating test
cases on mozilla.dev.apps.thunderbird list?</p>
<p>Actually, do we have a specific list dedicated for mail Add-on
developers? If not, maybe it would be something that would be
worth while for Ryan to set up.<br>
</p>
<p>Axel<br>
</p>
<br>
<blockquote type="cite" style="margin-bottom: -20px !important;
padding-bottom:20px !important;">
<div id="newHeaderAG1" style="font-size: x-small; padding:1em;
background-color:rgba(220,220,240,0.4); border-radius:3px;"><b>Subject:</b>Re:
Supporting future addon development<br>
<b>From:</b>Magnus Melin <a class="moz-txt-link-rfc2396E" href="mailto:mkmelin+mozilla@iki.fi"><mkmelin+mozilla@iki.fi></a><br>
<b>To:</b>Tb-planning <br>
<b>Sent: </b>Saturday, 21/04/2018 15:05:46 15:05 GMT ST +0100
[Week 16]<br>
</div>
</blockquote>
</div>
<blockquote type="cite"
cite="mid:a6132b96-ed7f-6240-fe60-63755048bace@iki.fi"
id="mid_a6132b96_ed7f_6240_fe60_63755048bace_iki_fi" class=" cite">We're
still working to see if it's viable to allow the traditional
overlay mechanism for 61 and beyond, Patrick B has a patch to
simulate it using JavaScript.
<br>
But bootstrapped add-ons, which will at least still be supported,
can change/access anything overlay add-ons can, so there is no
loss in functionality. Only that it's a bit more elaborate to do.
<br>
<br>
-Magnus
<br>
<br>
On 21-04-2018 16:53, Axel Grude wrote:
<br>
<blockquote type="cite" id="Cite_4004022" class=" cite">Both at
least XPCOM access and the overlay mechanisms are vital for
writing functioning "deep" add-ons (whether you label that
legacy or some other term doesn't really matter and does not
detract from the fact that it is currently not replaced with a
viable alternative that gives full access to everything.
<br>
</blockquote>
_______________________________________________
<br>
tb-planning mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:tb-planning@mozilla.org">tb-planning@mozilla.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/tb-planning">https://mail.mozilla.org/listinfo/tb-planning</a>
<br>
</blockquote>
<br>
<br>
</body>
</html>