Mobile/Notes/20-Oct-2008: Difference between revisions

From MozillaWiki
< Mobile‎ | Notes
Jump to navigation Jump to search
Line 67: Line 67:


=== Other ===
=== Other ===
* Start working on "unified" panning
** Single panning layer, not content panning and UI panning mixed together
** Panning would be removed from deckbrowser
** Browser (deckbrowser) would always be sized to the extents of the actual web content
** Panning happens in the UI layer - sidebars, browser and anything else all move together
** deckbrowser/canvas only needs to paint the current viewport
* Non-canvas based ideas for deckbrowser
** Canvas method is not without issues
** How bad is the "just browser" method
** Should we add panning into the platform (we need it for more the deckbrowser)


== Embedding ==
== Embedding ==

Revision as of 15:04, 20 October 2008

Details

  • Mondays - 9:00am Pacific, 12:00pm Eastern, 17:00 UTC
  • 650-903-0800 or 650-215-1282 x91 Conf# 8605 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 8605 (US)
  • irc.mozilla.org #mobile for backchannel

Notices

Fennec Tree Status

  • M9/A1 is out the door.
  • On to M10

UX design

  • if you open a bug that needs some UI/UX attention, use the "uiwanted" keyword -- I'm watching for those

UI

Platform

Windows Mobile

Performance

  • Graphics

Stability

  • Out of memory
  • Talos
    • Working now, needs to be handed off to build.
  • Mochitest (bug 454613)

Builds

  • bug 430200 Linux hourly/nightly builds
    • We have builds going, needs a little cleanup on ftp.

QA

  • Big Blockers for Mochitests (unlocks a large number of mochitests)
  • Lesser issues, related to plugin support:
  • started running mochitests on Nokia - working on retooling Heather's script to run directory by directory since we're still hitting resource issues with running the full suite of mochitests on the N810.
  • working on getting --enable-tests to work in the build environment (should be fixed by bug 459699)

Other

  • Start working on "unified" panning
    • Single panning layer, not content panning and UI panning mixed together
    • Panning would be removed from deckbrowser
    • Browser (deckbrowser) would always be sized to the extents of the actual web content
    • Panning happens in the UI layer - sidebars, browser and anything else all move together
    • deckbrowser/canvas only needs to paint the current viewport
  • Non-canvas based ideas for deckbrowser
    • Canvas method is not without issues
    • How bad is the "just browser" method
    • Should we add panning into the platform (we need it for more the deckbrowser)

Embedding

Initial tasklist

Other

Retrieved from "https://wiki.mozilla.org/index.php?title=Mobile/Notes/20-Oct-2008&oldid=113091"