>From discussion on fltk.general "FLTK Based Project" Hello All,
We've started digging into the abstraction layer task. We need a naming convention for the abstraction layer code. We are considering a file/function prefix of fal_/FAL_ (FLTK Abstraction Layer). The plan is to create a C api that will represent the abstraction. We also plan to move platform specific files to their own sub-directories under the src directory (ala FLTK2). The goal is to end up with a well defined api that can be used to create other ports. Each port would implement the FAL api interface as a separate library (ie; libfal_win32 etc.). This would actually be a two layer abstraction. The platform api and a thin wrapper between the platform api and the widgets. This will provide some additional insulation in case the platform api would ever need to change. We still intend to implement SDL as a test port. Why separate libs? This would allow someone to work with a particular port without the need to worry about the other ports at all. We believe this will lead to better, cleaner, and lower maintenance code. This would also serve to isolate programming errors. Why an additional wrapper? Over time, the various ports will continue to evolve. OS updates, new features, api changes, etc. These types of changes are being driven by a particular port and not the widget library. This will provide some additional flexibility to accommodate these changes without impacting the widget library. Any thoughts? Thanks, Gerry _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
