<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=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@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:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
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:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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 lang="PT-BR" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">In an initial analysis, in my opinion I would discard the "Alternate Concept 3", because it goes against the heuristic number #6 of Nielsen (recognition rather than recall), it soon becomes difficult
for the user remember where are the options.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Also discard the "Alternate Concept 1", because it blends vertical and horizontal menus, it soon avoids a pattern (system of meaning) and confuses the user.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<p class="MsoNormal"><span lang="EN-US">Date: Tue, 24 Dec 2013 07:49:39 -0500 (EST)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">From: Eldan Hildesheim <<a href="mailto:ehildesh@redhat.com">ehildesh@redhat.com</a>><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">To: Shahar Havivi <<a href="mailto:shaharh@redhat.com">shaharh@redhat.com</a>><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Cc: engine-devel <<a href="mailto:engine-devel@ovirt.org">engine-devel@ovirt.org</a>><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Subject: Re: [Engine-devel] Options for embedding Cloud init features into VM dialog - Need Input<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Can we merge those 2 pages together?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Eldan<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">----- Original Message -----<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">From: "Shahar Havivi" <shaharh at redhat.com><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">To: "Malini Rao" <mrao at redhat.com><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Cc: "engine-devel" <engine-devel at ovirt.org>, "Eldan Hildesheim" <ehildesh at redhat.com>, "Omer Frenkel" <ofrenkel at redhat.com>, "Michal Skrivanek" <michal.skrivanek at redhat.com><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Sent: Tuesday, December 24, 2013 2:33:28 PM<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Subject: Re: [Engine-devel] Options for embedding Cloud init features into VM dialog - Need Input<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">We have a feature page for the VM Init (including Cloud-Init and Windows<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Sysprep):<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="http://www.ovirt.org/Features/vm-init-persistent">http://www.ovirt.org/Features/vm-init-persistent</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">>From: "Malini Rao" <mrao at redhat.com><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">>To: "engine-devel" <engine-devel at ovirt.org><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">>Cc: "Eldan Hildesheim" <ehildesh at redhat.com><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">>Sent: Monday, December 23, 2013 11:43:07 PM<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">>Subject: [Engine-devel] Options for embedding Cloud init features into VM dialog - Need Input<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">>Hello all, <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">>There is a current feature to embed cloud init configuration which was originally part of the Run dialog to be part of the create/ Edit VM dialog. This presents a challenge in terms of good display of the hierarchies
of information since the VM dialog is already having subtabs stacked vertically. Please find here (<a href="http://www.ovirt.org/UX/cloud_init">http://www.ovirt.org/UX/cloud_init</a>) alternate concepts of how we might represent all the levels of hierarchy
from the VM dialog sub tabs to the cloud init categories and the content ( which is also nested sometimes) for each.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">>I have provided brief explanations of each concept and I would like your feedback on these ... esp with regard to feasibility. The general goals that govern the various concepts are -
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">>- Correct representation of the hierarchy<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">>- Not overloading the users with too much info and cluttering the screen<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">>- Not utilizing the same UI paradigm ( like expand/ collapse) for different types of info. For example, we have categories of info where the fields are distinct from each other and then we have times where the user is
able to add multiple instances of the same object type - e.g NICs and have the same set of fields be defined for each instance.
<o:p></o:p></span></p>
<p class="MsoNormal">><o:p> </o:p></p>
<p class="MsoNormal">>Your feedback is appreciated.<o:p></o:p></p>
<p class="MsoNormal">><o:p> </o:p></p>
<p class="MsoNormal">>Thanks<o:p></o:p></p>
<p class="MsoNormal">>Malini<o:p></o:p></p>
</div>
</div>
</body>
</html>