widgetx coming soon... maybe?

Once the trunk/branch situation gets finalized I'd like to start a new subdirectory in the main tree for a little widget r&d. You may see a couple widgets duplicated (in name only) here and there, but it's not meant to be a competing sort of directory....Purely just research and fact finding stuff. 

If you don't like the idea of doing it just shield your eyes and pretend it isn't there. ;) Hopefully this will allow easy collaboration with others while also not impacting the core widget development tasks. 

I think a few of us have "an itch that needs itching" wrt to how a few things regarding widgets/objects/etc are done, so this seems like the ideal place to do it. If you are one of those people this message is meant to start your gears turning in the interim. 

The goals of what are to be done here aren't clear or formalized yet at all, so don't bother trying to pin anything down. It's just a general idea of "there has to be a better way". I know it's not stuff that fixes any one particular bug, but I've found that refactorings like this one tend to have side effects of fixing large globs of bugs without even knowing it. 

Generally speaking, my personal goals here are to :

-) Reduce and compact the widget code by finding ways of re-using common blocks to do internal things...Maybe mix-ins will do well here. Not sure. 

-) Make the widget system & rendering of widgets "as fast as possible". 

-) Create and enforce some common styles of how to do things via a set of shared/common behaviors that people can expect. Simple things like escape key handling/whether or not to mangle or re-use existing html/etc...

Probably more but there's too much potential to say for sure. I don't want to own the new subdir, just get it started so people interested can all collaborate and help figure this stuff out without traumatizing the current widget infrastructure. 

-- 
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer

Open source based consulting work centered around dojo/tapestry/tacos/hivemind. 
http://blog.opencomponentry.com
_______________________________________________
dojo-contributors mailing list
dojo-contributors@xxxxxxxxxxxxxxx
http://dojotoolkit.org/mailman/listinfo/dojo-contributors