Changes between Version 131 and Version 132 of Developer/OpenProjects


Ignore:
Timestamp:
Jan 26, 2010, 1:33:52 AM (10 years ago)
Author:
JoelSherrill
Comment:

/* Nano-X (formerly MicroWindows?) */ cut down

Legend:

Unmodified
Added
Removed
Modified
  • Developer/OpenProjects

    v131 v132  
    294294= Third Party Packages =
    295295
    296 =  Nano-X (formerly MicroWindows)   =
    297 
    298 
    299 '''Status:''' Work for [wiki:GSoC  Google Summer of Code] is in progress by Roxana Leontie with [wiki:User:AaronGrier_  Aaron Grier] as mentor.  Preliminary frame buffer drivers for the pc386 and ARM BSPs have been checked into RTEMS CVS.  Patches are still pending submittal to the Nano-X project, and can be found at http://code.google.com/p/rtems-nano-x/ .
    300 
    301 '''Introduction:''' Nano-X is a graphics library providing both Microsoft- and X Windows-like graphics programming APIs for embedded systems.
    302 
    303 '''Goal:''' To provide more frame buffer drivers and examples that run on various BSPs.  Frame buffer drivers are wanted for BSPs that have simulators.  In particular, we would like an appropriately licensed pc386 frame buffer driver for MicroWindows.  Any drivers that will run on Skyeye are also desired.
    304 
    305 '''Requirements:''' The developer should be familiar with RTEMS development.  Most of this work can be done outside the RTEMS source tree and treating MicroWindows and its demos as example applications.
    306 
    307 '''Resources:''' Nano-X ports to RTEMS of various quality are pre-existing.  The Nintendo DS BSP submitter is a recent user of it so should be able to provide advice.  [wiki:User:AaronGrier_  Aaron Grier] also has some experience with Nano-X on custom hardware.
    308 
    309 '''Extention and Related Projects:'''
    310 
    311  *  NXLIB -- NXLIB is a binary replacement for the libX11 library to allow applications to be run under Nano-X instead of full-blown X11.  It assumes that a native port of the X Window System is available for the target in question, which is often the case for Linux, but not for RTEMS.  Rather than port X11 to RTEMS, it seems like it would be more feasible to package the necessary collection of X11 headers and build utilities (imake) for RTEMS and NXLIB.
    312 
    313  *  Qt Embedded (http://qt.nokia.com/products/) -- While the Qt/X11 port could likely be run under NXLIB, performance may be better with a native Nano-X port.
    314 
    315  *  TinyWidgets (http://www.tnw2000.org/) -- Last updated in 2007, but source is still available.
    316 
    317  *  wxWidgets for Microwindows (http://www.wxwidgets.org/docs/embedded.htm#wxmwin) -- incomplete port, appears to need some work to make it threadsafe.
    318 
    319  *  directfb (http://www.directfb.org/) -- Linux' DirectFB API provides additional graphics acceleration and limited windowing support.  It may be possible to provide a similar API under RTEMS to allow porting of Linux DirectFB applications.
    320 
    321 '''URLs:'''
    322 
    323  *  http://www.microwindows.org/
     296=  RTEMS Graphics Toolkit   =
     297
     298
     299See the [wiki:RTEMSGraphicsToolkit#Open_Projects  Open Projects] section of the [wiki:Projects/GraphicsToolkit  RTEMS Graphics Toolkit] for current status of the kit and ideas for  future work.
    324300= LWIP =
    325301