@Tom, divs, css and tab it's cool, but as not UI developer i will expect "building blocks" that will allow me just to use form and databinding. This will also allow enhance/fix problems only in this block that will automatically apply to other places.
More thoughts. - I think that other UI problem is maintainers/developers programming knowledge and lack of good documentation with good variants for them. After INFRA changes i hope people will finally be able to start enhancing documentation. Many plugins configurations are based on checkboxes, even -ETOOMANYCHECKBOXES in ui that leads to mess in UI and code. Maintainers are not bothering to ask any experienced jenkins devs to review their changes. Some PRs after good review ends with only few lines of change instead of many new classes and changes. Also jenkinsci plugin hosting for any jenkins plugin looks like a trash can that ends with bad end-user experience in jenkins, i see many jenkins installations and many times i'm wasting time searching what plugin provided what configuration (because help files not created, or configuration names are the same, for example, maven builders from artifactory, maven and other plugins). (Should we create injected test for help files that will fail build?) - Slide, I think email-ext absorbed many issues at once. a) It obvious that everybody want configure job steps in any order and sending emails (or do any action) in any step. If freestyle job had had no such limitations and allow to reuse publishers, email-ext would have no implemented mix of cases in publisher (default template, for example, may exist in JobProperty). b) AFAIR email-ext needs some better forms for some ui configurations c) Some forms has very huge borders, intends, margins, etc. (repeatable-hetero-list?) d) conditionals that are not provided in core and plugins implementing them and using i.e. flexible-publish loses different integrations because it not core. This all pure API of core/freestyle that need to be enhanced and plugin developers inventing difficult code -> UI. Wait, but workflow-plugin should resolve this issues? Do we need UI configuration now at all or should we configure jobs with coding in groovy workflow/DSL? -- 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/d3943d7e-4648-41af-9160-ca87b5825700%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
