Re: No alternatives to MicroB?
 

(Ignoring the obvious trollishness of this post)

If it's a crasher it's likely to be fixed (that said, I'm still dubious as to whether this is a real crasher or just the typical constrained-device instability). Even if it's only fixed for the next release, Nokia's increased openness means it'll be a lot easier for the community to get it running on current hardware than it was for the 770.

It really depends on the team. Some teams have moved on to only major/critical stuff (crashers, etc) some are still pushing more minor fixes (mvo just push a lot of minor stuff for h-a-m, for example). Generalizing isn't very helpful here, and in the case of the browser team, I believe they'll still be fixing lots of stuff (especially considering that the engine-level changes really aren't dependent on anything from Fremantle).

Also:

s/Freemantle/Fremantle/g

Please keep it in mind.

Re: No alternatives to MicroB?
 

Run Opera on computer with NX, VNC, or RDP server running. Connect to this server using your NIT (all 3 protocols are supported with 3rd party applications; qtnx, pyrdesktop, ...). Then you got all your tabs and windows available at your command.

I tend to use SSH + Screen for all my applications. There are beautiful ncurses applications for just about everything. Many even support a specific colour scheme (Irssi default; terminal black bg + blue bg + white text). Runs very nice on a large screen such as the NIT.

I can attest MicroB crashes with too much open. You could try to increase your virtual memory, or not leave too many windows open. In Chrome every tab is a seperate process; this is something I'd like to see back in other browsers as well, but I'm not sure this will be backported into WebKit. WebKit is used in many browsers nowadays; its an adult rendering engine, lightweight, well comformant. Tear and Midori are 2 lightweight, open source browsers using WebKit I'm aware of. But there are more, and have been more; such as Konqueror/E(mbedded). Its just that Tear is the only browser in extras/ which uses WebKit...

Re: No alternatives to MicroB?
 

Just last week I was wondering what was happening with microb behind the scenes.

(In wrong forum though, Software -> Apps; clearly the likes of MS and Nokia know better than Mozilla and the US DOJ that the browser is part of the OS... :rolleyes: )

Anyway, based on the relatively informed hearsay in here it appears that Diablo along with its major integrated parts is on the slow lane to oblivion and Fremantle will not be supported by Nokia on the current hardware.

My personal lesson here is not to expect software support from a hardware vendor beyond the hardware's shelf-life.

Re: No alternatives to MicroB?
 

I use the Firefox offspring Minefield on my N810 and I am very happy with it. After a longer start it works quite fast and offers all plugins. That's much better than Fennec and more versatile than Tear.

Re: No alternatives to MicroB?
 

I'll say again: it really doesn't matter all that much whether Nokia supports current hardware with Fremantle, because a community provided backport will be much easier this time around. . . .

Re: No alternatives to MicroB?
 

Of course if there are some 3D drivers involved... :)

Re: No alternatives to MicroB?
 

You call it trollishness, I call it personal experience (besides, I'm not alone thinking this way)

Re: No alternatives to MicroB?
 

a) Non-solution: "RDP to a real machine"
b) Good Solution: "Get over Java-less anal retention, get Opera mobile".
c) Great Solution: "Finger friendly, Integrated webkit browser".


(a) sounds like a "buy a netbook" to me. I'd rather see a Hildonized finger-friendly (and, no, microb doesn't fit that) approach.

Sheesh, even a circa 2000 Palm will run Opera.... (in some incantation, in a full moon, with the wind at your back)

Re: No alternatives to MicroB?
 

Actually, I kid you not, it is a solution but it has a problem: you need 24/7 connectivity. The NIT doesn't provide that. Most netbooks don't provide this either. Besides, its indeed not touch or finger friendly. I had this on a Nokia Communicator in 2000. With Opera, PuTTy, RDP client, and even VNC client. Over GPRS no less. And except for VNC it worked pretty well, just RDP was set to low quality graphics to save bandwidth.

I experimented with Fennec + SSH tunneling over a good, stable WiFi connection running Fennec on a fast Linux/x86-64 machine; yet there was no performance increase. I'm not sure why.

The problem with Opera (search around; someone has tried to port it) is that there is no correct Java port for NIT. There is a full fledged Java port, but not J2ME which runs on Symbian and the like for which Opera Mini was build. IIRC it ran, but performance was laughable.

So you're, as of now, left to current options:
A) MicroB
B) Minefield
C) Fennec
D) Tear
E) Port Midori/Dillo/Links2/Elinks/W3m/Lynx
F) Deblet or one of its variants with Firefox or Konqueror
Z) Something above, home brewed, with some patches...

For the future (Fremantle and such) I put my money on option C or one of the WebKit-based browsers; its not as if a good WebKit-based browser is impossible on a mobile device; its just as possible as Gecko-based or Presto-based one; the engines are all competitive. For now, its a difficult situation.

Re: No alternatives to MicroB?
 

only if there's a build. is there a N810-friendly build of Opera Mobile?