(yes, I did consider adding the possibility for xfconf in ekiga)

I of course looked at dconf/GSettings (among many other things) before writing xfconf, but, as others have noted, I wanted something ready that we could use in a reasonable amount of time. I also wanted something simpler, without requiring schema (though I’ve since come to think better of them in many respects). Of course, xfconf has grown beyond the “little simple centralised config system” I first envisioned, but it’s still decently small.

Anyhow, I’d be thrilled to help sharing it with the GNOME community were anyone interested. It could still use a lot of work and a lot of optimisation… I didn’t really know anything about configuration management before I started, and I’m sure that shows in both the design and implementation.

For the record, I was considering xfconf to be more of a temporary solution until dconf/GSettings (or maybe something else) had worked itself out, but it’d be cool to see xfconf get a bit more use if people find it worthy.

And as Stephan says, we can certainly change the name to help quell NIH syndrome ^_~.

What I actually meant to say is that we are always willing to consider alternatives, if they are real alternatives (i.e. released software). We’re not really in a position where we can afford to use external components that are too much in flux.

On the other hand, yeah, sometimes it’s easier (in the short run) to do something ourselves than to work with other people. And — hello Rob — it _is_ our sandbox after all.