[Dev] Re: redirect and Who, About and Date

Mimi Yin mimi at osafoundation.org
Wed Mar 8 16:58:14 PST 2006

I guess what I'm asking is:
Can we store a different Who attribute on a per-item basis?

Within a single view (e.g. the Dashboard), can we have 2 incoming  
items and for one of them, feed the <From: attribute> to the <Who:  
attribute>; and for the other one, feed the <To: attribute> to the  
<Who: attribute> for another one. In other words, can we allow the  
user to over-write whatever logic we specify in the Python code to  
feed attribute into the Who: column? There wouldn't be any computed  
attributes involved.

This isn't a requirement, I'm just asking to understand where the  
boundaries are.


On Mar 8, 2006, at 4:45 PM, John Anderson wrote:

> Mimi Yin wrote:
>>>> + Could a user change which attribute to feed into the explicit  
>>>> Who attribute? e.g. Show To: instead of From:
>> Hmm, might there be a way for an end-user to force the view to  
>> display something different? ie. Delete To: John and replace it  
>> with From: Mimi. Or right click on the cell and choose which Who- 
>> type attribute to display. (Not necessarily for 0.7.)
> If I understand you correctly, the simplest way I can think of  
> doing something like this would be to do the equivalent of adding a  
> new column with the new attribute.
> We run into problems whenever we try to make these attributes  
> "computed only", e.g. not stored in the repository (because search  
> only works for things stored in the repository); or when we store  
> them in the repository and we need to change all the values when  
> the view changes (potentially a slow operation).
> John

More information about the chandler-dev mailing list