> > AFAIK in Django, the admin tool properties are defined right in the model. > > I'm not sure what's "the right way" for it, but I kinda like the django > > approach, because it's really a "model" properties. In other hand, we could > > have different setups for different admin controller subclasses in the > > applications. Need to think about it more. > > Yes, I wondered about putting more stuff in the model to define how > you want to be able to view it, but it feels wrong to me - the model > feels like it should be a generic data structure without view specific > stuff in there too.
FYI they are actually moving these options/properties out of the model class, instead using a separate options subclass : http://code.djangoproject.com/wiki/NewformsAdminBranch --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
