[Chandler-dev] Re: DefaultValue on displayName: not yet

[Morgen Sagen]

To summarize what we're doing about this:

- Assigning a defaultValue to displayName breaks some sharing code  
which maintains backwards compatibility with existing shares
- Removing that sharing code would be required in both trunk and  
branch, could cause alpha4 instability, and would break existing shares
- Assigning a defaultValue isn't really required anyway, as we can  
change the code which was relying on getItemDisplayName( ) to, in  
essence, provide a default
- When we move to the new EIM-based sharing, and the old sharing code  
is removed, we can re-assess whether displayName needs a defaultValue
- I've already removed calls to getItemDisplayName( ) from my code,  
and now John and Bryan are removing the rest
- Andi can then remove the getItemDisplayName( ) API altogether

On Nov 20, 2006, at 2:06 PM, Bryan Stearns wrote:

> In IRC last Thursday (at 15:18 in http://wiki.osafoundation.org/ 
> script/getIrcTranscript.cgi?date=20061117), I offered to add a  
> defaultValue (u"") to ContentItem.displayName... unfortunately, I  
> ran into problems:
>
> - TestXMLCompatibility.py failed because it still thinks that mail  
> messages have a 'subject' attribute, though we now redirect it to  
> displayName.
>
> - It appears that there are several places where 'subject' is  
> special-cased in osaf/sharing/formats.py.
>
> - Getting rid of 'subject' looks like a sharing-format change?
>
> Because I haven't been able to figure out how to fix the special  
> cases, and since this isn't in the way of any of my alpha5 stuff,  
> I'm going to punt on displayName's defaultValue for now. If you  
> (Morgen) want to take a shot at this along with the other sharing  
> format stuff that's coming up, that'd be great...
>
> ...Bryan
>