(replies inline) On Thursday, May 19, 2016 at 6:56:31 PM UTC+10, Samat Davletshin wrote: > > > 3. Tom was proposing a step by step new job creation. Currently it would > contain only 2 steps - job name and job type. "Next, next" process would be > more intuitive and quicker to understand what to do. That may be done with > only JavaScript and CSS by hiding and showing parts. Tom liked this idea. >
I think this makes sense. > > So I am not saying that I do not want to do anything except JavaScript and > CSS. It is just may be better to start from more manageable surface and > then move deeper. What do you think? Kirill, Michael? > Much of the work now happens in javascript so I don't think there is a problem with that unless you really dislike javascript ;) > > Then about job validation. I personally think that there are now two ways > of improvements that could be a good place for me to start at: > 1. Job name is checked for validity only when it loses focus. I think that > should not be hard to display a warning message right after the user types > in an invalid character > Invalid character is one, but validating the whole job name in the background (for duplicates) could be good. > 2. It is possible to submit job creating form with an invalid name. It > takes user to unnecessary empty page with error message forcing to click > back button. I tried to fix it yesterday but had difficulties with the GET > request to check the name. Apparently I cannot block form submission with > IF statement as it is done with empty name and no job type selected. So the > validation is better happen on server side? If so how should I approach > prevention of job submittion? > If #1 above is addressed, this would be less of an issue right? > > > Finally about job configuration page: > 1. Changing help information probably stays now as in proposal. > 2. More intuitive configuration page. There are now a lot of improvements > in 2.0. However, I think there are some new approaches to try such as > accordion based configuration. This part is very open to discussions and > feedback. > Yes it is a bit different now, it uses a scrollspy to combine scrolling with tabs (http://www.w3schools.com/bootstrap/bootstrap_scrollspy.asp). I am not sure about accordion, would be interested in what Kirill thinks on this. I think its a big improvement on how it was, for sure, but one thing that keeps irritating me is the text editor for freestyle or pipeline - isn't big enough and I can't resize it. > > > I would love to hear any feedback. > Kirill, Michael if you think it is reasonable to talk I would be glad to > do so and get your feedback almost any time. > -- 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-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2e52807d-8362-495b-a380-45727265b942%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
