This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
wiki:development:roadmap [2015/02/05 08:51] stefanbaur |
wiki:development:roadmap [2017/05/11 09:45] (current) stefanbaur New section: NX-Libs (missing) features table |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| - | * [[wiki: | + | {{:wiki: |
| - | * [[wiki: | + | * [[wiki: |
| - | * [[wiki: | + | * [[wiki: |
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| ====== X2Go Roadmap ====== | ====== X2Go Roadmap ====== | ||
| Line 23: | Line 28: | ||
| At present, X2GoClient on OS X goes into an endless loop and has to be force-terminated after the second or third connection attempt. | At present, X2GoClient on OS X goes into an endless loop and has to be force-terminated after the second or third connection attempt. | ||
| + | |||
| + | Task assigned to: Mihai | ||
| **Run multiple instances of X2GoClient**, | **Run multiple instances of X2GoClient**, | ||
| Line 43: | Line 50: | ||
| h1 has a design in mind that addresses multi-sesson support in one X2Go Client instance (also x2goclient2.git on git.x2go.org is capable of that, but at the moment it is half-baked and probably temporarily discontinued). | h1 has a design in mind that addresses multi-sesson support in one X2Go Client instance (also x2goclient2.git on git.x2go.org is capable of that, but at the moment it is half-baked and probably temporarily discontinued). | ||
| - | Step 1: Fix Multi-Instance on Windows | + | Steps: |
| - | Step 2: Write wrapper to turn Multi-Instance into Multi-Session mode (especially important for OS X, where Multi-Instance isn't supported) | + | - Fix Multi-Instance on Windows |
| + | | ||
| - | Task assigned to: Mihai, Mihai, and again, Mihai | + | Task assigned to: Mihai, Mihai, and again, Mihai - with some help by Mike#2 for the Windows client |
| === Prio #2 (not started yet) === | === Prio #2 (not started yet) === | ||
| Line 69: | 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) | ||
| - | < | + | < |
| 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, ...? | ||
| - | < | + | < |
| 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 188: | Line 199: | ||
| + | ==== first attempt at documenting missing NX-libs features for certain applications and desktop environments ==== | ||
| + | ^Feature/ | ||
| + | |XServer: RANDR| | | | | ||
| + | |XServer: RENDER| | | | | ||
| + | |XServer: Composite| | | | | ||
| + | |XServer: GLX| | | | | ||
| + | |XServer: DRI| | | | | ||
| + | |XServer: BIGREQUESTS| | | | | ||
| + | |Client: libXrandr| | | | | ||
| + | |Client: libXrender| | | | | ||
| + | |Xinerama| | | | | ||
| + | |MESA| | | | | ||
| + | |VirtualGL| | | | | ||