RFC: problems with splitting up kdebase

[David Faure]

On Wednesday 27 June 2007, Thiago Macieira wrote:
> The difference being that the file you process is an actual adaptor. So 
> you can write your class in C++, *use* it and generate the XML and the 
> interface from it. The generated adaptor is the same class, with the 
> small difference that it will contain the XML embedded as a classinfo.
OK.

> >Why? Surely you will add more methods later. Nothing is "one time only".
> 
> Only if the XML file you keep is a "copy".
> 
> If you're using an installed copy, the auto-generation will break as soon 
> as the interface is updated. The existing C++ class won't implement all 
> methods.

This is exactly why my thinking is that it's the implementation (the server object)
that should install the xml file. When it's updated, the server does provide the new
methods. The reason we install xml files is for -clients- (dbus interfaces). No problem
for them.

But indeed if we put kdepim-kdenetwork interfaces in kdelibs then it has to be
a copy of the xml, to avoid the problem of "more recent xml than the implementation
in e.g. kdenetwork, so kdenetwork doesn't compile".

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).