Forums

forgotten to mention, the render() will be handled separately. the render code will be splitted to renderUI, bindUI, and syncUI in case by case basis. some transformation will be done, e.g. an id with # will be converted back to the YUI2 style.

the whole objective is to YUI2 features with YUI3 in a more YUI3-ish style.

it's just an experimental idea and i dare not to say it is good. There are two issues:
1. Y.mix to support binding
2. should we/how do we wrap YUI2 with YUI3

re. 1, i just got a new usage that is to do some kind of pseudo AOP to do sth before and after any function. e.g. say the Y.mix is enhanced with an additional argument that take a function to process the function before it is assigned to the receiver, e.g.

function(prop, r, s){
if (Y.Lang.isFunction(prop) ){
return Y.bind( prop, r._delegate)
}
return prop;
}

one usage is to add logging before the fn is called, e.g.
function(prop, r, s){
if (Y.Lang.isFunction(prop) ){
return function() {
Y.log( "target: " + r._delegate + ", function: " + prop + ", arguments: " + arguments, "debug", "Y.mix injected logger")
Y.bind( prop, r._delegate)
}
}
return prop;
}

re. 2, the reasons/benefits to do in this way:

• i want to minimize and isolate any YUI2 style code, and ultimately remove them all
• when we need to implement more complex features, such as a datatable that is both editable and support customizing columns, it is the best way to subclass the table in YUI2. i'm not sure if it is a good idea or doable to create a YUI3 class that extend a YUI2 class, but i would prefer the subclass code to use YUI3 style.
• we could utilize the attribute and event of Base for our own function on top of YUI2 API easier
• for debugging, unless the console log is ported for YUI2, i indeed think it's easier to log and trace issues in YUI3. if you run with a debugger, you can step on the code anyway. i suppose you mean, if there are some kind of YUI3 attribute to YUI2 mapping, then it introduces a layer of complexity. it's true. I use Y.log to log anything with Y.JSON.stringify to log anything.

i dare not to say its a good approach. just to evolve an idea.