Has anyone experimented with porting Aaron's behaviors <http://www.clientcide.com/code-releases/bootstrap-3-0-clientcide-3-1-0-behavior-1-3-0-and-more-behaviors-1-0-8/> to HTML5 custom tags <http://www.html5rocks.com/en/tutorials/webcomponents/customelements/>?
Our toolset targets business 'power users' who are not js experts, but do learn basic markup. I've found behaviors are a very powerful tool in enabling this user base to achieve things that normally require 'traditional' coding. However, we also have client shops with JS expertise (usually jQuery), and I am weighing porting our custom behaviors to HTML5 custom tags, and allowing JS devs to create new custom tags following a similar structure using jQuery, instead of requiring MooTools. (I continue to love Moo; just trying to leverage existing knowledge bases out there. I'm in an enviable position of generally dictating the browser to our user base, so I get to ensure an evergreen <http://tomdale.net/2013/05/evergreen-browsers/> browser.) Anyway, just wondering if anyone on this list has weighed pros and cons of such an approach, of if you might be interested if I just put this in GIT for joint development? -- --- You received this message because you are subscribed to the Google Groups "MooTools Users" 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.
