nanogui: Linking nano-X into my application?
Subject:
Re: [nanogui] Linking nano-X into my application?
From:
Lars ####@####.####
Date:
15 Dec 2004 07:32:06 +0000
Message-Id: <001201c4e278$1a00a7e0$3d0aa8c0@Lasse>
Hi Steven,
I'll try to answer some of your questions. I'm still a newbie but some
things I understand, I think :-)
----- Original Message -----
>
> Is it possible to link only the needed parts of nano-X directly into my
> FLTK application?
>
It's possible to link the nano-X server into your application. I've done
this. I don't use a window manager but I'm not sure if it gets built anyway
or not. Got to check that. I also don't use FLTK so I don't know if that
complicates things.
> src/config reads
>
> ####################################################################
> #
> # NanoX: Put Y to the following line to link the nano-X application
> # with the server. This is required for ELKS, if no network is present,
> # or for speed or debugging. This affects the nano-X server only.
> #
> ####################################################################
> LINK_APP_INTO_SERVER = N
>
> But I guess "the nano-X application" is the nanowm, right? So how could do
> something like this with my FLTK application?
>
No, it's your application. Your client gets linked together with the server
meaning, among other things, that you don't have to start the nano-X server
separately.
> BTW: what's the difference between
>
> MICROWIN = Y and
> NANOX = Y
>
Manfred Gruber answered this already. The naming is a bit confusing.
Microwin supports 2 APIs. One is called Microwin and the other is called
nano-X. Historical reasons I suppose. Would be easier for us newbies with a
name change.
> --
> Steven Scholz
>
Hope this helps.
/ Lasse T.
