nanogui: Thread: FLTK 2.0 with NanoX

All;

Has anyone created a version of fltk 2.0 that will work with Nano-X? 

Graham.....


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

630 406 1724 (home)
630 862 6474 (cell)
801 406 6008 (fax )
       
---------------------------------
Luggage? GPS? Comic books? 
Check out fitting  gifts for grads at Yahoo! Search.

If you link FLTK with nxlib, it should work.
I did not try it, however I have a recent version of FLTK 1.7 working
with nano-X.
FLTK does not require any changes, only nxlib if needed.
Martin


-----Original Message-----
From: Graham Henderson ####@####.#### 
Sent: Thursday, July 19, 2007 11:07 AM
To: ####@####.####
Subject: [nanogui] FLTK 2.0 with NanoX

All;

Has anyone created a version of fltk 2.0 that will work with Nano-X? 

Graham.....


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

630 406 1724 (home)
630 862 6474 (cell)
801 406 6008 (fax )
       
---------------------------------
Luggage? GPS? Comic books? 
Check out fitting  gifts for grads at Yahoo! Search.

Martin:

Thank you for the reply.  I am working with eCos targeted to the ARM processor.  I have gotten nxlib to compile with minimal changes and am currently working to get FLTK to compile.  I needed to add XInput.h from an external source.  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..........

Best,

Graham....

Martin Kajdas ####@####.#### wrote: If you link FLTK with nxlib, it should work.
I did not try it, however I have a recent version of FLTK 1.7 working
with nano-X.
FLTK does not require any changes, only nxlib if needed.
Martin


-----Original Message-----
From: Graham Henderson ####@####.#### 
Sent: Thursday, July 19, 2007 11:07 AM
To: ####@####.####
Subject: [nanogui] FLTK 2.0 with NanoX

All;

Has anyone created a version of fltk 2.0 that will work with Nano-X? 

Graham.....


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

630 406 1724 (home)
630 862 6474 (cell)
801 406 6008 (fax )
       
---------------------------------
Luggage? GPS? Comic books? 
Check out fitting  gifts for grads at Yahoo! Search.



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

630 406 1724 (home)
630 862 6474 (cell)
801 406 6008 (fax )
       
---------------------------------
Park yourself in front of a world of choices in alternative vehicles.
Visit the Yahoo! Auto Green Center.

:  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

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. 

Hi Graham,

I have been running fltk 1.7 with nano-x on our arm based target. I have compiled fltk2.0 for nano-x but it has been a few months since I tried to work with it so please bear with me. I initially ran into problems linking against a non-existant libXext but in the end I believe the functions called in libXext were not needed. I did produce a set of fltk2.0 libraries but even the simplest of applications produce segmentation faults when run on our target, I'm not sure what is causing this but I think it may be related to something with fonts. 

Sorry I can't offer more info, but it is possible to produce the fltk2.0 libraries with nxlib-0.45. I'm just not sure what you've got in the end lol. 

Mike McCune
Navigation Solutions
248 282 5407

-----Original Message-----
From: Graham Henderson ####@####.####
Sent: Thu 7/19/2007 1:06 PM
To: ####@####.####
Subject: [nanogui] FLTK 2.0 with NanoX
 
All;

Has anyone created a version of fltk 2.0 that will work with Nano-X? 

Graham.....


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

630 406 1724 (home)
630 862 6474 (cell)
801 406 6008 (fax )
       
---------------------------------
Luggage? GPS? Comic books? 
Check out fitting  gifts for grads at Yahoo! Search.

>  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.

Therein was the first mistake.  FLTK 2.0 is bigger, and not necessarily
better, which is why FLTK 1.x is still being used.  And this is also
the reason why NXLIB doesn't quite work, since FLTK 2.0 requires
bringing in libXext and libXi, so even more (useless) stubs will be
required in nxlib/stubs.c.  I recommend using FLTK 1.x and dropping
2.0.

Regards,

Greg





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.