Hey Marius, Thanks for your awesome feedback. You express a concern about the delays of server round-trips, so before I take your comments in order, I want to say, I am envisioning these changes not actually requiring much functional change to the existing config/create form. Mostly these are DOM layout and CSS changes only (plus a little JS for page effects). The big thing with that is that these changes are meant to avoid changes to the forms data model, the inputs data binding mechanism, and the page loading sequence. ...so any showing and hiding I am showing here is just the superficial sort, where the dom elements are statically loaded up front, same as they ever were. For better or worse, I am just changing the display styles on them.
- *Dropdown menus:* So for choosing your SCM system, I don't like the compactness of a dropdown because I think a user wants to see the options available for this important choice up front. I suspect in many cases a particular company or group will always use the same SCM system, so equally important might be the ability to set a default for the Jenkins Master as a whole so you don't need to answer this question over and over. ...but if you do often switch between SCM, the SCM you are using is probably a significant context indication of what sort of job you are creating. ...let me know if that rings true. We pretty much always use Git, here. I haven't always used Git, but I can't remember when I worked at an organization that used switched SCM systems from project to project (or ever, honestly). - *Missing Question marks: *Bad GUS! Sorry, I just didn't add them in into my mock-ups. I am envisioning that they wouldn't change all that much - *Collapsed sections look the same: *Yeah, for that to work well, I would need to find some way to bubble up differences between the steps even when collapsed. At the moment, I am lacking a good solution. - *Will it be slow:* I hope not. See above about my plan to mostly not change the page-load dynamics On Tue, Apr 21, 2015 at 4:52 AM, Marius Gedminas <[email protected]> wrote: > 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 a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/6BdWZt35dTQ/unsubscribe. > To unsubscribe from this group and all its topics, 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. > -- 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/CAOcHHXxMGNy26vLAKDpac6xLa1VmXM%3D8q7urhSPROBFbZ4cwwg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
