Matt Campbell wrote: > VNC3 codebase. My primary concern about TigerVNC is that none of the > main contributors listed on the home page seem interested in the Windows > server. I say this for two reasons: First, all three of these > organizations use TigerVNC for projects in which only the Unix server is > relevant. Second, the Windows autotools build system only covers the > viewer. So I wonder if someone will do something to TigerVNC that > breaks the Windows server, making me the Windows server maintainer by > default if we use TigerVNC. I'm not complaining about that; I > understand that open source is about giving back, not just getting > software for free (and then profitting from it). I just want to > understand this project's scope and priorities before I get involved.
The VirtualGL Project has some limited interest in the Windows server, certainly enough to make sure that it's easy for us to build and use. I have a prototype version of the VirtualGL OpenGL interposer that runs on Windows and is designed to be used in conjunction with WinVNC to provide remote 3D capabilities for Windows hosts. It's unclear whether that's the "right" approach for doing remote 3D on Windows, but I plan to provide the capability with VirtualGL 2.2 nonetheless. I think we do plan to build WinVNC with autotools eventually-- it just didn't make it into this release. ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
