canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,798
edits
Fennec/NativeUI/Architecture Overview: Difference between revisions
Jump to navigation
Jump to search
Fennec/NativeUI/Architecture Overview (view source)
Revision as of 15:06, 12 October 2011
, 12 October 2011no edit summary
MarkFinkle (talk | contribs) (Created page with "It's always nice to have a bird's eye view of how something is working to help make it easier to understand. With that in mind here is quick summary of the current Java Fennec sy...") |
MarkFinkle (talk | contribs) No edit summary |
||
| Line 20: | Line 20: | ||
* I like the JSON messaging from XUL to Java, but I think we need the reverse too. Also, GeckoAppShell.handleGeckoMessage could use a good refactor. It's already getting too big. | * I like the JSON messaging from XUL to Java, but I think we need the reverse too. Also, GeckoAppShell.handleGeckoMessage could use a good refactor. It's already getting 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. | * 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. | ||
==Interaction with Other Teams== | |||
* Add-ons: The add-on system will be impacted by the native UI change. We need to put together some information about how it's impacted and what we might be able to do to add back some level of support. | |||
* L10N: Localization of the native UI can work very similar to how we localize Java UI parts now. Even that could be made easier though. The bigger issue is the affect of native UI on the dynamic way we can change localizations of the XUL UI without being locked or affected by the OS locale. I mean, Firefox Mobile (XUL) can be launched in a locale that isn't even shipped with the OS itself. This ability might be affected. | |||