Issues

Remove z-index (carefully) from view layouts

#16

· dcporter opened

on Jun 26, 2013

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.

enhancement

#11

· geojeff opened

on Jun 19, 2013

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

enhancement

question

#10

· geojeff opened

on Jun 19, 2013

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

#9

· geojeff opened

on Jun 19, 2013

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

#8

· geojeff opened

on Jun 19, 2013

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

enhancement

#7

· geojeff opened

on Jun 19, 2013

Persistence -- Use SproutCore local storage.

enhancement

question

#6

· geojeff opened

on Jun 19, 2013

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?

enhancement

question

#5

· geojeff opened

on Jun 19, 2013

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

enhancement

question

#4

· geojeff opened

on Jun 19, 2013

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.

enhancement

#3

· geojeff opened

on Jun 19, 2013

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.

enhancement

#2

· geojeff opened

on Jun 19, 2013

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?

enhancement

question

#1

· geojeff opened

on Jun 19, 2013

Navigation Menu

Uh oh!

All issues

Remove z-index (carefully) from view layouts

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.

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

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

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

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

Persistence -- Use SproutCore local storage.

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?

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

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.

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.

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?

Uh oh!

Search results