KAboutData ownership (Re: KInstance redesign)

[David Faure]

On Wednesday 31 January 2007, Matthias Kretz wrote:
> What are the uses cases for KAboutData not owned by 
> KComponentData?
None that I can think of, so I like solution too.

> Multiple KComponentData objects using the same KAboutData? 
It's basically what happens in koffice (the app and the part have the same aboutdata),
but this is already coded like 

KAboutData * newKWordAboutData()
{
    KAboutData * aboutData=new KAboutData(...);
    [...]
    return aboutData;
}
and that code is shared between the app and the part [by being inline
since they don't link to each other, but usually apps which provide a part
simply have a shared lib for the common code].
So, no problem if the aboutdata is owned by the componentdata, there.

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