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

Chris Riccomini commented on SAMZA-32:
--------------------------------------

Woah. This is great.

bq. For improving the layout of the AM webapp, there are a few changes I want 
to make, including making the list of running containers and partitions display 
better.

[~jakobhoman] had some thoughts on this in SAMZA-107.

bq. Other options I am considering include adding tabs or to split into 
multiple pages. I would like to run some more jobs to get a sense of how the 
current UI looks for jobs that are a bit more complex.

Personally, I feel like JS+tabs would be a bit more intuitive, but I think the 
only real way to tell is to actually implement and see how it feels. I'm sure 
people will be vocal once they see what we come up with. :)

> Update Samza AM dashboard look and feel
> ---------------------------------------
>
>                 Key: SAMZA-32
>                 URL: https://issues.apache.org/jira/browse/SAMZA-32
>             Project: Samza
>          Issue Type: Bug
>          Components: yarn
>    Affects Versions: 0.6.0
>            Reporter: Chris Riccomini
>            Assignee: David Chen
>              Labels: newbie
>         Attachments: Screen Shot 2014-05-05 at 6.48.54 AM.png
>
>
> We should update Samza's YARN AM look & feel to match the branding/CSS on the 
> website. This includes:
> * White background, black font, blue accent color and link color (#1B91E0)
> * Samza logo (font-family: 'Ropa Sans', sans-serif; color: white; 
> background-color: rgb(255, 0, 0)\;)
> * Grey-ish bar on top (background-color: #F5F4F0\;) with Samza logo embedded 
> in upper left.
> * Helvetica body font
> * Font awesome for icons (color: #d3d2d0\;)
> We should also take a look at making the AM layout a little more intuitive. 
> Maybe it makes sense to add separate pages, or a better layout?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to