Recent Changes - Search:

TurboVNC Home

About TurboVNC

Downloads

Documentation

Reports

Developer Info

Contact

Related Projects

TurboVNC Roadmap

TurboVNC 2.2

Other Features on the Radar

  • Improvements to noVNC to allow it to support the RFB flow control extensions (this work is funded and should be completed before November)
  • WebSockets support in the TurboVNC Server (for noVNC-- will probably make it into TurboVNC 2.2)
  • Possible inclusion of noVNC as an optional zero-install viewer (or at least facilitating its use as much as possible-- I don't really want to fork noVNC)
  • Zero-install high-performance browser-based viewer (based on WebAssembly-- waiting on the technology to gel a bit more)
  • Adding TurboVNC support to a hardware-accelerated Wayland compositor (currently blocking until nVidia and the Wayland developers reconcile their disagreements, and until Wayland makes its way into RHEL)
  • Built-in web portal
  • Accelerated H.264/NVENC support (have not had time to complete the research to determine the relative efficacy of this-- hopefully will get a chance to complete it this Fall)

Sponsors and/or Contributors Needed!

A reminder that VirtualGL and TurboVNC would not exist without outside funding. If your organization can benefit from one of the aforementioned features, or if you have other features in mind, please consider funding the development of one or more of those features. This type of funding is what allows me to release this software free of charge and to maintain its high standards of quality, performance, and usability. I spent something like 300 hours in August preparing for the 2.1.2 release, of which only about about half of that was funded. The TurboVNC General Fund, which provides funding for 200 hours of labor a year and renews every May, is already exhausted through May of 2018. With the exception of the must-have items for TurboVNC 2.2, very little else can be done until next year unless more funding is secured for next-gen TurboVNC projects. Furthermore, this funding ensures that I can continue to work on VirtualGL and TurboVNC full-time (VirtualGL alone would not be enough to pay my bills), and this ensures that these products remain free of any one organization's agenda. Your patronage is critical to the success of VirtualGL and TurboVNC.

We accept (well-crafted) patches/pull requests too! Some of the premiere features in TurboVNC were code contributions. If you want to get your hands dirty and would be interested in implementing one of the aforementioned features yourself, I'm happy to work with you.

Creative Commons LicenseAll content on this web site is licensed under the Creative Commons Attribution 2.5 License. Any works containing material derived from this web site must cite The VirtualGL Project as the source of the material and list the current URL for the TurboVNC web site.

Edit - History - Print - Recent Changes - Search
Page last modified on September 25, 2017, at 02:29 PM