On Tuesday, June 3, 2014 10:48:10 PM UTC+10, Tom Fennelly wrote: > > > That said... I personally don't think that matters all that much for the > core Jenkins UI. I think no matter what we do with the core UI, there > would be a good argument to be made for staying away from such > frameworks, in which case we'd just perform bog standard ajax rpc calls > from the UI. Where it might cause headaches is for people building > their own custom interfaces on the Jenkins API and they want to use > something like AngularJS ($resource + other bells and whistles). I > think this was the point that Tyler was making. > > > I actually think using angular or anything else would cause more problems for people wanting to extend the UI than not using it (they may want a different framework altogether which just won't work). It is a fast changing fashion-driven landscape - so nothing you pick will be liked in about 6 months time, and I am sure will be regretted anyway ;)
-- 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]. For more options, visit https://groups.google.com/d/optout.
