Sander, Thanks! No, I don't need the data anywhere else and your suggestion is the way I currently have it set up - thanks for the reassurance. I simplified the scenario a little bit, but yes, I do have the actual generation of the PDF partitioned out into it's own non-angular JS lib.
I'll continue on with this design unless anyone else has a different opinion. Thanks again! On Tuesday, April 15, 2014 11:36:10 PM UTC-4, Sander Elias wrote: > > Hi John, > > Do you need the data somewhere else as in your directive? If you need to > keep this data around, put it in a service, if not just keep it in the > directive. > > To me this sounds like a directive with a controller. You can inject all > services you need into this controller. > Also it sound like you are trying to stuff to much in 1 thing. I would > split up the generation of the PDF onto its on service, this is more > reusable. > > Regards > Sander > > > > > -- 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/d/optout.
