To manage risk, this roadmap proposes that major graphics and layout work - especially the cairo-substrate and reflow-branch changes - be scheduled as early as possible, in staged landings. ![]() ![]() They form the core of the architectural shifts in 1.9, and are considered to be the most difficult and riskiest elements. Graphics and layout changes represent some of the most invasive work proposed for the Gecko 1.9 development cycle. Some elements could reasonably be categorized multiply, so tags would be better than categories. Some will be new standards.Ī rough attempt to categorize these development areas can be found below. Many of these web-facing enhancements will be implementations of existing standards, in whole or in part. There are several major areas of development for Gecko 1.9, intended to serve both the applications built on top of it (chiefly Firefox 3) and applications built on the web which need or would benefit from improvements in web technology. In the case of a tie, disputes will be settled by single combat. Brendan Eich continues to drive the vision and architecture of the platform in the large, and his influence on the platform roadmap is both significant and indispensible. The owner of record for this document is Mike Shaver and all errors or omissions within it are first and foremost his responsibility. In due, and short, time, this document will link to more detailed "sub-roadmaps" for such work this distribution of ownership will better reflect the structure of our development organization, and should facilitate improved maintenance of the collected roadmap information over the course of Gecko 1.9 While this roadmap is intended to provide a statement of direction for the platform in Gecko 1.9, responsibility for detailed planning of such areas of development is necessarily devolved to the groups doing - or, in the case of some larger tasks, leading - the design, development, and testing of specific capabilities. Readers of this document will notice a conspicuous absence of bug lists, detailed schedules, or decomposition of development work into individual tasks. We will preserve all API (declared-frozen or not) compatibility on the 1.8 branch, so only selected additional APIs are thinkable. Some of the features listed below may be pulled forward into that 1.8 branch if needed for product releases off that branch, but you shouldn't count on it. The work described in this document will be performed - in several cases it is already being performed - on the trunk of Mozilla CVS, with the 1.8 branch preserved largely intact. ![]() Products such as Thunderbird, and projects such as Sunbird, will likely adapt their roadmaps to match the product/platform pair centered on Firefox and Gecko. The other document, the "product" roadmap, builds on this one to detail the plans for Firefox 2 and Firefox 3. The product delivery vehicle for this platform will be explored, discussed, and refined in another roadmap process, to which this document will soon link. This roadmap describes the planned capabilities of the Mozilla platform, often known as "Gecko", in the 1.9 release. 3.7 Miscellaneous platform improvements. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |