Yes I agree, let's do this!. It might even get some more front end developers into the project if they find the tooling somewhat familiar.
I just misunderstood Tom's proposal at first :) /B On Mon, Sep 7, 2015 at 3:46 PM, Kohsuke Kawaguchi <[email protected]> wrote: > I want to second this proposal as a great progress for us. It reuses a lot > of existing projects and tools from NodeJS, and allow small modules of > JavaScripts to refer to each other more easily and in a "standard" fashion, > compared to adjuncts. > > I see this as a key step to enable extensibility in the frontend. > > 2015-09-05 5:28 GMT-07:00 Tom Fennelly <[email protected]>: > >> There are a few changes being proposed/planned for Jenkins Core that will >> require some UI changes e.g.: >> >> 1. Unbundling plugins. See dev list thread >> <https://groups.google.com/forum/?hl=en#!topic/jenkinsci-dev/kRobm-cxFw8>. >> The UI changes here would be a new "Plugin Selection Wizard" to help new >> users of Jenkins get up and running quickly, filling the gap left after >> removing the currently bundled plugins. >> 2. Hopefully making improvement to the config pages ala what KK and >> Gus Reiber are doing on the config-ui-changes branch >> <https://github.com/jenkinsci/jenkins/tree/config-ui-changes>. >> >> In order to implement these changes as hoped, we're going to need to use >> client-side JavaScript (better UX etc). At the moment, in Jenkins, >> JavaScript is a bit of a mess. It would be nice to start addressing this >> problem in some way under the assumption that, going forward, we can make >> more use of client-side JS for better UX, but do it in a more maintainable >> way (Vs everything being in hudson-behavior.js). >> >> Some of us at CloudBees have been developing and using some patterns and >> tools to help build Jenkins plugins that have GUI elements that make better >> use of modularized JavaScript (using CommonJS modules etc). We think it has >> worked quite well and would be keen to reuse some of the same techniques >> and tools in Jenkins core if possible. >> >> One of the tools we developed to help us assemble these JavaScript >> components is a build time utility we call jenkins-js-builder >> <https://github.com/tfennelly/jenkins-js-builder>. It's an NPM utility >> for assembling CommonJS module "bundles", built on Gulp >> <http://gulpjs.com/>, Browserify <http://browserify.org/> and more. >> >> My question .... would there be community objection to introducing >> something like this into Jenkins core? We're not trying to suggest it as a >> silver bullet for all JS related issues, but we do think it would help >> improve things. >> >> Regards, >> >> T. >> >> -- >> 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/9f36b348-aacc-4fbc-85f6-ea6761e9cb22%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/9f36b348-aacc-4fbc-85f6-ea6761e9cb22%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Kohsuke Kawaguchi > > -- > 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/CAN4CQ4xr_YG%3DDPZV3nkRbNivb-xuKo7CSO%3Dyb8xLSNNqLHspTQ%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xr_YG%3DDPZV3nkRbNivb-xuKo7CSO%3Dyb8xLSNNqLHspTQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Robert Sandell *Software Engineer* *CloudBees Inc.* -- 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/CALzHZS1FSTivYJ0BGZpPzL%3DK%2BS-kXOGe-m8hpuz0xOVFH6PNSg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
