> More specifically, does anyone know of any similar projects based on gecko that have a Windows build?
I'm in charge of a similar project (MozGlade, please look at cvs rather than the last release if you check it out). One could argue that it's more generic. However, it's not generic enough to be built on Windows.
At this point MozGlade requires Mozilla (m15, m16, cvs) and Gtk, but not Gnome. This will likely change simply because I want an easy way to configure things (I like gnome-config;-). [Gnome, KDE, etc. are designed largely to make application writing easier on the developer, and I would rather use Gnome than duplicate Gnome's functionality... I like gnome-config:-)].
MozGlade doesn't have as many features as Galeon, but it does have a better (in my biased opinion) connection to libglade. My goal was to create an app that could be easily customized by designers and end users, and modular enough that outside programmers could add to it easily. Galeon's objective (as near as I can tell) was to make a nice, lightweight app. I think we both achieved our goals.
Currently MozGlade is more lightweight (i.e., uses fewer resources) than Galeon, but that's because it's missing several of the features that Galeon has (bookmarks, download manager). It is my intention to make such things available for it, but to make them optional. My way of doing this is to use loadable modules (shared libs, ala Apache's DSOs, etc.). Done right, this can be configured by the user for whatever level of power / resource usage he or she wants.
My other reason for using modules is because the mozilla browser annoys me. Gecko may be a lightweight, fast rendering engine, but gecko is not the only thing loaded when you link in libgtkembed.so (try "ldd libgtkembed.so").
Solution? Allow other backends. I have a GtkHTML backend partially done, and I'm planning to write my own widget (don't ask now; there's lots of reasons for creating my own that we need not bring up here). MozGlade will soon be splitting into multiple projects to help accomodate this flexibility. Ideally, one will be able to use the bookmarks, download manager, etc. with the other backends.
I.e., pick your power/size ratio. Everything in bloated apps (Mozilla, MS Word, etc.) is there because it may at some point be used; it's just not used often. With a flexible, modular design, that stuff can be activated when necessary.
Slashdot Mirror
> More specifically, does anyone know of any similar projects based on gecko that have a Windows build?
I'm in charge of a similar project (MozGlade, please look at cvs rather than the last release if you check it out). One could argue that it's more generic. However, it's not generic enough to be built on Windows.
At this point MozGlade requires Mozilla (m15, m16, cvs) and Gtk, but not Gnome. This will likely change simply because I want an easy way to configure things (I like gnome-config ;-). [Gnome, KDE, etc. are designed largely to make application writing easier on the developer, and I would rather use Gnome than duplicate Gnome's functionality... I like gnome-config :-)].
MozGlade doesn't have as many features as Galeon, but it does have a better (in my biased opinion) connection to libglade. My goal was to create an app that could be easily customized by designers and end users, and modular enough that outside programmers could add to it easily. Galeon's objective (as near as I can tell) was to make a nice, lightweight app. I think we both achieved our goals.
Currently MozGlade is more lightweight (i.e., uses fewer resources) than Galeon, but that's because it's missing several of the features that Galeon has (bookmarks, download manager). It is my intention to make such things available for it, but to make them optional. My way of doing this is to use loadable modules (shared libs, ala Apache's DSOs, etc.). Done right, this can be configured by the user for whatever level of power / resource usage he or she wants.
My other reason for using modules is because the mozilla browser annoys me. Gecko may be a lightweight, fast rendering engine, but gecko is not the only thing loaded when you link in libgtkembed.so (try "ldd libgtkembed.so").
Solution? Allow other backends. I have a GtkHTML backend partially done, and I'm planning to write my own widget (don't ask now; there's lots of reasons for creating my own that we need not bring up here). MozGlade will soon be splitting into multiple projects to help accomodate this flexibility. Ideally, one will be able to use the bookmarks, download manager, etc. with the other backends.
I.e., pick your power/size ratio. Everything in bloated apps (Mozilla, MS Word, etc.) is there because it may at some point be used; it's just not used often. With a flexible, modular design, that stuff can be activated when necessary.
- Bob