Re: Important news regarding future YUI development
Guy Pyrzak <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.bugzilla.devel |
|---|---|
| Message-ID | <CAC7fAQdHaO2hNS=nokz0tRrkDtCxkjtgGJw5s6X9T7fFuFZoAg@mail.gmail.com> |
To help clarify. Mocha, qunit, and jasmine are all for testing JavaScript. Mockjax, Sinon would help with that. These are framework/library independent and could be used with yui3, bootstrap, or jquery ui. The fact that Bugzilla has JavaScript code that has no testing code associated with it ( other than selenium scripts) is something that should be considered and corrected. I agree that Angular, React, Polymer, ember, gulp, grunt or broccoli are not as worth while as they are frameworks or node.js dependent. -Guy On Monday, September 1, 2014, Byron Jones <[email protected]> wrote: > Gervase Markham wrote: > > I would certainly back a process where we stepped back and looked at > where things are now in client side web development best practice and > where they are going. This should be led by someone who had already > heard of Grunt, Broccoli, Gulp, Backbone, React, Ember, Polymer, > Angular, Mocha, Casper and Karma before reading the YUI announcement! (I > hadn't heard of most of them - perhaps that's just me, though.) > > most of those aren't relevant to bugzilla (task runner, client-side asset > builder, build system, testing, complete frameworks, ...). > > modern javascript web development generally doesn't mesh well with large > legacy applications, and i'm concerned that taking a step back at this > stage to evaluate a large rewrite of the UI would not result in timely > decision. > > our immediate need is to determine if we should continue the yui3 path, or > move to a jquery based widget library. > if we decide to move to jquery, then we should be talking about widget > libraries, not wholesale rewrites. > > -- > byron jones - :glob - bugzilla.mozilla.org team - > >