235
edits
User:Mnyromyr: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
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.) | 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.) | ||
While the actual transition to toolkit is outlined like this: | |||
<pre> | |||
KaiRo 1) pack the toolkit version via jar.mn where we have a null diff | |||
KaiRo 2) work on doing the same for all easy cases (contribute eventual | |||
improvements from our side to toolkit) | |||
KaiRo 3) for the hard stuff: eventually create new xbl files/bindings in the | |||
communicator/ package that extend toolkit versions, or that do our | |||
own implementations where applicable | |||
</pre> | |||
making /xpfe toolbars base upon /toolkit (in #3 above) will be problematic: | |||
1. Make chrome://global/content/bindings/* refer to /toolkit and introduce chrome://xpfe/content/bindings/* for /xpfe | 1. Make chrome://global/content/bindings/* refer to /toolkit and introduce chrome://xpfe/content/bindings/* for /xpfe | ||