Am 27.06.2009 7:54 Uhr schrieb "Gerry Weaver" unter <[email protected]>:
Hi Gerry, > 1. CMake - We all use CMake so the first order of business is to create a > CMake build. As mentioned before, most of that work has been done. However, we failed to rebuild the Cmake setup after moving from 1.1 to 1.3. Any help here is greatly appreciated. > 2. Doxygen - We plan to add Doxygen headers throughout the source. We believe > that it will create a valuable reference resource. It will also be a good way > to get more familiar with the current source. Done. Don't worry. > 3. Platform layer - Analyze and rework (where necessary) any platform specific > code (including #ifdef) and push it down to the platform layer rewriting in c, > where necessary. Yes, wonderful. I have been pleading for this for quite a while now. In the back of my hea, I have a minimal driver that only needs the ability to read a mouse and draw a pixel, and everything else is done in the abstraction layer. A HAL would allow wonderful things like FLTK widgets inside OpenGL windows or on top of live video. Yummy. Not to mention easy ports to all kinds of minimal platfomrs. > 4. SDL - Add SDL support as a test of the platform layer design. This should > be possible without making any changes above the platform layer. Yes, perfect. > Note: I should probably mention that we don't intend to include FLUID in this > work. There is no need whatsoever to include Fluid, simply because Fluid is merely an application. By installing a HAL, no user applications should be harmed in the way they work. > Disclaimer: > > We/I have the utmost respect for the developers/creators of FLTK. We are not > doing this work because we believe our skills or ideas to be any better than > anyone else's. We are just a group of people with a slighly different vision > of how we would like to use FLTK. We are stepping up to do the work ourselves, > instead of expecting someone else to do it for us. We do, and always will, > give full credit and our thanks to the FLTK development team for the excellent > work they have done. It would be very nice if our work could benefit the FLTK > project in some way. Um, thanks. However, none of your suggestions are outlandish in any way. Actually, pretty much everything was planned for FLTK sooner or later. Wouldn't it be much easier to join the FLTK team and use al the existing infrastructure, like web page, SVN, bug list, and mailing lists? Why would you want to fork a perfectly healthy project? Matthias _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
