<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 08/21/2015 10:39 PM, Aline Manera
wrote:<br>
</div>
<blockquote cite="mid:55D75B63.8020906@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<br>
<br>
<div class="moz-cite-prefix">On 21/08/2015 11:36, Walter Niklaus
wrote:<br>
</div>
<blockquote cite="mid:55D7375F.7010806@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<br>
<br>
<div class="moz-cite-prefix">Am 21.08.2015 um 15:40 schrieb
Aline Manera:<br>
</div>
<blockquote cite="mid:55D72A56.6000708@linux.vnet.ibm.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<br>
Hi Jan,<br>
<br>
What is the proposal of that?<br>
<br>
We've already had a new UI design documentation to cover all
the new UI elements and what you are proposing here is very
different from what we are doing on new UI.<br>
<br>
</blockquote>
The new UI design documentation contains some great usability
improvements but they are based on the current "master-branch"
Kimchi/Ginger design where Kimchi and the framework are tightly
interconnected.<br>
The existing design document is proposing the following base
navigation:<br>
<img src="cid:part1.06030706.09030508@linux.vnet.ibm.com" alt=""><br>
<br>
What's getting confusing from a usabiltiy point of view are
especially the main menue points Storage and Networks because
they are refferring to Virtual-Networks and
libvirt-Storage-Pools and in the section of Host-Management
there are similar menues for Host-Network and Host-Storage
management. The menue points of Kimchi are expanding into the
top horizontal section whereas the menue points of the
Host-Management and Admin area are expanding into a vertical
selection position.<br>
The horizontal section is limited in how much content it can
display.<br>
We should also think about additional plugins like Containers
and how we would have them show up in the UI.<br>
I guess what I'm pleading here is to take the chance and look at
the UI-design again considering the changed circumstances and
benefit from the skill some new community members like Samuel,
Jan and others are bringing in here.<br>
<br>
Thanks, Walter.<br>
</blockquote>
<br>
Thanks for the clarification, Walter!<br>
<br>
My concerns are about Kimchi plans. Related to that, I want to
make clear some points:<br>
<br>
1) At this time, the new UI will be develop (and released for 1.6)
as it was designed (Check: <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://github.com/kimchi-project/kimchi/wiki/UI-Design-Proposals">https://github.com/kimchi-project/kimchi/wiki/UI-Design-Proposals</a>)<br>
We've already had a lot of discussion on that and the new UI
is planned for the end of September, ie, less than 2 months from
now.<br>
So no new changes fit Kimchi schedule at this moment.<br>
<br>
That *does not* mean we can not improve and discussion new
ideas. But it will be implemented only after new UI is released.<br>
<br>
2) Wok is a web server framework for plugins. It will provide
basic UI elements and widgets which *can be* reused for the
plugins.<br>
How the plugins are designed is only related to the each
plugin.<br>
<br>
3) The vertical menu is in the new UI documentation for small
screens (responsive web design) so the UI will adjust the elements
according to screen size.<br>
<br>
4) I don't see any benefit in grouping content in one tab. Each
plugin can launch as many tabs as it wants. Kimchi decides for 4.
=)<br>
<br>
Let us take one fine example of showing network/storage details of
host vs virtual machines by means of tab concept. I can not think
of best possible fit with existing tab approach. On the other hand
if I segregate the Host, Virtualization and Containers as an
individual tabs and features of them shown/accessed in different
mean (similar to mock up Jan proposed), I can have luxury of
dealing with such conflicts easily represented from UI and at the
same time user experience is very much simplified across all the
tabs.<br>
<blockquote cite="mid:55D7375F.7010806@linux.vnet.ibm.com"
type="cite">
<blockquote cite="mid:55D72A56.6000708@linux.vnet.ibm.com"
type="cite"> Regards,<br>
Aline Manera<br>
<br>
<div class="moz-cite-prefix">On 21/08/2015 05:21, Jan
Schneider wrote:<br>
</div>
<blockquote cite="mid:55D6DF6C.7070800@linux.vnet.ibm.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
Hello,<br>
<br>
I started a Kimchi GUI Prototype with the Pencil tool. <br>
<br>
First topic I would like to discuss is the base navigation
proposal shown below<br>
1) There is a horizontal main navigation area which contains
'Host' and 'Virtualization'. 'Containers' is an example for
a future plugin.<br>
2) There is a vertical sub navigation area. Each item in the
sub navigation has an icon and a label (1 or 2 lines). <br>
<br>
I am very interested in your feedback and would like to come
to an agreement on this.<br>
<br>
I will discuss with Aline if we can store the Kimchi GUI
Prototype at a central place. It is packed in a single file
PencilGuiPrototype.zip<br>
Please extract this file and read ./readme.txt<br>
To view the Kimchi GUI Prototype open file
./htmlExport/index.html in your browser and navigate by
clicking on navigation tabs/buttons. <br>
If you want to edit the Kimchi GUI Prototype you will find
further information in ./readme.txt<br>
<br>
Kind regards<br>
Jan<br>
<br>
<br>
<br>
<br>
<img src="cid:part3.02020405.04020709@linux.vnet.ibm.com"
alt=""><br>
Alternate design with the same navigation<br>
<br>
<img src="cid:part4.04020008.09020300@linux.vnet.ibm.com"
alt=""><br>
<br>
<br>
<br>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>