Closed Foxandxss closed 10 years ago
I'm mostly :+1: but I'm worried about the cognitive overhead for users who can grasp angular and the rest of what's going on, but for whom bower is new or unfamiliar.
Yeah, but Lineman is not only about newbies, it is also a work tool. The idea is to clone the repo and start working :)
Otoh, that is not something that cannot be resolved with proper docs :)
Lineman is only used by hundreds of people at this point, so I favor the quickstart templates like this one to serve as a gentle introduction to lineman. The templates are more of a demo and an example than they are meant to be the correct answer to the question "what should I do when I want to start an X project?".
For that question, I'd much rather point to lineman's plugins. After all, if you're an expert you could just as well start with a vanilla project and npm install --save-dev lineman-bower lineman-angular
and more or less be ready to go without this repo.
:thumbsup: :thumbsup: :thumbsup:
Uhm, I like that perspective. In fact, I love it. Better to use a vanilla project and just add what you need (or what I need actually).
That raises another question. I like to see this project as a quickstart template. What about renaming it to lineman-angular-example
or something like that and provide some information of how to start a fresh project.
But that also means that we should think more about that lineman-protractor that seems to be the last part to be extracted from this example.
Well, that raises another question more. Shouldn't angular vendor/helpers stuff be on lineman-angular
? Or we should add that by hand/bower if we go the vanilla way?
@Foxandxss to answer your question, the vendor/helpers stuff isn't specially packaged so my sense is that it'd just be moving the goal posts to sweep it into lineman-angular, forcing us and users to keep them up to date / overridden (just like asset gems in Rails are a pain in the ass for all parties). But I would say if there's a concrete problem we can solve with a build-time helper, then perhaps it makes sense to package it.
Angular is on fire, we get updates every week more or less and I am always updating it by hand. Shouldn't we add bower? I am not a bower lover, but maybe we can leave the dependencies updates to it.