User Tools

Site Tools


wiki:development:roadmap

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
wiki:development:roadmap [2015/02/05 08:53]
stefanbaur
wiki:development:roadmap [2017/05/11 09:45]
stefanbaur New section: NX-Libs (missing) features table
Line 1: Line 1:
-====== Development Planning ====== +====== ΞX2Go Developer Meetings ====== 
-  * [[wiki:development:planning:whiteboard]] +{{:wiki:development:x2go-mascot-ccc.png?nolink&100 |}} 
-  * [[wiki:development:planning:schedule]] +  * [[wiki:development:planning:start|Planning the next meeting]]. 
-  * [[wiki:development:planning:start]]+  * [[wiki:development:planning:meetings_list|Past ΞX2Go Developer Meetings]] 
 + 
 + 
 +---- 
 + 
  
 ====== X2Go Roadmap ====== ====== X2Go Roadmap ======
Line 72: Line 77:
 Task assigned to: Stefan, aided by Mike#1 (hard to say, Mike#1 will coach Stefan for an equivalent of 4h to get things straight, no matter how long it takes) Task assigned to: Stefan, aided by Mike#1 (hard to say, Mike#1 will coach Stefan for an equivalent of 4h to get things straight, no matter how long it takes)
  
-<del>**HTML5 Client**</del>tagged as unrealistic given current budget+<del>**HTML5 Client**</del> tagged as unrealistic given current budget
  
 If budget remains, a HTML5 client would be nice. If budget remains, a HTML5 client would be nice.
 +
 //There seems to be a disagreement amongst the developers regarding how such a client should be implemented.// //There seems to be a disagreement amongst the developers regarding how such a client should be implemented.//
 +  - One option would be to copy what other remote solutions are using - which means sub-par performance compared to our native NX/X2Go speeds.
 +  - A from-scratch approach would bring native speeds, but is a time and money sinkhole.
  
 Task assigned to: <none yet> - could be Alex, Mihai, ...? Task assigned to: <none yet> - could be Alex, Mihai, ...?
  
  
-<del>**Alternative to NX-Rewrite**</del>tagged as unrealistic given current budget+<del>**Alternative to NX-Rewrite**</del> tagged as unrealistic given current budget
  
 h1 has some ideas what other F/LOSS codebases might be suitable as a time- and money-saving alternative to doing the NX-Rewrite. h1 has some ideas what other F/LOSS codebases might be suitable as a time- and money-saving alternative to doing the NX-Rewrite.
Line 191: Line 199:
  
  
 +==== first attempt at documenting missing NX-libs features for certain applications and desktop environments ====
 +^Feature/Application or DE^NX-libs Version^V. req'd for Gnome 3.14^V. req'd for KDE5 ^
 +|XServer: RANDR| | | |
 +|XServer: RENDER| | | |
 +|XServer: Composite| | | |
 +|XServer: GLX| | | |
 +|XServer: DRI| | | |
 +|XServer: BIGREQUESTS| | | |
 +|Client: libXrandr| | | |
 +|Client: libXrender| | | |
 +|Xinerama| | | |
 +|MESA| | | |
 +|VirtualGL| | | |
  
wiki/development/roadmap.txt · Last modified: 2017/05/11 09:45 by stefanbaur