Hi guys, quick question, I've found out the combo 'FormField+widget' does not solve my flexibility needs (actually, my semantic markup guy's needs), so the same form rendered in different contexts uses different markup for its widgets (tags and classes), so instead of using the field's widget, I wrote a few tags that get the BoundField as first argument and render it as appropiate using a custom template. So I thought, wouldn't it be cleaner for everyone to have their 'widgets' belong to the 'template/templatetags' domain rather than belong to the 'customfields/customwidgets' domain? That way it also seems to be easier for my guys to write widgets themselves (since they can leverage what they have learned using the templating system, and is less intimidating than concatenating strings in python)
Just want to hear how (If) this is wrong from the current development perspective, and if anyone remembers (and has a link) to a discussion related to widgets. (My "mad google skillz" aren't yielding any satisfactory results) So far my approach will still work as long as BoundField's public interface doesn't change, but I also would like to hear if anyone has done the same and wants to 'unify' a 'widgets in templates domain' library. So far I have equivalents for all current widgets and a few as_p and as_table widgets. (that recieve N forms and include the enclosing <p> or <table> tags. best regards ----nubis :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
