Re: Design question for a cross platform GUI (FLTK)
- Posted by Mike Nelson <MichaelANelson at WORLDNET.ATT.NET> Oct 15, 2001
- 552 views
Ray Smith wrote: <snip> > I have to make a decision as to how I will expose the classes > and methods of FLTK. It has a rather different design than that > of Windows (i.e. Win32Lib) and I have the option of trying to > manipulate my FLTK wrapper to look a bit like Windows (ie > Win32Lib) or do a straight wrapper to FLTK as FLTK works. > > For example ... Radio buttons. In FLTK a radio button is just a > "Round" command button with the RADIO attribute set. > I could force my wrapper for the "Round" command button to set the > RADIO attribute to make it look like windows ... or I could leave > it as FLTK does and let the programmer decide how they want to use it. > > At this stage I'm leaning towards the "leave it as FLTK" does it method > as it is the most flexible and powerful. The down side is that this > method is also the most "foreign" to current Windows and Win32Lib > programmers. </snip> I think that leaving it a s FLTK does it is the better approach for a general library. It would be considerably easier to extend the basic library to make it more windows-like when that was desired than to have to "unextend" a windows-like library when FLTK behavior was desired. If fact, if you're feeling ambitious, why not try both: Code your library using the leave it as FLTK approach, and as a separate include file, code wrapper functions for the basic library for more windows-like behavior. -- Mike Nelson