On Wed, 24 Apr 2013 15:26:25 -0400 Bill Davidsen <[email protected]> wrote:
> Paul B. Gallagher wrote: > > Beauregard T. Shagnasty wrote: > > > >> Composer is extremely old and hasn't been looked after in many > >> years. I'd suggest, if you want something this simple, that you > >> look into BlueGriffon, which is still currently being developed. > > > > Given that situation, and since BlueGriffon is a "next-generation > > Web editor based on the rendering engine of Firefox," how about the > > developers start bundling /that/ instead of Composer? > > > Sure, take out the part that the rest of us use for what we do, and > replace with something that suits you better. Composer works > perfectly for what it does, ideal for small simple web pages, HTML > documents, etc. A quick look the Composer component at bugzilla seems to indicate that much of what it does is not working perfectly. > If someone wants additional features by all means > identify what suits you and go use it. Contribute time and/or money > to get it added to seamonkey. NOTE: added not swapped. > > You were given the web site, can't you even be bothered to go get the > tool yourself and not break the workflow of hundreds or thousands of > other users who are using the tool you want to remove. Why don't you > go BUY one of the commercial tools if they suit you better? I don't expect it will be replaced, but IMO* the day will come when the unmaintained Composer will be too far bitrotted to continue including it with SeaMonkey. You might want to start archiving SeaMonkey installers, so you'll always have it handy. * I'm not part of the SeaMonkey team, so take my opinions about SeaMonkey's future with a big grain of salt. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
