Re: Features added to QuickForm

"Bertrand Mansion" <bmansion@mamasam.com> wrote in message news:8DDF2CFA-DAE3-11D5-B411-00039311F000@mamasam.com... > Jonas Delfs a écrit : > > I'm using QuickForm to create HTML forms and found some missing features > > that I've now added: > > > [snip added features] > > > > The new and better QuickForm.php is to be found on: > > http://delfs.dk/QuickForm.php > It is pretty pretentious to call it better I think !?! It's the same class just with a few extra features. That's all. Sorry if I didn't form the sentence right. > Excuse me, but I believe it is quite > stupid to add $bgColor or $bold to addHeader(), why not add $red, or > $small, ... Because you've chosen one way to style forms, which is too bound for me. All i wanted to do was to let people decide a little more when it comes to the presentation of the form. But still, I could not just dump the current way of styling cause people is probably already using the package. > Maybe, instead of that, you should add a new $attributes > parameter (converted by HTML_Common) which will pass your bgcolor stuff > (or even the css class you want to use). Yeah, good idea, but am i allowed to dump the current way of styling (align=right, font-weight: bold) in favour of providing a less tied way of presenting the generated form? > The real missing thing for now is the ability to parse form elements and > to return them as an array (which could then be processed by the parser > you want to use : ITX, Smarty, XML, HTML_Table...). If you could come up > with a good idea on how to do this, that would be great ! To answer that question I need to know: what do you excatly mean that either IT[X], HTML_Table or any other non-form-package should do with this array? -and would you pleasy clarify what array you want to get out of it? > > I also have a few comments to the original developers of QuickForm: Why > > is > > HTML-kode in uppercase? -XHTML standards says in lowercase. > Personally, I don't care about XHTML, but I can understand some people > do. > Do you think the validation javascript should be treated as containing > #PCDATA ? Sorry, what? > Maybe some day Adam will modify his HTML_Common class to throw > lowercase, but really, this is just a detail. Tell me why this is so > important ? It could be nice with XHTML complient output (lowercase tag names, qutoed attributes, etc.) Actually it's not the attributes-strings thats in uppercase, but just regular HTML-tags like <TD>. If it all ends up in me making some ajustments that you will accept, is it ok. if I change HTML to lowercase? > About your last point I don't get what you are talking about. Could you > give an example please. First, why not let your brilliant Table-class do the boring job of putting elements in tables? Last, if I add an element of the type checkbox (or radio) to my form, the specified label gets displayed both just infront of the element and just after it. That doesn't look good. Only when the element is a part of an element-group, the label should be displayed after the element. I've thought of an solution to this, but ended up by deciding that you'd might be the best to find out how this is done easiest and most pretty. -- Mvh./Best Regards Jonas Delfs, http://delfs.dk