Web Browser
From Openmoko
Contents |
Overview
This article defines the Web Browser Application, an application designed for the OpenMoko platform. This is a Native Stylus-Based application.
Use Cases
Here are some possible use cases:
- (TBD)
Layout Components
(TBD)
Application Area
Key Features:
- Tabs
- (Standard stuff)
Footer Area
Status Bar
(TBD)
Constraints
(TBD)
Sessions
(TBD)
Architectural Details
(TBD)
Implementation Recommendations
- May be implemented using webcore or webkit. ( Possibly start with gtk-webcore and osb-browser reference implementation or owb. )
- May use gpe-browser as starting point.
- Could possibly use minimo. A Linux version is available, although I don't think it's as actively developed as the WinCE version.
- Last (and only) version for GNU/Linux is 0.1, released in 2004. If we want use a browser with gecko engine, may use Mozilla for Maemo
- Could be Konqueror Embedded. Small browser with no kde library requirements, but is made for the QT/Embedded platform. Standard KHTML rendering engine.
- I think Dillo would be good for a starter browser. Since no one has started development, it would be easiest to go with Dillo in order to make it in time for phase2. --Mateo 23:53, 12 August 2007 (CEST)
- Dillo has no support for CSS, Javascript (so no AJAX apps), Java, XHTML and etc...
- Most of that you don't want on a small screen anyways. But the point in using Dillo is that the code is so small and easy to translate. I think it's important that a browser is ready for phase2. You can always make a more sophisticated browser later. I think it's important to do things in steps and not think too big too soon.--Mateo 02:52, 13 August 2007 (CEST)
- With the sudden boost in mobile apps being developed for the iPhone/iPod, I would have a tendency to disagree. Eg: we're developing a mobile WordPress admin theme. It'll work without JS and CSS, but from the specs I see, the devices targeted by open moko can definitely handle the extra fluff, IMHO --Stephane 04:10, 16 September 2007 (CEST)
- Most of that you don't want on a small screen anyways. But the point in using Dillo is that the code is so small and easy to translate. I think it's important that a browser is ready for phase2. You can always make a more sophisticated browser later. I think it's important to do things in steps and not think too big too soon.--Mateo 02:52, 13 August 2007 (CEST)
- Dillo has no support for CSS, Javascript (so no AJAX apps), Java, XHTML and etc...
- If java gets working, Opera Mini could be a temporary replacement. It most certainly runs inside Microemu (the demo on the official site uses it).
Interactions
(TBD)
Unresolved Issues
(TBD)
Questions and Answers
(TBD)
- Q: performance considerations?
- A: render benchmark roundup; webkit seems to be the fastest
- Q: Memory consumption considerations, assuming typical applications running?
- A: Perhaps lynx or links can be available for fast text-surfing. (i hope for links2)
- Good idea, I personally prefer elinks though.
