MozillaZine

Mozilla 1.0 RC1 Released

Thursday April 18th, 2002

mozilla.org today released the first 1.0 Candidate, in preparation for a final 1.0 build. They'll be using RC1 to evaluate where the 1.0 branch stands as far as crash bugs, and other things that drivers@mozilla.org are tracking. RC1's changes since 0.9.9 include the abilty to view the source of a cgi (the most duped bug), reorganized context and main menus, LDAP over SSL, return recipts, new animated mail alerts on Windows, Download Manager, final xul syntax changes, and numerious other bug fixes.

You can download RC1 from mozilla.org's Releases Page or read the Release Notes. We highly encourage you to download the talkback enabled builds, so crashes can be found and logged prior to 1.0. (These pages haven't reached mozilla.org yet, you can grab builds from the FTP site.)

Once people start using RC1 and drivers@mozilla.org get a handle on how the reception of it goes, they will be deciding whether or not to release another candidate or 1.0 itself. We'll keep you updated on this process, and let you know what is decided.


#15 Composer Shortfalls

by CosmicDreams <cweber@gac.edu>

Thursday April 18th, 2002 4:50 PM

You are replying to this message

I enjoyed using mozilla for about 3 years now and I'm very happy that a 1.0 release is quickly approaching. I know that only a few key bugfixes stand between this release candidate and primetime. I would like to take this time to talk a little about were I'd like to see my favorite component (Composer) by the next release (2.0)

These issues are composer as I see it:

1. Lack of Composer specific sidebars. Dom inspector, Javascript editor, and especially Advanded editing would be great to have as side bars or a collection of sidebars.

2. Nasty parser bugs: My personal most hated bug, Composer reformats source code (even though turned off in prefs) is still haunting composer. There are a few other parser bugs still spooking around that should be squashed if serious web programming with composer is mozilla's aim.

3. In the far future we main even be able to implement rudimentary command compleletion, code snippets, and other features advanced (yet current-generation) programming development interfaces use.

4. Support for WebDAV, CSS, XML, MathML, P3P, and the W3's Web Accessibility Initiative integrated into the GUI as well as the app.

Thankfully this time around we won't have to reinvent the wheel again. With higher system requirements, dedicated programmers, and cooperation within the community this is all possible.

I hope that someone directly involved with composer can comment on what it will take to make this happen and how I can get started in grasping the scope of these issues.