KFlowRects proposal (planned for next Monday)

[Thomas Zander]

On Tuesday 07 August 2007 10:34:23 Andreas Pakulat wrote:
> > I suggest you wait until 4.0 is out the door and postpone the search
> > for a (kdelibs based) solution to after that point.
>
> You didn't get the idea did you? If kdefx is not removed now (which has
> users, who have to have some replacement to not drop features), KDE4
> will have it always. There is a replacement in the works for KDE 4.1,
> but it has to be removed for 4.0.

I understood that :)

Maybe what I thought was an obvious solution is not one, so allow me to 
state the solution that will work binary compatible and allow us to work 
within the time constraints set for the 4.0 release.

The alternate solution you have not talked about is by providing the 
functionality without providing public API in KDELibs.

The simplest way of doing that is by moving the code in question towards 
the applications. Either inlining it, or simply moving a class there as 
private API.

Then when the freeze is lifted post release (there is always life after 
the next release...) a proper peer reviewed and complete solution may be 
created that is ready for inclusion in kdelibs.

In other words; there is no reason to rush a new class into the libs.
> So far Matthew didn't propose to add new untested code, he proposed to
> move, rename and cleanup a class from kdefx.

Its not new untested code I was talking about, its new untested API I was 
talking about. Code can be fixed after the release, APIs can't be.

For clarity; IMO untested API is a class that has not seen various real 
life usecases and various developers use it (for peer review reasons).

Thanks for listening.
-- 
Thomas Zander
-------------- 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/20070807/ab0cea0a/attachment.sig>