nanogui: Thread: X v.s. Nano-X in embedded systems

Hello,

	My group is arguing about using X or Nano-X in embedded systems.

	Say, the target is a electronic book running Linux.

	For me, X is big and hard to adapt.

	But it has a lot of resources like widgets, ready applications.

	On the contrary, Nano-X is small and flexible.

	But it needs some effor for porting existed applications.

	BTW, how fast is Nano-X, as compared to frame-buffered X?

	I'd like to hear any kind of comments from you.

	( For now, I prefer Nano-X for embedded systms. :)

-------------------------------------------------------
Murphy Chen (陳正哲) ####@####.####
Design Engineer, Internet Embedded System Department
Computer & Communications Research Laboratories
Industrial Technology Research Institute, Taiwan

: For me, X is big and hard to adapt.
: 
: But it has a lot of resources like widgets, ready applications.
: 
: On the contrary, Nano-X is small and flexible.
: 
: But it needs some effor for porting existed applications.

I am working on getting the source for a gtk+/gdk port
to Nano-X.  Paolo has been working on this and promises
to upload the source to the gtk CVS shortly.  This will
bring a superior widget set for use.  In addition, I am trying
to further plans to get the fltk port running well on Microwindows,
which will bring a small toolkit to more users.

If the application is ported to Xlib, then it may be a simpler
port to get the application running.  Otherwise, I recommend
porting the lower level of the application's widget set, if any.



: 
: BTW, how fast is Nano-X, as compared to frame-buffered X?
: 

I've not run any test metrics for speed.  For the smaller screens found
on embedded systems, it's probably not very noticable.  For larger
1024x768 screens, the current lack of hw acceleration and routine
duplications in regards to clipping will most likely show noticable
speed differences, that's one reason why Nano-X is still small.

Regards,

Greg

> I am working on getting the source for a gtk+/gdk port
> to Nano-X.  Paolo has been working on this and promises
> to upload the source to the gtk CVS shortly.

It's already there...

export ####@####.####
cvs login
cvs -z3 get gtk+

take a peek at gtk+/gdk/nanox... I haven't tried the code so I have no idea
what shape it's in. Good luck.

Dan

Dear all,

  I am sorry to bother all of you again I have spent much time in it.

  My environment is Redhat 6.1 and the kernel is 2.2.1-14p.  No matter what option I gave to config, framebuffer, svgaliv or X11, the error messages when I run demo program is

device /dev/fb0 cannot be found
cannot initialise graphic device.

Did I miss anything?

By the way, how to use the patch file patch.tar?

Thanks.

Lance