Re: Galeon extensions

On Thu, 2002-10-17 at 20:16, Marco Pesenti Gritti wrote:
> 
> I'll create a branch when I'll start working on the concrete items I
> posted. Future galeon developement will follow the lines I posted in the
> abstract rationale document. It will be possible to extend it for power
> users and web developers with plugins. Tko has already some code and I
> agree with his ideas, I hope he will keep up on it.

The patch I've done so far can be found at
http://tko.ods.org/galeon-tools.diff  I might work up another patch that
also throws in the javascript toggles (it's basically as easy as
copypasting from the patch I've submitted in bugzilla.)  But for more
than that I don't think I have the time right now.

The idea is that to get the extensions hooked in, you call one function
from some part of the 'basic' code.  That function can then attach (or
not) itself to galeon however it chooses.  The example in the patch does
this statically, but it should be rather straightforward to convert load
plugins instead if anyone wishes.

Of the suggested alternatives, I'm convinced plugins are the most used,
and most easily understood (even by users) way of adding new
functionality.  I welcome you to prove me wrong.


-- 
Tommi Komulainen                                 [email protected]
GPG 1024D/68388EE6    6FD6 DD79 EB38 BF6F 3533  09C0 04A8 9871 6838 8EE6

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQA9r0TjBKiYcWg4juYRAlk4AJ9rTlKg3QvtXoeflgrnr1eBf75e9gCguAq0
iqCCtRdTGcUDu7xlHGwFNuE=
=G893
-----END PGP SIGNATURE-----