<html><head></head><body bgcolor="#FFFFFF"><div><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">On May 19, 2012, at 11:03 PM, Basil Chupin <<a href="mailto:blchupin@iinet.net.au">blchupin@iinet.net.au</a>> wrote:</span><br></div><div><br></div><div></div><blockquote type="cite"><div>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div class="moz-cite-prefix">On 20/05/12 07:09, Alex Jordan wrote:<br>
</div>
<blockquote cite="mid:791DA80E-95E1-4E9C-B073-71BA9459DE08@gmail.com" type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=utf-8">
<div><span class="Apple-style-span">On May 18, 2012, at 10:58 PM,
Basil Chupin <<a moz-do-not-send="true" href="mailto:blchupin@iinet.net.au">blchupin@iinet.net.au</a>>
wrote:</span><br>
</div>
<div><br>
</div>
<blockquote type="cite">
<div> What is so special about this TB nightly version that none
(bar one) of the most popular Themes (Nautipolis being my
favourite) are compatible with it?!<br>
<br>
Nautipolis, thank heavens (and the author <span class="moz-smiley-s1"><span> :-) </span></span>), is
finally now compatible with Firefox 15.x, but ALL Most Popular
Themes are incompatible with Thunderbird 14.x.<br>
<br>
Anybody know why this is so? Thanks.<br>
<br>
BC</div>
</blockquote>
<br>
<div>Because none of these themes have been updated to work with
that version. Also, when talking about nightly builds, version
numbers are largely useless, and build IDs (or the hg revision
your build was built from) are much more helpful.</div>
<div>A lot of theme developers don't officially support builds
other than release builds because of the difficulty of keeping
their themes compatible.</div>
</blockquote>
<br>
Because both my Thunderbird and Firefox are Nightlies they are
therefore automatically updated - if there is an update that is -
when I start them.<br>
<br>
Therefore I saw - nor see - a reason to specify which "build" I am
using because it is always the very latest overnight build.<br></div></blockquote><div>It's standard to specify the build ID. Makes it easier for all of us to figure out what version you're using.</div><div>(This becomes especially important if you're asking about a regression.)</div><br><blockquote type="cite"><div>
Furthermore, I cannot see which "build" it is. Are you talking here
about some number or the date of the "build"/Nightly? If the latter
than I have already answered this. But if there is a number then
please tell me where to find it.<br></div></blockquote><div>Where did you answer it? In any case, I think Jeff answered this.</div><br><blockquote type="cite"><div>
The Nightly Thunderbird comes from this directory:<br>
<br>
<a class="moz-txt-link-freetext" href="http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-aurora/">http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-aurora/</a><br>
<br>
Is this the right or wrong directory?<br></div></blockquote><div>This is incorrect. This is built nightly, but it is not on the Nightly channel. It is on the Aurora channel. (I think.)</div><div>Bleeding-edge nightly builds with the very latest code can be found at <a href="http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-central/">http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-central/</a>.</div><br><blockquote type="cite"><div>
I seem to recall that some years ago one could make an Add-on work
because in its code was hard-coded a version of FF or TB and if the
version of FF or TB did not match this then the Add-on would not
work. But, using an editor, if one went into the code and changed
this hard-coded version number the Add-on would then work.<br></div></blockquote><div>The add-on would not necessarily work. Anytime this works, you're basically getting lucky that the add-on doesn't break.</div><div>This behavior was implemented because pre-Rapid Release, new versions of FF or TB were basically guaranteed to have API changes that could break add-ons. Because of this, FF assumed that add-ons would break with each new version. Nowadays, API changes happen at the same rate, but FF releases more often. Therefore, authors can now make their add-ons qualify for default-to-compatible, where FF assumes that the add-on _doesn't_ break.</div><div>In any case, themes are different. They tend to always break between releases.</div><br><blockquote type="cite"><div>
Which is what made me ask the question: what is so special about TB
14.x. But then, obviously, there is more to it than this.<br></div></blockquote><div>Again, as far as I know, there is nothing special about this version. Theme authors just haven't updated their themes to support it.</div><br><blockquote type="cite"><div>
BC</div></blockquote></body></html>