<< Weekly Status Report, W20/2007 | The roads I take... | Integration eines Magento-2-Webshops mit FreeFinance und selbstgebautem Warenmanagement >>
Working on SeaMonkey 2.0
Using the internal codename of "suiterunner", our development team, has been working for almost 1.5 years now on a project officially named "Turn on the MOZ_XUL_APP flag for SeaMonkey", and esp. Mark Banner (Standard8 on IRC) has invested uncounted hours of work into that (sub)project. While it sounds easy on the surface - after all it's just turning on one simple build flag - this means completely replacing a significant layer in SeaMonkey's codebase with different, newer code, which is to a big part derived from our old code, but has evolved a lot to support Firefox and a growing base of other toolkit-based applications.
Looking at a diagram of the Mozilla Platform recently posted by Mike Schroepfer in a recent blog post, one can get a rough impression of what we're doing here, as we're replacing the layer titled "Toolkit" in this graphic. The changes range from the application startup process via extension management to available/supported/different UI "widgets" and touches a really big range of code areas in between.
The good news is that after having experimental builds of such a SeaMonkey version available for some time, we got them working well enough so that we can retire the old xpfe-based suite and replace it with that new toolkit-based variant on the development trunk. Those are still versions intended for developers and may not work as expected, it's trunk nightlies after all - they just make all your data get lost and your computer to explode. Well, even if this might probably not happen, they are still not though for production use and will have many bugs and regressions - but they should be basically usable. Note that we're changing the base toolkit, but we still haven't managed to get everything working with that new toolkit, so we're still not using the same code as stock XULRunner everywhere, we're excluding some toolkit parts and using our old code instead - until we figure out how to get all that stuff done in the new world (wallet and download manager are examples of that).
Still, pretty major changes are happening throughout the code - for users, the new extension management and new profile location are probably the most notable changes caused directly by that toolkit change. But then, we also have the new icon set as a very visible change, and cairo-based Gecko gives us an additional palette of changes. The more we were thinking about version numbers for a release that will result of this work, we realized that such major changes call for a full major version bump, just upping the minor version number one or more steps from the previous 1.1 version wouldn't fit what's actually happening here.
Because of that, we decided that the suite based on Gecko 1.9 will be called SeaMonkey 2.0.
Of course, we are not anywhere near a real release yet, so when the switch to "suiterunner" will actually land on trunk this week, we'll change the version number to clearly tell that this code is still preceding a first alpha of 2.0, or to make this description fit into a version code, that this is 2.0a1pre code.
Still, this will be a quite important step on the road to a SeaMonkey 2.0 - thanks for everyone helping us to get here, and everyone still helping us continue on that path!
Entry written by KaiRo and posted on May 22nd, 2007 21:57 | Tags: Mozilla, release, SeaMonkey | 5 comments | TrackBack
Hey, you want to tell the people in charge of the form manager that the "new" one in the 2.0 alphas stinks out loud? It doesn't fill in form fields. What it does is remember what I've entered in to every field ever bloating some database file and not even offering to save my personal info the way 1.x did. It's stupid and needs to go back to how it was, SRSLY.
hi, the seamonkey 2.01 looks good and works good, thanks -
but here is my suggestion - a suite is not complete if
it does not provide some sort of calendar or lightning.
( 90% all in one seamonkey 2.0 ? )
Jaisen has adapted lightning to work with SM2. I have been using it for 10 months without problems and it has data 2yrs old so it willtransfer your history.
how to get the mentioned adapted lightning version
for SM2.01 ? thanks in advance.