Re: Composer as a separate application
Jean-Marc Desperrier <[email protected]>
| Newsgroups | gmane.comp.mozilla.devel.editor |
|---|---|
| Message-ID | <[email protected]> |
Juhani Tenhunen wrote: > Thanks, Jean-Marc! And the connections with SeaMonkey Composer??? Well, I can't say much about that. I know SeaMonkey Composer did gain a few enhancements in the last years, but not exactly how it happened. It seems to me that even though Nvu developement was in a separate tree, some of it's enhancements did make it to SeaMonkey Composer. In the future Mozilla Composer might make it quite obsolete, except if the Seamonkey team makes, when the time comes, the effort to reintegrate M/C inside Seamonkey in a Sunbird/Lightning way. Except also if some of the M/C changes are in components that are still shared with SeaMonkey Composer, so that it can get those enhancements easily. Don't forget in what I say that the M/C project is just in early infancy, and has for now little existence outside of some mentions in developer's blogs.