Seems like Angularjs is not for your project. Its design aims to made easy single page web apps, fatty clients, etc. It expects that the client will do API calls to the server to get data, not templates (it's a contradiction use the word template, templates are static by definition), thus providing division between data and views. That's why you are getting frustrated by the routing system, you are developing on the neanderthalian www, where you do all the job on the server. For this cases there are out there a ton of tools, asp.net, jsp, etc. etc...
Good luck! On Monday, 5 August 2013 13:56:16 UTC+2, Maximilian Eberl wrote: > > > It seems the simplest solution to what you are trying to do is to > > not use routes at all, but just put a watch on $location.path(). > > This watch handler could simply keep a mapping of fragment > > paths to server urls, find the right server url for the given "route" > > and set it to a scope variable. You then just use ng-include to > > have angular load that from the server. > > Yes, to play around with raw $location.path does the job, but > I am loosing the comfort of $routeProvider and many other > developers are used to invoke routing. > > My idea was very, very simple: make caching configurable with > a boolean flag and proceed request params to those templates. > Maybe rethink the concept of a static root provider. > Not one Higgs Particle more. > > >> -- 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.
