GPE mini browser [Archive] - maemo.org

zarco

11-27-2005, 07:22 PM

Which are the advantages of the GPE mini browser.
Is it quicker? does it replace the opera or can you have both browsers?
thank you

gultig

11-28-2005, 02:05 AM

konttori

11-28-2005, 10:51 AM

also better javascript support

Milhouse

12-02-2005, 06:03 AM

Truly, it's main feature is that it is open source. Not that, in the context of maemo, that isn't important. It's just that I'm waiting for MANaOS (Minimo).

Speaking of waiting: http://tonikitoo.blogspot.com/

Oh and yes, the browsers will run side by side.

Minimo is being developed by Doug Turner and he has evidence of Mnimo running on the 770 here (http://weblogs.mozillazine.org/dougt/archives/009289.html). MANaOS appears to be embedded Mozilla (Gecko?) which is not the same as Minimo, I suspect "true" Minimo is (or will be) better tuned for the smaller devices.

gultig

12-02-2005, 12:46 PM

Minimo is being developed by Doug Turner and he has evidence of Mnimo running on the 770 here (http://weblogs.mozillazine.org/dougt/archives/009289.html). MANaOS appears to be embedded Mozilla (Gecko?) which is not the same as Minimo, I suspect "true" Minimo is (or will be) better tuned for the smaller devices.
I'm not sure what you mean. If you go to the link you gave to Doug's site it says that "Screen shots and alot of the work done by Antonio Gomes." which is who is working on MANaOS. And at Antonio's site it says It uses a almost default Minimo build, except for the disabling XUL (--disable-xul specified on the mozconfig file (mozilla/minimo/config/mozconfig/linux_x86) and a simple extension for zoomming based on the colorzilla algorithm (this component is built in JS and suchs on a real device).

tonikitoo

12-02-2005, 06:47 PM

andymulhearn

12-02-2005, 07:05 PM

Dudes,

We do use the same Minimo build for MANaOS, and its UI is in GTK through. The main problem so far is the footprint -> 17mb :o

but anyhow, I promisse I'll be releasing MANaOS 0.2 sources/.deb/howtoinstall it before christmas ;)

--Antonio Gomes
http:// tonikitoo dot blogspot dot com

Toni (hope that's an acceptable short version of your name), where are the savings in size likely to come from? I can only see removal of features as a way of decreasing memory footprint - unless you're streets ahead of the other Firefox developers in terms of code optimisation :)

tonikitoo

12-05-2005, 11:15 AM

hey andy (hope that's an acceptable short version of your name as well :D ). That's a good and hard to anwser question. Well, we had some time ago a guy working full-time on compile options for code reduction, and we reliazed that it wouldn't be a piece of cake getting significant reduction through this path. But if you check the your target_dir/ (after 'make install') after building minimo, you'll notice some directories not relevant for us (they are for minimo, not for manaos), like

____'chrome'

[sbox-meamo: /usr/lib/mozilla-manaos-engine] > du -sh chrome/
3.0M chrome

____'res' - it could be also removed out (at least partially)

[sbox-meamo: /usr/lib/mozilla-manaos-engine] > du -s res/
928 res

:cool:, isn't it a good start point ?! I got 4 mb easily.

We are working on the mozconfig file as well. I hope to get 11 mb before the end of this year !

that's what I can say for instance ... What do you think ?

--Antonio Gomes
http:// tonikitoo dot blogspot dot com

Milhouse

12-05-2005, 07:40 PM

We do use the same Minimo build for MANaOS, and its UI is in GTK through. The main problem so far is the footprint -> 17mb :o

Apologies for creating any confusion - look forward to future releases! :)

andymulhearn

12-06-2005, 09:23 AM

hey andy (hope that's an acceptable short version of your name as well :D ).

Yep :D

That's a good and hard to anwser question. Well, we had some time ago a guy working full-time on compile options for code reduction, and we reliazed that it wouldn't be a piece of cake getting significant reduction through this path.

I guessed as much. Short of crippling the browser by removing features, I guess there's not much that can be done.

But if you check the your target_dir/ (after 'make install') after building minimo, you'll notice some directories not relevant for us (they are for minimo, not for manaos), like

____'chrome'

[sbox-meamo: /usr/lib/mozilla-manaos-engine] > du -sh chrome/
3.0M chrome

____'res' - it could be also removed out (at least partially)

[sbox-meamo: /usr/lib/mozilla-manaos-engine] > du -s res/
928 res

:cool:, isn't it a good start point ?! I got 4 mb easily.

Definitely a good start :)

We are working on the mozconfig file as well. I hope to get 11 mb before the end of this year !

that's what I can say for instance ... What do you think ?

It's a very good improvement. I looked on my 770 and the Opera executable is around 4meg, though that doesn't included any specific libraries which are required. It also doesn't stop it using up to 21meg of RAM with some web pages though - the Lost episode guide for example :( And when you have two of those running for some reason, there's not a hell of a lot of memory left to run anything else.

tonikitoo

12-07-2005, 08:40 AM

It is really a small set of binaries, and I have to keep these numbers in mind.

The point is: opera has a complete different browser for each supported plataform. I mean, the opera browser running on the 77'device is totaly different from the one running over a linux desktop, that's different of those running on symbians, and on win-desktops, and on winCE, and so on. This isn't definitly what mozilla wants at all. The same sourcebase runs over all this boxes above (except, Symbian so far).

Well, So there are good and not-so-good issues about this choice of mozilla regarding portability.

>> It also doesn't stop it using up to 21meg of RAM with some web pages though -

What do you mean ?! It crashed ?!

>> And when you have two of those running for some reason, there's not a hell of a >> lot of memory left to run anything else.

that's absolutily true. I hope you can 'rm' opera from your /usr/whatever soon :)

andymulhearn

12-07-2005, 09:08 AM

It is really a small set of binaries, and I have to keep these numbers in mind.

The point is: opera has a complete different browser for each supported plataform. I mean, the opera browser running on the 77'device is totaly different from the one running over a linux desktop, that's different of those running on symbians, and on win-desktops, and on winCE, and so on. This isn't definitly what mozilla wants at all. The same sourcebase runs over all this boxes above (except, Symbian so far).
That sounds like a recipe for a lot of wasted effort, unless the core of the browser - rendering engine for example - is the same in all cases. yeuch!

Well, So there are good and not-so-good issues about this choice of mozilla regarding portability.

>> It also doesn't stop it using up to 21meg of RAM with some web pages though -

What do you mean ?! It crashed ?!

Nope, it complained about low memory but still rendered the page. I was quite impressed.

>> And when you have two of those running for some reason, there's not a hell of a >> lot of memory left to run anything else.

that's absolutily true. I hope you can 'rm' opera from your /usr/whatever soon :)
Or get an image that excludes Opera and the newsreader. I've never seen the benefit of RSS on a disconnected device, as my 770 is for most of it's life.

tonikitoo

12-09-2005, 01:50 AM

Or get an image that excludes Opera and the newsreader.

that would be difficult. :confused: I see a lot of money involved between these 2 giants

Disconnect

12-09-2005, 09:39 AM

FYI you sounded surprised that opera would crash - www.bge.com takes it out reliably, at least with plugins and js enabled. (In other news.. looking forward to getting some form of moz running on this thing. I do my rss reading with gregarius (http://www.gregarius.net) and opera does Bad Things with this AJAX app.)