-
1. Re: quickstart project directory structure
I like the changes.
My only comment is to not combine different tasks with the same commit. I see the jquery version updates are also in here. Before you send the pull request to AeroGear please break these out to separate commits.
Regarding the jQuery updates - did you have any luck with the update? The comments I added to the jira this morning 1.7 will not be supported until JQM 1.1 (end of feb).
-
2. Re: quickstart project directory structure
+1 to the changes in general
a small remark is that I'm not sure if I really like the js/libs, maybe js/lib would fit better (library is a mass word, right? WEB-INF/lib ringing on my head), and I've seen lots of people using assets or vendor for javascript libraries - too many options for sure
Do you know if there's an emerging layout for all mv{c,p} js frameworks we could stick to?
-
3. Re: quickstart project directory structure
my original commit was "lib" singular, as it sounded better to me as well. I agree.
-
4. Re: quickstart project directory structure
I am definitely a fan of h5bp as an example of a good structure. I would actually lean towards libs over lib since it will house multiple JS libraries (jQuery, underscore, etc.).
As for JS MV* structure, I am a fan of https://github.com/tbranyen/backbone-boilerplate as a pretty good example.