ask and you shall receive. ; )
you can either comment on the screenshot attached to
or svn up to rev3061 and
play around with it. currently, since this *is* a prototype, i haven't
done anything for autogroups or resources groups yet. i'm open to any
and all ideas on what each summary tab should show, including the one
that i took a screenshot of in RHQ-1575.
John Mazzitelli wrote:
My concern with another top level tab is the width of this. The width
of the resource view is too long as it is right now (IMO). Adding
*another* tab makes it wider no? At least, it widens the number of
tabs. Guess I'd have to see it.
Having a summary landing page sounds like the best idea yet! This way,
the events mica icon/tab can be hidden from view when needed (which
helps my first point about keeping the # of tabs down), adds more
similarity to emb jopr (not that that matters all that much, but, its
a nice touch) plus like you said its a good fit for the timeline
(thus, it doesn't seem like we shoe horned it in somewhere). Of
course, I reserve final judgment until I see a prototype :)
Joseph Marques wrote:
> i still like the separate tab idea better. i want to emphasize again
> that the timeline view isn't just events, it's for display data from
> multiple subsystems simultaneously. the timeline view didn't feel
> right when it lived as a child under the monitor tab, and i guess it
> doesn't feel right living as a child under the events tab either.
>
> svn up and take a look at the resource browser; it's much cleaner
> right now. since only a few resources actually implement the event
> facet, the 'e' icon doesn't show up very often, which is a huge
> benefit to the "mica" icons in the first place.
>
> how about an entirely different strategy. greg, you know how we were
> thinking of mimicking the embedded console by providing a landing
> page. why don't we have a "Summary" tab that provides quick info
> about the resource, but where the timeline view will also live. this
> way, we'll 1) have consistent navigation for subcategories (and
> subsubcategories) because their default click action from the nav
> tree would hit this new summary tab, and 2) we'll have a perfect spot
> for the timeline page which due to the fact that it encompasses data
> from all different subsystems is a rather good fit for a summary view.
>
> John Mazzitelli wrote:
>> > My suggestion is don't hide the events tab. Why not just disable
>> the "history" subtab under events
>> > for resources that don't have events... and default the views to
>> the timeline?
>>
>> That sounds good.
>> _______________________________________________
>> jopr-dev mailing list
>> jopr-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jopr-dev
>
> _______________________________________________
> jopr-dev mailing list
> jopr-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jopr-dev
_______________________________________________
jopr-dev mailing list
jopr-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jopr-dev