Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6DE65200B88 for ; Thu, 22 Sep 2016 23:06:26 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6C850160AAD; Thu, 22 Sep 2016 21:06:26 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B0A6A160AA9 for ; Thu, 22 Sep 2016 23:06:25 +0200 (CEST) Received: (qmail 79691 invoked by uid 500); 22 Sep 2016 21:06:25 -0000 Mailing-List: contact dev-help@edgent.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@edgent.apache.org Delivered-To: mailing list dev@edgent.apache.org Received: (qmail 79680 invoked by uid 99); 22 Sep 2016 21:06:24 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Sep 2016 21:06:24 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 66D1FC876A for ; Thu, 22 Sep 2016 21:06:24 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.344 X-Spam-Level: X-Spam-Status: No, score=-4.344 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.124] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id pbl7w_G18ckt for ; Thu, 22 Sep 2016 21:06:23 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id D96945F299 for ; Thu, 22 Sep 2016 21:06:22 +0000 (UTC) Received: (qmail 79422 invoked by uid 99); 22 Sep 2016 21:06:22 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Sep 2016 21:06:22 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E37562C0050 for ; Thu, 22 Sep 2016 21:06:21 +0000 (UTC) Date: Thu, 22 Sep 2016 21:06:21 +0000 (UTC) From: "Dale LaBossiere (JIRA)" To: dev@edgent.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (EDGENT-179) console: oplet coloring gradients "too close" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 22 Sep 2016 21:06:26 -0000 [ https://issues.apache.org/jira/browse/EDGENT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15514476#comment-15514476 ] Dale LaBossiere commented on EDGENT-179: ---------------------------------------- Any Edgent user can create their own oplets, as can new connector implementations, or any other enhancement to Edgent as/if needed. Seems like a better alternative would be to randomly allocate colors but keep track of what's been allocated and redo the random allocation until it's "not too close" to an in-use color. There can still be pre-allocated ones with predictable/static colors for "known" oplets (which of course will become out of date over time). You could also have different color allocation schemes for org.apache.edgent defined oplets vs non-edgent defined ones (if that might be helpful to users). There's no single place where all of the Edgent defined oplets are located in the repository nor registry of them. To identify Edgent's currently defined oplets, in Eclipse you can open the "Oplet" interface and select the "Quick Type Hierarchy" action on it. The result will include abstract classes (nothing the console will encounter) and test specific ones but these are pretty easy to identify based on their full class name. > 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)