[
https://issues.apache.org/jira/browse/EDGENT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15507280#comment-15507280
]
Queenie Ma commented on EDGENT-179:
-----------------------------------
Currently, the oplet colors are hard-coded by oplet kind ({{invocation.kind}})
in {{graph.js}}. The issue wih the "ParallelBalancedRecipe" sample is that the
Peek oplet's kind ({{org.apache.edgent.oplet.functional.Peek}}) was not defined
in {{graph.js}}, so its color was generated randomly and was chosen to be the
same color as the Union oplet. To fix this bug, we need to assign a new color
to this Peek oplet.
However, I suspect that other oplet kinds may have been missed when hard-coding
these colors. Is there a way to get a list of all possible kinds without
manually looking at each of the classes?
In the future, if an oplet kind has not been assigned a color (e.g., because it
was missed or because it is new), I think it would be a good idea to perhaps
hard-code a set of unused colors and pick one of them to assign to the oplet
kind. This way, there will be no overlap.
> console: oplet coloring gradients "too close"
> ---------------------------------------------
>
> Key: EDGENT-179
> URL: https://issues.apache.org/jira/browse/EDGENT-179
> Project: Edgent
> Issue Type: Bug
> Components: Console
> Reporter: Dale LaBossiere
> Priority: Minor
> Attachments: EDGENT-179_oplet_colors.png, Screen Shot 2016-09-19 at
> 2.22.00 PM.png
>
>
> The oplet color generator ends up yielding two light purple-ish colors for
> two different kinds of (adjacent) oplets and one can't tell them apart. One
> is a Sink the other is a subtype of Peek - a StreamScope.
> I was seeing this in a ParallelBalancedRecipe app of mine. I can provide it
> if really necessary to repro/improve this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
