emberjs/starter-kit

A starter kit for Ember

starter-kit

Warning

For almost all use cases, you should use https://ember-cli.com to create your ember application. Ember starter kit is no longer recommended for new projects and you will find that you are limited in what you can do compared to ember-cli, and documentation will be misleading due to the different style of app construction in ember-cli.

A starter kit for Ember

Your Ember.js project is almost ready! Here's how to get started:

• Start writing your app in js/app.js.

• Describe your application HTML in index.html.

• During development, you can link to js/libs/ember-*.js to get the unminified version of Ember.js.

• Add CSS to css/style.css.

• Open index.html in your browser.

Tests

This starter kit comes with an integration test sample, written for QUnit runner.

You can run the tests by opening the index.html?test page in your browser.

The test is located in the tests/tests.js file. You can see how such an integration test should be written, using QUnit assertions and ember-testing helpers.

For more information about ember-testing package see ember-testing.

For more information about the QUnit testing framework, see QUnit.

Contact

www.emberjs.com

starter-kit's Issues

Unnecessary and potentially harmful reference to "no-js" class in index.html

tag in index.html contains a "no-js" class, but the starter kit doesn't contain Modernizr

"don't clone, download" is distracting

The don't clone, download message turns me off as a developer for several reasons:

• It tells me not to do something without telling my why (but at least it provides an alternative)
• Cloning is a valid approach
• There's more than one way to do it
• It disrupts the flow of checking out your repositories

Why is the message there? Is it so commits can be made but not released? How about moving development off of the master branch if it's going to be broken for a while?

To me using git is a valid way of moving files around. Plus git has an alternative for copying the directory and deleting .git, and this is likely to get better.

remove first / from the src references in index.html.

There is a / before the script source locations. This results in not finding the src files.

change:

"/js/libs/jquery-1.9.1.js"
"/js/libs/handlebars-1.0.0-rc.3.js"
"/js/libs/ember-1.0.0-rc.1.js"
"/js/app.js"
"/css/style.css"
to
"js/libs/jquery-1.9.1.js"
"js/libs/handlebars-1.0.0-rc.3.js"
"js/libs/ember-1.0.0-rc.1.js"
"js/app.js"
"css/style.css"

add example of using templates

Hello there, could you help me to example using template in this starter-kit?

thank you so much

Incorrect script type attribute in index.html

In the starter kit's index.html the templates are included with a <script type="text/html"> tag which should be changed to <script type="text/x-handlebars"> tag

Where is ember-template-compiler-1.10.0.js??

Where is the eember-template-compiler-1.10.0.js file that index.html tries to include in line 26:

<script src="js/libs/ember-template-compiler-1.10.0.js"></script>

¿Is this the reason the starter-kit doesn't work at all?

"App" code not mentioned in 2.0 guide

Both index.html and app.js have App code in them, and the guide never comments on it, or mentions that you're meant to remove it. It's confusing for a n00b

rm

rm

Failed to load resource: file://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js

v1.11.0 test fails for "Application header is rendered"

I cloned the repository and runned the test.

Application header is rendered
Expected:   
"Welcome to Ember.js"
Result:     
""
Diff:   
"Welcome to Ember.js" "" 
Source:     
    at http://ember.local/tests/tests.js:28:22
    at andThen (http://ember.local/js/libs/ember-1.11.0.js:37216:35)
    at http://ember.local/js/libs/ember-1.11.0.js:37943:25
    at isolate (http://ember.local/js/libs/ember-1.11.0.js:38137:15)
    at http://ember.local/js/libs/ember-1.11.0.js:38120:16
    at tryCatch (http://ember.local/js/libs/ember-1.11.0.js:50466:16)
    at invokeCallback (http://ember.local/js/libs/ember-1.11.0.js:50478:17)

I tried just opening the index.html file and also accessing it through server. No console errors shown.

Second starter-kit with build tools

What about a starter-kit which includes some kind of build tools / package management.
During development it should not be the recommend way of putting everything into one JS file and all templates into one html file.
A better way would be to split everything into multiple files and provide the user with a basic folder structure (like rails does). So that every project would have the same structure.
The build tools would concatenate and minify everything.
On getbpm.org the Sproutcore 2 packages are still available. This was a start to target this problem. However after reading a little on stackoverflow it seems that the Tilde guys are suggesting to use Rake-Pipeline.

It would be nice to a have a boilerplate template for new projects with preconfigured Rake-Pipeline setup or something else. Any plans?

Starter-kit.1.0.pre.zip link is broken on the site

when you try to download the new starter-kit on the site you will have Github 404 page error.

Execute Permissions on all the files?

Not a big deal (quick fix: find . -type f -exec chmod 644 '{}' + ) but...

This is referenced in #42 but I just downloaded and unzipped the starter-kit-master and the index.html was marked +x

Update master to have latest sproutcore

The zipfile has sproutcore-2.0.beta.1: https://github.com/downloads/sproutcore/starter-kit/starter-kit.2.0.beta.1.zip

However, the master branch still has sproutcore-2.0.a.3.

Any chance of pushing the latest to the starter-kit git repo too?

red = yellow = blue = black!?

Hi there, thanks, for nicely providing an app skeleton to newcomers like me, but it took me like 15 minutes to realize that the missing colors are not due to some obscure local configuration issue (I'm running it over my custom-hacked http server on a war-torn, old frankenstein XP+Debian machine), but they are just not in fact colors at all... To be honest, I'm still unsure, whether they should appear in black or in their respective, named colors.

Could you please remove this extra confusion by simply calling them cats and dogs and hamsters or apples, oranges, bananas, or any other favorite household items, which don't have trivially corresponding CSS props. that one would automatically expect to work in such a context, and feel terrified seeing that for some hopelessly obscure reason they just still don't? :) Cheers!

min version of ember.js in starter kit doesn't work

ember-0.9.2.js is fine, but the min version doesn't work.

errors on test

Just downloaded the latest starter kit (1.9.0), and run ?test on the querystring on the default code and get the following error:

global failure (1, 0, 1 )Rerun 0 ms
Uncaught ReferenceError: App is not defined
Source:
http://www.***********.com/ember/tests/tests.js:2

the released version of 1.9.0 contains handlebars v1.3.0.

In the master branch, handlebar version is updated to v2.0.0. However, the 1.9.0-tagged released version still contains v1.3.0 which is downloadable from Ember.js website. New comers may be struggling when they download the starter-kit from the website.

2.0.a.2 Doesn't work in Firefox 3.6

Object.create is not a function
3715: ret = m.mixins = Object.create(ret);

I haven't tried any other versions yet. According to the console Object only has observes, observesBefore, and property.

No #todos mentioned

The CSS linked to from the 2.0 guide (ie. from Todos-Example) depends on a #todos wrapper around the whole todo app which is not present in the index.html in the starter-kit nor mentioned in the guide.

Wrong handlebars filename in the zip archive

Hello,
on the website http://emberjs.com/ the download-button ("Download the Starter Kit") links to https://github.com/emberjs/starter-kit/archive/v1.2.0.zip This Build-Version has the wrong filename of the handlebars file. It is named "handlebars-v1.1.2.js" instead of "handlebars-1.1.2.js" (so without the "v"), that causes the index.html file not to work, because the src links to js/libs/handlebars-1.1.2.js

Kind regards,
Sebastian

The starter-kit doesn't work at all!!!

I have tried the source version and the website version. I think them same.

1. The file 'ember-0.9.8.1.min.js' doesn't define Ember.
2. With the file 'ember-0.9.8.1.jg', the Em.Controller has not extend method.

And there are more problems when I expend 3 days on router.

These things make me a bad impression on this framework and feeling terrible on wasting so much time.

[enhancement] Add missing bower.json.

Hey, maintainer(s) of emberjs/starter-kit!

We at VersionEye are working hard to keep up the quality of the bower's registry.

We just finished our initial analysis of the quality of the Bower.io registry:

7530 - registered packages, 224 of them doesnt exists anymore;

We analysed 7306 existing packages and 1070 of them don't have bower.json on the master branch ( that's where a Bower client pulls a data ).

Sadly, your library emberjs/starter-kit is one of them.

Can you spare 15 minutes to help us to make Bower better?

Just add a new file bower.json and change attributes.

{
  "name": "emberjs/starter-kit",
  "version": "1.0.0",
  "main": "path/to/main.css",
  "description": "please add it",
  "license": "Eclipse",
  "ignore": [
    ".jshintrc",
    "**/*.txt"
  ],
  "dependencies": {
    "<dependency_name>": "<semantic_version>",
    "<dependency_name>": "<Local_folder>",
    "<dependency_name>": "<package>"
  },
  "devDependencies": {
    "<test-framework-name>": "<version>"
  }
}

Read more about bower.json on the official spefication and nodejs semver library has great examples of proper versioning.

NB! Please validate your bower.json with jsonlint before commiting your updates.

Thank you!

Timo,
twitter: @versioneye
email: [email protected]
VersionEye - no more legacy software!

newer jQuery?

How about using jQuery 1.7.1 instead of 1.6.1? I'm getting this warning.

missing http:

line 29 of the hello world index.html in the starter kit.

<script src="//ajax.googleapis.com/ajax/libs/jquery/1.6.1/jquery.min.js"></script>

Bad url on Readme

Bad url refered to "http://ember-cli.com/"

This PR fix the error.
#70

Thanks.