> > Xvnc can be used to display local X-clients > > I realize that, but I thought VNC needed a layer of software underneath it > to produce the graphics that are transmitted over the VNC protocol. It > could be that standard versions of VNC include a minimal X11, but I had > the impression that it was more common to just use what the system offers. > Is this not accurate then?
VNC is a wire protocol designed to send screen images and input events from one machine to another. Xvnc is a program that runs an X11 server and sends the screen output via VNC (instead of actually drawing to a real screen). You can therefore use Xvnc and a VNC client as a crude X11 environment. There are other programs that send the actual contents of the Mac OS X screen across VNC. These can't be used as an X11 environment. > This is basically what I meant, almost: Orobor_ous_ is a window manager, > while Orobor_OSX_ is an all-in-one package for running rootless X11 > alongside Aqua, using Oroborous as the window manager [hence the punning > name] and XDarwin as the display engine. OroborOSX is not an all-in-one package. Recent versions contain a custom copy of XDarwin.app itself, but do not contain the other pieces of X11. You still need the rest of XFree86 installed before you can run OroborOSX. In any case, there's not much alternative to XDarwin unless you want to pay for Xtools or eXodus. -- Greg Parker [EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
