> Pardon me for jumping in, but I think that retaining two widgets for > the sample feature is a very bad idea.
Your pardoned, but your more than welcome to jump in :D I don't think one solution, in such an open ended situation, is possible. > each option has pros and cons I may want to output a calendar that only uses xhtml, no Javascript at all, if there was only one widget that output a bulky Javascript implementation what am I meant to offer the users that are using text browsers? A text box is useless if you are trying to show dates that are available or unavailable for selection! Another use: a calendar application may use an xhtml calendar that takes up the best part of the screen and could be populated by Javascript + JSON / AJAX. Oh Kay perhaps I am pushing the purpose of form widgets there, but do you get what I mean. This one widget that itself doesn't work for a part of my audience and doesn't even fall back to anything useful!
