[UX] Jenkins controls compaction proposal

[oliver gondža]

One of the things that bothers me about Jenkins layout is the way some
buttons are placed on the page rather randomly. Namely: "Disable Project",
"Keep this build forever", "Mark this node temporarily offline", "Launch
slave agent" and friends. Things can get even worse when different plugins
contribute floatingBoxes with graphs making the buttons on the right edge
of the screen visually disappear.

What I propose[1] is moving all these icons to sidepannel, where controls
ware always supposed to be.

WDYT?

[1] https://github.com/jenkinsci/jenkins/pull/1703

--
oliver

[Marius Gedminas]

On Thu, May 28, 2015 at 10:03:03AM +0200, oliver gondža wrote:
> One of the things that bothers me about Jenkins layout is the way some
> buttons are placed on the page rather randomly. Namely: "Disable Project",
> "Keep this build forever", "Mark this node temporarily offline", "Launch
> slave agent" and friends. Things can get even worse when different plugins
> contribute floatingBoxes with graphs making the buttons on the right edge of
> the screen visually disappear.
>
> What I propose[1] is moving all these icons to sidepannel, where controls
> ware always supposed to be.
>
> WDYT?

Not a fan of the idea. The left sidebar is rather cluttered. Also,
clicking on a link is not as enjoyable as clicking on a large button.

> [1] https://github.com/jenkinsci/jenkins/pull/1703

Marius Gedminas
--
We did it for smallpox, we'll also win over on ISO 8859-1 ... ;-)
-- Markus Kuhn after eradicating one more ISO 8859-1 file from his disk

[domi]

I also don’t like it - the left navigation is a really cluttered menu which I think needs some more thinking too

/Domi

-- 
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visithttps://groups.google.com/d/msgid/jenkinsci-dev/20150528084041.GA3880%40platonas.
For more options, visit https://groups.google.com/d/optout.

[Ullrich Hafner]

I think removing these big ugly buttons is a good idea.

I’m not sure if the left sidebar is a good place. Wouldn’t it be better if such properties could be changed inline? E.g., In Jira you can change several issue properties inline (priority, component, etc.) by hovering over this property: then an edit icon is shown where one can change the value.

So the project page will then have several sections that show the important properties: project name, project description, enable state, etc. Each of these properties could then be changed by clicking on the selected property.

> --
> 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 jenkinsci-de...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/op.xzb5zdnrsbfict%40dhcp-10-40-2-219.brq.redhat.com.

[ogondza]

I am quite surprised how many people is dissatisfied with the sidepanel in current form. However, shell we ever do something about sidepanel, we will have to deal with it gracefully as plugins can contribute sidepanel tasks in several ways. Representing controls in an uniform way would be helpful actually (or at least something we will have to do anyway).

This PR comment might be related: https://github.com/jenkinsci/jenkins/pull/1703#issuecomment-103482968

--

oliver