> With some studying on this program and FLUID code I'll make,
> I think I'll get things down before too long.
Yes; Fluid should be able to also make code just like this
as well; it's well designed for it.
I have several commercial programs managed by fluid, one
that's quite large and complex, full of custom widgets,
dialogs, multiple screens. Here's the fluid code browser for that app:
http://seriss.com/people/erco/fltk/fluid-big-app.jpg
There's plenty of manually maintained code that this app calls,
so not /all/ the code is maintained by fluid, just the widget-y stuff.
Some files are just easier to maintain as a text file, and then either
#include into the fluid app, or reference as modules.
For instance, I used to have all my #includes in fluid.
But it was getting too large and took up a lot of screen space
in fluid's browser, so I moved it all into a separate .h file,
and just have a single #include in fluid to load it all in.
Fluid's been great.
> On a side note, do you plan on making any more FLTK videos?
> They are a HUGE help and I'd love to get into some class stuff
Yes, I'd like to do a few more, but it's been hard to get
into the swing of it again.
One of the videos does cover the subject covered here
of how to turn a "C" style FLTK demo into a "C++" style program.
I think the last part of the "Hello World" video touches on that.
That subject should probably be covered more in an advanced video.
It's a broad subject, has to be planned out. That's what's been
taking the most time is to know where to start. Over the years
I've been taking notes how to break it out, but just haven't been
motivated to take it on.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
