Thanx for the comments. I really do understand all this concepts, I'm maybe 
not very into patterns how to use specific dirrectives (and sorry but I'm 
still seeing too many examples showing to my mind wrong patterns in this 
regard), but I do understand (conceptually) the concepts behind Angular 
system (and as I mentioned in some of the posts a lot of them match the 
philosophy of our current code base, which was the main reason for me to 
explore Angular).

What my problem is, is the fact that (probably) all provided directives are 
documented and show cased as attribute dirrectives (some have even quirks 
specific to attribute represenation, showcased on ng-repeat-start and 
ng-repeat-end, as element directive wouldn't need this at all). Though I'm 
failing to convince you, to me element style syntax (although being more 
verbous) is superior to attribute style syntax, be it for templating 
purposes or be it for any other purpose directive is used for.

Currently I have a situation where I have a choice to translate all my code 
into Angular suggested syntax (attributes) or implement few directives that 
just reimplement our templating. The only semi good thing about first 
approach is "it matches Angular way", other then that it only has downsides 
for our code base (to my opinion). So I think I'll go with implementing 
those directives instead of trying to convince you to iplement them for me 
:P. There still few conceptual differences in rendering (directive 
processing) between the two technologies that I will have to overcome but I 
think it's worth a try as it is much less effort. So I think there will be 
more "very very very interesting" posts on the way ;)

Off topic: as you touched directives in general in your posts (my personal 
opinion) - the problem for people to "get" directives correctly right away 
is in the fact that they solve too many problem spaces, it feels too low 
level for most high level tasks I get from business - on day to day basis 
I'm mostly writing components and directives doesn't feel like something I 
would write on daily basis for that purpose, and dumping it all in the view 
logic is not what I'm trying to achieve.

In any case thanx for your effort to help, more coming soon ;)

-- 
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.

Reply via email to