> I do think the conclusion of using WRT1.1 for PhoneGap is the right
> approach.  This API has all the features of PhoneGap so just needs a
> Javascript layer to translate between the 2 APIs.

> WRT1.1 already exists and can be found in the Nokia 5800.  This is a
> touch phone with a Safari brower and its possible to create code which
> runs across all the PhoneGap handsets (with the possible exception of
> Blackberry -dependent on your Javascript). The 5800 has a screen size
> of 360x640 pixels so you just have to be aware your code has to take
> account of screen dimensions and/or use CSS 100% commands.  I am
> currently developing an application which runs on 5800, with the same
> (HTML,CSS and JS) code running on the iPhone via PhoneGap  (I am not
> using location, contacts etc so have not written any JS translation
> layers).

> Th next Nokia phone where this is possible is the N97 due in summer.
> Even though it may take several years for all Nokia phones to support
> WRT1.1, I would be aware that the number of phones sold for each model
> is signficant outside the US.

> Robin

> On Feb 18, 11:02 pm, Mikko Ohtamaa <sna...@gmail.com> wrote:
> > Hi,

> > We have made some experiements with Nokia Series 60 "Browser Control"
> > component. Basically I think we know  what it would take to port
> > PhoneGap to S60 and I know want to share this (so that no one needs to
> > bang head to a wall again).

> > There are two ways control the browser in S60: Browser Control and
> > application overlay. The application overlay opens a new browser
> > window on the top of your application. You cannot customize the
> > browser UI, the options menu or anything else, so I think this is not
> > a good approach because of the lack of control.

> > Then there is Browser Controlhttp://
> www.forum.nokia.com/info/sw.nokia.com/id/47d8a7fe-768c-44e5-bc...
> > which is "the right way" to embed
> > WebKit in your application. You have total control over the surrouding
> > UI. But looks like it the Browser Control itself is not the most
> > robust piece of software and tends to have uncatchable crashes in
> > various situations (page does not load, the page load is interrupted)
> > and is stable enough only for offline applications.

> > Also, we lack something like stringByEvaluatingJavaScriptFromString in
> > the public API, so we cannot feed any data from the phone to the
> > Javascript easily. However, it is possible for the shell application
> > to have native code to listen to localhost socket for which Javascript
> > connects using AJAX requests. Kuneri's KuneriLite does exactly this
> > for Flash Lite.

> > The third option is just wait 5 years when Nokia device base is
> > satured by Series 60 fifth edition device which supports Nokia's Web
> > Run-Time 1.1. WRT is Nokia's proprietary, closed, PhoneGap like
> > platform.

> > http://wiki.forum.nokia.com/index.php/Category:Web_Runtime_(WRT)<http://wiki.forum.nokia.com/index.php/Category:Web_Runtime_%28WRT%29>

> > Some Nokia Series 60 devices support Web Run-Time 1.0 with an software
> > update, but version 1.0 lacks all "PhoneGap abilities" like GPS. Both
> > WRT technologies allow capsulating web application to installable
> > Series 60 packages. Nokia doesn't seem to be keen on backporting WRT
> > 1.1 to older devices, so this technology has currently near-zero
> > market base.

> > I think we are not pursuiting Series 60 very actively anymore, unless
> > we got a customer case for it. We'll just wait that WRT 1.1 is
> > widespread enough and make a PhoneGap adapter for it.

> > Some experiemental Python code:

> > https://code.launchpad.net/~jussi-toivola/pys60community/browserbranch<https://code.launchpad.net/%7Ejussi-toivola/pys60community/browserbranch>

> > Cheers,
> > Mikko

> > http://www.twinapex.com