Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 2 days, 23 hrs ago -
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 4 days, 20 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 5 days, 17 hrs ago - more...
| The Following User Says Thank You to Android_808 For This Useful Post: | ||
|
2012-01-28
, 19:20
|
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#2
|
I've been looking over the patches for microb-engine on the garage page to see the extent of the modifications that are present vs. the original source tree and to compare them to Firefox 9.0.1. After going through some of them I found the actual source for the most recent microb package, but I haven't looked into that yet.
The good news is that although the line numbers are quite a way out on the code I have examined, the overall flow hasn't changed that much. In some cases, password manager for example, the code flow is actually more like that in the patches so they could be made simpler.
The bad. I don't have scratchbox installed for starters. I haven't got the time at the moment to get much further into this or the disk space on my pc. Not sure I fancy building it on my netbook either. Secondly, I don't know what effect the javascript changes will of had, could be able to drop the previous patches but some may need a rewrite.
Some patches are already updated (https://bugzilla.mozilla.org/show_bu...id=422540#c226 updated GStreamer patch from Maemo6 queue)
Even as a straight forward recompile of existing source, there would be the option of removing the following when thimb2 fix is in CSSU:
to improve memory handling.
Finally, the requirements for building a stock version of Firefox/xulrunner:
The good news is that although the line numbers are quite a way out on the code I have examined, the overall flow hasn't changed that much. In some cases, password manager for example, the code flow is actually more like that in the patches so they could be made simpler.
The bad. I don't have scratchbox installed for starters. I haven't got the time at the moment to get much further into this or the disk space on my pc. Not sure I fancy building it on my netbook either. Secondly, I don't know what effect the javascript changes will of had, could be able to drop the previous patches but some may need a rewrite.
Some patches are already updated (https://bugzilla.mozilla.org/show_bu...id=422540#c226 updated GStreamer patch from Maemo6 queue)
Even as a straight forward recompile of existing source, there would be the option of removing the following when thimb2 fix is in CSSU:
Code:
configopts += --without-arm-thumb2
Finally, the requirements for building a stock version of Firefox/xulrunner:
A recent POSIX Shell
A C++ compiler. GCC 3.4 or higher is recommended, or your platform's native C/C++ compiler.
Perl 5.6 or higher. Older perl versions may work if you upgrade File::Spec to version 0.8
GNU make 3.80 or higher. Other varieties of "make" will not work.
CVS 1.11 or higher
the GTK2 widget toolkit, version 2.10 or higher
libXt-devel for X11/Intrinsic.h, X11/Shell.h
libIDL 0.6.3 or higher Source snapshots are available from Mozilla via ftp. If using the RPMs, you'll need both the regular rpm and the -devel rpm. If you already have ORBit installed, then you do not need to install libIDL as ORBit bundles libIDL. You may need to install the ORBit-devel package if you use packages.
zip 2.3 (or higher)
freetype 2.1.0 (or higher)
fontconfig
pkg-config 0.9.0 (or higher)
dbus-1-glib-devel (Developer package for D-Bus/GLib bindings)
libasound2-dev (needed for Ogg support)
libnotify-dev
Yasm version 1.1.0 or newer.
autoconf-2.13 (requires GNU m4) - Autoconf 2.5x will not work. See bug 104642 for details.
I was wondering if anyone has any further news on this. I've done a quick search but can't seem to find any info.
The idea of updating the browserd gecko engine whilst retaining the current, closed source UI sounded quite appealing at the time. It could hopefully fix several rendering errors, increase HTML5 support (increasing important now adobe is finished with flash for mobiles) and, most importantly, close any security flaws that exist in the current version.