Confirmed users
1,031
edits
Fennec/NativeUI: Difference between revisions
→Other
MarkFinkle (talk | contribs) |
(→Other) |
||
| Line 103: | Line 103: | ||
=== Other === | === 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 <browser>. 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>The current helpers in browser.js are wrong or inadequate. This should be easy to fix. The code is also designed for a single <browser>. 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 | * <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 | ||
| Line 111: | Line 111: | ||
* Also, GeckoAppShell.handleGeckoMessage could use a good refactor. It's already too big. | * 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. | * 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 | |||
==QA== | ==QA== | ||