GUI on VxWorks

[Narasimha Swamy]

We have to do a project in which we have to develop GUI (Graphical
User Interface) in a VxWorks OS platform. The GUI does not change
automatically but values shown in the GUI will be changing
continuously. The hardware is an Intel Pentium PC with a standard
monitor. We are not sure about how to go about this. Please let me
know what is the best method for such a problem. Please also let me
know where I can get relevent literature and other material like
Tools.
Thank you for any suggestion.

[Bruce]

In comp.os.vxworks
trns...@netKracker.com (Narasimha Swamy) wrote:

VxWorks has Zinc or you can use MetaGraphics for VxWorks.

[Werner Schiendl]

Hi,

Directly from WRS you can have the following 3 products I know of:

WindML
Zinc
Java VM (including graphics)

WindML is a C graphics primitive library with driver interfaces for display,
input devices and other things. It forms the foundation of the other two
products. It is the successor of a product called UGL (or, to be precise:
WindML is a new version of UGL, but WRS renamed it to have a sounding name).

Although there are no high-level windowing capabilities, it may be
sufficient for your application if it is basically for displaying
information rather than providing a point and click interface in a windows
manner. If you need 'real' controls this is probably not for you.

Zinc is a C++ graphics library that was available free of charge for Windows
and Linux free of charge. I'm not sure if this is still the case, since
WindRiver acquired the company. Anyway, this provides the usual controls,
and they look pretty much like Windows (95). It is also pretty fast,
especially on a Pentium class target system.

Java has the well-known problems inherent to that system as well as its
advantages: Needs tons of memory, tons of CPU power (your machine may be
sufficient, I guess - but try it anyway before buying), ugly (in my opinion)
AWT window widgets, portability.

You'll find information on these products on WRS web pages.

The main problem with using an embedded OS on a of-the-shelve PC is, that
you won't get WindML graphics drivers for the graphics board used in the PC.
If you plan to setup the system in larger quantities, you need to make sure
that you select components that are available for a longer time.

You'll probably end up writing your driver(s) yourself.

BTW: The drivers that come with WindML for pcPentium are crap, at least when
we evaluated them (very slow, limited to only few modes). The standard VESA
driver is of course very, very slow since no hardware accerleration is
available.

hth
Werner

"Narasimha Swamy" <trns...@netKracker.com> wrote in message
news:b432d10c.02042...@posting.google.com...

[ChanSeong Mike Kim]

Hi ~

We're developing App. using x86 board.
I used following component.

1. CPU : PENTIUM(AMD K6-266)
2. MAINBAORD : x86 Board(All-ine-one, SOUND, LAN, 4-SERIAL PORT, HDD,
FDD,VGA)
MODEL NO:HS-4500 ( www.boser.com.tw)
3. LAN - Realtek8139 ( I recommend Intel LAN CHIP , cause Intel driver is
free of charge)
4. VGA - CHIPS 69000(you can 256 color driver if you find or request to WRS)

And I used Vxworks 5.4 + UGL(former version of WindML) + Zinc 5.0( not Zinc
6.0) + Tornado 2.0

Bootloader:
I used floopy disk. And used 'mkboot.exe' as floopy diskette bootable in
host computer running Windows2000 Prof. .

Then boot in target computer using floopy driver. (boot through network
card - I used realtek driver)

I built a vxworks os image with standalone boot mode(not network booting)
including ugl and zinc.
[builing ugl.o and zinc.o is a another step of building object.]

Then I made hdd bootable using 'mkbootAta' command.

After all above steps I could see my own ZINC initial screen.

......debugging....

Best regards
ChanSeong Mike Kim

"Narasimha Swamy" <trns...@netKracker.com> wrote in message
news:b432d10c.02042...@posting.google.com...