User:Mnyromyr: Difference between revisions

Jump to navigation Jump to search
no edit summary
(use communicator.css for the toolkit derivation issue)
No edit summary
Line 3: Line 3:
  <li>[[User:Mnyromyr#SeaMonkey_.2Fxpfe_to_.2Ftoolkit_widget_transition|SeaMonkey /xpfe to /toolkit widget transition]]</li>
  <li>[[User:Mnyromyr#SeaMonkey_.2Fxpfe_to_.2Ftoolkit_widget_transition|SeaMonkey /xpfe to /toolkit widget transition]]</li>
  <li>[[User:Mnyromyr:TB2SM|Stuff we (may) want to port over from Thunderbird into SeaMonkey MailNews]]</li>
  <li>[[User:Mnyromyr:TB2SM|Stuff we (may) want to port over from Thunderbird into SeaMonkey MailNews]]</li>
<li>[[User:Mnyromyr:MailFilters|Improvements for SeaMonkey MailNews filters]]</li>
</ul>
</ul>


Line 60: Line 61:
neglect the XULRunner case. Targetting XULRunner will mean that we have no (nice) chance of tinkering with the toolkit itself, we're bound to derive from it.
neglect the XULRunner case. Targetting XULRunner will mean that we have no (nice) chance of tinkering with the toolkit itself, we're bound to derive from it.


But then Neil told me about the communicator.css, and now the toolbar transition [https://bugzilla.mozilla.org/show_bug.cgi?id=282188 bug 282188] has a nice patch that even allows for usage of both toolkit and XPFE bindings...
But then Neil told me about the communicator.css, and now the toolbar transition [https://bugzilla.mozilla.org/show_bug.cgi?id=282188 bug 282188] has a ''little'' patch that even allows for usage of both toolkit and XPFE bindings...


The derived bindings there are stored in chrome://communicator/content/bindings/, more are likely to follow.
The derived bindings there are stored in chrome://communicator/content/bindings/, more are likely to follow.
(Oh, I now see that Neil proposed that, too - nice :) )
(Oh, I now I alter this page I see that Neil proposed that, too - nice :) )
235

edits

Navigation menu