On Tue, 2007-06-05 at 12:00 +0400, Ivan Sagalaev wrote: > Malcolm Tredinnick wrote: > > What I'd like to see us do is move "editable" out of the model field > > declaration entirely as part of newforms-admin. It's presentation > > related > > I disagree with this specific point. "Editable" is useful to distinguish > calculated (or automatically produced, if you prefer) fields from those > set by a user. A form can have its own logic to show/hide/process fields > but this "editable" thing has a strong data-related semantics
No. It has strong "user created semantics", which are orthogonal to the data itself. The number "4" exists as a piece of data, irrelevant of whether it was created by a user, a machine or a bunny rabbit. The database doesn't care. Code using that data doesn't care. It is not part of the meaning of the data. > and it > is used in forms as a hint very conveniently as much as form uses field > types to pick up a right widget. Which is why I pointed out that people can very easily create a tuple of fields they would like to be editable as part of automatically created forms and then use that to create the forms. It's only half a dozen lines of code to do so. We aren't removing functionality here. We are only removing information that is tied to one specific presentation (and only one -- so it's already a flawed concept as it's useless for saying "editable on this form, but not on this one") from the data definition. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
