Well, after a long time of work on it, I've committed a new version of django-values, incorporating feedback from the previous discussion on the topic[1]. There's still a little work I'd like to do on it, but it's very functional right now, and ready for use and testing by anyone who's interested..
http://code.google.com/p/django-values/ The syntax has changed a bit to incorporate some of the concerns that were raised. Values are provided on subclasses of a new class, values.Options. This class can then be instantiated either in the main module or in an individual module. A single declared Options class can be instantiated multiple times, even in multiple modules, and each instantiation will be able to store a different value. The rest is mostly code cleanup, but it's much easier (for me) to work with now. So anyone with mroe ideas, feel free to bring them up! -Gul [1] http://groups.google.com/group/django-developers/browse_thread/thread/d79bec0a8ed29f7/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
