In a previous message I wrote:
>> The long term goal of unifying the 1.1 and 2.0 developments, or at
>> least harmonising them, still needs to be addressed[*]
>> [...]
>> [*] What would this mean in practice? Refactoring 1.1 to use 2.0
>> data structures? Re-engineering 1.1 features and bug fixes to fit
>> in 2.0? I haven't looked at 2.0, so I have no idea what people have
>> in mind.
On Tue, 29 May 2007 19:55:22 +0200
matthiasm <[EMAIL PROTECTED]> wrote:
> Fact is, FLTK 2.x and FLTK 1.1 are quite far apart. Too far to just
> throw a compatibility layer on top and everything's peachy.
This is going to sound a bit like Monty Python and the Holy Grail :-)
("Apart from roads and sanitation, what have the Romans done for us?")
but apart from UTF-8, C++ namespaces, consistent naming, and the change
of Widget/Group inheritance, what are the differences between 1.1 and
2.0 ?
No, seriously. There are clearly some *big* changes that can't be
undone in 2.0 or retroported into 1.1 overnight, but there must be
a whole load of smaller things that can be harmonised to bring the
code bases somewhat closer. Some of these things could be done as
baby steps, and would ease the move of users (and developers) from
1.1 to 2.0.
Oh, and another minor point. [Maybe this should be a new thread?]
There has been talk of 1.2 before and people have even referred to
*using* fltk-1.2 already. See the links below:
http://www.fltk.org/articles.php?L230+I10+T+M10+P1+Qutf
http://www.ecos.sourceware.org/ml/ecos-discuss/2004-05/msg00027.html
To avoid possible confusion, it might make sense to call the new
version 1.3 (or even 1.5). This would make it clear that this is
a big jump from 1.1.8, is more recent than any other 1.2 that may
have been discussed or even created in the past, while still being
clear that this is not as advanced as 2.0. Once the new version is
available, thought should turn to harmonising it and 2.0 into 2.1.
Cheers
Duncan
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
