Re: Ideas for future of Galeon 2

On Thu, 2002-10-17 at 14:38, [email protected] wrote:
> 
> Yeah the menubar sounds easy. (Where would the code go though, a .so ?).
> I see more problems for prefs. If people want them to be merged with the
> others, it's going to be a fork of all that code. An advanced page with
> subcategories could be done without duping though.
> And there is Mime UI ... Hardly a module would be worth for it.

I simply named it 'galeon_tools_setup_window' and the code is in just
another file statically built in galeon.  However, there is absolutely
nothing preventing the actual code being in a loadable module, or
modules.  You could very easily load the module in that function and
call its setup_window function or whatever.

The prefs could be more difficult, but the granularity there should
propably be one page per extension module.  Like, one page for 'Web
development' thingies or something.  Micromanaging existing dialogs
doesn't sound constructive.


-- 
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)

iD8DBQA9rqVdBKiYcWg4juYRAt8TAJ4uUbGv8pdazGtUkft6BBcCMAuLpwCgz03t
UIjjQdJb+sR4m2YcmYb1VO8=
=nA0D
-----END PGP SIGNATURE-----