Re: FormBuilder: field rendering options

Hi,

Now back to your original question. I'm still not sure that there are enough examples where the specific QF type needs to be specified. Given all of the above can you still think of any other times you would want to change a type where you wouldn't have to do extra configuration? For an autocomplete, for example, you have to specify the autocomplete options. If you have to do this extra processing you might as well create the element as well.

I notice that you advocate using post- and pre- GenerateForm, which is IMHO not what the FormBuilder should be - it should try to be as intelligent and as much as developer-friendly as possible while at the same time not becoming bloated with unnecessary functions. My ideal is to get FormBuilder build complex forms without writing long pre and post Generate procedures, which sometimes really makes using FB at all pointless. Writing few lines for a password field each time you need one is not in nature of code reuse. On the other hand, FormBuilder is very monolithic and is hard to subclass, so that I could implement the behaviour discussed without modifying the FormBuilder code. I didn't try out Structures_DataGrid, but how does this package deal with these issues when displaying a DBO? Does it, for example, display 1 and 0 for boolean value or a regular checkbox? Please have in mind that some people are developing heavy form-driven applications with forms containing up to 20 fields (arranged in a friendly UI, of course ;-) that would drastically benefit from such a behaviour. Esad