On Mon, Apr 20, 2015 at 02:41:07PM -0700, Gus Reiber wrote: > So I have let this thread go idle for over a month now, but over the > course of the last few weeks I have had some pretty interesting discussions > with both KK and Tom here inside CloudBees and now have some wireframes > that examine the item creation and configuration GUI in jenkins and looks > at ways to make the GUI a little more approachable for new users, while not > losing or significantly changing the existing screens' general approach to > collecting and displaying the configuration settings. > > I am going to post them here in the hopes that all of you interested in the > Jenkins GUI will toss in your comments and feedback. So, here we go....
Loving this! > <https://lh3.googleusercontent.com/-VQTnSplC6g0/VTVuEFAfhiI/AAAAAAAAAvs/rEGmmI4VP2w/s1600/freestyle_3.png> > Similarly for radio buttons. Here with the "Source Code Management", all is > the same as it ever was... Have you considered a dropdown instead of radio buttons? > <https://lh3.googleusercontent.com/-79DlKNvDDGk/VTVuxbx-JJI/AAAAAAAAAv8/2GEn0gan4Js/s1600/freestyle_5.png> > ...not all steps in a freestyle build however are just basic item > selections. Some are iterative step configurations that are particularly > defining of what the build process is going to do. (arguably, "Build > Triggers" is a similarly fundamental input category, so please argue > away.... ). Because of this importance, and iterative sub-process nature, I > am pulling the list of step operations out of its current pull-down list > and giving each a bit of visual meat. Beyond being decorative, this is > meant to help the user scan quickly for the process step he/she wants and > in a sense, wake the user up with a little reminder that this is likely to > be where the important choices need to be made. > > <https://lh3.googleusercontent.com/-Rbbgi2_94Ww/VTVwOiRCNVI/AAAAAAAAAwI/WMlqbIX2sDY/s1600/freestyle_6.png> > Once selected, the inputs for that new build step should be similarly > framed for emphasis and simplicity. The nesting of the layout should be > clearly communicating the subroutine nature of creating steps. I'd love a "(?)" button somewhere near the bottom right corner of the text are, with a popup listing what environment variables I can use in the shell script. (Ideally plugins that define new variables should be able to extend that list.) > <https://lh3.googleusercontent.com/--CdfQbVIfYU/VTVwwQJM0OI/AAAAAAAAAwQ/4wTYXNw60Es/s1600/freestyle_7.png> > Once created, the step, along with the existing steps is collapsed back to > its minimized form, helping to keep the workspace clean and to allow > more efficient dragging and reordering of step items (notice now the > collapsed panel, "Step: Execute shell script" above the newly re-opened add > step control). I have some doubts about reordering collapsed steps when they look the same ("Execute shell script"), but perhaps that's not common. I hope expanding will be instant (i.e. pure JavaScript/CSS without HTTP roundtrips), and that it will be possible to expand more than one step, in order to see the entire build process. > <https://lh3.googleusercontent.com/-9Tz4ic1EEIc/VTVxlAh6zII/AAAAAAAAAwY/9NnZLAhIYnM/s1600/freestyle_8.png> > After the steps are created, the "Post-Build Actions" employs the same, > "look at me" style GUI. I felt this guy should get extra weight as well, as > this is likely where your deployment action would happen. Does that really > make it more important than the trigger? Maybe. > > "Notifications" would be another boring control set, so I am not going to > bother showing it, but hopefully you get the idea. > > As always, feedback is something I love. These are excellent! Marius Gedminas -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. -- Avi Kivity -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20150421115239.GC12329%40platonas. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
