Talk:SeaMonkey:First Release

Features

• In general I think it's too late to enable new features, we are too close to the release. What about enabling SVG, Calendar, MNG etc In 1.9? We should first try to learn how to do a release without the help of the Mozilla Foundation. I suppose that alone will be much work.

If we do so we could tell the SVG and Calendar maintainers about this plan so they can concentrate on making their components ready for the end user. --Krohlas 00:17, 14 Mar 2005 (PST)

I second the idea that it's too late for any new features. Is this first release going to be a beta released near the time of the Firefox 1.1 Developer Release? Or are we foregoing betas and going to try to just do a final release? I suppose we need a roadmap... -- Schapel 12:47, 17 Mar 2005 (PST)

Calendar

• I personally do not think Calendar is ready to be turned on by default yet, I have it on in my builds, and trunk needs alot of [overall] work right now. The branch would be good, however the trunk calendar uses the new "storage" mechanics (Mozilla2:Unified_Storage) with no (as of yet) existing migrator; Justin Wood (Callek) 09:53, 11 Mar 2005 (PST)
• Indeed. We shipped all the 1.7 and 1.8 builds on OS/2 including calendar, but for 1.8b1 we had to skip it, it was just unusable. If it improves significantly until beta 2 or beta 3, we can reconsider. (But now that we have drivers or "divers" it's not our decision any more.)--Peter Weilbacher (paepse) 09:46, 15 Mar 2005 (PST)

SVG

• I feel building this is a good idea, however it is unclear to me if we would want to enable the pref to "turn it on" once built or if we would be best served leaving the pref off to make it easier for those who would want to view a page with an SVG plugin. Justin Wood (Callek) 09:53, 11 Mar 2005 (PST)

• There is lots of space in the Prefs panel under Advanced. Just add another button for SVG.
• well you did not sign this... But I feel that would be implicit in actually including SVG at all, but the question was if we enable or disable it by default? --Justin Wood (Callek) 15:42, 14 Mar 2005 (PST)

• (Sorry, am neither used to wikis nor to IRC...) I didn't follow too closely the SVG development, but I think tor had a reason not to enable it by default, we should honor that. A button in prefs should be easy enough to find.--Pweilbacher 09:40, 15 Mar 2005 (PST)

• Actually, I think this is not a good idea, at least not for the first release. If it was already on in trunk builds by default, then I might support it... but turning it on just for this release which is supposed to resemble Mozilla trunk sounds like opening a can of worms. --Alex Vincent (WeirdAl) 20:29, 15 Mar 2005 (PST)

• OK, we can always do contributed "+svg" builds of this release on the platforms where it works well.--Peter Weilbacher (paepse) 03:37, 16 Mar 2005 (PST)

• Opera 8 will be with SVG (as it seems) so we should also provide SVG enabled "1.8" releases. -- Opi 05:37, 17 Mar 2005 (PST)

• I just tested a SVG-enabled nightly build of Seamonkey. While the support is not complete, IMO it is definitely enough to have it built by default, but turned off. This way, interested users can simply turn it on via about:config (svg.enabled -> true, doesn't even need a browser restart), giving web developers something to play (and learn) with, and could lead to valuable feedback to the people working on SVG. And remember: as Seamonkey isn't Firefox, we don't have a five-megabyte download size limit! What do you all think? --Jens.b 13:10, 17 Mar 2005 (PST)

MNG

Any more thoughts on MNG? There are still lots of voters for Bug 18574 and from previous discussions it always seemed to me that there is quite some overlap between MNG wanters and Seamonkey lovers. I am running in the configuration where MNG is even used to decode PNG images since mid of last year, and since November 2004 or so (libmng 1.0.8?) I didn't have any more display problems at all, and no crashes. For the "first release" I would recommend not replacing the PNG decoder but just to add the MNG/JNG decoder which has fairly low risk. --Peter Weilbacher (paepse) 08:38, 22 Mar 2005 (PST)