Hi team,
I was about to integrate Ginger sidebar mockup that I’ve sent but it
occurred to me that is still impossible to work with this sidebar
without performing some changes in Wok JS due to user access roles,
unless all tabs in administration are under the same rule. Right now
the tab-ext.xml lists all tabs with the same roles:
<access role="admin" mode="admin" />
<access role="user" mode="none" />
Should I keep this role to just the “Administration” tab and check
other pages by the capabilities?
I'd say to keep the configuration only for Administration tab and we can
discuss more about Ginger authorization later.
As per configuration:
<access role="admin" mode="admin" />
<access role="user" mode="none" />
The Administration tab should not be loaded for a normal user. It will
be visible and accessible only for admin.
Is that the right approach? Maybe not. As Chandra said in the other
email, maybe it is better to let a normal user has a read-only for some
features.
But I don't think we should change that right now.
Changing the layout first is better and then we start a new discussion
related to authorization levels on Ginger community.
Regards,
Samuel
*From:*Aline Manera [mailto:alinefm@linux.vnet.ibm.com]
*Sent:* quinta-feira, 21 de julho de 2016 14:24
*To:* Samuel Henrique De Oliveira Guimaraes
<samuel.guimaraes(a)eldorado.org.br>; Daniel Henrique Barboza
<dhbarboza82(a)gmail.com>; kimchi-devel(a)ovirt.org
*Subject:* Re: [Kimchi-devel] [RFC] Wok / Ginger sidebar
On 07/21/2016 01:15 PM, Samuel Henrique De Oliveira Guimaraes wrote:
I’m not saying we will remove the tab-ext.xml, what I meant is that:
1-Move the tabs for network, storage and system services (and
firmware and other panels as well) as nested tags inside the
administration tab in the tab-ext.xml and use ginger.capabilities
object to hide them once the user lands on the administration tab.
OR
2-Keep only administration tab in tab-ext.xml and insert all
available sidebar options as static HTML elements but still use
ginger.capabilities to hide unavailable options.
Options 1 requires minor changes in wok.main.js inside the navbar
functions. Option 2 would require same amount of work on Wok but
would keep functions exclusive to Ginger.
I see Option 1 requiring changes on Wok. Option 2 seems simpler to be
implemented as it only involves changes on Ginger.
Samuel
*From:*Aline Manera [mailto:alinefm@linux.vnet.ibm.com]
*Sent:* quarta-feira, 20 de julho de 2016 11:34
*To:* Samuel Henrique De Oliveira Guimaraes
<samuel.guimaraes(a)eldorado.org.br>
<mailto:samuel.guimaraes@eldorado.org.br>; Daniel Henrique Barboza
<dhbarboza82(a)gmail.com> <mailto:dhbarboza82@gmail.com>;
kimchi-devel(a)ovirt.org <mailto:kimchi-devel@ovirt.org>
*Subject:* Re: [Kimchi-devel] [RFC] Wok / Ginger sidebar
Hi Samuel,
There is no way to remove the tab-ext.xml file.
It is used by wok to load the plugins and changing/removing them
will affect all plugins and we do not want that.
The tab-ext.xml file needs to be update to only contain one tab
"Administration".
That tab will be related to one HTML file which will create the
sidebar menu created according to Ginger needs.
On 07/13/2016 12:18 PM, Samuel Henrique De Oliveira Guimaraes wrote:
Sure. I’m considering that this will be a huge amount of work
because we’ll have to look up for the capabilities before
rendering the main Ginger landing page OR we put the Ginger
panels as static elements instead of using tab-ext.xml. Either
way we would have to create a single .html.tmpl file for each
panel and remove the accordions and maybe move or create new
JS functions to initialize them.
Samuel
*From:*kimchi-devel-bounces@ovirt.org
<mailto:kimchi-devel-bounces@ovirt.org>
[mailto:kimchi-devel-bounces@ovirt.org] *On Behalf Of *Daniel
Henrique Barboza
*Sent:* quarta-feira, 13 de julho de 2016 10:29
*To:* kimchi-devel(a)ovirt.org <mailto:kimchi-devel@ovirt.org>
*Subject:* Re: [Kimchi-devel] [RFC] Wok / Ginger sidebar
Looks good Samuel
Just a reminder: make sure to also consider that there are
some features
that will not be available at a given time in the host but
should be considered
in this design too. In your screenshot we're missing the Power
Management and the Firmware Update features, for example, probably
because you do not have tuned-adm and WoK isn't running in a Power
system.
Daniel
On 07/13/2016 10:13 AM, Aline Manera wrote:
Looks really good for me!
+1
On 07/12/2016 05:54 PM, Samuel Henrique De Oliveira
Guimaraes wrote:
Created a new variation with a sticky fixed floating
sidebar and single contente on the page. I also
removed the accordion because if we are going to
display only one item per page, we shouldn’t have
hidden elements on the page.
Samuel
*From:*Aline Manera [mailto:alinefm@linux.vnet.ibm.com]
*Sent:* terça-feira, 12 de julho de 2016 09:53
*To:* Samuel Henrique De Oliveira Guimaraes
<samuel.guimaraes(a)eldorado.org.br>
<mailto:samuel.guimaraes@eldorado.org.br>;
kimchi-devel(a)ovirt.org <mailto:kimchi-devel@ovirt.org>
*Subject:* Re: [Kimchi-devel] [RFC] Wok / Ginger sidebar
Hi Samuel,
I'd say to keep the menu always visible in a left
panel/menu and with a default first view when user
enters on Administration tab.
Regards,
Aline Manera
On 07/11/2016 06:12 PM, Samuel Henrique De Oliveira
Guimaraes wrote:
Hi team,
Based on the feedback I’ve created a new mockup
putting all Ginger features in a floating vertical
menu (I’ve only put some of them but you’ll get
the idea).
Samuel
*From:*kimchi-devel-bounces@ovirt.org
<mailto:kimchi-devel-bounces@ovirt.org>
[mailto:kimchi-devel-bounces@ovirt.org] *On Behalf
Of *Chandra Shekhar Reddy Potula
*Sent:* quinta-feira, 7 de julho de 2016 09:50
*To:* kimchi-devel(a)ovirt.org
<mailto:kimchi-devel@ovirt.org>
*Subject:* Re: [Kimchi-devel] [RFC] Wok / Ginger
sidebar
Hi Samuel,
First of all thanks for your extensive
investigation on various possibilities in front of
us !!!
I personally liked the option
https://www.sitepoint.com/ which would be ideal to
have with possibly 3 level navigation.
Nevertheless, let us start with having side pane
to provide immediate relief with the way proposed
in the figures ginger_sidebar_1.png and
ginger_storage_2.png and eventually make it more
better if it is too complex doing all of it ones.
I agree with Daniel recommendation for the for
ginger_sidebar*.png, ie. have one second level tab
for now and all the functionalities go under the
side pane which would be enabler in future some
thing similar to your proposal of
https://www.sitepoint.com/
Thanks and Regards
Chandra
On 7/5/16 12:32 AM, Samuel Henrique De Oliveira
Guimaraes wrote:
Hi team,
We currently have an issue with
Ginger/Gingerbase navigation bar in small
screen resolutions and we also have huge
tables in System Services page. Since working
on the navigation bar involves editing Wok
styles, I’m sending this e-mail to Wok mailing
list instead of Ginger group.
I looked for successful combinations of
sidebar + horizontal navigation bars and so
far I couldn’t find any example that would
exactly fit with Wok and its plugins. The
majority of examples I’m listing below are
very good with traditional pages with deep
subcategories and the navigation bars can work
as sitemaps and replace breadcrumbs:
·http://www.worldwildlife.org/ -
https://vimeo.com/166812605
·https://www.theguardian.com/us -
https://vimeo.com/166812599
·https://next.ft.com/fastft -
https://vimeo.com/166812597
Wok currently has two navigation levels.
Kimchi doesn’t have multiple sections but
Ginger and Gingerbase uses collapsible panel
groups to separate sections that could be
third level elements on a sidebar. This was
already discussed when we moved some features
from Ginger to Gingerbase but I think we could
achieve a functional sidebar with up to three
levels without using a “landing page” for
second-level elements.
In the attached screenshots ginger_sidebar1
and ginger_sidebar2 are mockups for an
off-canvas menu that would slide the main
content and hide itself once an option is
clicked. It would also hide the other panel
accordions. Here are two off-canvas menu in
action:
·http://codepen.io/SitePoint/full/uIemr/
·https://codepen.io/benske/full/cxrta/
Since this would require a change in Wok tabs
and ginger/gingerbase tab-ext.xml, I think we
could implement something entirely different
that would with Wok and all plugins. This site
menu only have first-level options on the
sidebar but I think we could add collapsible
links like a tree-table menu:
https://www.sitepoint.com/
In addition to the sidebar, we could put a
search/filter input on the top that would
allow the user to type the desired option and
show its position on the menu. Please take a
look at the remaining attached screenshots. I
did one variation with the content aligned to
the center and another one aligned to the left.
Regards,
Samuel
_______________________________________________
Kimchi-devel mailing list
Kimchi-devel(a)ovirt.org
<mailto:Kimchi-devel@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/kimchi-devel
_______________________________________________
Kimchi-devel mailing list
Kimchi-devel(a)ovirt.org <mailto:Kimchi-devel@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/kimchi-devel
_______________________________________________
Kimchi-devel mailing list
Kimchi-devel(a)ovirt.org <mailto:Kimchi-devel@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/kimchi-devel
_______________________________________________
Kimchi-devel mailing list
Kimchi-devel(a)ovirt.org <mailto:Kimchi-devel@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/kimchi-devel
_______________________________________________
Kimchi-devel mailing list
Kimchi-devel(a)ovirt.org <mailto:Kimchi-devel@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/kimchi-devel