On 10.11.2010, at 01:30, Domingo Alvarez Duarte wrote: > I'm trying to learn a bit more about fluid and fltk for that I started trying > to make fluid with fluid, the attached file is the first amalgamation of > fluid sources now I'll sort out duplicates and declaration order, at first > fluid seems to be good enough with a 400kb fluid file no slowdown, small > memory footprint.
Fluid should be quite fast. There is not much magic going on, just linear code generation. > I'm using declaration blocks to create sections and to allow collapse large > parts of code. Yes, that is a good idea. > I'm showing it here just in case someone could have an interest on it an > maybe give some ideas about possible modifications in fluid to allow it work > with big projects. I have not looked at the files yet, but I tend to have multiple Fluid files in single larger projects. But if we could handle large projects in a single file, that would be great as well. > One of my main reasons to do it is cutting down the need of duplications by > hand and fluid seems very good at that. > > One thing that I could see as an improvement to fluid is the possibility of > create sections of code and assign then to individual files on code > generation. Is that useful? I mean, the files generated by Fluid are not meant to be edited by the user. There is no reason to make them well readable or cut them up into readable parts. And todays compilers have no problem to handle source files of pretty much arbitrary size. It would be something else if we were to do away with .fl files alltogether and use markers inlined into the C code to go back and forth between using Fluid and manually changing code, but that *is* kind of risky (very useful nevertheless). - Matthias _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
