Widget discussion

* We talked a lot about characteristics of the current system, how it evolved and what would be ideal.  Different things are (obviously) more important to different people.  (See the list below).

* Alex brought up the concept of thinking about restricting all of the degrees of freedom that we currently allow:
    HTML vs SVG/VML
    Parser vs Prodedural
    Complete CSS flexibility vs taking a step in the ground on class names, etc
    Fewer code paths
    Behavior vs template instantiation
    Flexibility in options per widget

* We listed the following characteristics of the current system/an optimal system.  Everyone who was interested then was given 5 "votes" so we could try to get a straw poll of what was characteristics were most important to the folks in the room.  The items are listed in order of the number of votes received.  Note that this is NOT intended to say "we'll support this and not this" but rather to get a sense of which lines we should optimize on.

    Votes    Item
    --------    ----------------------------------------------------
    16        Cheap to instantiate programmatically
    11        Modularity - get just what you need
    9        Data binding
    7        Accessibility
    7        CSS themeability/skins
    6        Markup/script duality/ability
    6        Attach points (dojoAttachPoint)
    6        Nested/composite widgets
    5        Internationalization
    5        Easy to learn and understand
    4        Event attachment
    2        Template system
    1        Cheap to instantiate from markup
    1        Code footprint/size
    1        Basic API such as show/hide
    1        Promotional ability (take an existing node and promote to a widget)
    0        Dynamic templates/macros
    0        Auto-require based on in-page widget specification
    0        Fascades (embedding widget x in dropdown, in popup, in page)