On 03/11/12 14:54, Duncan Gibson wrote:
> OP described 2 separate issues:
> 1. slow performance of offscreen overlays, and
> 2. improving the look/performance of widgets using Cairo
>
>> I agree that improving the widget's look is a good idea,
>> and perhaps it should start with making a new set of parallel
>> widgets that can easily be used or enabled in parallel with
>> our current releases.
>
> I would hesitate to add a whole slew of parallel widgets as such, where
> you would have the original Fl_* widgets and equivalent Fl_Cairo_* ones.
>
> IMHO it would be better to keep the Fl_* names as adaptors that either
> used conditional compilation to use the original or cairo (or whatever)
> internals, or used some environment variable to choose at run-time.
>
> Then people would have the same interface to FLTK and wouldn't have to
> change their code to use the Cairo (or whatever) alternatives.
My thinking was development of these parallel widgets
could go in directions that don't need to precisely follow
our existing API, and one could still choose between them.
(ie. a straight FLTK interface, but only cairo styled buttons)
This would allow development to be slow, yet allow people to add
nicer widgets to their existing applications.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
