I'm diverting this to fltk.development rather than this specific RFE...

Greg wrote:
> It occurs to me maybe I should write an article or make a video or
> something on how to make an FLTK widget, all the wacky details and
> implications. I wish I had one when I was writing Fl_Tree and Fl_Table,
> as there's a lot of stuff about keyboard nav and when() that I didn't
> know about until much later.. making it hard to go back and retrofit..!

It would certainly be useful to have a set of hints on all of the
areas that need to be considered, and in what order they should be
addressed during development. For example, I rarely customize a new
desktop and always stick to the default themes, so I have no idea
whether themes have to be built in from the start, or if they are
easy or difficult to retrofit later.

It might actually be useful and fun to work through the design and
implementation of a new widget, one step at a time, using such a set
of hints, and eliciting feedback from the [widget] developers along
the way, in order to (a) debug and improve the hints, and (b) give
the basis for a "Designing your own widget" page in the documentation.

D.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to