There are projects that reduce that can bring down the size (see
Minimo). You can get it down to 4 to 5 mb if you trim out a good
majority. There are issues though mostly dependent on the requirements
of embedded devices and the platform you are using. Linux based devices
with 8-16mb of memory allocatable to gecko when running (minimum) and
8mb of space to store mozilla is about what you need from what I tested.
We evaluated using Gecko on a recent project at Texas Instruments, but
decided against it in favor of Opera and NetFront from Access (the
company that bought the PalmOS).
Part of it was licensing, since LPGL, GPL, and MLP code is hard to use
with embeddable projects when there is no way to dynamically link in
many embedded OSs' (everything is compiled together including OS and
applications) and then our customers would not really have a way to load
their customized versions of the code on to the device as required under
the LGPL.
The other issue is that Gecko (and most of the Mozilla code base) is
written in C++. I don't have a problem with C++ but using it in an
embedded project is an expensive use of resources. (We use C and ARM
assembly on most of our projects since we have to milk the embedded
controls for all they got, since resources are heavily restricted)
Hope that helps...
Zac
Bo Yang wrote:
I want to know is there any precedent that using Gecko
in a embedded device?
Gecko's footprint is about 20M, Is there any way to reduce
this to adapt it to a resource limited embedded device?
Thanks in advance!
_______________________________________________
dev-embedding mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-embedding
_______________________________________________
dev-embedding mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-embedding
