title: Should a directive talk to a controller in Angular JS?
body: <p>I have been watching the videos by John Linquist and in one video he gives this as an example:</p>
  
  <pre><code>var app = angular.module('twitterApp', [])
  
  app.controller("AppCtrl", function ($scope) {
     $scope.loadMoreTweets = function () {
        alert("Loading tweets!");
     }
  }
  
  app.directive("enter", function() {
     return function (scope, element, attrs) {
        element.bind("mouseenter", function () {
           scope.LoadMoreTweets();
        })
     }
  }
  </code></pre>
  
  <p>One thing I am wondering about is should the directive in this example talk back to the controller or would it be a better programming practice to create a service and then have the directive talk to a service? I guess I am still not sure if it is common practices for directives to talk to controllers in this way. </p>
  
  <p><a href="http://www.youtube.com/watch?v=LJmZaxuxlRc&amp;list=PLP6DbQBkn9ymGQh2qpk9ImLHdSH5T7yw7&amp;index=14">U tube video</a></p>