VISPA web issueshttps://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues2019-05-20T16:30:03+02:00https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/668Features for 4.02019-05-20T16:30:03+02:00Benjamin FischerFeatures for 4.0See sub-tasks
*(from redmine: issue id 2294, created on 2016-04-07 by benjamin.fischer)*
* Relations:
* child #1530
* child #1619
* child #1875
* child #2233
* child #2295
* child #2296
* child #2297
* child #2298
* ...See sub-tasks
*(from redmine: issue id 2294, created on 2016-04-07 by benjamin.fischer)*
* Relations:
* child #1530
* child #1619
* child #1875
* child #2233
* child #2295
* child #2296
* child #2297
* child #2298
* child #2299
* child #2301
* child #2302
* child #2303
* child #2304
* child #2305
* child #2306
* child #2311
* child #2314
* child #2315
* child #2327
* child #2347
* child #2351
* child #23634.02015-04-30https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/632sorting of preferences2019-05-20T17:08:11+02:00Benjamin Fischersorting of preferencessort list of extensions in preferences by priority
*(from redmine: issue id 2233, created on 2015-05-29 by Daniel.Van.Asseldonk, closed on 2016-07-14)*
* Relations:
* parent #2294sort list of extensions in preferences by priority
*(from redmine: issue id 2233, created on 2015-05-29 by Daniel.Van.Asseldonk, closed on 2016-07-14)*
* Relations:
* parent #22944.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/631setting preferences with multiple instances of an extension2019-05-20T17:08:11+02:00Benjamin Fischersetting preferences with multiple instances of an extensionsetting preferences does not work in some cases, when multiple instances
of an extension are open
*(from redmine: issue id 2232, created on 2015-05-29 by Daniel.Van.Asseldonk, closed on 2016-07-14)*setting preferences does not work in some cases, when multiple instances
of an extension are open
*(from redmine: issue id 2232, created on 2015-05-29 by Daniel.Van.Asseldonk, closed on 2016-07-14)*4.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/620Dynamical adding of menu entries should be possible2019-05-20T17:08:16+02:00Benjamin FischerDynamical adding of menu entries should be possible*(from redmine: issue id 2216, created on 2015-04-29 by root, closed on 2016-07-14)*
* Relations:
* parent #2312*(from redmine: issue id 2216, created on 2015-04-29 by root, closed on 2016-07-14)*
* Relations:
* parent #23124.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/531default path2019-05-20T16:28:26+02:00Benjamin Fischerdefault pathmake default path workspace dependend
*(from redmine: issue id 2041, created on 2015-01-01 by Daniel.Van.Asseldonk, closed on 2016-07-14)*
* Relations:
* parent #1530make default path workspace dependend
*(from redmine: issue id 2041, created on 2015-01-01 by Daniel.Van.Asseldonk, closed on 2016-07-14)*
* Relations:
* parent #15304.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/411Add a WindowMananger2019-05-20T16:27:03+02:00Benjamin FischerAdd a WindowManangerOn the way to a fully integrated UI (and to “resist” incoming feature
requests), a WindowManager is required.
Its tasks should be:
- Browser/Window history handling (pushState Api, history.js)
- Shortcut handling
- Message handli...On the way to a fully integrated UI (and to “resist” incoming feature
requests), a WindowManager is required.
Its tasks should be:
- Browser/Window history handling (pushState Api, history.js)
- Shortcut handling
- Message handling
- …
*(from redmine: issue id 1875, created on 2014-10-01 by root, closed on 2016-07-14)*
* Relations:
* child #1845
* child #1905
* child #2308
* child #2310
* child #2373
* parent #2294
* Changesets:
* Revision 1765 by Benjamin Fischer on 2014-12-02T21:51:09Z:
```
Implement UI abstraction: UIElement & UIJuggler
Migrated Workspace, WorkspaceView & PreferenceView accordingly
Importand changed to API:
- to focus or show an UIElement use .focus() since this will be required to handle multiple simultaniously visible UIElements properly
- UIJuggler takes care of all the management of other peer instances and their visual components - no meddling required anymore
- Workspace: (de)select methods & the belonging events (de)selected have been replaced by focus/blur methods & the events focus/blur
refs #1875, #1845
```
* Revision 1765 by Benjamin Fischer on 2014-12-02T21:51:09Z:
```
Implement UI abstraction: UIElement & UIJuggler
Migrated Workspace, WorkspaceView & PreferenceView accordingly
Importand changed to API:
- to focus or show an UIElement use .focus() since this will be required to handle multiple simultaniously visible UIElements properly
- UIJuggler takes care of all the management of other peer instances and their visual components - no meddling required anymore
- Workspace: (de)select methods & the belonging events (de)selected have been replaced by focus/blur methods & the events focus/blur
refs #1875, #1845
```
* Revision 1772 by Benjamin Fischer on 2014-12-05T14:51:11Z:
```
Migrated ExtensionView, CenterView (including Workspace integration), Terminal to use UIElement & UIJuggler. refs #1875, #1845
```
* Revision 1772 by Benjamin Fischer on 2014-12-05T14:51:11Z:
```
Migrated ExtensionView, CenterView (including Workspace integration), Terminal to use UIElement & UIJuggler. refs #1875, #1845
```
* Revision 1800 by Benjamin Fischer on 2014-12-12T21:41:34Z:
```
Implemented (workspace) session saving & restoring and some minor changes:
- the ExtensionView features a state that can be used to store session persitent data (e.g. working directory, open file name, current selection, ...)
- it can be accessed with the functions getState(key) and setState(key, value, delay)
- the delay (given in seconds) should be used to lessen the load on the server and not immideatly save upon the every change; here an example: the scroll position in saved as a state, this should be done with a good delay (e.g. 10s) so one won't overload the connection with lots of save requests
- every state change will emit an "stateChange" event with the changed states key as first parameter - or null if the entire state was loaded from scrach (during init)
- the state saving does not account if one logged in multiple times (e.g. from phone & laptop): the latest save will be stored
- restoring the state available only when starting a new session (e.g. (re)connecting the workspace, reloading the page, logging in on another maching)
- restoring can be enabled in the settings (Workspace Handler -> continueSession) - even to always resore session
- minor change: cleaned up the parameter handling during class creation (init)
- also fixed various bugs
refs #1875, fix #1905, #1845
```
* Revision 1800 by Benjamin Fischer on 2014-12-12T21:41:34Z:
```
Implemented (workspace) session saving & restoring and some minor changes:
- the ExtensionView features a state that can be used to store session persitent data (e.g. working directory, open file name, current selection, ...)
- it can be accessed with the functions getState(key) and setState(key, value, delay)
- the delay (given in seconds) should be used to lessen the load on the server and not immideatly save upon the every change; here an example: the scroll position in saved as a state, this should be done with a good delay (e.g. 10s) so one won't overload the connection with lots of save requests
- every state change will emit an "stateChange" event with the changed states key as first parameter - or null if the entire state was loaded from scrach (during init)
- the state saving does not account if one logged in multiple times (e.g. from phone & laptop): the latest save will be stored
- restoring the state available only when starting a new session (e.g. (re)connecting the workspace, reloading the page, logging in on another maching)
- restoring can be enabled in the settings (Workspace Handler -> continueSession) - even to always resore session
- minor change: cleaned up the parameter handling during class creation (init)
- also fixed various bugs
refs #1875, fix #1905, #1845
```
* Revision 1825 by Benjamin Fischer on 2014-12-22T23:10:42Z:
```
Implemented browser history handling:
- the URL can now represent the currently active tab
- this also generates new browser history entrys which, when navigated to, are attempted to be reconstruced
- CenterView can provide further data to be represented (e.g. a file path): done by overriding getFragment & applyFragment
refs #1875
```
* Revision 1825 by Benjamin Fischer on 2014-12-22T23:10:42Z:
```
Implemented browser history handling:
- the URL can now represent the currently active tab
- this also generates new browser history entrys which, when navigated to, are attempted to be reconstruced
- CenterView can provide further data to be represented (e.g. a file path): done by overriding getFragment & applyFragment
refs #1875
```
* Revision 2294 by Benjamin Fischer on 2015-07-15T09:13:46Z:
```
Implemented new window management features: Tabs can now be rearranged into any desired layout via drag and drop. refs #1875
```
* Revision 2294 by Benjamin Fischer on 2015-07-15T09:13:46Z:
```
Implemented new window management features: Tabs can now be rearranged into any desired layout via drag and drop. refs #1875
```4.0Benjamin FischerBenjamin Fischerhttps://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/338Open with in context menu2019-05-20T16:26:17+02:00Benjamin FischerOpen with in context menu“Open with” in context menu
*(from redmine: issue id 1669, created on 2014-04-15 by martin.urban, closed on 2016-07-14)*
* Relations:
* parent #2309“Open with” in context menu
*(from redmine: issue id 1669, created on 2014-04-15 by martin.urban, closed on 2016-07-14)*
* Relations:
* parent #23094.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/316Joint preferences/shortcuts.2019-05-20T17:08:51+02:00Benjamin FischerJoint preferences/shortcuts.There are a lot of overlaps between preference/shortcut definitions
of extensions (e.g. FileBrowser <->FileSelector) or platform
components
(e.g. WorkspaceView <->PreferenceView).
This “ambiguities” can be solved by introducin...There are a lot of overlaps between preference/shortcut definitions
of extensions (e.g. FileBrowser <->FileSelector) or platform
components
(e.g. WorkspaceView <->PreferenceView).
This “ambiguities” can be solved by introducing joint preferences.
However, such an approach may require some changes in the class
structure
as well as the Preference GUI.
*(from redmine: issue id 1619, created on 2014-03-30 by root, closed on 2016-07-14)*
* Relations:
* parent #22944.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/295Edit workspaces2019-05-20T17:08:54+02:00Benjamin FischerEdit workspaces*(from redmine: issue id 1536, created on 2014-01-28 by root, closed on 2016-04-29)*
* Relations:
* duplicates #2299*(from redmine: issue id 1536, created on 2014-01-28 by root, closed on 2016-04-29)*
* Relations:
* duplicates #22994.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/289Extension AND workspace specific preferences2019-05-20T17:08:57+02:00Benjamin FischerExtension AND workspace specific preferencesExtension AND workspace specific preferences are needed. Example:
Bookmarks in Filebrowser depend on the Extension and the Workspace
*(from redmine: issue id 1530, created on 2014-01-27 by martin.urban, closed on 2016-07-14)*
* Relati...Extension AND workspace specific preferences are needed. Example:
Bookmarks in Filebrowser depend on the Extension and the Workspace
*(from redmine: issue id 1530, created on 2014-01-27 by martin.urban, closed on 2016-07-14)*
* Relations:
* child #2041
* parent #22944.0