In our discussion, Nathan and I first defined design pattern libraries and component libraries. A pattern library is a repository for ideas and solutions to design interaction problems. Component libraries are comprised of actual functioning parts with real code. An example would be a log-in process. Your pattern would define the experience of logging into your application, from the interaction, and often visual standpoint. Your component would be the chunk of code that represents the set of fields and controls that can be replicated across your organization’s web properties, so that you can easily create a consistent experience for your users, no matter where they may enter your system.
SpoolCast: Achieving Pattern and Component Reuse with Nathan Curtis
Also huffduffed as…
-
SpoolCast: Achieving Pattern and Component Reuse with Nathan Curtis
-
Achieving Pattern and Component Reuse with Nathan Curtis
-
Achieving Pattern and Component Reuse with Nathan Curtis
-
Achieving Pattern and Component Reuse with Nathan Curtis
-
Achieving Pattern and Component Reuse with Nathan Curtis
-
Achieving Pattern and Component Reuse with Nathan Curtis
Possibly related…
-
Scalable JavaScript Design Patterns at Web Directions South 2011 | Lanyrd
Would you like to learn how to organize your JavaScript applications so they can scale? Be able to write apps that support switching out Dojo or jQuery without rewriting a line of code? Application architecture is one of those aspects to development where minor problems can lead to major issues later on if it isn’t done right.
Developers writing client-side apps these days usually use a combination of MVC, modules, widgets, plugins and frameworks for theirs. Whilst this works great for apps that are built at a smaller-scale, what happens when your project really starts to grow?. In this talk, I’ll be presenting an effective set of design patterns for large-scale JavaScript application architecture that have previously been used at both AOL and Yahoo amongst others to develop scalable applications.
You’ll learn how to keep your application logic truly decoupled, build modules that can exist on their own independently so they can be easily dropped into other projects and future-proof your code in case you need to switch to a different DOM library in the future.
Tagged with javascript patterns bestpractices addyosmani
-
Jared Spool – Mobile & UX: Inside the Eye of the Perfect Storm Live! » UIE Brain Sparks
-
Usability Testing - Jeffrey Zeldman / Jared Spool
Dan and Jeffrey talk with special guest Jared Spool about usability testing in the real world, with practical advice for designers, UI engineers, and developers alike.
Jared Spool is the founder of User Interface Engineering, the largest usability research organization of its kind in the world. He’s been working in the field of usability and design since 1978, before the term “usability” was ever associated with computers.