> I must say that I'm really surprised by the fact that it is actually
> practically deciding whethet to drop FLTK 2.x or not.
No, the folks that are currently working on 2.x will continue
to work on 2.x, whether 1.x freezes or not.
The question seems to be whether the continued maintenance of 1.x
has any effect on 2.x's development or not. If it doesn't, continuing
it past 1.1.8 shouldn't affect 2.x.
Mike, this might be something only you can answer; so far the
opinions against 1.x continued dev seem based on a perception
that 1.x dev is holding back 2.x development.
But is that actually the case?
If not, that might quell a lot of the concern over this issue.
This being a volunteer effort, I don't think there are actually
folks being pulled away from 2.x because they're forced to maintain 1.x.
I perceive folks work on 2.x or 1.x as they please, and are driven
by their own whims. The decision to continue 1.x or not should
(hopefully) not deter 2.x dev, and only be driven by a need for
its continuance.
I'd be surprised if 1.x maintenance has been slowing down 2.x,
but I might be wrong.
> use (end make it [more] portable)? If it's not, than why bother with C++,
> FLTK 1.x anyway uses it very little so IMO FLTK 1.x might be even more
> smaller (don't know if faster) if it's (re)written entirely in C, and with
> much more ASM routines. I'm really not trying to be ironcih, but after
> reading "arguments" that Greg and others are putting, I really mean that.
You may be thinking of toolkits that draw directly to the hardware,
where one can take advantage of DMA and fast memory moves. But these
are all hardware specific; FLTK is not trying to be a hardware toolkit.
At the end of the day, FLTK is making function calls to other libraries
to do its drawing (WIN32/Xlib..). Making those calls in C or even
assembly
won't make it go any faster. Critical code like: "*c++ = *p++;" won't go
any faster whether it be C or C++.
FLTK tries to be as fast as possible, but not at the expense
of portability. So let's get over that.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
