That would be very helpful if we would have a more modular layout. So individual pages can use individual libraries without loosing the other core definitions. One problem I see here is that the breadcrumbs, footer, header, etc. already use some of these old libraries. If we do not load them then this part of the layout will be destroyed (or at least modified).
And for the overall job, build and view pages this is even more complex. Here the layout is defined in core and cannot be changed easily. So if I want to show some nice trend charts I currently have no chance to provide a required library somewhere in the overall layout. But I think it is worth to invest something here as this can improve the look and feel of Jenkins quite easily without requiring to write a complete new application (see the Blue Ocean dilemma). All plugins could benefit from such a change without changing the overall architecture of the corresponding views. > Am 29.05.2019 um 13:05 schrieb Daniel Beck <[email protected]>: > > > >> On 28. May 2019, at 17:53, Matt Sicker <[email protected]> wrote: >> >> parallel set of layout tags > > We could also parameterize the regular l:layout. We already do something > similar for columns. > > l:html was quickly deprecated and integrated into l:layout. > > (Or perhaps we could move inclusion of libraries as an st:once / st:adjunct > on demand into the elements that use it, such as f:form? Then views that do > not use them will not have them.) > > > -- > 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/91060642-B405-4DD8-85CC-134E1B4410FB%40beckweb.net. > 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/2E88E44D-BE37-45FB-AFDA-046C969B8C9A%40gmail.com. For more options, visit https://groups.google.com/d/optout.
