Mozilla 2/Work List: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(Link to obsolete APIs page)
Line 26: Line 26:
** fast-path DOM
** fast-path DOM
** [http://wiki.mozilla.org/Mozilla_2/EventHandlingCleanup EventHandlingCleanup]
** [http://wiki.mozilla.org/Mozilla_2/EventHandlingCleanup EventHandlingCleanup]
** Removal of obsolete APIs
** Removal of [[Gecko:Obsolete_API|obsolete APIs]]
** [[Mozilla 2/GFX/Compositor|GFX - Compositor]] -- one widget per window, frame rate controls
** [[Mozilla 2/GFX/Compositor|GFX - Compositor]] -- one widget per window, frame rate controls
** [[Mozilla 2/GFX/Software Rendering Performance|GFX - Software Rendering Performance]]
** [[Mozilla 2/GFX/Software Rendering Performance|GFX - Software Rendering Performance]]

Revision as of 21:18, 18 February 2008

See the short template and the detailed template.

  • Big, invasive, destabilizing changes. These are the sort of tasks that don't respond well to compression (e.g. throwing more people at it) and touch large pieces of the code and/or can destabilize other parts of the development. These are the sort of changes that once landed into the mainline development tree can become the long-pole for release and are difficult to unwind. From the Moz2 meetings it appears the following are in this category:
    • mmGC (including XPCOMGC) - bsmedberg
    • "Strings" -- sharing strings with JS or moving to STL, moving to UTF8, sanifying the existing string classes - bsmedberg
    • Exception support out for Moz2, but work will continue for post-2 - taras
    • deCOM - taras
    • ActionMonkey: Taramin JIT replacing SM *already underway* - actionmonkey stage 4/5 - jorendorff
    • Better threading support in the core layout engine
    • Centralized security checks - brendan
    • Protected mode - jmathies
    • out-of-memory handling - figure out how to do OOM handling, allocator hooks to free up memory, etc. - stuart
    • GFX - 3D Acceleration