[Adium-devl] Ticket #4501

[Chris Forsythe]

On Dec 9, 2007, at 10:10 PM, Colin Barrett wrote:

> On Dec 9, 2007, at 12:28 PM, Peter Hosey wrote:
>
>> On Dec 09, 2007, at 11:18:24, Chris Forsythe wrote:
>>> Users go into plists all the time...
>>
>> Sure, if they're user-visible. Not so often when they're wrapped in
>> bundles. And when they are wrapped in bundles, the user generally
>> shouldn't be digging around in there in the first place.
>>
>> I can imagine a user having to go in there on our instruction,
>> though, and extended attributes would make that much harder. So if
>> nobody has any case for xattrs, I say we go with a plist.
>
> Why have a bundle when one is not needed?
>

I think it's needed. I think extended attributes isn't worth our time  
when we have plists.

> Extended attributes are easy to set. Search ADC. They are inspectable
> from Terminal by using the xattr(1) command.
>

ya, users are going to do that a lot.

> What good reason do we need a bundle for? Just seems like a bunch of
> code that is unneeded to me.
>
>

What are we actually talking about here, 100 lines of code  
difference? 200?

Bundles are appropriate as it's a single file that we have a level of  
control over, and they provide us with a way to present a incomplete  
download to the user that doesn't make them get as confused as 2  
separate files. In my opinion, from the way Jordan described it, that  
method is just plain bad compared to the elegant bundle.

It's worth the code difference imho.

>
> It's also not very clear what use cases we are aiming to support,
> here. Maybe we should agree on those first, and THEN figure out how we
> want to implement it?


This point is moot, both methods are trying to achieve the same  
result but with different presentations. I'm pretty sure that we've  
covered this already..

Chris