From: Aaron R> <ant...@gm...> - 2009-03-15 23:55:17
|
I've used FLTK a fair amount in the past and usually set my projects to use the following development process. - Design a form in fluid, then save the myform.fl file - Implement the call back routines in a myFormCallbacks.cpp - Set up my build system to: run fluid on the fl file, creating the cxx, then compile the cpp and cxx into my app. Can someone give me advice on the proper development approach with pyFltk? Do I build a form with fluid, generate my cxx, and run swig on it to get access to the form in python? I want to keep my gui layout and presentation isolated from my control and logic code. I could build the forms in pure python, but that defeats the use of the fluid layout editor. Thanks, Aaron R> |