nanogui: Thread: Porting of Xwindows application on microwindows


[<<] [<] Page 1 of 1 [>] [>>]
Subject: Porting of Xwindows application on microwindows
From: Mutturaj Bhavikatti ####@####.####
Date: 12 Oct 2001 07:28:04 -0000
Message-Id: <3BC6965D.34C3F63B@inablers.net>

    Hi ,
          I ported xwindows application on to microwindows having nanox
API. But some library functions   are not implemented.  Where can i find
the wrappers of nanox for xwindows API. How would i be able to port an
available xwindows application (like star office etc) on to nanox, would
it be too much of a rework?

    Thanking You,
     M . S. Bhavikatti


Subject: Re: [nanogui] Porting of Xwindows application on microwindows
From: "Greg Haerr" ####@####.####
Date: 12 Oct 2001 21:33:43 -0000
Message-Id: <001001c15364$d3a93000$3aba46a6@xmission.com>

:           I ported xwindows application on to microwindows having nanox
: API. But some library functions   are not implemented.  Where can i find
: the wrappers of nanox for xwindows API. 

Currently, this is implemented using macro wrapper functions in the
CVS file include/XtoNX.h.  I have a yet-unreleased project where
I actually am going to the trouble of completely implementing the 
Xlib API and redirecting it to Nano-X calls.


How would i be able to port an
: available xwindows application (like star office etc) on to nanox, would
: it be too much of a rework?

It's very likely that star office uses a layer above Xlib known as a widget
set, like GTK, KDE, QT or something like that.  If that's the case, porting
the widget set to Nano-X will bring over the entire application set.  If
the application is just using Xlib directly, then one of the two methods
above could be used, or, you could rewrite the Xlib calls directly to 
Nano-X.

Regards,

Greg


[<<] [<] Page 1 of 1 [>] [>>]


Powered by ezmlm-browse 0.20.