client-side templating in jquery

There is a power for loading data that will be manipulated within the interface by user action. Templates also let you chunk your interface into manageable, re-usable pieces.

[ SXSW Bios ] #sxsw #jquerytmpl (Archive)

Brief

This session will review the options available today and in the future for client-side templating in jQuery. We will show the libraries available today, including jQuery Templates, knockout.js, and JsRender/JsViews.The past year has been rather tumultuous in the jQuery Templating space. Before the jQuery Templates plug-in even had a chance to come out of beta, the project was terminated in favor of newer templating libraries currently under development. However, even though it is still unclear which templating library is the best to use, the concept of client-side templating is too important to ignore or put off using. This talk will review the various options Web developers have today for performing client-side templating, and will present guidance on what to look for in the coming year as newer libraries are released. Continue reading “client-side templating in jquery”

one codebase, endless possibilities — real HTML5 hacking

[ SXSW Bios ] #hack5 [ Presentation Files ]

  • @joemccann

Brief

HTML5 is no question the “buzzword du jour” in tech nowadays, but looking past the vernacular cruft one will discover that the HTML5 technology STACK is actually an incredibly powerful & useful framework for apps well beyond the traditional web browser. Massive companies like Google and Hewlett Packard are placing huge bets on the future of “HTML5 App development”. From HP/Palm’s WebOS to be used in their mobility products to Google’s Chrome OS, HTML5 is not simply another buzzword that can be treated as a mere passing trend, but should actually be taken seriously for app development. But what makes up the HTML5 stack and how will it truly be the future of software? What are the benefits & risks associated with using the HTML5 stack? Prove to me it works. All of these questions & demands will be answered & showcased in the presentation including important issues such as: What constitutes the HTML5 stack Benefits of using the HTML5 stack Use a single codebase Rapidly prototype an app targetting multiple devices including: iPhone, iPad, Android Devices, Chrome OS Devices, Mobile Webkit Browsers, Desktop Browsers Target thousands of developers for extensibility & community development See code & install an actual working HTML5 app that works on a number of devices See code best practices in use for tailoring the UI based on the user’s device See code using Phonegap to create native mobile apps See code using Titanium to create native desktop apps Continue reading “one codebase, endless possibilities — real HTML5 hacking”

javascript architecture: the front and back of it

UI Architecture: all the stuff that it takes to process, package, deliver, and communicate with the client (templating url routing, data validatiion, formatting, ajax). “Between the front and back end”: stuff between presentational javascript and the backend logic. The middle end gives a web 2.0 app performance.

We need to talk about this because of issues with performance and optimization, the MVC model spaghetti code failure (outputting html if a condition exists: the mixture of model code inside view template, too tight coupling between presentation layer and model layer), “don’t repeat yourself” (DRY: repeating code over and over again, i.e., duplicating validation in the client and the server, “any time there is more than one copy of something, one copy is always wrong”), and role separation (wearing multiple skillset hats and mixing contexts–markup/css switch to javascript switch to backend app–without being able to focus on one context at a time).

This isn’t another framework, it’s an optimized/reworked “alternate pattern” of MVC in an attempt to solve some of the weaknesses/problems of MVC. Can we decouple the view from the existing architecture stack?

CVC + JavaScript puts the power of UI architecture in the hands of front-end engineers.

[ session description ]

Presenter(s)
Kyle Simpson
Date
14 March 2010
Tag(s)
#frontandbackofit
#jsarch
Sites
Getify
Demo of HandlebarJS
Speaker Feedback
BikechainJS
HandlebarJS

Continue reading “javascript architecture: the front and back of it”

web framework battle royale

Web frameworks make building websites easier. Common tasks are abstracted for faster development. Here is an analysis of five different frameworks: Zope (Python), Rails (Ruby), Sinatra (Ruby), Seaside (Smalltalk), and Symfony (PHP).

[ session description ]

Presenter(s)
(lots)
Date
13 March 2010
Tag(s)
#frameworkbattleroyale

Continue reading “web framework battle royale”

designers and developers:why can’t we all just get along?

I arrived at this session and it was SRO and full. I got some final ideas (after making it inside with 15 minutes to go):

  • When designers push their vision out to “version 10”, it can cause tension with developers who are usually starting from the other end (i.e., Agile). Developers want to start small (and efficient/elegant) and progressively build toward a design. Balance is key.
  • The best possible thing a designer can do for a developer is to share the problem and challenges, not just ask for a composed feature. That way the designer is asking to partner on the solution with the developer. Happiness ensues.
  • The best possible thing a developer can do for a designer is to communicate principles and needs to designers to create a more common ground. For example, talking to designers about considering both real-time interactivity and asynchronous actions.
  • The best possible thing both can do is hang out with each other outside the office.
  • Build trust.

For the rest of the notes, I depend on my trusty Michigan friend, daniel slaughter. He takes amazing notes.

These are notes from a session at sxsw interactive. My own take on topics are mixed in with what the presenters were actually saying, so do not assume all of this content is my own.

designing our way through web forms

Forms suck. Creating a style guide for form design is difficult.

Presenters
Christopher Schmitt – Heat Vision
Eric Ellis – Bank of America
Kimberly Blessing – Comcast Interactive Media
Date
Sunday, March 15
Sites
web form elements research
jquery validation
moz monkey

Continue reading “designing our way through web forms”

core conversation:should i build my startup on ruby on rails?

What are the most important qualities of a programming language when you are starting from scratch?

  • how easy to get a prototype out?
  • will it scale? or do i need to scale right now?
  • what existing code libraries are out there and do they support my industry?
  • what kind of talent is out there?
  • do i already know the language?
  • does the language encourage good developer habits?
  • is the language well accepted by a large community/industry?
Date
Saturday, March 19
Sites
Ruby on Rails

These are notes from a session at sxsw interactive. My own take on topics are mixed in with what the presenters were actually saying, so do not assume all of this content is my own.