User:Mnyromyr: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
No edit summary
 
(20 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Some thoughts on the Seamonkey /xpfe to /toolkit transition ==
Some unordered thoughts about SeaMonkey and things I'd like to see hacked, maybe even by myself. '''<tt>;-)</tt>'''
 
<ul>
Apart from the backend stuff like /bootstrap etc., porting the Seamonkey bindings will pose quite some problems. Toolbars, for example, are quite different: /xpfe has grippies, /toolkit's toolbars are customizable... (And both are non-movable, btw.)
<li>[https://bugzilla.mozilla.org/show_bug.cgi?id=360488 Stuff we (may) want to port over from Thunderbird into SeaMonkey MailNews (bug 360488)]</li>
 
<li>'''[[SeaMonkey:MailNews:CodingStyle|Guide on approved SeaMonkey MailNews coding style]]'''</li>
Making /xpfe toolbars base upon /toolkit will be problematic:
<li>[[User:Mnyromyr:MailFilters|Improvements for SeaMonkey MailNews filters]]</li>
 
<li>[[User:Mnyromyr:MessageViews|Fixing Message Views]]</li>
1. Make chrome://global/content/bindings/* refer to /toolkit and introduce chrome://xpfe/content/bindings/* for /xpfe
<li>[[User:Mnyromyr:BayesFacts|Technical Notes on the Bayesian Junk Filter]]</li>
 
<li>[[User:Mnyromyr:SeaMonkeyXPFE2toolkit_widget_transition|SeaMonkey /xpfe to /toolkit widget transition]] (historic)</li>
<ul>This means touching all Seamonkey stuff that relies upon the /xpfe implementation and will break lots of addons doing the same!</ul>
</ul>
 
2. Keep chrome://global/content/bindings/* refer to /xpfe and introduce chrome://toolkit/content/bindings/* for /toolkit
 
<ul>This will not work without changes to /toolkit, because /toolkit bindings expect to be available via chrome://global/content/bindings/* (as do /xpfe bindings) and so would refer to the (wrong) /xpfe ones.</ul>
 
3. Drop /xpfe and put all the stuff into /toolkit
 
<ul>This means putting lots of #ifdefs into /toolkit, because they most probably won't accept all the stuff back they dropped. Furthermore, it's a quite ugly.</ul>
 
4. Make /xpfe binding files include the /toolkit files via some ?xbl-include? magic
 
<ul>This will mean implementing such an ?xbl-include? processing instruction in the first place (''or do we already have something like that?''). It will have problems with some edges of XBL inheritabce, too.</ul>
 
Currently, I see only 4. as a useful way to make /xpfe bindings be based upon /toolkit, and that still needs some exploring...

Latest revision as of 20:11, 21 August 2009

Some unordered thoughts about SeaMonkey and things I'd like to see hacked, maybe even by myself. ;-)

Retrieved from "https://wiki.mozilla.org/index.php?title=User:Mnyromyr&oldid=163511"