On 19.12.2010, at 11:02, Domingo Alvarez Duarte wrote: > Doing my experiments with Layout Manager I make fl_Widget derived from > Fl_Rectangle (Rectangle from fltk 2.0) and typedefed int to coord_t and > made it as float to test, only a few casts was needed on fluid when > gereating code and using "%d" on printf like functions, and on > Fl_Gl_Device_Plugin "fl_draw_image(baseAddress + (int(glw->h()) - 1) * > mByteWidth, x, y , glw->w(), glw->h(), bytesperpixel, - mByteWidth);". > > Also noticed that a similar typedef is in use on Fl_Device.H:
there are many questions in this respect for the future of FLTK. - should coordinates be in Floating Point? - should font sizes be in FP? - how can we add an alpha channel (transparency) to our color setup (and keep the color lookup table at the same time)? - how doe we handle screen resolution? There are many more types that need to be reevaluated: - fonts are indices - shouldn't they be a pointer? - box types are indices - pointer? - labeltypes are integers - they could be pointers? - keystrokes are encoded in 16 bit, but Unicode may need 24 bits and more - shortcuts are still ASCII only - they should be USC4 plus modifier. - what about events and their parameters? How can we add user events and their parameters? We will need that if we want to support multitouch and gestures. Once 1.3 is out, we need to discuss quite seriously how we want to keep FLTK modern while still fast and light. Cheers, Matthias _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
