nanogui: FLTK 2.0 with NanoX


Previous by date: 20 Jul 2007 14:18:33 +0100 Re: Interfacing problem: How do I connect my touchscreen driver to nano-X?, Wein, Peter \(ext\)
Next by date: 20 Jul 2007 14:18:33 +0100 Re: Interfacing problem: How do I connect my touchscreen driver to nano-X?, Wein, Peter \(ext\)
Previous in thread: 20 Jul 2007 14:18:33 +0100 Re: FLTK 2.0 with NanoX, Greg Haerr
Next in thread: 20 Jul 2007 14:18:33 +0100 Re: FLTK 2.0 with NanoX, McCune, Michael

Subject: Re: [nanogui] FLTK 2.0 with NanoX
From: Graham Henderson ####@####.####
Date: 20 Jul 2007 14:18:33 +0100
Message-Id: <318114.10084.qm@web32008.mail.mud.yahoo.com>

Greg:

My application currently links with FLNX and eCos with Nano-x 0.92.  I wanted to move to a standard distribution of FLTK to take advantage of FLTK's continued development.  I felt "why not go for 2.0" as it will be the future and receive more developer attention.  eCos does not support dynamic libraries...everything needs to compiled and linked statically.

My application (GUI) runs on both the embedded target and under windows.  It is based on an XML that controls the rendering of the screen and the linking to the data source that provide the widgets content.  This will allow the user to modify the GUI by editing the XML file.

I have changed FLTK in two ways to simplify the application:

1.  I have added virtual void end() {}; to the widget class so I can call end() without needing to know if the widget actually supports it.

2. I have added the pattern Observer to the widget class.  Now, all widgets can observe their date source objects and be notified when they change.  The data source object serve as a proxy to the actual data in the embedded system and allows the GUI and application to connect locally, or over a serial or ethernet connection.

I will be linking and testing today and will report my progress and/or questions.

Graham....



Greg Haerr ####@####.#### wrote: :  Once compiled, the next step is to get eCos and the nxlib and fltk 2.0
libs to link to an application.  If anyone has helpful advice..........

If the application already links with FLTK 2.0 and X11, then replacing
libX11 with NXLIB is the next step.  If you link statically, then you
will find whether there's any undefined references to the NXLIB
library rather than waiting for an unresolved link to get called at
runtime.  NXLIB is a binary replacement for libX11, which
means that neither FLTK nor your application needs to be
recompiled.

After testing for the above link issues, going to standard dynamic
libraries is recommended.

Regards,

Greg


---------------------------------------------------------------------
To unsubscribe, e-mail: ####@####.####
For additional commands, e-mail: ####@####.####




Graham W. Henderson
241 Sauk Drive
Batavia, IL 60510-8660

630 406 1724 (home)
630 862 6474 (cell)
801 406 6008 (fax )
       
---------------------------------
Yahoo! oneSearch: Finally,  mobile search that gives answers, not web links. 

Previous by date: 20 Jul 2007 14:18:33 +0100 Re: Interfacing problem: How do I connect my touchscreen driver to nano-X?, Wein, Peter \(ext\)
Next by date: 20 Jul 2007 14:18:33 +0100 Re: Interfacing problem: How do I connect my touchscreen driver to nano-X?, Wein, Peter \(ext\)
Previous in thread: 20 Jul 2007 14:18:33 +0100 Re: FLTK 2.0 with NanoX, Greg Haerr
Next in thread: 20 Jul 2007 14:18:33 +0100 Re: FLTK 2.0 with NanoX, McCune, Michael


Powered by ezmlm-browse 0.20.