Thanks for the reply,
The different divs are created to allow for the different design options. Since the label, error, fields, and columns can all be positioned and styled individually, they need corresponding html elements.A form builder form can switch between designs by changing the .css alone, in order to account for a diversity of designs, the html used needs to account for the options available.
I understand now why there's so much code but from a developers perspective, it really puts you off wanting to use it due to the amount of code which is only there because of the different design options which will never all be used anyway. Do you think a future version of the extension would just output the design option that the user chose instead of every single possibility? It would make it so much easier to use.
Server Validation and Spry validation can be added to existing forms using the Form Builder Server Validation Server Behavior on an existing form and applying Spry Validation through Dreamweaver is a valid way to accomplish this with existing forms.
If I was to use the Form Builder Server Validation Server Behavior, would I need to run the form wizard? I thought I read somewhere that even if you have your own form, you need to enter the wizard, but if I do that it's just going to add all that extra code isn't it?
Also, if I use Dreamweaver's Spry Validation, will this interfere with the original elements of the form?
