I should also add that I haven't changed the name yet. I've opted for the name Options to describe a collection of values that can be applied to a module or model, but I'm not sure how to best name and describe the framework as a whole. Google Code won't let me change the URL from django-values, but I can change any of the rest of it once I settle on a name. Any suggestions?
-Gul On May 9, 10:48 pm, Gulopine <[EMAIL PROTECTED]> wrote: > 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... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
