Epiphany follow up

Options also have a cost to the developer. Most importantly they lead to more complex code (thus harder maintenance) and less reproducable bugs. Often when implementing new features, existing options can make it more difficult because the feature has to work right with all possible combinations of options.

Another "user visible" danger of putting obscure options into gconf is, that there is less pressure to make the default configuration just work for everyone.

It is no accident that those applications which I find most useful practically all employ this philosophy of "less is more". It's all about quality over quantity.

Possible, but what's the point? Most features can be implemented through Epiphany extensions, instead of being implemented in Epiphany itself. Epiphany extensions

1. When you import Mozilla bookmarks, Epiphany will preserve the nested structure, by adding a -> (dash, greater than) arrow in the topic name. However, the Epiphany bookmarks system is designed to be topic-based, because it simply makes sense that a bookmark doesn't fit in one single (sub- sub-) category alone. Besides that, a large percentage of users have difficulties handling hierarchies well. With Epiphany you don't have to.
2. The latest Epiphany-extensions contains an RSS reader extension. Please test it and report bugs.
3. Most likely a Mozilla problem, like so many others- we are getting those fixed, but it takes time.

how is anyone supposed to install the extensions?

You install the extensions the same way you install Epiphany itself. If your distro doesn't have packages for the latest development releases of GNOME (including epiphany-extensions 1.7.x), you can use the jhbuild or Garnome build scripts.

I can't even figure out how to install these, and the readme file gives no good instruction.

Funny, to me it seems that the INSTALL file included in the epiphany-extensions tarball contains rather clear instructions. Do you also complain that you can't figure out how to install Firefox when you download the source tarball of it?

....may not be that easy as you think. As the developers have stated, Epiphany is aimed to be easy to use, even for a complete newcomer, and how can you expect a complete newcomer understand how to compile some extensions themselves and even less have it all installed in correct places? I have no idea what jhbuild or garnome are, but I still doubt a newcomer would touch those even with a long stick. Besides, did he mention he installed Firefox from sources? I'd assume he just installed it using the distro provided tools, whichever distro that may be. For example installing an .rpm can be as easy as two mouse button clicks, but show me how you do that to source tarballs...

-WareKala

I don't use Fedora myself, but epiphany and epiphany-extensions 1.7.x RPMs for Fedora are available here: http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/Fedora/RPMS/

Hope that helps...

I overlooked that. Using rpm.pbone.net, I found this:

ftp://download.fedora.redhat.com/pub/fedora/linux/extras/development/i386/

It has e-e 1.7.1, which isn't the very latest beta release unfortunately. :-/

and how can you expect a complete newcomer understand how to compile some extensions themselves and even less have it all installed in correct places?

We don't expect that from newcomers. Where did you read that? A pre-compiled package of Epiphany-extensions is usually available from the same source as Epiphany itself, depending on your distro.

I suggested to use garnome/jhbuild in the case there are no binary GNOME 2.11 packages available for your distro, and you still want to test the RSS extension.

I hope everything is clear now?

The problem is a lack of development going on, due to a shortage of developers, not controversy over proposed features.

If only a few more developers joined the team...