Fennec/NativeUI: Difference between revisions

Jump to navigation Jump to search

Fennec/NativeUI (view source)

Revision as of 03:41, 30 January 2012

4,926 bytes removed ,  30 January 2012
→‎Known Issue: rip out the known issues section, it's waaay out-of-date
(→‎Build for Mac OSX: update ndk to r5c)
(→‎Known Issue: rip out the known issues section, it's waaay out-of-date)
Line 96: Line 96:


Overview and detail here: https://wiki.mozilla.org/Fennec/NativeUI/UserExperience  
Overview and detail here: https://wiki.mozilla.org/Fennec/NativeUI/UserExperience  
== Known Issue ==
=== Near Term ===
*tabs (dougt / ram)
*favicons
*Dialogs
**http auth (wesj)
**nsIPrompt (wesj)
**contextmenus (wesj)
**select/form input (wesj)
**cert auth (xul)
*door hangers (gcp)
**content permission (geolocation, desktop notification, indexedDb, OWA)
**popup permission
*preferences (alexp)
*bookmarking (blassey)
*Panning perf (clord)
*zooming perf (clord)
*IME (alexp)
*link styles (visited/unvisited)
*Don't initialize this early. https://github.com/snorp/mozilla-central/blob/faster/embedding/android/GeckoApp.java#L383. So far, the only usage is here: https://github.com/snorp/mozilla-central/blob/faster/embedding/android/GeckoAppShell.java#L1717 -- which is after a page has loaded. I would recommend the initialization happen right there, when the mDb is null. Or probably at the end of onCreate in GeckApp.java
*https://github.com/snorp/mozilla-central/blob/faster/embedding/android/AwesomeBar.java#L178 -- This can be moved to an AsyncTask. A database access can happen in the background and the results can be pushed to the UI. In that way, the responsiveness of AwesomeBar will be faster and better.
*Setting the FilterQueryProvider automatically processes the SQL in a background thread (see http://developer.android.com/reference/android/widget/CursorAdapter.html#runQueryOnBackgroundThread%28java.lang.CharSequence%29). I verified this by adding a Thread.sleep() call in the filter - the UI remains responsive.
*Better to use styles in layout. This helps in reusability. (sriram)
*<strike>GeckoApp activity uses a lot of static variables. This has issues while rotation (they tend to hold previous values). It's better to avoid static variables and use getter and setters. [see http://stackoverflow.com/questions/2475978/using-static-variables-in-android]</strike> (done as of 0c46f65505f0)
*Change directory structure under embedding/android to follow a more traditional Android app layout (src, res, gen, etc) for better integration with Eclipse.
*Take into account best-practices and coding conventions from http://developer.android.com/guide/practices/design/performance.html since the whole point of this is to speed up the UI. In particular, the current code:
**creates a lot of string objects which (from my past experience) triggers the GC mechanism more often and slows things down
**uses unnecessarily visible (public or package instead of private) and non-final variables, which prevents certain classes of compiler optimizations. (these are also just bad coding conventions)
*attach session history to browser elements, send SESSION_BACK message to nsAppshell from java to control session history
*On Galaxy Tab 10.1, the Awesomebar is not high enough, causing j's and g's to be cut short.
=== Mid Term ===
*Sync support (thebnich)
** Sync team [[Services/NativeSync|working on this]].
*[http://limpet.net/mbrubeck/2010/05/10/fennec-meta-viewport.html &lt;meta name="viewport"&gt;] support (mbrubeck)
*page info
*sharing
*Ability to pan around last screen shot (in pcwalton's patch queue)
*Remove unused cruft from the APK.
=== Longer term  ===
*[[Fennec/NativeUI/addons|addons]] (going to use jetpack - mossop)
*login/password management
*Download
*find on page
*selection
*removing xul
*profile migration
*Touch events
=== Low priority bugs  ===
*OpenURI is not supposed to load the frame, only provide the frame:
http://hg.mozilla.org/mozilla-central/file/2f3d39316c54/mobile/chrome/content/browser.js#l80
=== Other  ===
*<strike>The current helpers in browser.js are wrong or inadequate. This should be easy to fix. The code is also designed for a single &lt;browser&gt;. We need to add tab support (coming) and see that it works well in the XUL/Java setup.</strike> - mostly done in multiple changesets
*<strike>We are not using any Gecko session history (back/forward). I think this is a mistake. We should be capturing as much session in Gecko as possible. Any reason not to?</strike> done - cd8813d5469d
*We are not using favicons in awesomebar. Just missing? or intentional?
*<strike>URL edit box is not of "URL" type. The keyboard should change to show URL keys.</strike> done - b4bbaa96238a
*<strike>I like the JSON messaging from XUL to Java, but I think we need the reverse too.</strike> done - ca107c8ed542
*Also, GeckoAppShell.handleGeckoMessage could use a good refactor. It's already too big.
*Plans for splitting the work between non-visual Java components (like a History or Bookmark object), the visual Java UI (dialogs or buttons that use the non-visual components) and the XUL/JS helpers used to send/receive messages to Java. These seem to be the basic areas of coding. Planning how to attack any particular feature will help make sure we don't have coders stepping on each other and will make the work go faster IMO.
*investigate using system sqlite, system zlib
*about:crashes sounds broken


== QA ==
== QA ==
Kats
Confirmed users
586

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/391560"

Navigation menu