I am a newbie to Dojo, but Im very impressed with what it can do and Im currently Dojo enabling my application. However, there seems to be some important omissions that Im hoping is my lack of understanding.
1) No equivalent of the <select>
According to Mastering Dojo Every HTML form control has a Dijit counterpart and for <select> its FilteringSelect. However <select> has functionality that FilteringSelect does not.
a) You can use optgroups to group your selections
b) You can use size to display multiple selections all the time when the control does not have focus.
c) Sometimes you just dont want a user input box
2) Validation
This is such a fantastic feature, and I just love the popup that tells you youre typing rubbish. But what do you do about radio buttons and check boxes? I would like the same popup to appear if a radio button is mandatory when the user clicks save after I have called form.validate(). I can see the problem as each check/radio is a separate html element with a separate id(although common name), but Im disappointed if Dojo has no way to cope with it.
3) form disable
How do you disable a form like you see when you show a modal dialog box? I would like to do this when Im waiting for the server to save my data.
4) Documentation
Although methods and properties are documented well, the attributes dont seem to be documented anywhere. Ive just got them from the Dojo campus examples and the book. Same comment for constraints, icon class etc.
5) If you want a normal button, the Dijit version does not have rounded corners like its HTML counterpart and doesnt look as good.
The general advice seems to be always use the digit control as mixing and matching with html will look odd, but unless they can offer at least the same functionality, I might have to.
