Features/TigerVNC

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(need email and more detailed test plan--see hidden comments for suggestions)
m (Removing QA category)
 
(14 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= Replace RealVNC by TightVNC =
+
= Replace RealVNC by TigerVNC =
  
 
== Summary ==
 
== Summary ==
There was no update from RealVNC upstream since May 18 2006 and upstream is focused on their enterprise non-open vnc. Trunk TightVNC is RealVNC fork with many improvements/bugfixes so it makes sense to use it. Main problem is that current Fedora vnc has also many changes so patches have to be merged.
+
Make TigerVNC the default VNC client in Fedora.
  
== Owner ==
+
There was no update from RealVNC upstream since May 18 2006 and upstream is focused on their enterprise non-open vnc. Trunk TigerVNC is RealVNC fork with many improvements/bugfixes so it makes sense to use it. Main problem is that current Fedora vnc has also many changes so patches have to be merged.
* Name: AdamTkac
+
* '''FIXME'''--please add your email address so you can be notified about the meeting where FESCo will discuss your feature
+
  
 +
== Owner ==
 +
* Name: [[AdamTkac| Adam Tkac]]
  
 
== Current status ==
 
== Current status ==
 
* Targeted release: Fedora 11
 
* Targeted release: Fedora 11
* Last updated: 2008-10-17
+
* Last updated: 2009-03-03
* Percentage of completion: 80%
+
* Percentage of completion: 100%
 
+
- tightvnc package hit F11 CVS branch
+
  
 
== Detailed Description ==
 
== Detailed Description ==
TightVNC has successfully implemented "Tight" protocol enhancements which save bandwidth and are generally better than the original RealVNC's RFB 3.8 protocol. On the other hand Fedora vnc has by far a much better server (Xvnc) which is based on X 1.5 and supports more extensions. Fedora changes have to be carefully merged to TightVNC upstream and then we will use it as default Fedora vnc system.
+
TigerVNC has successfully implemented "Tight" protocol enhancements which save bandwidth and are generally better than the original RealVNC's RFB 3.8 protocol. On the other hand Fedora vnc has by far a much better server (Xvnc) which is based on X 1.6 and supports more extensions. Fedora changes have to be carefully merged to TigerVNC upstream and then we will use it as default Fedora vnc system.
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
Line 23: Line 21:
  
 
== Scope ==
 
== Scope ==
Merge Fedora changes to upstream and make TightVNC ready for Fedora
+
Merge Fedora changes to upstream and make TigerVNC ready for Fedora
  
 
== Test Plan ==
 
== Test Plan ==
* Push TightVNC based vnc to rawhide as soon as possible and users will test it
+
* Check that libvnc.so module to Xorg works fine
 
+
* Check that vnc installation works as expected
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The QA team will turn this information into a more complete test plan.  The more specific you can be, the better the final test plan will be.
+
* Check that viewer works fine when you connect to Xvnc and to different servers (vino)
 
+
* Check that Xvnc works with other viewers (vinagre)
Remember that you are writing this test plan for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
+
 
+
A good Test Plan should answer these four questions:
+
 
+
0. What special hardware / data / etc. is needed (if any)?
+
1. How do I prepare my system to test this feature? What packages
+
need to be installed, config files edited, etc.?
+
2. What specific actions do I perform to check that the feature is
+
working like it's supposed to?
+
3. What are the expected results of those actions?
+
 
+
-->
+
  
 
== User Experience ==
 
== User Experience ==
 
* Better encodings save bandwidth and processor time
 
* Better encodings save bandwidth and processor time
* Improved keyboard handling when server and viewer uses different keyboards
 
 
* Viewer internationalization
 
* Viewer internationalization
 +
* IPv6 support in viewer
  
 
== Dependencies ==
 
== Dependencies ==
Anaconda has to use tightvnc package instead vnc
+
Anaconda has to use tigervnc package instead vnc
  
 
== Contingency Plan ==
 
== Contingency Plan ==
Line 55: Line 41:
  
 
== Documentation ==
 
== Documentation ==
* '''FIXME'''
+
* http://www.tigervnc.com/
  
 
== Release Notes ==
 
== Release Notes ==
* '''FIXME'''
+
* TigerVNC is used as default VNC project. Package names were changed to tigervnc, tigervnc-server and tigervnc-server-module. Binary names are same as in previous version, libvnc.so module has been moved to tigervnc-server-module subpackage. Otherwise there should be no difference
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==
  
See [[Talk:Features/TightVNC]]
+
See [[Talk:Features/TigerVNC]]
 +
 
 +
== Use Cases ==
 +
 
 +
'''Gnome menu item:'''
 +
 
 +
* Applications -> Internet -> VNC Viewer is present and has correct icons
 +
 
 +
'''Regression use cases:'''
 +
 
 +
* F11 tigerVNC client <--> F11 tigerVNC server
 +
* F11 tigerVNC client <--> other VNC server (vino)
 +
* generic VNC client (vinagre) <--> F11 tigerVNC server
 +
* F11 tigerVNC client username/pw dialog
 +
 
 +
'''tigerVNC extensions (both client and server are tigerVNC):'''
 +
 
 +
* optional JPEG compression
 +
* Automatic SSH tunneling on Unix
 +
 
 +
'''Misc:'''
 +
 
 +
* vncconfig runs; clipboard support
 +
* ipv6 support using client
 +
* libvnc.so is used by Xorg server
 +
* presents clipboard/primary selection options to viewers
 +
* anaconda uses tigervnc server for vnc installation
 +
* encoding and color level selection (list options tested)
 +
* view only (client)
 +
* shared (client)
 +
* full-screen mode (client)
 +
* basic RandR support in Xvnc (resize)
 +
 
 +
'''Internationalization (list all i18n's used):'''
 +
 
 +
* $ LANG=de_DE /usr/bin/vncviewer (where LANG= depends upon users)
  
  
----
 
  
[[Category:FeaturePageIncomplete]]
+
[[Category:FeatureAcceptedF11]]
<!-- When your feature page is completed and ready for review -->
+
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
+
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
+
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
+

Latest revision as of 17:36, 17 April 2009

Contents

[edit] Replace RealVNC by TigerVNC

[edit] Summary

Make TigerVNC the default VNC client in Fedora.

There was no update from RealVNC upstream since May 18 2006 and upstream is focused on their enterprise non-open vnc. Trunk TigerVNC is RealVNC fork with many improvements/bugfixes so it makes sense to use it. Main problem is that current Fedora vnc has also many changes so patches have to be merged.

[edit] Owner

[edit] Current status

  • Targeted release: Fedora 11
  • Last updated: 2009-03-03
  • Percentage of completion: 100%

[edit] Detailed Description

TigerVNC has successfully implemented "Tight" protocol enhancements which save bandwidth and are generally better than the original RealVNC's RFB 3.8 protocol. On the other hand Fedora vnc has by far a much better server (Xvnc) which is based on X 1.6 and supports more extensions. Fedora changes have to be carefully merged to TigerVNC upstream and then we will use it as default Fedora vnc system.

[edit] Benefit to Fedora

vnc will have more features and will get benefit from upstream development instead of the current one man show in Fedora CVS. Overall quality should be better.

[edit] Scope

Merge Fedora changes to upstream and make TigerVNC ready for Fedora

[edit] Test Plan

  • Check that libvnc.so module to Xorg works fine
  • Check that vnc installation works as expected
  • Check that viewer works fine when you connect to Xvnc and to different servers (vino)
  • Check that Xvnc works with other viewers (vinagre)

[edit] User Experience

  • Better encodings save bandwidth and processor time
  • Viewer internationalization
  • IPv6 support in viewer

[edit] Dependencies

Anaconda has to use tigervnc package instead vnc

[edit] Contingency Plan

  • Use Fedora 10 codebase

[edit] Documentation

[edit] Release Notes

  • TigerVNC is used as default VNC project. Package names were changed to tigervnc, tigervnc-server and tigervnc-server-module. Binary names are same as in previous version, libvnc.so module has been moved to tigervnc-server-module subpackage. Otherwise there should be no difference

[edit] Comments and Discussion

See Talk:Features/TigerVNC

[edit] Use Cases

Gnome menu item:

  • Applications -> Internet -> VNC Viewer is present and has correct icons

Regression use cases:

  • F11 tigerVNC client <--> F11 tigerVNC server
  • F11 tigerVNC client <--> other VNC server (vino)
  • generic VNC client (vinagre) <--> F11 tigerVNC server
  • F11 tigerVNC client username/pw dialog

tigerVNC extensions (both client and server are tigerVNC):

  • optional JPEG compression
  • Automatic SSH tunneling on Unix

Misc:

  • vncconfig runs; clipboard support
  • ipv6 support using client
  • libvnc.so is used by Xorg server
  • presents clipboard/primary selection options to viewers
  • anaconda uses tigervnc server for vnc installation
  • encoding and color level selection (list options tested)
  • view only (client)
  • shared (client)
  • full-screen mode (client)
  • basic RandR support in Xvnc (resize)

Internationalization (list all i18n's used):

  • $ LANG=de_DE /usr/bin/vncviewer (where LANG= depends upon users)