Re: The future of Galeon

În data de Du, 23 oct 05 la 00:03, Philip Langdale a scris:

[snip]

> As such, we've reached the conclusion that we have to change our
> approach if we're going to avoid Galeon getting stale or bit-rotting;
> which is important for all of us, as we all use Galeon because we
> still think it's the best thing out there :-)

I really don't know if this is good news or bad news... I've been using  
Galeon for the last 5 years and I've got very used to it, my browsing  
needs have grown in strong dependency with Galeon's features. But there  
is something I don't get it. Will you keep the "Galeon" name? Or you'll  
switch to Epyphany completely and only keep compiling Galeon against  
new Mozilla releases for a limited period of time?

Lately I have to use Windows at work, so I'm trying to make Firefox  
work as Galeon using the available extensions. But I don't think it is  
100% possible... Persistent zooming is one of the things that seems  
impossible to configure. And no extension seems to be capable of  
configuring Firefox's behavior in regards to tabbing exactly as I had  
Galeon configured. My guess is that Epyphany won't be capable of this  
either, even with Galeon's developers help, unfortunately.

But in the end, it's obvious there are not enough resources for two  
competing GNOME browsers nowadays, with Firefox growing very strong.  
However, I think there is a need for a non-GNOME GTK+-based browser in  
the free software world. The Xfce project strongly needs something like  
this. How about approaching the Xfce project by getting rid of the  
GNOME depedencies (it probably won't be easy). There are some very  
talented developers in the Xfce team. I was also hoping for a Galeon  
without Mozilla dependencies based on Gtk+ WebCore. This was proved  
possible and will attract even more interest from the free software  
community and beyond.

As you can see, I'm a fan of Galeon leaving GNOME and Mozilla behind  
and focusing on becoming the only usable GTK+-only (with native  
widgets) browser with a small footprint and best start-up time and  
rendering speed. Unfortunately my coding skills are way below par for  
such a job, but I'm offering my support for advanced testing of the new  
Galeon in addition to translating it in Romanian.

By the way, what happens with all the translations in Galeon? I've been  
translating Galeon to Romanian for the past 5 years. I've also  
initiated the Romanian Epyphany translation using the Galeon one. But  
now Epyphany's Romanian translation is maintained by someone else. I'm  
lucky because he's a friend of mine and we have pretty much the same  
vision. What about the situation in other languages? Epyphany and  
Galeon translators might be people with very different opinions on  
terminology. Not to mention the translation efforts wasted when  
abandoning such a project...

[snip]

> I've added a wiki page at:  
> http://live.gnome.org/Epiphany_2fGaleonIssues which lists current  
> stuff I can think of. I encourage anyone to add anything that I've  
> missed, but if you want to list a Galeon 1.2 feature please  
> categorise it separately :-)
> 
> --phil
> 

What bothered me most with Epyphany was that when using dark themes  
(inverted colors) it insisted on using the theme background when no  
background color was set in an HTML page. But sometimes the HTML page  
has a predefined color for the text and no predefined color for the  
background. Or the other way around. This usually results in  
unreadeable pages...

While testing this in Epiphany 1.6.5 I've also notice another thing  
which I use frequently and doesn't seem to be configurable in Epiphany:  
loading links from the clipboard by middle-clicking in a page.

Cheers,

--
     .
/^)/_/(/
     '

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

iD8DBQBDW4OSWGHETwLAB1ERAtKdAJ4maCo32DNK1Ga8AkmCJwQV+kEbhQCeNIpb
zCTrjGxSuCfMEFkGNkPcE+U=
=dz4a
-----END PGP SIGNATURE-----