Mobile/Fennec/Architecture: Difference between revisions

Mobile/Fennec/Architecture (view source)

841 bytes added , 4 February 2009

canmove, Confirmed users, Bureaucrats and Sysops emeriti

2,798

edits

@@ Line 37: / Line 37: @@
 ===Chrome Elements===
-[talk about the stack and the toolbars]
+Fennec tries to not use any dialogs. There are still some, used by the platform, but we are working to removing them all. Instead of dialogs, Fennec uses other UI to interact with the user. Firefox does similar things with modeless notification boxes and error pages in content.
-[talk about the use of boxes instead of panels]
+In those situations where a dialog or secondary window would be used, Fennec typically brings a pseudo-panel into view. Fennec does not use real <code><panel></code> elements, as those tend to cause performance issues. Instead, a <code><vbox></code> containing the desired UI is brought into view. The boxes are children of the <code><stack></code>, can be positioned as needed, and are hidden until needed - also to improve startup performance.
+Some examples are Bookmark List, Bookmark Editor and the Tools Panel (Add-ons, Preferences and Downloads). These elements are very similar to the toolstrips, but they are not managed by the WidgetStack.
 ==Performance Related Coding Guidelines==