Phillip J. Eby wrote:
It's certainly *possible*, if perhaps not advisable for user-level
control on a per-item basis. We would have to have additional fields
to *store* that choice, for each field that allows a choice, on every
single item.
However, it's definitely possible for individual kinds to do this
programmatically on a per-item basis (e.g. by detecting whether a
message is outbound or inbound), which is probably more useful in the
short term and doesn't impose any additional storage overhead.
I also think that what Mimi is talking about is more of a user-level
(i.e. view-level) issue than a model-level issue. Perhaps the view could
annotate the model to indicate which attributes it cares about?
In fact, I kind of wonder if this whole concept of who/about/etc is
really a view-level annotation on specific kinds.
(I'm not wed to this idea, but I thought I'd throw it out there)
Alec
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
