[Kimchi-devel] Kimchi GUI Prototype, Base Navigation

Tue Aug 25 15:02:01 UTC 2015


On 21.08.2015 19:09, Aline Manera wrote:
>
>
> On 21/08/2015 11:36, Walter Niklaus wrote:
>>
>>
>> Am 21.08.2015 um 15:40 schrieb Aline Manera:
>>>
>>> Hi Jan,
>>>
>>> What is the proposal of that?
>>>
>>> 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.
>>>
>> 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.
>> The existing design document is proposing the following base navigation:
>>
>>
>> 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.
>> The horizontal section is limited in how much content it can display.
>> We should also think about additional plugins like Containers and how 
>> we would have them show up in the UI.
>> 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.
>>
>> Thanks, Walter.
>
> Thanks for the clarification, Walter!
>
> My concerns are about Kimchi plans. Related to that, I want to make 
> clear some points:
>
> 1) At this time, the new UI will be develop (and released for 1.6) as 
> it was designed (Check: 
> https://github.com/kimchi-project/kimchi/wiki/UI-Design-Proposals)
>     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.
>     So no new changes fit Kimchi schedule at this moment.
>
>     That *does not* mean we can not improve and discussion new ideas. 
> But it will be implemented only after new UI is released.
Now I understand that you are targetting to have the new UI in the 
master branch by end of September, begin of October in order to have any 
new development for 1.6 based on the new UI.  This makes a lot of sense.
I'm glad to hear that we will evaluate the ideas of improving the design 
and I hope that with additional folks working in the UI area we would be 
able to even integrate some of them initially depending on the effort of 
course considering the end of September date.

>
> 2) Wok is a web server framework for plugins. It will provide basic UI 
> elements and widgets which *can be* reused for the plugins.
>     How the plugins are designed is only related to the each plugin.
I agree from a very generic and high level point of view to this 
statement. But when it comes to plugins which have to coexist together 
we have to consider the overall user experience. As an exagerated 
example you could think of 2 plugins exposing the same menue point on 
the same level but having a complete different scope and semantics.

>
> 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.
>
> 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. =)
I agree that we should not limit a plugin to one single tab and on the 
other side some plugins may not even have their own tab and simply 
plugin to an existing one.
Grouping/separating content covering certain aspects in different tabs 
is a proposal on how to overcome the problematic we currently have with 
storage and networking being required menue point for host- and for 
guest-management but having a different scope in the different context:
Network for host is dealing with host networking aspects whereas 
Networks for guests is dealing with the virtual networking aspect.
I experienced some confusion when I started working as a user with 
Kimchi/Ginger and I got some feedback from other users on this aspect as 
well.
The separation via different tabs is one possible option, looking 
forward for other ideas.

>
>
>>> Regards,
>>> Aline Manera
>>>
>>> On 21/08/2015 05:21, Jan Schneider wrote:
>>>> Hello,
>>>>
>>>> I started a Kimchi GUI Prototype with the Pencil tool.
>>>>
>>>> First topic I would like to discuss is the base navigation proposal 
>>>> shown below
>>>> 1) There is a horizontal main navigation area which contains 'Host' 
>>>> and 'Virtualization'. 'Containers' is an example for a future plugin.
>>>> 2) There is a vertical sub navigation area. Each item in the sub 
>>>> navigation has an icon and a label (1 or 2 lines).
>>>>
>>>> I am very interested in your feedback and would like to come to an 
>>>> agreement on this.
>>>>
>>>> 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
>>>> Please extract this file and read ./readme.txt
>>>> To view the Kimchi GUI Prototype open file ./htmlExport/index.html 
>>>> in your browser and navigate by clicking on navigation tabs/buttons.
>>>> If you want to edit the Kimchi GUI Prototype you will find further 
>>>> information in ./readme.txt
>>>>
>>>> Kind regards
>>>> Jan
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Alternate design with the same navigation
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Kimchi-devel mailing list
>>>> Kimchi-devel at ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/kimchi-devel
>>>
>>>
>>>
>>> _______________________________________________
>>> Kimchi-devel mailing list
>>> Kimchi-devel at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/kimchi-devel
>>
>>
>>
>> _______________________________________________
>> Kimchi-devel mailing list
>> Kimchi-devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/kimchi-devel
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/kimchi-devel/attachments/20150825/a88e5bb2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 9602 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/kimchi-devel/attachments/20150825/a88e5bb2/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 34925 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/kimchi-devel/attachments/20150825/a88e5bb2/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 35068 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/kimchi-devel/attachments/20150825/a88e5bb2/attachment-0002.png>