On 21 Jan 2013, at 15:28, Christopher James Huff wrote: > There seems to be little in the way of an organized abstraction of the > underlying platform, with platform-specific code instead being > scattered here and there through the codebase. Has it been considered > to take the approach used for graphics drivers and apply it for for > general platform support? > > The main idea here is something that would give a well-defined > interface to implement for things like window operations and event > handling, better separate FLTK and platform-specific code, and would > make it easier to do port to "platforms" including frameworks like SDL > or GLUT. It would also allow extension of a platform by subclassing to > modify behavior or support different OS versions.
Yeah... I think we are heading that way, but there's a lot of legacy code to get through... Maybe for fltk3...! As ever, a competent volunteer is more than welcome to take a stab! _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
