An analysis about a generic desktop application configuration management system

[Philip Van Hoof]

On Mon, 2005-04-11 at 23:27 +0100, Richard Moore wrote:
> On Mon, Apr 11, 2005 at 11:48:11PM +0200, Philip Van Hoof wrote:
  
> > Are you suggesting that the people who are planning to make this project
> > happen should kill you first? :-)
> 
> Well, you could try convincing me first. ;-)


 
> > I don't think those people are in need of your approval. So I'm sorry to
> > tell you that those people (including me) aren't going to wait for your
> > dead body nor your approval to use Glib.
> 
> Well, I've been working on KDE for quite some time, so I think I might
> have a reasonable idea how a lot of the developers feel. Of course you
> don't need to wait for my approval, but you might want to consider what
> the other KDE people think about your proposal.

To that I only have to say that for me, personally, you need more then
the respect and experience you got from the other KDE developers. For a
starter, you can try being polite. And then I'll consider listening. I'm
always interested in mind sharing with other intelligent developers.
Provided they have respect for each other. You can express respect by
being polite.

Since you're an experience KDE developer, I'm sure you have a very good
idea of the requirements which KDE has for a generic desktop application
configuration management system. Therefor you are invited to add those
requirements to the wiki.

Note that "It has to use DCOP" isn't a real requirement IMHO. Note that
"It shouldn't use ORBit-2" has already been added to the list of
requirements. You don't have to duplicate that one.

And if you are really against the usage of Glib/GObjects then please
feel free to talk about the alternatives on the wiki. The reason for
GObjects is currently because it would be nice to "generate" the
programming language bindings. At this moment it's very easy to create a
language binding for a GObject oriented library: For most languages it
can easily be generated (gtk-sharp is a nice example). Whats the
alternative? I honestly don't know: I'm not an experienced KDE
developer. You are one.

Or are bindings for the different programming languages unimportant? I
would disagree with such a statement. I'm not going to be the only one.

Nevertheless is the project open for suggestions.


-- 
Philip Van Hoof, Software Developer @ Cronos
home: me at pvanhoof dot be
gnome: pvanhoof at gnome dot org
work: philip dot vanhoof at cronos dot be
junk: philip dot vanhoof at gmail dot com
http://www.pvanhoof.be/