Gerry Weaver wrote: > Hello All, > > First let me say thanks to all of you that took the time to answer the > questions in my previous posts. I really appreciate your help. > > I have managed to put a small group of developers together to work on what > amounts to a combined wish list. We have all used various toolkits in the > past, but have always wanted to use FLTK. However, the thing we all agree on > is that there are a few things we would like FLTK to do differently. We have > spent a couple of days discussing this and looking at the FLTK source. It was > decided that the best way to proceed is to pick up one of the FLTK versions. > We have narrowed it down to 1.1.9 or 1.3.0. Any advice on this would be > appreciated. We also need to come up with a name for the project. Someone > suggested FLNG, but that's as far as we went. Again, any suggestions would be > welcome and appreciated. Our discussion also resulted in some initial tasks, > which I've listed below. > > 1. CMake - We all use CMake so the first order of business is to create a > CMake build.
There are already CMake files in the distro, and we discussed using CMake or another tool for development and for generating the IDE project files. The lack of developers using VC++ (and maybe other) project files is a problem, because we can't easily modify them without testing. It would be a great help, if your group would give feedback of this part of your work. If you all use CMake regularly, and if you know how to generate the needed project files, we would appreciate your help. > 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. FLTK 1.3.0 already has Doxygen comments (and utf-8). > 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. I don't really understand what you mean here. Do you want to redesign the structure (layers), or do you think that there are so many things to improve? Do you intend to add more platforms, or maybe new "devices" like framebuffer support ? > 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. > > These 4 items would represent the first milestone. We intend to make > snapshots available for each of the above items as they are completed. It would be interesting to watch your progress, so maybe public svn access would be a nice feature. > Note: I should probably mention that we don't intend to include FLUID in this > work. It will probably be removed if/when the platform layer work breaks it. > This is why we plan to do snapshots of each step. If someone just wanted a > CMake/Doxygen build they could pick it up with FLUID included. > > 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. > > FYI: When we get a web site up, I will come back and post the URL. > > Thanks Again, > Gerry Albrecht _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
