Hi Adrian, I started a post to your reply that talked about what I would like to see and whatever, but as I got into it, I realized that this whole thing could get quite messy. As soon as you do anything that is "customer facing", I think you are going to lose people (like me) because what we do with widgets could never approach what their specific toolkit can do. I am using nearly the full breadth of the Dojo Toolkit and the things that have been mentioned so far are rather small compared to the Dojo capability and I imagine the same is true with Prototype and others.
I just think the work of trying to add some common features that can be supported by all tool kits will not be useful because it will never go far enough. And it will be a lot of work that will not add much advantage over just working in the toolkit (this is particularly true of Dojo since it has an XML markup language that lets me mix it with the widget environment within .ftl files.) I am thinking that the effort should stick to things that would be useful in an admin environment and things that could be done without any toolkit. The thing that comes to mind is just allowing lookups as embedded panes (divs) instead of opening a window. The date/time control is another useful one. Sortable columns starts pushing my dividing line of doing stuff that does not require a particular toolkit, but it would be useful in an admin environment. I guess I would just advocate not going too much farther than those guidelines allow, but then I wasn't thinking that way an hour ago. -Al
