sproutcore/getting-started issues and pull requests

#17 - Rename README to README.md

Pull Request - State: closed - Opened by ghost over 9 years ago - 2 comments

#16 - Remove z-index (carefully) from view layouts

Issue - State: open - Opened by dcporter over 11 years ago

#15 - Todo Item -- Clicking the checkbox marks the todo as complete by updating it is completed value and toggling the class completed on its parent <li>.

Issue - State: closed - Opened by geojeff over 11 years ago
Labels: enhancement

#14 - Mark all as complete -- Checkbox toggles all the todos to the same state as itself. Make sure to clear the checked state after the the "Clear completed" button is clicked. The "Mark all as complete" checkbox should also be updated when single todo items a

Issue - State: closed - Opened by geojeff over 11 years ago
Labels: enhancement

#13 - New todo -- New todos are entered in the input at the top of the app. Pressing Enter creates the todo, appends it to the todo list and clears the input. Make sure to .trim() the input and then check that it is not empty before creating a new todo.

Issue - State: closed - Opened by geojeff over 11 years ago
Labels: enhancement

#12 - Code Style -- Edit files for using tabs as required, instead of spaces.

Issue - State: closed - Opened by geojeff over 11 years ago - 1 comment
Labels: enhancement

#11 - Counter -- Add a label to the todos counter (e.g., 1 item left, singular, and 2 items left, plural). Assure <strong> tag around Counter number.

Issue - State: open - Opened by geojeff over 11 years ago - 2 comments
Labels: enhancement

#10 - Editing -- A new editing state should hide #main, list, and #footer, destroy if empty input, discard on escape. What about blur vs. enter?

Issue - State: open - Opened by geojeff over 11 years ago
Labels: enhancement, question

#9 - Item -- Add an "X" icon and button that should appear on hovering over a todo item for item deleting.

Issue - State: open - Opened by geojeff over 11 years ago - 1 comment

#8 - Item -- Add an item edit state to handle editing on double-click.

Issue - State: open - Opened by geojeff over 11 years ago - 3 comments

#7 - Routing -- Use SproutCore routing for #/, #/active, #/completed, and do required filtering and displays.

Issue - State: open - Opened by geojeff over 11 years ago - 1 comment
Labels: enhancement

#6 - Persistence -- Use SproutCore local storage.

Issue - State: open - Opened by geojeff over 11 years ago - 11 comments
Labels: enhancement, question

#5 - Structure -- The bower_components directory contains base.css, base.js, bg.png. Do we need to use this? Especially for CSS -- do we need to adapt as best we can for use in SproutCore todos?

Issue - State: open - Opened by geojeff over 11 years ago - 4 comments
Labels: enhancement, question

#4 - Compatibility -- Check the list of required browsers to support. Does SC offer required browser support?

Issue - State: open - Opened by geojeff over 11 years ago - 1 comment
Labels: enhancement, question

#3 - UX -- This general requirement, that it work like the template, will be done when all the items in the spec are completed, to the extent appropriate for SproutCore.

Issue - State: open - Opened by geojeff over 11 years ago - 4 comments
Labels: enhancement

#2 - Readme -- Write it when dust settles. If fixtures is not used in the todomvc rendition of SproutCore todos, take note. And also, link to the SproutCore Getting-Started guides and the todos app there.

Issue - State: open - Opened by geojeff over 11 years ago
Labels: enhancement

#1 - General -- Almost done for hiding #main and #footer, but there should be a little spacing above the input when it exists by itself. Do these references to #main and #footer need to be in the html as anchors, or are these just references?

Issue - State: open - Opened by geojeff over 11 years ago - 3 comments
Labels: enhancement, question

Ecosyste.ms: Issues

GitHub / sproutcore/getting-started issues and pull requests

#17 - Rename README to README.md

#16 - Remove z-index (carefully) from view layouts

#15 - Todo Item -- Clicking the checkbox marks the todo as complete by updating it is completed value and toggling the class completed on its parent <li>.

#14 - Mark all as complete -- Checkbox toggles all the todos to the same state as itself. Make sure to clear the checked state after the the "Clear completed" button is clicked. The "Mark all as complete" checkbox should also be updated when single todo items a

#13 - New todo -- New todos are entered in the input at the top of the app. Pressing Enter creates the todo, appends it to the todo list and clears the input. Make sure to .trim() the input and then check that it is not empty before creating a new todo.

#12 - Code Style -- Edit files for using tabs as required, instead of spaces.

#11 - Counter -- Add a label to the todos counter (e.g., 1 item left, singular, and 2 items left, plural). Assure <strong> tag around Counter number.

#10 - Editing -- A new editing state should hide #main, list, and #footer, destroy if empty input, discard on escape. What about blur vs. enter?

#9 - Item -- Add an "X" icon and button that should appear on hovering over a todo item for item deleting.

#8 - Item -- Add an item edit state to handle editing on double-click.

#7 - Routing -- Use SproutCore routing for #/, #/active, #/completed, and do required filtering and displays.

#6 - Persistence -- Use SproutCore local storage.

#5 - Structure -- The bower_components directory contains base.css, base.js, bg.png. Do we need to use this? Especially for CSS -- do we need to adapt as best we can for use in SproutCore todos?

#4 - Compatibility -- Check the list of required browsers to support. Does SC offer required browser support?

#3 - UX -- This general requirement, that it work like the template, will be done when all the items in the spec are completed, to the extent appropriate for SproutCore.

#2 - Readme -- Write it when dust settles. If fixtures is not used in the todomvc rendition of SproutCore todos, take note. And also, link to the SproutCore Getting-Started guides and the todos app there.

#1 - General -- Almost done for hiding #main and #footer, but there should be a little spacing above the input when it exists by itself. Do these references to #main and #footer need to be in the html as anchors, or are these just references?