[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KDE4 Libs components
From:       Olivier Goffart <ogoffart () kde ! org>
Date:       2006-03-03 22:11:42
Message-ID: 200603032311.48209.ogoffart () kde ! org
[Download RAW message or body]


Le Jeudi 2 Mars 2006 21:05, Aaron J. Seigo a écrit :
> hi all...
>
> whipping up KAutoStart reminded me of something most of you will probably
> remember this from akademy 2k5:
>
> 	http://www.kdedevelopers.org/blog/15
>
> has anyone put any thought to what the layout of the "Libs-Components" part
> may look like?
>
> if yes, what are your thoughts?
> if no, then when can we start discussing this? or rather, can we start
> discussing this now?
>
> i suppose we would aim to work towards a proposal (or set of proposals) to
> hand over to the TWG to sort out?


Maybe it's a bit late, but I'd like to add my 2 cents.

I fail to see the real interest of separating 'components' and 'framework' in 
two different library.
Anyway, i see potential problems: we are limiting ourself.

If later we want to modify a class to make it depends of another, we can't 
anymore.
(this may happen if we add a global configuration key that change the 
behaviour of a class in the 'components' library.  Or simply if we want to 
share some duplicate code that may appears later)
We can't move a class to another library after the release or it will break 
the binary compatibility.

On the other side, if someone want to use a class from 'components' in his Qt 
application, ha can take it no matter in which library the class is.

--
Olivier

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]