VISPA web issueshttps://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues2019-05-20T17:09:31+02:00https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/123Designer with Full Touch Support2019-05-20T17:09:31+02:00Benjamin FischerDesigner with Full Touch SupportChange the behavior of the Analysis Designer
to grant full touch support.
Add a “Switch” to choose between Touch and Desktop Mode.
*(from redmine: issue id 825, created on 2012-02-15 by root, closed on 2012-03-03)*Change the behavior of the Analysis Designer
to grant full touch support.
Add a “Switch” to choose between Touch and Desktop Mode.
*(from redmine: issue id 825, created on 2012-02-15 by root, closed on 2012-03-03)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/124Adjust the Designer to the new Extension Management2019-05-20T17:09:30+02:00Benjamin FischerAdjust the Designer to the new Extension ManagementThe Extension Management has slightly changed.
*(from redmine: issue id 826, created on 2012-02-15 by root, closed on 2012-02-15)*The Extension Management has slightly changed.
*(from redmine: issue id 826, created on 2012-02-15 by root, closed on 2012-02-15)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/125Adjust the PxlBrowser to the new Extension Management2019-05-20T17:09:30+02:00Benjamin FischerAdjust the PxlBrowser to the new Extension ManagementAdjust the Designer to the new Extension Management
*(from redmine: issue id 827, created on 2012-02-15 by root, closed on 2012-04-05)*Adjust the Designer to the new Extension Management
*(from redmine: issue id 827, created on 2012-02-15 by root, closed on 2012-04-05)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/126Consistent names needed in view.js and extensionmanager.js2019-05-20T17:09:30+02:00Benjamin FischerConsistent names needed in view.js and extensionmanager.jsThe naming of Tabs, TabContainers, ExtensionTabs and ExtensionButtons
(etc)
is not consistent.
A distinct and clear naming is necessary!
*(from redmine: issue id 830, created on 2012-02-18 by root, closed on 2012-04-18)*
* Relation...The naming of Tabs, TabContainers, ExtensionTabs and ExtensionButtons
(etc)
is not consistent.
A distinct and clear naming is necessary!
*(from redmine: issue id 830, created on 2012-02-18 by root, closed on 2012-04-18)*
* Relations:
* relates #866https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/127view.js: Several Layout Bugs2019-05-20T17:09:30+02:00Benjamin Fischerview.js: Several Layout BugsThere are many bugs in the layout behavior (basically the tab
containers).
Swipe gestures aren’t detected in some cases
and crazy border/padding issues at the top occur when swiping too fast.
Fix along \#830.
*(from redmine: issue ...There are many bugs in the layout behavior (basically the tab
containers).
Swipe gestures aren’t detected in some cases
and crazy border/padding issues at the top occur when swiping too fast.
Fix along \#830.
*(from redmine: issue id 831, created on 2012-02-21 by root, closed on 2012-04-18)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/128JavaScript Event Values "layerX" and "layerY"2019-05-20T17:09:30+02:00Benjamin FischerJavaScript Event Values "layerX" and "layerY"These values are deprecated and will be removed from the webkit engine
in the near future.
Substitution: pageX/Y or clientX/Y.
*(from redmine: issue id 832, created on 2012-02-21 by root, closed on 2012-02-24)*These values are deprecated and will be removed from the webkit engine
in the near future.
Substitution: pageX/Y or clientX/Y.
*(from redmine: issue id 832, created on 2012-02-21 by root, closed on 2012-02-24)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/129The Messenger is not working properly2019-05-20T17:09:29+02:00Benjamin FischerThe Messenger is not working properly1. The close function does not work on touch devices yet.
2. The queueing and the underlay removing is buggy.
*(from redmine: issue id 833, created on 2012-02-24 by root, closed on 2012-03-03)*1. The close function does not work on touch devices yet.
2. The queueing and the underlay removing is buggy.
*(from redmine: issue id 833, created on 2012-02-24 by root, closed on 2012-03-03)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/130Module Adding isn't always working.2019-05-20T17:09:29+02:00Benjamin FischerModule Adding isn't always working.The function “updateSinksAndSources” in module.js
throws - from time to time - errors. Maybe there’s a timing
error although the ajax call is synchronous.
*(from redmine: issue id 834, created on 2012-02-24 by root, closed on 2012-...The function “updateSinksAndSources” in module.js
throws - from time to time - errors. Maybe there’s a timing
error although the ajax call is synchronous.
*(from redmine: issue id 834, created on 2012-02-24 by root, closed on 2012-02-25)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/131Center Panels of Extensions aren't scrollable with TouchScroll2019-05-20T17:09:29+02:00Benjamin FischerCenter Panels of Extensions aren't scrollable with TouchScrollThis should be solved.
There will be an other machanism in the meanwhile.
*(from redmine: issue id 835, created on 2012-02-26 by root, closed on 2012-05-21)*
* Relations:
* relates #866This should be solved.
There will be an other machanism in the meanwhile.
*(from redmine: issue id 835, created on 2012-02-26 by root, closed on 2012-05-21)*
* Relations:
* relates #866https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/132Designer: Grid action buttons can be fired only once2019-05-20T17:09:29+02:00Benjamin FischerDesigner: Grid action buttons can be fired only onceAfter a click/tap on an action button in a grid,
the same button cannot be clicked/tapped again.
*(from redmine: issue id 836, created on 2012-02-29 by root, closed on 2012-03-03)*After a click/tap on an action button in a grid,
the same button cannot be clicked/tapped again.
*(from redmine: issue id 836, created on 2012-02-29 by root, closed on 2012-03-03)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/133Static Extension Content2019-05-20T17:09:29+02:00Benjamin FischerStatic Extension ContentThe static mount path of extensions is not working correct
when running either w/ Apache or w/o Apache.
*(from redmine: issue id 837, created on 2012-03-03 by root, closed on 2012-03-03)*The static mount path of extensions is not working correct
when running either w/ Apache or w/o Apache.
*(from redmine: issue id 837, created on 2012-03-03 by root, closed on 2012-03-03)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/135Modules should have a "Refresh" function2019-05-20T17:09:28+02:00Benjamin FischerModules should have a "Refresh" functionA refresh funciton for modules is needed in order to update
Sinks&Sources, Name, label, etc.
*(from redmine: issue id 859, created on 2012-04-03 by root, closed on 2012-04-26)*
* Relations:
* relates #923
* Changesets:
* Revisio...A refresh funciton for modules is needed in order to update
Sinks&Sources, Name, label, etc.
*(from redmine: issue id 859, created on 2012-04-03 by root, closed on 2012-04-26)*
* Relations:
* relates #923
* Changesets:
* Revision 588 by Marcel Rieger on 2012-04-26T07:16:33Z:
```
Designer: Fixed #859. Refresh works.
```
* Revision 588 by Marcel Rieger on 2012-04-26T07:16:33Z:
```
Designer: Fixed #859. Refresh works.
```https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/136Dashboard extension2019-05-20T17:09:28+02:00Benjamin FischerDashboard extensionThe dashboard extension should offer two main functions:
1. Check the status of on or more analyses.
2. Reload an analysis from the Server (from the existing Analysis
py-object, not the xml file)
*(from redmine: issue id 860, creat...The dashboard extension should offer two main functions:
1. Check the status of on or more analyses.
2. Reload an analysis from the Server (from the existing Analysis
py-object, not the xml file)
*(from redmine: issue id 860, created on 2012-04-03 by root, closed on 2012-04-19)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/137Scrolling of Extension Content2019-05-20T17:09:28+02:00Benjamin FischerScrolling of Extension ContentManage automated scrolling of Extension’s tab content. Currently it is
not possible to scroll when modules are outside the visible area or if a
assigned component is simply larger than the available space through
resizing the Web-Browser...Manage automated scrolling of Extension’s tab content. Currently it is
not possible to scroll when modules are outside the visible area or if a
assigned component is simply larger than the available space through
resizing the Web-Browser window (e.g. TableView of PXLBrowser).
*(from redmine: issue id 864, created on 2012-04-05 by root, closed on 2012-08-06)*
* Relations:
* relates #866
* relates #920
* Changesets:
* Revision 737 by Marcel Rieger on 2012-05-21T09:36:53Z:
```
Fixed #864
```
* Revision 737 by Marcel Rieger on 2012-05-21T09:36:53Z:
```
Fixed #864
```0.2https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/138Closing Tabs2019-05-20T17:09:28+02:00Benjamin FischerClosing TabsIf all tabs of a kind (e.g. Designer) are closed, an empty selector
remains in the top view.
*(from redmine: issue id 865, created on 2012-04-05 by root, closed on 2012-04-18)*
* Relations:
* relates #866If all tabs of a kind (e.g. Designer) are closed, an empty selector
remains in the top view.
*(from redmine: issue id 865, created on 2012-04-05 by root, closed on 2012-04-18)*
* Relations:
* relates #866https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/139Main View upgrade2019-05-20T17:09:28+02:00Benjamin FischerMain View upgradeThe current main view has alpha status and
needs to be upgraded/improved.
Since most of the extensions are in development by now,
there are more/differing requirements.
The code needs to be redisigned using way more encapsulation....The current main view has alpha status and
needs to be upgraded/improved.
Since most of the extensions are in development by now,
there are more/differing requirements.
The code needs to be redisigned using way more encapsulation.
A redesign of the layout/gui itself won’t (?) be the primary
intention.
*(from redmine: issue id 866, created on 2012-04-05 by root, closed on 2012-04-18)*
* Relations:
* relates #865
* relates #864
* relates #835
* relates #830https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/140Designer: context menus are overlapped by connections2019-05-20T17:09:27+02:00Benjamin FischerDesigner: context menus are overlapped by connections*(from redmine: issue id 910, created on 2012-04-19 by root, closed on 2012-04-19)*
* Changesets:
* Revision 539 by Marcel Rieger on 2012-04-19T08:59:58Z:
```
Designer: fixed #910. Analysis work.
```
* Revision 539 by Marcel Riege...*(from redmine: issue id 910, created on 2012-04-19 by root, closed on 2012-04-19)*
* Changesets:
* Revision 539 by Marcel Rieger on 2012-04-19T08:59:58Z:
```
Designer: fixed #910. Analysis work.
```
* Revision 539 by Marcel Rieger on 2012-04-19T08:59:58Z:
```
Designer: fixed #910. Analysis work.
```https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/141Designer: Floating panes are extremely slow and buggy2019-05-20T17:09:27+02:00Benjamin FischerDesigner: Floating panes are extremely slow and buggyFloatingPanes should be exchanged by Divs or BorderContainers.
Working example: ExtensionFrames.
*(from redmine: issue id 914, created on 2012-04-19 by root, closed on 2012-04-26)*FloatingPanes should be exchanged by Divs or BorderContainers.
Working example: ExtensionFrames.
*(from redmine: issue id 914, created on 2012-04-19 by root, closed on 2012-04-26)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/142Multiple Tabs and Frames for Extensions2019-05-20T17:09:27+02:00Benjamin FischerMultiple Tabs and Frames for ExtensionsAt the moment, each extension is allowed to create only one (distinct!)
Tab or Frame.
The creation of tabs or frames should be more dynamic. To grant
uniqueness and
instance control, each tab or frame should have an identifier.
*(f...At the moment, each extension is allowed to create only one (distinct!)
Tab or Frame.
The creation of tabs or frames should be more dynamic. To grant
uniqueness and
instance control, each tab or frame should have an identifier.
*(from redmine: issue id 915, created on 2012-04-19 by root, closed on 2012-04-29)*
* Relations:
* relates #916
* Changesets:
* Revision 606 by Marcel Rieger on 2012-04-29T12:46:36Z:
```
New ExtensionManager and Extension Setup! Your Extension won't work unless you update it according to the new structure (see extensionmanager.js or dummy or the Wiki Page). Fixed #915 and #916.
```
* Revision 606 by Marcel Rieger on 2012-04-29T12:46:36Z:
```
New ExtensionManager and Extension Setup! Your Extension won't work unless you update it according to the new structure (see extensionmanager.js or dummy or the Wiki Page). Fixed #915 and #916.
```https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/143Distinction between tabs and frames is interfering and causes programmatic pr...2019-05-20T17:09:25+02:00Benjamin FischerDistinction between tabs and frames is interfering and causes programmatic problemsInstead of distinguishing between tab and frame (too) deep in the
code,
the decision to “render” the content as a tab or a frame should be taken
by a single
flag “tag” or “frame”
*(from redmine: issue id 916, created on 2012-04-19 ...Instead of distinguishing between tab and frame (too) deep in the
code,
the decision to “render” the content as a tab or a frame should be taken
by a single
flag “tag” or “frame”
*(from redmine: issue id 916, created on 2012-04-19 by root, closed on 2012-04-29)*
* Relations:
* relates #915