I pulled your branch and had a peek. Comments inline...
On 19/06/2014 00:45, Gus Reiber wrote:
Following Tom's lead, I am also starting to poke around at the Jenkins
UI.
My initial branch is here:
https://github.com/gusreiber/jenkins/tree/gustables
What I am most excited about in what Tom has done so far is replacing
the main table layout with responsive bootstrap columns.
In addition to making the UI line up a little better and be a little
neater, it offers the promise of better cross device usability, which
I think would be huge.
In my first stab here, I am looking at doing 2 things:
1) Give the Jenkins projects/build pages a bit of client-side richness
with minimal intrusion on the potentially customized or plugin
modified DOM that might live within that main table.
I have started with this JQuery
plugin: http://www.datatables.net/examples/styling/bootstrap.html
It has the nice feature of accepting the rendered static table as its
datasource and then adds a host of client-side magics: filtering,
sorting, grouping, and column switching resizing and pegging. I don't
see this as being particularly revolutionary in terms of UI/UX, but so
far anyway, its insertion seems to be going smoothly and for users
with big job lists, rich sorting tools seems like it could be a nice win.
+s:
* I think it looks a LOT better than the original project view tabs.
* Love that more tables are gone and replaced with divs
-s/risks:
* Any side effects on other page?
* Anything we need to be careful of wrt plugins?
* Creates a hard dependency on jQuery. Maybe that's not such a
biggie, but one we need to watch.
2) I find the Jenkins action list (the list of hyperlinks shown in the
left column above the build queue) a little jarring, in that all the
links are given equal display weight despite what is often radically
different amounts of functional utility. As an example configuring the
job and viewing the console out (two things I do a good amount), are
the same simple blue links that configuring roles is (something I
never do). Compounding that a bit is the fact that those links are
always contextual, namely, depending on your view, that list changes
around quite a bit.
As a possible remedy to that bit of awkwardness, I am looking at
pulling some of the 'action' link list items out and displaying them
in a global toolbar sort of context. Jenkins Management, in particular
seems like it really should be clearly separated as a global set of
actions, and not bound to any particular build or custom view.
At the moment, I am merely doing a proof of concept examination of how
the link list gets generated, but I would love to get community
feedback as to whether or not it does make sense to separate out a
portion of the Jenkins actions, splitting the contextual from the
global and the high-use/high-value actions from necessary but
tangential or highly specialized actions.
The navigation is something that others have id'd as being
confusing/awkward, so I think it's grat to start a conversation on
this. I do think, however, that we should probably split it into a
separate discussion.
I think it makes sense to make better use of the top navbar for global
stuff along the lines you've shown here. From Daniel's comments though,
it's clear we need to work out what can and can't go there if this
approach is followed. I wonder too... for global management type stuff
you don't use too often, how about providing access to it through a
settings type icon (a spanner/cog type icon e.g. from Github
http://goo.gl/Y7wRBW) in the top right (to the left of the search),
which is an approach many apps follow?
Can someone explain to me why are the "People" and "Credentials" nav
items not inside "Manage Jenkins"?
I think it would be great to draw a app nav map as things stand today
and from that, hopefully we could extract some patterns.
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
