<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="PT-BR" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Hi Jan,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I’m not sure if I’m following you. Did you mean changing the second-level navigation to tabs instead of panel areas? If
so should we merge Hosts and Admin tab in one page and collapse the panels like old-ui behavior (maybe keeping the dashboard statistics on top unchanged) but with new-ui styles OR add two new tabs to the toolbar?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I think the concept of accordion/collapsible elements works for Admin, but I don’t see it working for the panels on Hosts
tab, unless we group Basic Information, Repositories and Debug Reports in one single collapsible area.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I also discussed with Aline if we should move Peer Hosts from top to the toolbar and make it a plugin. Here’s a mockup
I did with Chrome:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><img width="1111" height="386" id="Picture_x0020_1" src="cid:image005.jpg@01D10286.CB9A5F20"></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><img width="1118" height="388" id="Picture_x0020_2" src="cid:image006.jpg@01D10286.CB9A5F20"></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">The reason why I think all panels in these pages can’t be merged in one tab is because if all panels were collapsed, the
page height would be around 3757 pixels. If admin items were hidden, it would be around 2108 tall. I believe we would have to set the accordions to hide other items when one item is collapsed. They don’t seem that tall in the PDF because the images were resized.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I believe we have to study this following a “mobile-first” approach because once we all agree with the new design, even
if we don’t include the mobile design in 2.0 release, we’ll have to keep some markup ready for responsive design to receive the new styles. I think this new tab design would need some updates in tab-ext.xml and the JS files before 2.0 release, assuming other
people or teams would start developing new plugins from 2.0 and on. If we update how the tabs are built in the UI from 2.0 to 2.1 for instance, that may turn against us with retro compatibility issues.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><img width="1024" height="436" id="Picture_x0020_3" src="cid:image007.jpg@01D10286.CB9A5F20"></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Samuel<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> kimchi-devel-bounces@ovirt.org
[mailto:kimchi-devel-bounces@ovirt.org] <b>On Behalf Of </b>Jan Schneider<br>
<b>Sent:</b> quinta-feira, 8 de outubro de 2015 13:10<br>
<b>To:</b> Aline Manera <alinefm@linux.vnet.ibm.com><br>
<b>Cc:</b> kimchi-devel@ovirt.org<br>
<b>Subject:</b> [Kimchi-devel] UI Change Request - Navigation<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hello Aline,<br>
<br>
I refer to the latest version of the <br>
User Interface Design Specification - Kimchi, 2014-12-23 (aka UI Design Spec)<br>
which defines the following structure of functionalities:<br>
<br>
<b>Host</b> (second level navigation via panel areas)<br>
Performance (System Statistics)<br>
Basic Information<br>
Repositories<br>
Debug Report<br>
Software Updates <br>
<br>
<b>Guests</b><br>
no second level functionalities<br>
<br>
<b>Templates</b><br>
no second level functionalities<br>
<br>
<b>Storage</b><br>
no second level functionalities<br>
<br>
<b>Networks</b><br>
no second level functionalities<br>
<br>
<b>Administration</b> (second level navigation via collapse/expand)<br>
Firmware Update<br>
SEP Configuration<br>
Power Options<br>
Configuration Backup<br>
Network Configuration<br>
SAN Adapters<br>
Sensor Monitor<br>
<br>
<br>
<br>
<b><span style="color:#3333FF">Problem Statement</span></b><br>
<br>
We already decided to move all Administration functionalities to Host (currently not updated in the UI Design Spec).<br>
<br>
We are currently facing the following problems:<br>
1) Host now contains 12 second level functionalities, all other (Guests, Templates, ...) none.<br>
We need to introduce a second level navigation for Host other than collapse/expand<br>
2) The navigation bar elements Storage and Network (refering to Virtualization) also exist in the Host context.
<br>
This might confuse the user.<br>
<br>
<br>
<br>
<b><span style="color:#3333FF">Proposal</span></b><br>
<br>
The described problems can be solved with the following changes:<br>
<br>
1) Introducing a second level navigation<br>
2) Changing the structure of functionalities as follows:<br>
<br>
<b>Host</b><br>
Performance (System Statistics)<br>
Basic Information<br>
Repositories<br>
Debug Report<br>
Software Updates <br>
Firmware Update<br>
SEP Configuration<br>
Power Options<br>
Configuration Backup<br>
Network Configuration<br>
SAN Adapters<br>
Sensor Monitor<br>
<br>
<b>Virtualization</b><br>
Guests<br>
Templates<br>
Storage<br>
Networks<br>
<br>
<b>Containers (future extension)</b><br>
to be defined<br>
<br>
<br>
<br>
Let's start a discussion on this.<br>
<br>
Kind regards<br>
Jan<o:p></o:p></p>
</div>
</body>
</html>