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.
#43 Yes we need Composer!
by pkb351 <firstname.lastname@example.org>
Wednesday May 7th, 2003 8:03 PM
You are replying to this message
If we drop composer by stating it cannot compete with commercial offerings such as Dreamweaver, there will be no viable option to Frontpage.
Frontpage developes sites best viewable with IE on Windows. I have encountered some commercial sites developed with Frontpage and many non comercial ones. Composer promotes a web which is viewable and fully functional regardless of the OS and browser used. Frontpage often promotes the ideal "best viewable with IE and Windows." In the free category for WYSIWYG web site development tools Composer is the only competition (I believe) to FrontPage. For the future of the Web (being viewable/functional regardless of OS or browser) we must not let Composer die.