[
https://issues.apache.org/jira/browse/EDGENT-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527334#comment-15527334
]
Dale LaBossiere commented on EDGENT-178:
----------------------------------------
The png looks good for the stream hover. Just a bit of rationale... if a user
adds an alias to a Stream it's because they want to dynamically control some
aspect of it via the ControlService. As such it's probably at least as
important an item to display as "tags".
Hence if tags are being shown in the oplet hover it makes sense to me that an
alias would also be presented. But adding two more columns for that info (one
for source streams one for target streams) makes me grimace a bit. It's
already a pretty wide hover popup.
One option could be to change the (multiline) tags column header and data to be
alias and tags:
[6] alias: theAlias, tags: t1, t2, ...
[7] alias: theAlias, tags: t1, t2, ...
Though maybe that won't help enough with the overall popup width.
The font size of the column headers could probably also be a bit smaller.
Perhaps another alternative would be to migrate the tags (and aliases) column,
and maybe Sources and Targets columns, to a new "row" in the hover, making it
deeper and more narrow?
Do either of those resonate with you? Other layout ideas?
> console: stream hover should report "alias" in addition to tags; maybe oplet
> hover too
> --------------------------------------------------------------------------------------
>
> Key: EDGENT-178
> URL: https://issues.apache.org/jira/browse/EDGENT-178
> Project: Edgent
> Issue Type: Improvement
> Components: Console
> Reporter: Dale LaBossiere
> Assignee: Queenie Ma
> Priority: Minor
> Labels: newbie
> Attachments: alias_stream_hover.png
>
>
> TStream.alias("someAlias") manifests itself in graph.Connector similar to
> tags. I'm pretty sure the graph json captures the alias already.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
