eZ Community » Forums » Discussions » Changes to YUI and how it affects eZ...
expandshrink

Monday 08 September 2014 3:35:39 pm - 4 replies

» Read full blog post

Introduction

On August 29th Yahoo! announced that they are dropping further development of YUI, the javascript framework eZ Publish Platform have been using for several years now. In this blog post we will summarize the consensus we got with others during eZ summer camp, including changes we’ll do now and in the future.

Wednesday 10 September 2014 8:11:04 am

Thanks for clearing this up.

However, I'm curious as to why you now have decided to go for the "traditional" Symfony-controller based interfaces as apposed to the YUI based ones. Is this solely based on the discontinuation of YUI, or has it perhaps simply proven to be too time consuming to build the latter?

Thursday 11 September 2014 2:03:47 pm

The current code has both as it was made in iterations (admin part was started on before focus shifted to editorial part which is also partly the reason we have not shipped something sooner). So main point is to avoid creating new parts of the interface completely on top of YUI, implementation time has been an aspect but rather because a base was needed on several parts before the interface itself could be started on.

Wednesday 17 September 2014 9:41:53 am

 

However we will most likely prefer HTML5+ / ES6+ / CSS3+ features over use of jQuery which with time might get the same fate.

YUI was a perfect bad practise tool which was leading frontend developers to misunderstand their own job.

jQuery is a compatibility layer to avoid frontend developers becoming mad because of browsers-specific javascript implementations and is used as a base for many projects whereas YUI was just a crappy gadget just like GWT from Google.

The fate of a GUI cannot be compared with the fate of an API.

I hope you were kidding or, at least, I hope you wanted to write "jQueryUI"...

Modified on Wednesday 17 September 2014 9:43:53 am by Charles-Edouard Coste

Tuesday 18 November 2014 9:53:20 am

Charles: I was not, but it's not black and white for course, what I intended to say was we use jQuery on frontend but prefer native features when we can.

But yes I was serious about jQuery fading out over time: See blog posts from Javascript people about how jQuery forces you to write DOM oriented javascript which is inherently bad, see how Angular 2.0 (which is a major rewrite btw) does not plan to use jQuery at all, and additionally see how many of the jQuery features are by now or soon more or less replaceable by native features. I'm not saying you should drop jQuery if you like working with it, it's about how we build eZ Platform, and the importance of exposing ourselves to how the underlying native features work internally among the core devs.

Modified on Tuesday 18 November 2014 9:53:38 am by André R

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from