On 15 March 2011 21:46, Ross Gardler <rgar...@apache.org> wrote:
As you can see I've recently built a few templates demonstrating different
ways of building widgets. I see templates as both a means to document how to
build certain behaviour into widgets and a means to provide a quick start
way of building widgets.
However, these two objectives are not complimentary. The more detailed a
template becomes the less likely it is to be reused as it will have features
that are not needed and not have features that are needed. In addition, the
more detailed it becomes the less useful it is as a form of documentation.
Simple is best and act an easy starting point for specific development
What I propose to do is build a number of templates where each one
demonstrates a single key feature of W3C Widgets or Open Social Gadgets.
Note I say a *single* feature, I really mean it. If we focus on
demonstrating a single feature very well then each template becomes useful
as a documentation for the feature being demonstrated.
This has the benefit of clearly highlighting what is Wookie without
confusing generic web app issues
Does this sound like a sensible strategy. That is attack each of these tasks
- build templates as documentation for features of widgets and gadgets
- integrate these templates into our website
- provide a clever "jumpstart" system for widgets/gadgets