wiki:development:roadmap
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
wiki:development:roadmap [2015/01/26 10:35] stefanbaur Sponsored Improvement Requests |
wiki:development:roadmap [2015/02/05 08:49] stefanbaur |
||
|---|---|---|---|
| Line 20: | Line 20: | ||
| === Prio #1 (not started yet) === | === Prio #1 (not started yet) === | ||
| + | **Fix Lockup of OS X client when running multiple sessions // | ||
| + | |||
| **Run multiple instances of X2GoClient**, | **Run multiple instances of X2GoClient**, | ||
| * Windows | * Windows | ||
| Line 25: | Line 27: | ||
| * Linux (probably already does) | * Linux (probably already does) | ||
| - | I would love to see X2GoClient gain the multi-session feature from PyHoCa. | + | Stefan |
| limited to one session. | limited to one session. | ||
| + | |||
| + | Please look at the following screenshots/ | ||
| + | ^ X2GoClient current look ^ X2GoClient single-session ^ X2GoClient multi-session ^ | ||
| + | | {{: | ||
| If that is impossible, we need to make sure that multiple instances of x2goclient can co-exist in RAM. | If that is impossible, we need to make sure that multiple instances of x2goclient can co-exist in RAM. | ||
| Line 32: | Line 38: | ||
| 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 | ||
| + | Step 2: Write wrapper to turn Multi-Instance into Multi-Session mode (especially important for OS X, where Multi-Instance isn't supported) | ||
| Task assigned to: Mihai, Mihai, and again, Mihai | Task assigned to: Mihai, Mihai, and again, Mihai | ||
| Line 44: | Line 53: | ||
| **Improve x2go-broker functionality (shadowing, stable release)** | **Improve x2go-broker functionality (shadowing, stable release)** | ||
| - | Task assigned to: Mike#1 | + | Task assigned to: Mike# |
| **Improve x2go-broker documentation** | **Improve x2go-broker documentation** | ||
| - | Task assigned to: Mike#1, Stefan | + | Task assigned to: Mike#1, Stefan |
| **General improvement on documentation** | **General improvement on documentation** | ||
| - | Task assigned to: Stefan, aided by Mike#1 | + | Task assigned to: Stefan, aided by Mike# |
| + | |||
| + | < | ||
| + | |||
| + | 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.// | ||
| + | |||
| + | Task assigned to: <none yet> - could be Alex, Mihai, ...? | ||
| + | < | ||
| - | **Alternative to 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. | h1 has some ideas what other F/LOSS codebases might be suitable as a time- and money-saving alternative to doing the NX-Rewrite. | ||
| He should mention them on x2go-dev to get more feedback, then a competent C/C++ coder should look at the alternatives and evaluate them for suitability. | He should mention them on x2go-dev to get more feedback, then a competent C/C++ coder should look at the alternatives and evaluate them for suitability. | ||
wiki/development/roadmap.txt · Last modified: 2017/05/11 09:45 by stefanbaur
Imprint & Legal Disclaimer -
Data Protection & Privacy Statement
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3