Talk:SeaMonkey:Home Page: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 27: Line 27:
Mreimer, what are these disadvantages of the stand alone FF/TB apps?  Just curious.
Mreimer, what are these disadvantages of the stand alone FF/TB apps?  Just curious.
-[[User:drseuss9311|DrSeuss]]
-[[User:drseuss9311|DrSeuss]]
--[[User:Mreimer|Mreimer]] 09:13, 10 Mar 2005 (PST)
To name only a few of them:
- I don't like to install several apps (I don't like the concept of creating several applications out of something that fits great in a suite at all)
- I don't like the "simplified" interface of Firefox and Thunderbird
- Firefox and Thunderbird don't work together as good as mozilla mail and mozilla navigator in the suite (firefox deals with tb as good as with every "foreign" mailer)
- I don't have Composer and Chat if I use just the single applications

Revision as of 17:13, 10 March 2005

Difference between this effort and Mozilla2

- Could someone tell me the difference between this effort and Mozilla2?

Well, there no relation :-) Mozilla2 is about making major change in the Core (the low level part shared between all mozilla.org applications) to support new advanced functions. Between two release of an application, it's difficult to make such change, that involve a significant risk of unstability. OTOH not doing that means the evolution of the soft is impaired, and it will keep forever some code whose shortcomings are well known, and that at the end more time has been spent correcting that would have been needed to write again better.

The Seamonkey effort is about continuing to release new versions of the mozilla suite application, the original mozilla, that is in danger of dying in favor of Firefox and Thunderbird. Initially FF/TB were just separating the navigation/mail code from the whole of the suite, but they have now evolved in their own direction that not every user of the suite likes.

Idea about the best way to do new Seamonkey releases

I have some idea about the best way to do new Seamonkey releases. See my user page for that jmdesp

If would like to know if other people share my view, and if they approve including this plan on the Seamonkey effort pages.

Question - FF & TB under SM?

If the seperated Thunderbird and Firefox are going to be the focus from Mozilla now, and (IMHO) most Seamonkey (Browser Suite) users use the brower/mail over other Suite features in general, than why can't an "official" bridge be made for a unified interface to the 2 seperate apps? This would allow a seamless transisition between mail and browser, a standardized install routine, and insure no overlap of features for expediant processing and coding. Maybe call it the "ThunderFox Shell"? Justa' wonderin'...

MRK

--Mreimer 00:33, 10 Mar 2005 (PST) This is not the goal of this project. The goal is not only to have a single application for mail and browser. The goal is to have the whole look and feel including all the advantages of the (in my opinion more advanced) GUI in the suite and "backport" the few advantages that Firefox and Thunderbird have to the "new suite", but don't add the disadvantages of the two single applications.

Mreimer, what are these disadvantages of the stand alone FF/TB apps? Just curious. -DrSeuss

--Mreimer 09:13, 10 Mar 2005 (PST) To name only a few of them: - I don't like to install several apps (I don't like the concept of creating several applications out of something that fits great in a suite at all) - I don't like the "simplified" interface of Firefox and Thunderbird - Firefox and Thunderbird don't work together as good as mozilla mail and mozilla navigator in the suite (firefox deals with tb as good as with every "foreign" mailer) - I don't have Composer and Chat if I use just the single applications