> I think we might have discussed this before, but the discussion > fizzled out. What would you want to style -- the form HTML tag itself? > The <label>? The table row (in case of as_table())? > > Adrian
i'd like to see the data type classes from oldforms re-applied to the form elements in new forms. e.g. class="vIntegerField", class="vEmailField". these were great as they allowed differently sized field elements depending on the data type. e.g. you might want a textarea tag to be wider than an input text tag, you might want an input text tag for an email address to be wider than an input text tag for an integer or date. if people don't want to make use of these, they can ignore them, but i don't see the harm in having them in there as hooks, besides a few bytes in html size. if that's a problem, they could be switched on or off in settings.py or when the form.as_* and field.as_* methods are called. not having these hooks appears to be a fairly significant departure from the oldforms functionality, so i'd like to see it removed only after some consideration. as for the "error" and "required" classes being applied to the field containers, i'd like to see these renamed to something less generic and more form-specific. people may already have generic error or required classes defined that they don't particularly want to apply to the containers of forms with errors. "vError" / "vRequired" or "form- error" / "form-required" or something similar would work for me. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
