Fabien Costantini wrote:
> That said, yes we should IMHO stop fancy modifications/improvements and
> focus exclusively on bug fixes asap.
I agree in general (priority on fltk 1.3 release), but I still want
to get some ABI breaking things done before the release of 1.3.
IMHO there are four main things that must be done before a release:
(1) Get utf-8 support ready. There are still lots of things to do.
At least xft issues come to mind. More support for Eastern
languages may be postponed, though (IMHO).
(2) Check, which ABI issues should be solved before a FLTK 1.3
release. I don't want to imagine how long it will take, until
we get the next chance to break the ABI, although I hope that
it will not take too long after the first release that we
start working on FLTK 1.4 with the next ABI (and maybe also
API?) changes.
(3) Fix bugs.
(4) Improve documentation.
This is explicitly not an order of priority, but I think that
all parts are worth to be considered.
I can help with (2)-(4), but I can't help much with (1).
So I'll focus on (2)-(4), but someone needs to do (1).
Unfortunately those who did the most work there are
currently not much available... Others may only do other
parts, however.
For me issue (2) seems _very_ important, because there are
lots of old STR's, maybe already from 2005/06 or even earlier,
that say "we can't do this for 1.1, because it would break
the ABI". Now we have 2009, and FLTK 1.4 won't come before
2010 or 2011, right? Unfortunately, many of these STR's are
now classified as 1.4 feature requests, but we should have
an eye on those, too.
> We all like adding/improving features, and this is important that each and
> every one in the team can find an opportunity to do so ; afterall this is the
> least that a coredev deserves as a counterpart for so many everyday unfair
> maintanance tasks, but still what should be probably done now is focusing on
> a release.
Yes, we need a release soon. But see above. The most important
point is to get utf-8 ready, then we can look what should be
done before the release, and what maybe later.
> FLTK2 development history teached us a lesson of humility, IMHO: We should be
> happy of all that was already done in 1.3 !
Yes, that's true, we can be glad to have a growing developer
team :-)
Albrecht
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
