VISPA web issueshttps://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues2019-05-20T17:09:33+02:00https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/121Designer: server-side Connections (relies on #804)2019-05-20T17:09:33+02:00Benjamin FischerDesigner: server-side Connections (relies on #804)Connections aren’t submitted to the server yet.
This can be done, if there’s a ModuleManager.
*(from redmine: issue id 806, created on 2012-01-19 by root, closed on 2012-02-18)*Connections aren’t submitted to the server yet.
This can be done, if there’s a ModuleManager.
*(from redmine: issue id 806, created on 2012-01-19 by root, closed on 2012-02-18)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/120Designer: Connections2019-05-20T17:09:33+02:00Benjamin FischerDesigner: ConnectionsConnections are pretty buggy.
And there’s no touch support yet.
*(from redmine: issue id 805, created on 2012-01-19 by root, closed on 2012-02-18)*Connections are pretty buggy.
And there’s no touch support yet.
*(from redmine: issue id 805, created on 2012-01-19 by root, closed on 2012-02-18)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/119Designer: add a ModuleManager2019-05-20T17:09:33+02:00Benjamin FischerDesigner: add a ModuleManagerThe Modules are managed by the content class at the moment.
A ModuleHandler (like the ConnectionHandler) should take care of that.
In addition, it could offer more functionality and better overview.
*(from redmine: issue id 804, cr...The Modules are managed by the content class at the moment.
A ModuleHandler (like the ConnectionHandler) should take care of that.
In addition, it could offer more functionality and better overview.
*(from redmine: issue id 804, created on 2012-01-19 by root, closed on 2012-02-21)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/118Scroll in HTML Containers on Touch Devices2019-05-20T17:09:33+02:00Benjamin FischerScroll in HTML Containers on Touch DevicesOverflow:scroll and overflow:auto
are not working on some touch devices.
Scrolling is not possible when the content exceeds it’s container.
Example: ModulePane in the Designer Extension.
*(from redmine: issue id 803, created on 2...Overflow:scroll and overflow:auto
are not working on some touch devices.
Scrolling is not possible when the content exceeds it’s container.
Example: ModulePane in the Designer Extension.
*(from redmine: issue id 803, created on 2012-01-12 by root, closed on 2012-02-25)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/117First draft/Reanimation of the (Analysis)Designer needed.2019-05-20T17:09:33+02:00Benjamin FischerFirst draft/Reanimation of the (Analysis)Designer needed.The Analysis Designer of older versions can be partially reused in the
new version.
*(from redmine: issue id 802, created on 2012-01-10 by root, closed on 2012-01-12)*The Analysis Designer of older versions can be partially reused in the
new version.
*(from redmine: issue id 802, created on 2012-01-10 by root, closed on 2012-01-12)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/116sometimes extension instances are not show in tabs2019-05-20T17:09:34+02:00Benjamin Fischersometimes extension instances are not show in tabs*(from redmine: issue id 801, created on 2012-01-10 by gmueller, closed on 2012-04-18)**(from redmine: issue id 801, created on 2012-01-10 by gmueller, closed on 2012-04-18)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/115the layout functions needs to be called more often2019-05-20T17:09:34+02:00Benjamin Fischerthe layout functions needs to be called more oftenIn many situations the content of the tabs is not properly layouted
*(from redmine: issue id 800, created on 2012-01-10 by gmueller, closed on 2012-01-10)*In many situations the content of the tabs is not properly layouted
*(from redmine: issue id 800, created on 2012-01-10 by gmueller, closed on 2012-01-10)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/114too many effects2019-05-20T17:09:34+02:00Benjamin Fischertoo many effectsEven on a fast computer the effects (fade in/out etc) are to expensive.
*(from redmine: issue id 799, created on 2012-01-10 by gmueller, closed on 2012-01-10)*Even on a fast computer the effects (fade in/out etc) are to expensive.
*(from redmine: issue id 799, created on 2012-01-10 by gmueller, closed on 2012-01-10)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/113Improve 'devicematch' in tools/device.py2019-05-20T17:09:34+02:00Benjamin FischerImprove 'devicematch' in tools/device.pyAt the moment, the device matching is hardcoded.
Maybe there’s a simple framework for this job.
Otherwise, the if/else structure should be somehow improved.
*(from redmine: issue id 740, created on 2011-11-20 by root, closed on 201...At the moment, the device matching is hardcoded.
Maybe there’s a simple framework for this job.
Otherwise, the if/else structure should be somehow improved.
*(from redmine: issue id 740, created on 2011-11-20 by root, closed on 2011-11-21)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/110Methods in ajax.FileHandler and FileSystem.py2019-05-20T17:09:35+02:00Benjamin FischerMethods in ajax.FileHandler and FileSystem.pyUpdate and add functions in this files to change the behavior of the
FileBrowser.
*(from redmine: issue id 722, created on 2011-10-19 by root, closed on 2011-11-20)*Update and add functions in this files to change the behavior of the
FileBrowser.
*(from redmine: issue id 722, created on 2011-10-19 by root, closed on 2011-11-20)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/109JS mousemovement2019-05-20T17:09:35+02:00Benjamin FischerJS mousemovementExtJS seems to handle all mouse movements by itself.
This should be checked in order to work properly for the app in
core/js/sites/app/main.js
*(from redmine: issue id 721, created on 2011-10-19 by root, closed on 2011-10-19)*ExtJS seems to handle all mouse movements by itself.
This should be checked in order to work properly for the app in
core/js/sites/app/main.js
*(from redmine: issue id 721, created on 2011-10-19 by root, closed on 2011-10-19)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/108Div container for the FileBrowser2019-05-20T17:09:35+02:00Benjamin FischerDiv container for the FileBrowserCheck wether the FileBrowser made in ExtJs needs to have a div
container
that it’s rendered into.
*(from redmine: issue id 720, created on 2011-10-19 by root, closed on 2011-11-20)*Check wether the FileBrowser made in ExtJs needs to have a div
container
that it’s rendered into.
*(from redmine: issue id 720, created on 2011-10-19 by root, closed on 2011-11-20)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/107JS mousemovement2019-05-20T17:09:35+02:00Benjamin FischerJS mousemovementExtJS seems to handle all mouse movements by itself.
This should be checked in order to work properly for the app in
core/js/sites/app/main.js
*(from redmine: issue id 719, created on 2011-10-19 by root, closed on 2011-10-19)*ExtJS seems to handle all mouse movements by itself.
This should be checked in order to work properly for the app in
core/js/sites/app/main.js
*(from redmine: issue id 719, created on 2011-10-19 by root, closed on 2011-10-19)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/105use virtual paths2019-05-20T16:23:38+02:00Benjamin Fischeruse virtual pathsnot all paths (esp. root path) are not virtual!
*(from redmine: issue id 707, created on 2011-09-18 by gmueller, closed on 2012-05-21)*not all paths (esp. root path) are not virtual!
*(from redmine: issue id 707, created on 2011-09-18 by gmueller, closed on 2012-05-21)*