MozillaZine

Daniel Glazman Outlines Future of Mozilla Composer

Wednesday May 7th, 2003

The new Mozilla Roadmap set out clear paths for Mozilla's Web browsing and mail/news applications with the continuation of the Mozilla Firebird and Mozilla Thunderbird projects. However, the future of the other Mozilla Application Suite components, such as Composer (Mozilla's Web page editor), was left less certain. Last month, Daniel Glazman, a member of the Mozilla Editor team and author of the popular CaScadeS stylesheet editor (now landed on the Mozilla trunk but not built by default), volunteered to continue maintaining Composer. Daniel has published a weblog posting outlining his plans for the future of Composer, which will live on as a standalone application rather than as a Firebird extension. The laundry list of planned improvements includes better CSS editing abilities, XHTML 1.0 support, an extension to allow MathML to be used and support for HTML forms. Improvements will also be made to make it easier for authors to create new extensions, opening up even more possibilities for Composer's future.


#15 Re: How can they make it seperate?

by mlefevre

Wednesday May 7th, 2003 9:17 AM

You are replying to this message

it does. Mozilla Editor (linked in the article) is used by Composer and for the embeddable HTML editing widget used for mail and other stuff. That will (necessarily) stay part of Gecko and be shared by Firebird, Thunderbird and the "standalone" Composer. The bits of Composer (the UI, for example) that aren't part of that Gecko core will live in a separate app, instead of being an extension on top of Firebird (which would be more like the current situation, where of course browser, mail and composer are all part of the same big app)

that's my understanding, anyway...