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

List:       koffice-devel
Subject:    Re: impending doom in Krita
From:       Casper Boemann <cbr () boemann ! dk>
Date:       2005-12-21 14:45:42
Message-ID: 200512211545.42712.cbr () boemann ! dk
[Download RAW message or body]

On Wednesday 21 December 2005 14:16, Jaroslaw Staniek wrote:
> Casper Boemann said the following, On 2005-12-21 13:51:
> > Krita is about to hit a major restructuring in a couple of days. This
> > will mean that it won't work for a period of time until we have it back
> > together.
> >
> > It may even mean that some parts of Krita wont compile, although we will
> > try to keep that to a minimum, and disable troublesome code as soon as we
> > find out.
> >
> > Code most likely to fail compilation is that which is specified at
> > compiletime like scripting.
>
> Couldn't "not compilable" state be avoided? Is there a reason to have
> noncompliable state more than a few minutes?
I hope not ;)

> Within Kexi we're using :
> - KEXI_*** macros for suff we're working and need to share in SVN,
>     eg. KEXI_REPORTS_SUPPORT
> - KEXI_NO_UNFINISHED macro for alpha-stage features
>
You mean to be put into the code? This change is to enormous and complex for 
that.

> BTW: maybe you've already done this, but I'll mention: consider creating a
> branch for "most recently working" Krita version.
No we havn't but that might be a good idea. I need someone to do it for me 
though.
-- 
best regards / venlig hilsen
Casper Boemann
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]