Let's talk about writing patterns in general. How do you do it? Why? What makes user experience design patterns different from software design patterns and architectural design patterns (if anything)? and more...
I hope that the above update shows that pattern language and knowledge are not incommensurate, but that similar knowledge structures are an underlying condition for the _poosibility_ of a common pattern language.
I'd say one thing that make HCI/UE patterns so challenging is the referent context must encapsulate both subjective definitions for interaction, as well as many changing objective limitations (browsers, HTTP, javascript, flash, underlying data portability).
I'd say one thing that make HCI/UE patterns so challenging is the referent context must encapsulate both subjective definitions for interaction, as well as many changing objective limitations (browsers, HTTP, javascript, flash, underlying data portability).
Not sure I understand this correctly. Are you saying that the pattern itself needs to describe or detail things like browser, HTTP, Javascript, Flash, etc? Or are you saying that what makes UI patterns more difficult is that when designing a UI pattern, we have to think of and accommodate for these items?
If the latter, I agree. If the former, then I'd disagree. I've designed dozens of pattern libraries for clients w/o detailing out the specifics of HTTP, Javascript, and Flash.
Not sure I understand this correctly. Are you saying that the pattern itself needs to describe or detail things like browser, HTTP, Javascript, Flash, etc? Or are you saying that what makes UI patterns more difficult is that when designing a UI pattern, we have to think of and accommodate for these items?
If the latter, I agree. If the former, then I'd disagree. I've designed dozens of pattern libraries for clients w/o detailing out the specifics of HTTP, Javascript, and Flash.
I'm wrestling with a pattern library I'm currently writing.How should the structure or language of a pattern change when your audience is not user experience designers but product managers, visual designers, and web developers?
I'm wrestling with a pattern library I'm currently writing.
How should the structure or language of a pattern change when your audience is not user experience designers but product managers, visual designers, and web developers?
We are a group of HCID students (www.hcid.ch) just working on this topic. Well but we take it from a more User Centered Side. Our goal is to build a system, that is supposed to find patterns easily not how to use pattern when they are found already - normally the product managers, business people and others do not know what for patterns are there. So it is about to lead them with a system in the right direction that they find the right patterns - On the right level .. Structure, Skeleton, Surface...
We think it is important to analyze first the users for getting the patterns accepted in a real world project...
I'd love to hear more about this effort. Are you publishing it anywhere or is there a publicly visible site you can point to?
It will finished Spring 2009 - I'll will link it as soon as there is something ready
It will finished Spring 2009 - I'll will link it as soon as there is something ready