KDE4 Libs components

[Benjamin Meyer]

On Thursday 02 March 2006 11:20 pm, Aaron J. Seigo wrote:
> On Thursday 02 March 2006 15:00, Kevin Krammer wrote:
> >  > As I understand it, these classes are meant to be standalone building
> >  > blocks for use by other classes further up the stack.
>
> yes, as well as stand alone utility classes, like KAutoStart (assuming it
> gets the go ahead)
>
> >  > How about libKDEFoundationCore and libKDEFoundationGUI
> >
> >  or just libKDECore and libKDECoreGUI?
>
> thing is, none of these say "discreet building blocks and stand alone
> classes" to me. they say "central pieces" which may not even be true.
>
> perhaps a good place to start would be to actually categorize the classes
> we plan on putting into this layer?
>
> honestly, this is the kind of thing that would be really served well by
> having half a dozen of the more senior KDE devs converge somewhere quiet
> for a few days, sort classes out into groups and then report back with
> their efforts for comments and thereby get most of the starting work done
> quickly (versus weeks on the mailing lists)

Completely agree.  I actually started doing this at aKadamy when it was very 
quickly discovered how much every class somehow relied upon kapplication 
existing at which point I went off hacking on kapp for several months.  A lot 
of work has been done sense then so now is probably a good time to revisit 
the task.

-Benjamin Meyer

-- 
aka icefox
Public Key: http://www.icefox.net/public_key.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060309/e22eaf12/attachment.sig>