> > > > Would FLTK be a good fit for this? > > I'd say yes. We've used it in embedded devices. It works. We have a > number of other implementations in-house of similar devices, they have > generally proven to be more "problematic"... > > > >From what I have seen it would seem so - it is small and=20 > > cross platform. > > 3 things: > > 1] Is it small enough? > > Yes. > > > 2] Is it too limited in its offerings : i.e there is no tree control > > Although there are several nice tree-control widgets in the add ons. I > particularly like the one in the FLU add-on set. > > However - is this a hand-held device? Or perhaps a touch-screen device? > In either case, I'd strongly caution against using a tree-control at > all. > What works on a desktop idiom does not necessarily work in an embedded > device, and you need to think very carefully about how the GUI will work > - the rules are different. > > In particular, pointing accuracy tends to be much lower (small screens, > imprecise pointing mechanisms, vibration issues, etc....) so you need to > design everything with big, chunky buttons that are easy to hit, and no > double-clicks, no left-click/right-click context menus, and so forth.=20 > If you let desktop GUI designers do it, they generally mess it up badly, > at least the first time, so it needs a lot of thought. > Build demo prototypes, play with them. Find out how bad it is, then go > back and do it better. > Touch-screen monitors are cheap now - buy a few, do some experiments. It > is quite a different interaction experience. It very quickly becomes > natural to touch the widgets themselves... > Once you do that for a few weeks, try not to be surprised when, sitting > in the airport waiting for your flight, you keep pressing the screen of > your laptop to click things... > I now have an HP laptop with a touchscreen so I don't have to deal with > this issue anymore. > > > 3] What are the alternatives? > > wxWidgets? - lots of functionality but too big IMHO. > > I say not wxWidgets, but that's a matter of taste (not keen on their > API's). GTK and QT are worth a look, of course, and there are others. > > I'd still picj fltk though. > > > SELEX Sensors and Airborne Systems Limited > Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex= > SS14 3EL > A company registered in England & Wales. Company no. 02426132 > ******************************************************************** > This email and any attachments are confidential to the intended > recipient and may also be privileged. If you are not the intended > recipient please delete it from your system and notify the sender. > You should not copy it or use it for any purpose nor disclose or > distribute its contents to any other person. > ******************************************************************** >
Wow thank you for this input. I absolutely did not think of any of that stuff and would totally have designed it from the desktop point of view. I agree that FLTK is the best choice - I guess I just wanted to hear someone else agree with me out loud :) Thanks again Jason _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
