I may have missed something but doesn't the controller keep the scope for each label field pair. This needs no id scheme as the controller is in effect one whole scope and 'id' This is even before talking about the child relationships you can have and I'm not sure it ca help in your scenario.
Its a feature that services are kind of available to any controller. I don't see any point in enforcing some kind of Singleton pattern here. Just write ONE service for each kind of well domain maybe. Rereading your problem maybe I think you are asking to talk between controllers ? if this is the case then make a parent and child relationship. But cant you use a named method in a single controller that reffers to a single 'pair' so that within that scope one pair can see what another pair is doing and influence each other etc. I don't understand the way you use the word directive here maybe my understanding of them is lacking. -- 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.
