Kimmo Kinnunen wrote yesterday on the GTK+-WebCore developer mailing list that he has imported the Safari 2.0 WebCore branch into GTK+-WebCore. "This means that from the webcore/javascriptcore part, the code is mostly
the same as in current Safari. So if there are any crashes, they're not
from webcore/javascriptcore part of the codebase with very high
probability, rather my code."
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-01-03
"I'm not so sold on this one. Maybe you can convince me? People are scared of a "registry" sometimes, though obviously gconf isn't a big binary blob, but rather XML. I'm still not convinced that XML is the greatest way to store settings (as opposed to a more easily human readable flatfile). Instant Apply is nice, but one doesn't change settings all that often. Leaving aside my preference for flatfiles, what's the benefit of two DEs with mostly unrelated programs using the same config backend? Enlighten!"
I agree with you, XML is not always the best way to store configuration. Also, I certainly am not a huge fan of gconf. Although I've never really come up with a better idea for an alternative myself.
Nonetheless, I think the answer to your question about unrelated programs is that several linux users, myself included, tend to mix and match applications accross DE's. Personally, while I do try and maintain consistancy of my applications, it's more important to me to use the best o0f breed software. So while I run Gnome I use K3B because, in my opinion, it's leaps and bounds above Gnome-Baker.
In terms of configuration, different programss may suit different configuration formats better. But, sometimes it's better to think of the greater good of the whole, ie the complete ecosystem of Open Source software. It's better if all things may be configured in the same way. This will allow DE agnostic configuration schemes that can be managed centrally. Unfortunately this may hurt more for some applications than others but it is for the greater good of the entire DE and even will promote cross DE pollination that will help to improve everything. Whether a gconf style XML format is the best option is another matter. But I think at some point the community will decide to suck it up and adopt a single configuration standard for all software.
It may be a pipe ream but it's my pipe dream 
G
Member since:2006-02-20
Funny how some ideas never die out...
GConf ist not limited to XMl. It's not a "registry", it doesn't even remotely compare, except for the hierarchical namespace.
GConf is only an API. You can store all GConf-values in any kind of storage, be it a libsql-database or even a LDAP server. You can even use a flatfile-backend. All you have to do is write it.
Edited 2007-04-08 15:23
Member since:
2005-11-11
Im so impressed with kde and gnome they are working together a more.
Seriously though, the cross DE stuff is nice. DBUS, Webcore, etc. Yay!
Somehow it's fitting that the first KDE tech I can remember Gnome adopting came through Apple, Gnome's inspiration for simple and easy. Now I wonder if pressure will increase for KDE to drop KHTML and use Webcore. It's totally shallow, but I'd prefer KDE to use a KDE lib instead of an Apple one even if the ancestry is the same
maybe KDE should take the plunge and implement gconf
I'm not so sold on this one. Maybe you can convince me? People are scared of a "registry" sometimes, though obviously gconf isn't a big binary blob, but rather XML. I'm still not convinced that XML is the greatest way to store settings (as opposed to a more easily human readable flatfile). Instant Apply is nice, but one doesn't change settings all that often. Leaving aside my preference for flatfiles, what's the benefit of two DEs with mostly unrelated programs using the same config backend? Enlighten!
And yeah, GPLd Java will be nice. I've messed about a bit with Trolltech's Qt bindings. It was a bit annoying relearning stuff from Richard Dale's earlier bindings for KDE3, but I managed to get an app ported over.