> 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. > > > If you all use CMake regularly, and if you know how to generate the needed > project files, we would appreciate your help.
This is axactly what we intend to do. > FLTK 1.3.0 already has Doxygen comments (and utf-8). We just started looking at 1.3.x. I have now seen this work. It looks good. We certainly don't plan to duplicate existing work. We will be glad to provide feedback on this if/when necessary. > > 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 ? The goal here is to create a better separation between the platform specific and independent code. We would like to create a well defined and consistent api over the platform specific code. This would ease porting, maintenance, and hopefully form the basis of a porting guide. Another benefit we hope to realize from this are separate dynamically loaded libs (ala dlopen, LoadLibrary etc.) for each platform. This is a good mechanism for patching installed applications. It has worked very nicely on several other projects. > It would be interesting to watch your progress, so maybe public svn > access would be a nice feature. > It's on the todo list. However, everyone is always hot to trot at the beginning of a project. We will probably want to do a little bit of "wait and see" before we get too carried away. Thanks, Gerry _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
