Canmove, confirm, emeritus
2,798
edits
Changes
→Overview
==Overview==
* Application UI is comprised mainly of Android Java and layout XML files found in /embedding/android
** GeckoApp.java and gecko_app.xml comprise the main UI.
** AwesomeBarGeckoAppShell.java and awesomebar_search.xml are handles a lot of the main UI for non-visual tasks, like handling Android intents, starting the awesomebar screen. aweseombar_row.xml is the layout for a row in the listGecko thread, communicating with Gecko through JNI and messaging.** SQLite is currently The Java compositor, used to store the history. DatabaseHelper.java seems to be used to make the DBhandle panning and zooming web content is found in /embedding.android/gfx
* XUL/JS and still used primarily as a communication shim from the Gecko platform to the Java UI.
** browser.js and browser.xul create a single <deck> of <browser> "UI" s for only displaying the web contentscontent.** Some helpers in browser.js are used to communicate network activity and mouse gestures to Java. More helpers will be needed for adding support for different Gecko features. Easily poached from the current XUL-based code.
** A JSON based message system is used to [[Fennec/NativeUI/Messages|send messages]] from XUL to Java. nsIAndroidBridge is the XPCOM object that makes this happen, but the messages are just forwarded to GeckoAppShell and routed out to Java from there.
** An event based message system is used to [[Fennec/NativeUI/Messages|send messages]] from Java to XUL. From Java, you create a GeckoEvent with a subject and data strings. This is sent to XUL as an nsIObserver notification.
