SeaMonkey:suiterunner

From MozillaWiki
Revision as of 20:36, 25 April 2007 by Schapel (talk | contribs) (→‎Builds: add link to suiterunner builds)
Jump to navigation Jump to search
SeaMonkeylogo.png
Resources
SeaMonkey Homepage
FAQ / Help
Goals
Organization
QA
Supporters
Add-ons
Localization
Reasons
Branding
Release History
Tasks & Projects
IRC Chat Logs
Discussion
Suiterunner

Description

"suiterunner" is an internal code-name for the future version of SeaMonkey based on the "new toolkit", i.e. the same backend code already used by Firefox, Sunbird and for the most part also Thunderbird. The name is intentionally derived from "XULRunner", as the long-term goal of this project is to make SeaMonkey a XULRunner-based application.

Important changes

Compared to xpfe-based "conventional" SeaMonkey (1.0.x and 1.1.x), suiterunner will feature some quite important changes:

  • Incorporation of the same Add-On Management as Firefox, including uninstalling Add-Ons, automatic extension updates, etc.
  • Making Firefox and Thunderbird extensions compatible with suiterunner is easier than with "conventional" SeaMonkey (not all will work out-of-the-box though)
  • Profiles will be kept in a new directory, old profiles will need to be migrated (addition of a profile migrator opens doors to enable easier settings importing from other apps though)
  • New Windows installer will be based on NSIS, just like current Firefox installer

Why are we doing this?

Some of this has already been touched on above:

  • Using toolkit means we share more core files with Firefox, Sunbird, Thunderbird etc, this means we benefit from their fixes to the core code, and they benefit from ours.
  • It will be easier for extensions that work with Firefox/Thunderbird to be compatible with SeaMonkey.

Current development

Summary

For the moment, building SeaMonkey trunk in the "suiterunner" configuration is working on all platforms, but it currently ties some parts of xpfe and toolkit together in a temporary mix, still excluding some parts of toolkit from the build that we haven't yet figured out how to include without causing incompatibilities. Look for comments like "# XXX Suite doesn't want these just yet" in toolkit build files.

Bug state

The main tracking bug for suiterunner is bug suiterunner

Real blockers:

  • bug 329744 Write migrator for moving to Toolkit-based profiles
  • bug 348386 Download manager doesn't display on suiterunner builds
  • bug 351917 Create NSIS installer for SeaMonkey (suiterunner)

Possible blockers:

  • bug 349309 toolkit's extensions.js/OpenURL is app specific (GetMoreThemes/Extensions)
  • bug 363700 Software Installation (pref-smartupdate.xul) prefs page is designed for xpfe SM not suiterunner.
  • bug 370306 Move Address Book's autocomplete (and addressing widget) implementation to be based on toolkit's
  • bug 376912 Mac Classic tabbrowser looks bad.

Regression which would be caused by the switch, but no need to block:

  • bug 329742 Port SeaMonkey's splash screen code to work with Toolkit
  • bug 348437 Remove/fix nsKillAll.js for builds with MOZ_XUL_APP=1 set
  • bug 361682 Turbo mode won't work with suiterunner builds
  • bug 364168 Winhooks commandline options won't work in suiterunner
  • bug 378647 Get profile roaming working in suiterunner builds (extensions/sroaming)

No need to block:

  • bug 255807 Migrate Seamonkey UI from XPFE to New Toolkit
  • bug 336874 Make suiterunner use the same toolkit.jar as XULRunner
  • bug 342087 migrate SeaMonkey preferences to use an extended Toolkit Prefwindow
  • bug 366673 Remove remaining contents.rdf from Suiterunner (stop using installed-chrome.txt)
  • bug 373359 Suiterunner: update help viewer docs tracking bug.
  • bug 350215 Convert optional components in suiterunner to extensions.
  • bug 377185 Palm Sync extension problems on trunk builds for Thunderbird & Suiterunner.
  • bug 377953 build suiterunner package/installer via suite/installer.
  • bug 378545 Suiterunner: Change height of Location Bar Dropdown Window.

Need to decide on:

  • bug 329021 Get non-static builds of mailnews working when MOZ_XUL_APP set
  • bug 332203 Ensure the installers work with MOZ_XUL_APP set on SeaMonkey
    • Works apart from DOMI

To implement at the time of the switch:

  • bug 346604 Two "Using help" documents in suiterunner
  • bug 346605 Make openHelp() calls call suiterunner help correctly
  • bug 372856 Remove themes pane from preferences in suiterunner builds.

Already fixed:

  • bug 334478 Get suiterunner to actually run (start up a somewhat usable browser window)
  • bug 335154 Get SeaMonkey's themes registering and switching with Theme Manager (in suiterunner)
  • bug 338461 Get file -> new navigator window working in suiterunner
  • bug 339720 show warning page before showing about:config
  • bug 350221 Make suiterunner tabbrowser build on toolkit browser
  • bug 351152 Make SeaMonkey's Release Notes URL compatible with toolkit's version
  • bug 360109 make suiterunner help use SeaMonkey theme icons
  • bug 361159 Grippies missing on toolbars for Classic theme in suiterunner
  • bug 361161 Reporter doesn't work for suiterunner (MOZ_XUL_APP=1) builds
  • bug 361191 In suiterunner preferences once Mail & Newsgroups -> Tags pane is selected you can't get of it.
  • bug 361193 In suiterunner preferences, advanced -> Mousewheel pane doesn't display
  • bug 361203 Suiterunner: More Information button doesn't work on Smart Browsing pane.
  • bug 361303 Showing about as a dialog doesn't work in suiterunner.
  • bug 361683 Help buttons missing for mailnews items in suiterunner builds
  • bug 361903 Personal Toolbar expands when items are hovered
  • bug 364141 toolkitify composer's startup handler
  • bug 365181 loadHelpRDF with help window in SuiteRunner
  • bug 366367 SeaMonkey link on mailnews start page is incorrect in suiterunner
  • bug 366901 Edit->Copy doesn't work in the SuiteRunner Error Console
  • bug 370308 Color pickers on colors pref pane don't work in suiterunner
  • bug 371973 Links in Suiterunner Help has wrong color
  • bug 378279 [suiterunner] Missing sidebar (and wrong tabbrowser) close button in Classic

Note to Extension Authors

When suiterunner becomes SeaMonkey, extensions which supply contents.rdf files and chrome.manifest files will be broken if the the chrome.manifest does not explicitly define what is in the contents.rdf file (e.g. overlays, content etc).

The reason is that in suiterunner builds, contents.rdf files will be ignored if chrome.manifest files exist. If you need to define application specific overlays etc then Chrome Registration will tell you how to do it.

Related Wiki Pages

Builds

There are some experimental tinderboxes listed on the SeaMonkey-Ports tinderbox page, the phlox (mac) and tpol (win32) ones also upload suiterunner packages into the seamonkey/tinderbox-builds directory of ftp.mozilla.org.

For building yourself, just add the lines 

MOZ_XUL_APP=1
ac_add_options --enable-static-mail

to your SeaMonkey trunk .mozconfig file.

Retrieved from "https://wiki.allizom.org/index.php?title=SeaMonkey:suiterunner&oldid=55161"