Small SeaMonkey addons

This is interesting. This guy has repackaged many Firefox/SeaMonkey addons, making them much smaller:
http://code.google.com/p/firefox-extension-shrink/source/browse/trunk/?r=6

To give you an idea how much they are shrunk, look at this URL which has the full addons:
http://releases.mozillaonline.com/pub/mozilla.org/addons/
Or here:
http://ftp.acc.umu.se/Public/mozilla.org/addons/

Video_download_helper is here:
http://releases.mozillaonline.com/pub/mozilla.org/addons/3006/

...version 4.9.4 is 666KB, whereas the repackaged .xpi is only 349KB.


Posted on 27 Oct 2011, 8:17


Comments:

Posted on 27 Oct 2011, 15:45 by rjbrewer
video download helper
4.9.4 versions will not work with seamonkey 2.3.xx.
They also don't provide the option of selecting
video quality.

I'm using Wary uni with seamonkey 2.0.11-w5.pet;
A great combination that uses about 30% less cpu
than 5.2 on video files and streams.
It's a shame the 5.1.3.4-uni seems to have vanished
from the repo.


Posted on 27 Oct 2011, 16:45 by BarryK
Re Wary uni-CPU
Considering that Wary is targeting older hardware, and to increase the distinction from the other puppies, I am seriously thinking that the next Wary will have a uniprocessor-kernel (no SMP support).

I am also seriously considering either rolling SM back or using some other smaller/lighter browser.



Posted on 27 Oct 2011, 16:50 by BarryK
Re SM 2.3.x
I am getting increasingly disappointed with SM. The 2.3.x series has a new type of window that pops up when you first enter a password (or whatever), asking if you want SM to remember it -- but half the time the window disappears before I have a chance to make a choice. That is such incredibly bad design.

Then there's the bloat, oh, that is the worst development.



Posted on 27 Oct 2011, 17:35 by GM Budwrench
SM 2
@ Barry, I agree. SM 1 didn't have as many options as vers. 2 has, but to me, it runs circles around the later versions. Sm 1, is lightning fast and is snappy, but version 2 lags on my pc. I used to really like the Mozilla products, but I'm becoming irritated by the rush it out the door, full of bugs, attitude they have taken on. I like the all in one mail/browser idea of SM and hope that you decide to keep it, even if you have to revert back to SM 1. I'd be happy with that.


Posted on 27 Oct 2011, 17:57 by gjuhasz
packages to sfs
For a very old PII machine, I got up to 15% performance boost using uniprocessor kernel compared with SMP enabled version. Difference either in fps rate of glxgears; or in dropped frames rate in mplayer; or in cycle time of playing omelette.swf file is relevant.
Another performance boost can be freeing memory by moving frequently updated packages, such as Seamonkey, to sfs files. A built-in browser/office package unnecessarily reserves memory if the user installs another browser / alternative office s/w.
In case of default browser, I think a lightweight one such as Links2 should be built-in by default and a seamonkey.sfs package should be included in the iso.
Similarly, defaultoffice.sfs in the iso could help users who prefer alternatives.


Posted on 28 Oct 2011, 3:10 by Dougal
Shrinking Extensions
I just unzip them and delete all the locale files I don't care about... usually the Japanese locale is what makes up most of the bulk -- the rest is just a little bit of javascript etc.


Posted on 28 Oct 2011, 5:23 by technosaurus
automated shrinkage
If only there were an auto-magic way...
I posted a script in Scottman's Pup-Lite thread (now Akita) that does much of this already except that it was designed for shrinking the whole sfs filesystem.

javascript:
http://code.google.com/closure/
html:
using sed to remove whitespace
gif:
gifsicle
png:
optipng
jpeg:
jpegtran
duplicates:
rdfind or similar tool
locales,documentation:
remove/split-up
.xpi,jar files
use highest compression level
...


Posted on 28 Oct 2011, 8:28 by Dewbie
Lightweight Gecko/Mozilla build?
Have a look at this:
http://kmeleon.sourceforge.net/
It's lightweight and Gecko/Mozilla-based.
Unfortunately, it's only for Windows.

However, this might be a good reference/starting point for an equivalent Linux build.