On Friday, September 25, 2015 at 7:21:34 AM UTC+1, Kohsuke Kawaguchi wrote: > > As you say, for compatibility reasons I don't think we can remove them. > > But that "brand-new way of doing frontend development" that I mentioned > touches a related space. It borrows a lot of tooling from NodeJS, such as > writing JavaScript in CommonJS modules, using JavaScript template libraries > like handlebar, etc. My hope is that that provides a different way of > building pages that require high degree of interactivity. > > The workflow stage view > <http://softwaretest.jp/files/2015/01/CLO-DS-Enterprise-chart.png> is > built using this technology. I'll let Tom chime in to talk more about this. >
As far as stapler and jelly are concerned, I'd say the following: 1. We're probably stuck with it. 2. Even though there's much about them that I think sucks, I also think they have some very important qualities that have contributed greatly towards making Jenkins as popular as it is. The provide an easy way for people (often with little or no UI skills) to get going with Jenkins and create their first plugin that can contribute elements to the Jenkins UI. So, we shouldn't throw out the baby with the bathwater. I suppose the best place to start wrt the newer methodologies we've been adopting is to take a look at the following docs: - jenkins-js-modules <https://github.com/tfennelly/jenkins-js-modules>: A very simple JavaScript bundle loader tailored to the Jenkins "environment". The main reason I point to this is because the docs there try to explain the problems/challenges (+ there's a slide dec which people might find useful). - jenkins-js-builder <https://github.com/tfennelly/jenkins-js-builder>: An NPM module to tries to simplify the process of working with this stuff. Some docs there too. - jenkins-js-test <https://github.com/tfennelly/jenkins-js-test>: No prices for guessing what this is about. Builds on Jasmine and jsdom, making them a bit easier to use together. But, people can always use whatever they want. PLEASE note that we are not proposing to make any of this a mandatory part of learning or working with Jenkins. If you are happy with Stapler+Jelly and don't want to be bothered with any of this, then keep rock'n !! See this FAQ <https://github.com/tfennelly/jenkins-js-modules/blob/master/FAQs.md#do-i-really-need-to-learn-all-this-new-stuff> . -- 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/7d33e71e-b2be-43b0-8a55-cdd1e46d0cb4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
