I'd like to integrate the optgroup tag
(http://www.w3schools.com/tags/tag_optgroup.asp) into the FilePathField
(which would in code would lead to this being tacked onto the
SelectField object) and want to get people's thoughts before writing
the code.
My thought would be that:
NAME_CHOICES = (
('Male', (("John", "John"), ("Steve", "Steve"))),
('Female', ("Jane", "Jane")),
('?', "Unknown")
)
would produce:
<optgroup label="Male">
<option value ="John">John</option>
<option value ="Steve">Steve</option>
</optgroup>
<optgroup label="Female">
<option value ="Jane">Jane</option>
</optgroup>
<option value ="?">Unknown</option>
The main reason this functionality is desired is for the FilePathField.
When recursive = True, it would be nice if the directories would be
displayed inside a optgroup-enhanced select tag. If the directories go
more then 2 directories deep, I assume it would be best to revert back
to the regular method, displaying all the files in a single
non-optgroup enabled list, since it appears that only IE 5 for Mac
supports multi-nested-optgroups
(http://www.netmechanic.com/news/vol4/html_no20.htm).
Any comments/thoughts/enhancements? If you don't like this, is there
another way of doing this without mucking up the predefined objects?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
