On Mar 23, 2007, at 9:45 AM, Giuseppe wrote: > How i separate my interface FLTK from my program?
Please post your general requests in the "general" group. This group is for those who develop the library itself. To answer your question: there are hundreds of ways to do this. Books have been written about it. Some implement various types of slotting systems, threads, or message queues. Many give up and just mix UI and core code. I can not give you any recommendations here. This is totally to your taste. It does not matter at all if you use a dll or any other technical interface. The separation has to be within your code, not with the way you link. If your code is clean, you can later decide if you want to use a link module, a static library, or a dynamic link library. There are two main reasons to use a dll: 1: you want to be able to update (or exchange) your GUI library at *any* time *after* building your application. This can be useful if you distribute your app to a few thousand people, then discover a bug in a dll, and only redistribute the dll instead of the whole app. 2: your application uses plugins and those plugins need access to the same instance of FLTK. Here you *must* use a dll. The original idea was to have the library code in the system only once, een if multiple applications used the same version of FLTK. This issue is usually not critical with todays memory capacities and the small size of FLTK. It has become more a matter of taste... . ---- http://robowerk.com/ _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
