ENTRIES TAGGED "front end"

Event-driven application design with JavaScript

Look beyond jQuery to an MV* approach

When you start building dashboards for interacting with data, such as calculators, editors, or result browsers, understanding JavaScript and client-side MVC becomes important. Why do you need an event-driven application design and a separation of interface state and behavior? Let me walk you through some examples.

You’ve probably seen seen simple example editors, where the browser acts as an editor for to-do lists. In these applications, you edit to-do items, consisting of a text and a state (pending or done). These small editors are very helpful for studying monitoring events from the keyboard and partially updating page content. These are the main principles for building applications in web browsers.

Once you going beyond to-do list editors, the requirements quickly increase. For example, you might work with multiple counters that observe the cursor position, or the number of words in a text box. You might need to support multiple editing modes or text formatters, or edit actions and state synchronization with a backend.

Read more…

Comment |

Velocity Profile: Nicole Sullivan

Web ops and performance questions with Nicole Sullivan, architect at Stubbornella.

Nicole Sullivan discusses her favorite CSS tools and who she follows in the web ops & performance world.

Comment |
Velocity grows with more tracks, more topics and … bath products?

Velocity grows with more tracks, more topics and … bath products?

The state of the Velocity Conference.

Over its three-year history, the Velocity Conference has expanded to include mobile performance, "Velocity Culture," and a new line of bath products (that last one might not be the best fit).

Comments Off |