![]() ![]() Lists are also color-coded with a heat map to show the most pressing tasks at a glance. With Clear, there are only a few gestures you need to in order to use the app: pull down on a list to add an item, swipe to the right to complete an item or to the left to delete it, pinch apart two items to insert a new one in between, and pinch vertically to close the current list and see all the lists in the app. Somewhere, Steve Jobs, no fan of buttons (obviously – look at the iPhone, there’s just the one) is smiling. But Clear’s design is meant to tap into what’s already common knowledge among smartphone users: you can swipe, pinch and pull down on on-screen elements to interact. If you don’t know how to swipe and pinch, you could be lost for a second upon first launch (err, mom). The app is unique in that it forgoes common navigational elements – like buttons positioned either at the bottom of the screen or towards the top – in favor of an all-gesture interface. But if you’re regularly turning to a simple to-do list app, or even the iPhone’s built in notepad to make your lists, Clear is definitely going to wow you. If your current to-do list app needs are complex, you may not be in the market for Clear. There are no buttons with Clear, and yet, it’s surprisingly simple to use. The app is based solely on the use of now-common gestures: swipes, pulls and pinches. But it’s also representative of a major leap forward in smartphone app design, as it’s been built from the ground up for the touch interface. Why the big draw for what’s typically been a rather ho-hum app category, the lowly to-do list? Clear is pure eye candy, for starters. And by heavily anticipated, I mean this app was getting tech blog coverage based on demos, previews and teaser videos. Value = Y.im(inputNode.Clear, the heavily-anticipated touch-based to-do list app, is launching in the iTunes App Store tonight. Creates a new todo item when the enter key is pressed in the new todo tells it to delete itself from localStorage as well. todo-remove-icon to the todo model's `destroy()` method Next, some CSS to make the todo list look pretty.ĭelete icon courtesy of The Noun Project:īackground: url(./assets/app/remove.png) no-repeat This is generally a more maintainable way of embedding templates than storing them in JavaScript strings, but there's no requirement that you use this technique. We can then retrieve the contents of the element to get a convenient template string. We'll also add some invisible HTML templates to the page, which will be used to render our views later.īy putting this template HTML inside a element with type="text/x-template", we ensure that the browser will ignore it because it doesn't recognize the text/x-template type. I swear.įor a slightly more realistic use case demonstrating how the App Framework can make a complex task simpler instead of a simple task more complex, take a look at the GitHub Contributors example.įirst we'll create the HTML shell for our todo app. Also, our lawyers advised us that we were legally required to provide a todo example, so we had no choice in the matter. In other words, this example is not meant to be a recommendation for how to implement a todo app it's meant to be a demonstration of how models and views fit together to define application logic. In reality, this little todo app is so conceptually simple that it probably doesn't need to be broken into discrete components, but its inherent conceptual simplicity makes it convenient for explaining how models, model lists, and views work. Ironically, this example complexifies a very simple application in order to demonstrate concepts you might actually use to simplify a complex application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |