[
https://issues.apache.org/jira/browse/QUARKS-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale LaBossiere updated QUARKS-51:
----------------------------------
Description:
This is with a vintage 21Mar console. Layouts of more complex apps, such as
the sensorAnalytics sample app, result in flow graphs where streams
unnecessarily cross and some oplets for one stream are rendered overlayed on
another stream making it look like the oplet is associated with some other
stream (e.g., oplet 11 in the screenshots below)
See the two attachments. One shows the default / initial rendering. The other
shows a "manually adjusted" one (following a pause and dragging oplets).
was:
This is with a vintage 21Mar console. Layouts of more complex apps, such as
the sensorAnalytics sample app, result in flow graphs where streams
unnecessarily cross and some oplets for one stream are rendered overlayed on
another stream.
The "default" attachment shows the initial rendering.
The "adjusted" attachment shows the same app after pausing and dragging some of
the nodes so they render "cleanly".
> unnecessary stream crossing layout causes confusion
> ---------------------------------------------------
>
> Key: QUARKS-51
> URL: https://issues.apache.org/jira/browse/QUARKS-51
> Project: Quarks
> Issue Type: Bug
> Components: Console
> Reporter: Dale LaBossiere
> Attachments: Screen Shot 2016-03-21 at 3.13.45 PM.png, Screen Shot
> 2016-03-21 at 3.17.05 PM.png
>
>
> This is with a vintage 21Mar console. Layouts of more complex apps, such as
> the sensorAnalytics sample app, result in flow graphs where streams
> unnecessarily cross and some oplets for one stream are rendered overlayed on
> another stream making it look like the oplet is associated with some other
> stream (e.g., oplet 11 in the screenshots below)
> See the two attachments. One shows the default / initial rendering. The
> other shows a "manually adjusted" one (following a pause and dragging oplets).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
