> matthiasm wrote: > > Adding to my previous mail, here are a few features I would like to > > see in the next FLTK:
> > - plugin support from within FLTK > > Just rewrite it as scripting language. It should take me about 3-4 > weeks to do. I have noticed that there is a continued, if unfocused, goal of incorporating plug-in support in FLTK. If anyone is interested, I do have a working and functional component based plug-in framework written in C++. The plug-in code resides in dynamic library files containing one or more individual components. The components and the dlls can be specified using a XML file describing the individual components and their associated properties. The components are created inside the program and can be nested in a hierarchical manner to any depth. Parameters can be associated with the components and initialized individually. Individual components also can be assigned names in the XML file so that they can communicate with each other using asynchronous communication queues. Fluid allows programs to be designed and created as monolithic compile time programs. The component method would use an XML script to create the entire program, including GUI parts, dynamically at run time. It is even possible to modify the program to add new menus, dialogs, whatever, while the program continues execution. I have used this component framework for almost a decade for complex modeling and simulation programs. I have toyed with the idea of incorporating a dynamic GUI capability to allow users to display data and results in graphical formats as well as user access able runtime controls. FLTK seems to be better suited for this than most of the other GUI frameworks. Anyway, if there is any interest, let me know. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
