> I'm currently writing a simple demo app and would like to call a > script to render a node based on a mixin. It's currently only possible > to use register the script for the primary node type or to use > the special sling:resourceType property. > > What do you think about extending this to mixins? For instance, you could > add a mixin to an nt:folder which adds additional data to this folder. If > the mixin is available the folder is rendered differently. > I'm not sure if this is a good idea, therefore I would like to hear your > input on this. > > Supporting mixins here of course creates the problem if a node has more > than one mixin etc. I could also argue if I'm already adding a mixin to the > node, i can also add the sling:resourceType mixin as well. i think if the resolution rules are well defined for the nodetype hierarchy of a node, this is a good feature. this is not only cool for mixins but also for extended nodetypes. eg, when my:File extends nt:file i want the default nt:file script unless i create one for my:File.
-- toby
