![]() Support for, or lack thereof, web browser extensions is the biggest flaw in SeaMonkey's web browser functionality. SeaMonkey can render web pages as they should be rendered, and more advanced web pages relying on heavy JavaScript-use work fine. The rendering engine in modern 2.5x.x versions use the rendering engine from a recent Mozilla Firefox LTS release. The web browser part of SeaMonkey used to be used on its own thing. The non-browser parts have barely been maintained the last decade, they are nearly identical to what they were 20 years ago. The other "applications" in the SeaMonkey "application suite" are there and they can be used to read and write e-mail and chat on IRC. We also have a Suite Directory Layout document that describes how the new mozilla/suite/ directory in the Mozilla CVS and comm-central hg repositories should be structured.SeaMonkey v2.53.7 with a web browser window and the built-in HTML editor, and the buit-in ChatZilla IRC client. The SeaMonkey:New for 2.0 document details the new features we have been picking up for 2.0, these are mainly as a result of the toolkit transition. The suiterunner page has information on development that happened for the big platform conversion in SeaMonkey 2.0. If want to contribute to SeaMonkey localization, read our SeaMonkey:Localization page. To get started with the project, read the getting involved page and/or join in the developer discussions in or #seamonkey. We need help testing changes for SeaMonkey 2.x. You can help by working on SeaMonkey QA as you use SeaMonkey. Our Project Goals document describes where the project is basically headed. Many of those still need help from more developers if you want to lend us a hand there, please contact is a page with a list of the currently known supporters. The development community of SeaMonkey is structured into project areas which cover different parts of the SeaMonkey project. We also need people doing QA and regular testing on our product. That doesn't mean we don't need an even bigger group of developers working on the product or taking responsibilities of certain areas in the project. At the same time they promised to still provide the newly created, -hosted, SeaMonkey project with needed infrastructure to do further development on the suite code and release it under the project's new name.Ī group of very active SeaMonkey developers make up the SeaMonkey Council, which is responsible for project and release management. In 2005, the Mozilla Foundation released a "transition plan" for the Mozilla Application Suite, in which they announced that there won't be any more official releases of the Mozilla Application Suite. SeaMonkey 1.0, first released in January 2006.įor more details on the project status, see SeaMonkey:StatusMeetings.SeaMonkey 1.1, first released in January 2007.SeaMonkey 2.0, first released in October 2009.SeaMonkey 2.3, released in August 2011.SeaMonkey 2.4, released in September 2011.SeaMonkey 2.5, released in November 2011.SeaMonkey 2.6, released in December 2011.SeaMonkey 2.7, released in January 2012.SeaMonkey 2.12, released in August 2012.SeaMonkey 2.13, released in October 2012.SeaMonkey 2.14, released in November 2012.SeaMonkey 2.15, released in January 2013.SeaMonkey 2.16, released in February 2013.SeaMonkey 2.17, released in April 2013.SeaMonkey 2.20, released in August 2013.SeaMonkey 2.21, released in September 2013.SeaMonkey 2.22, released in October 2013.SeaMonkey 2.23, released in December 2013.SeaMonkey 2.24, released in February 2014.SeaMonkey 2.25, released in March 2014.SeaMonkey 2.27, planned for June 2014.SeaMonkey 2.28, planned for July 2014.SeaMonkey 2.29, released in September 2014.SeaMonkey 2.30, released in October 2014.SeaMonkey 2.31, released in December 2014.SeaMonkey 2.32, released in January 2015.SeaMonkey 2.33, released in March 2015.SeaMonkey 2.34, planned for April 2015.SeaMonkey 2.35, released in September 2015. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |