title: Combining Play! Framework 2.xx with Angular.js
body: <p>I am having trouble is this marriage of 2 seemingly powerful frameworks. It seems most things that can be done by 1 can be done by 2.How to best utilize the two? Are there any patterns of thinking?
  Take a basic example of a CRUD application -- 
  I can write a route mysite/listnames which maps to a controller in play! and this renders a template with the code --</p>
  
  <pre><code>@(names:List[String])
  @main("Welcome") {
  
  @for( name &lt;- names ){ 
      &lt;p&gt; Hello, @name &lt;/p&gt;
  }
  </code></pre>
  
  <p>Note that main is a typical bootstrapping template.
  However now the output this produces seems to be of no use to Angular if say i want to add a input box for filtering these names, or i want to do anything with them at all.
  What is a typical way of proceeding?
  The base thing seems to be-</p>
  
  <p>1) how to pass on data that arrives after rendering the template by Play to angular for later use at clientside.</p>
  
  <p>2) Is it adviseable at all to use these two frameworks together for a large-level app involving a mathematical object oriented backend + server, and a fairly intensive UI at frontend?</p>