Found CleverStack, which is certainly interesting. Might take this up as a learning experience though.
First step would be creating some backend generic modules: - ng-profile - ng-auth - py-oauth2-bottle-app - py-oauth2-rfc6749-lib - py-profile Then to create a yeoman generator with optional backend and choice of database: - [project-name]-ng-app (aforementioned ng-* &etc. is DI'd into here + boilerplate) - [project-name]-py-rest-api (aforementioned py-* are merged into here + boilerplate) This would create a basic website with authentication, state controlling, user profiles and an optional backend to match (in Bottle). This operation could also create repositories (integrating with Bitbucket and Github) with proper standards-compliant package layout and dependency management. Wheel reinventingly yours, Alec Taylor On Wednesday, July 9, 2014 7:26:51 PM UTC+10, Alec Taylor wrote: > > Dear AngularJS mailing-list, > > Like most of you, I have a RESTful API backend with a bunch of independent > and dependent "things". > > E.g.: UsersAuth, UserProfile, Articles, Posts, Comments, Authors, Tags > &etc. Each with their own CRUD of varying complexities and with varying UI > integrations. > > [that's an example, obviously my app isn't a textbook blog application] > > Currently I am dealing with dependencies in an ugly way: > > <project_name>.<controller/directive/factory/service>.<name> > > E.g.: "BlogApp.controller.user", "BlogApp.factory.user", " > BlogApp.service.user" > > With my RESTful backend I am using a Sinatra-style microframework for > Python (Bottle), and have separated each independent "thing" into not only > their own files, but their own repositories + package. E.g.: I have an > oauth2-bottle-app repo, an oauth2-rfc6749-lib repo, and an > <namespace>-models repo (which could be separated into one model per repo > if not for implementation issues). > > I have seen what the slides of what the AngularJS-ORM guy (Dean Sofer) > did, i.e.: http://slides.com/proloser/angularjs-orm#/8 > > However, I am thinking that idea doesn't go far enough on the component > decoupling stage. > > Would it be such a bad idea to push each independent "thing" into it's own > external module, and force it as a requirement in the dependent apps (e.g.: > main apps) bower.json and package.json? > > Or would that overly complicate the design + addition of new feature? > > Thanks for all discussion, > > Alec Taylor > -- 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.
