Hi all, Another conceptual topic that I would like to clarify on how it's done in angular.
So for now in most tutorials I see pepole using inline event handlers and in documentation I see loads of ngEventName directives.This part quite confuses me - in a framework with such a nice clear separation of concerns you suddenly have this ugly coupling, plus lack the concept to encapsulate that concern (again appologize if it is there and I'm just not digging deep enough). As I mentioned in the other post I'm trying to evaluate AngularJs as a platform for our web servers, while we have own set of libraries and home grown templating/view rendering framework. We do have a concept of Behavior which I believe is quite benefitial. Behavior is a class representing logic to listen UI events and translate them into actions on presentation model (like selecting item, invoking button action, etc.). You can reuse the class between templates as there are lots of generic behaviors (drop down, tooltip, d&d, etc.), you can store some state on behavior (like mouse delta for drag and drop), can access global event scope and listen to stuff like resize, scroll, mousedown (to close drop down), mousemove (for d&d), you can assign live listeners that are not bound to concrete instances, etc. I'm really failing to see the concept for this in AngularJS, some pointers or comments would be appreciated. Thanx in advance, Bohdan -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
