Easy embedded GUI

Looks a bit PC oriented, with things like an alloc module. Also the last update of that page was in 2007. But I will have a further look at it, thanks for the suggestion.

--
Stef    (remove caps, dashes and .invalid from e-mail address to reply by mail) 

Children are like cats, they can tell when you don't like them.  That's 
 Click to see the full signature
Reply to
Stef
Loading thread data ...

You might want to check out Crank Software's Storyboard Suite:

formatting link

It has a free evaluation, is multi-platform and completely designed for the construction

of high quality (ie non-cookie cutter) embedded user interfaces.

It runs on Linux/QNX/WinCE/FreeRTOS/ebOS/...

Thomas

--------------------------------------- Posted through

formatting link

Reply to
thomasf

Okay, good first impression. I'll have a better look at it, thanks.

--
Stef    (remove caps, dashes and .invalid from e-mail address to reply by mail) 

This is the theory that Jack built. 
 Click to see the full signature
Reply to
Stef

There are sort of two parts to that question:

1) Getting the GUI toolkit itself working on the board, i.e. making the library drive the hardware properly. This can be non-trivial and is quite dependent on your specific setup. 2) Implementing the GUI in your application. This is just a matter of using the toolkit. If you've never used the specific toolkit, there may be a bit of a learning curve, though they are mostly similar enough to each other that you can transfer some knowledge from one to another. If you have no experience at all, then there's a bit more to learn, but it's still not too bad. Get a tutorial and set aside a few days to work through some examples, then adapt example code to your application.

One meta-observation though is that while you can throw together a simple GUI pretty quickly, getting a really nice one takes quite a lot of iterative tweaking, since it's a human interface, and humans are complicated. So I'd suggest starting GUI development quite early in your project rather than tacking it on at the end. That gives you time for more refinement rounds, it gives your customer something to look at during development, and suggestions made by early users/testers can end up affecting the application itself. The tweaking is not exactly sustained technical effort, but rather, you might code something that seems to work fine, but after a while something will annoy you about it, so you make a change, which is an actual improvement; and this will repeat many times.

Similar things can happen "under the hood" in the software or hardware design, but the GUI is actually seen by the end user, so every improvement can help sell the product.

Reply to
Paul Rubin

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.