Prev: Neoware e140
Next: V3 V363EPC --Looking for user manual and complete data sheet
From: shoonya on 25 May 2010 10:28
>
>"Nobody" <nobody(a)nowhere.com> wrote in message
>news:pan.2010.05.15.13.35.40.407000(a)nowhere.com...
>> On Fri, 14 May 2010 14:35:52 -0500, msr wrote:
>>
>
>>
>> AFAICT, PEG is aimed at the level below that, where you might only have
an
>> 8-bit or 16-bit CPU or RAM measured in kilobytes rather than megabytes
(it
>> will run on more powerful systems, but then it's competing with Qt and
>> WinCE).
>
>I can't agree with that assessment
>
>I have worked on two systems where PEG was considered as an appropriate
GUI
>framework (one rejected it in favour of an "own" solution and the other
used
>it) and neither of these were 8 or 16 bit systems with limited memory,
they
>were both 32 bit systems with 100s of megabytes.
>
>In both cases, it came down to licensing cost.
>
>tim
>
>
>

Hi,

You might want to look at FLTK. You can use it on embedded linux or build
it
for your RTOS.
It comes with uClinux and though is X based, it can be made to work on raw
video buffer.

It has a GUI designer called FLUID which you can use to design your gui on
your linux desktop and just crosscompile it for your target.

I have used it on my previous project running uClinux on a softcore
processor. The gui with menus and buttons was overlayed on live video.

Regards
Manish




---------------------------------------
Posted through http://www.EmbeddedRelated.com
First  |  Prev  | 
Pages: 1 2 3 4
Prev: Neoware e140
Next: V3 V363EPC --Looking for user manual and complete data sheet