Introduce templates for quick start

[jbaron]

Implement template system to quick-start a new project. For example templates for:

1. Web app using Backbone.js and JQuery
2. Nodejs server side application
3. Windows 8 Application
4. Phonegap Application

Will help newcomers to be more quickly productive. Could also include some sample projects.

[jbaron]

List of quick-start templates candidates:

1. Phonegap/Cordova
2. AngularJS
3. Backbone.js
4. JQuery + UI
5. Firefox OS applications
6. Qooxdoo (since we are using this our selves)
7. Turbulenz
8. Windows 8/9 apps
9. Nodejs serverside apps
10. Nodewebkit apps

Idea is to host these templates somewhere on github and download them on a need-to-use basis. Have to come up with an API for both repository and format.

[dtrillo]

I've been thinking about templates and .... it is needed.
I don't know if this templates you propose can be together with my approach.

Where I have CATS, I also want a template directory. Under this directory I can add my personal templates, so, apart from "New File", I will add "New File from template", read the content of this directory in order to process like this:

• Create a new file
• Read the template
• The new file created in step 1 will have the code of the template selected
  Using this solution, one can:
• have their own templates, depending on what they like
• It's flexible (because CATS only need to veryfy if template directory exists, and in case it does, just offer the user to use one template.

I hope you like this point of view about templates! Of course, this way users can create TS templates, HTML templates, Javascript templates, .... And the way of giving action to templates is from a new file.

[jbaron]

Indeed I think templates would be a great addition. My current approach would be to adopt some existing system so there are already a few useful templates out there.

Ideally templating in CATS should support the following:

1. Project templates (so to quickly for example start a Nodejs or Cordova project for example)

2. File templates (quickly add a HTML5 file using some boilerplate content or anything else for that matter)

3. Code templates (add a for next loop). This is already in place (part of the ACE editor)

Number 1 and 2 need to be added. They could use the same base tempalitng structure.

On 11 May 2015, at 01:33, David Trillo notifications@github.com wrote:

I've been thinking about templates and .... it is needed.
I don't know if this templates you propose can be together with my approach.

Where I have CATS, I also want a template directory. Under this directory I can add my personal templates, so, apart from "New File", I will add "New File from template", read the content of this directory in order to process like this:

Create a new file
Read the template
The new file created in step 1 will have the code of the template selected Using this solution, one can:
have their own templates, depending on what they like
It's flexible (because CATS only need to veryfy if template directory exists, and in case it does, just offer the user to use one template.
I hope you like this point of view about templates! Of course, this way users can create TS templates, HTML templates, Javascript templates, .... And the way of giving action to templates is from a new file.

—
Reply to this email directly or view it on GitHub #25 (comment).

[dtrillo]

Is it difficult to implement my approach of using templates?