On 4.12.2012 17:05, Aaron Weitekamp wrote:
On 12/04/2012 10:27 AM, Tzu-Mainn Chen wrote:
>
> Just to address this particular question - in my opinion, it is
> absolutely a navigation problem. I agree that the table widget is
> nice, but that fixes specific pages. Jaromir's point (which I agree
> with) is that it's hard to even navigate to that specific page right
> now. If a first time user started up Conductor, he'd have no
> instinctive way to know where to manage providers.
>
> Mainn
>
Yes, navigation is broken, but just fixing the site map is not a very
difficult problem.
I have to disagree, It is really huge problem. Once you change
sitemap,
you need to have unified views all across the app. We even don't have
views for each and every item from the new navigation map. And even more
it is not easy do decide, how should the navigation look like and what
concept to keep to make it as easy as possible for the most user types
(personas).
Jaromír's wireframes address a deeper issue which is solved by
leveraging a widget model (soon to be part of Converge-ui/Alchemy?[1]).
Whole table
concepts should be part of Alchemy in the future. The goal
is to have one concept specified in the library and use it all across
the app, not to repeat ourselves and not to give opportunity to
implement each view differently. But what Katello does is not
coordinated with Aeolus right now and partly it is little bit different
from what will we need in the future. But this is longer term goal.
Along the way, as my post suggests, we're able to simplify
navigation.
By "action table" you can simplify navigation. It might help
with some
use cases, but they are not significantly important as others right now
and furthermore in many cases we even can't use batch functions in many
cases. Anyway it's not a problem to add them to the concept I suggested.
-- Jarda
--
Jaromír Coufal
Interaction Designer
Red Hat Czech s.r.o.
Mobile: +420 724 595 508
E-mail: jcoufal(a)redhat.com
IRC: jcoufal at #cloudforms-ui, #aeolus, #brno