[ 
https://issues.apache.org/jira/browse/QUARKS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202198#comment-15202198
 ] 

ASF GitHub Bot commented on QUARKS-20:
--------------------------------------

GitHub user home4slc opened a pull request:

    https://github.com/apache/incubator-quarks/pull/28

    QUARKS-20

    Tuple count view now shows tags and colors oplets for tuple counts instead
    Modified the edges in static and oplet kind view to be a darker grey
    Fixed an issue with checking / unchecking show tags where the refresh 
interval was no longer running.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/home4slc/incubator-quarks 
QUARKS-20_tuple_count_view

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-quarks/pull/28.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #28
    
----
commit bcbce8a4b4658a8a144c5445eeb9b067633da985
Author: Susan L. Cline <[email protected]>
Date:   2016-03-18T20:53:19Z

    QUARKS-20 tuple count view shows tags, fixed bugs with stream tags

----


> Improve usability of the quarks console
> ---------------------------------------
>
>                 Key: QUARKS-20
>                 URL: https://issues.apache.org/jira/browse/QUARKS-20
>             Project: Quarks
>          Issue Type: Improvement
>          Components: Console
>            Reporter: Susan L. Cline
>         Attachments: console_with_OP_X.png, console_with_just_X.png, 
> grey_counter_ops.jpg, opletkind_counterop_square_tags_rectangular.jpg, 
> static_flow_darker_edges_after.jpg, static_flow_light_edges_before.jpg, 
> tuple_count_new_colored_oplets_stream_tags_edges.jpg
>
>
> I sent out a note to the dev list with some suggestions to improve the 
> console.  This JIRA will be used to track suggestions and actual work items 
> that come out of that discussion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to