[Dev] Item Collection Spec 0.1

[John Anderson]

Phillip J. Eby wrote:

> At 01:54 PM 6/2/2005 -0700, Ted Leung wrote:
>
>> On Jun 2, 2005, at 1:38 PM, John Anderson wrote:
>>
>>> Phillip J. Eby wrote:
>>>
>>>>
>>>> I'm wondering about the "post(sourceItem, targetItem, methodName,
>>>> Event)" API; wouldn't it be simpler just to pass a callable, i.e.
>>>> "post(sourceItem, targetItem.someMethod, event)"?
>>>
>>>
>>> If I'm not mistaken, this information needs to persist and I don't
>>> think the repository has a datatype that persists a callable.
>>
>>
>> Yes, persistence is the reason.
>
>
> Okay, I missed that bit, probably because it's not really tied in to 
> the rest of the spec.  Why is it persistent?  How does that relate to 
> the use cases there?  I didn't get that part at all.  In what view(s) 
> is the event invoked?

If it's persistent it's simpler -- both because of how items work, and
because you don't need to add and maintain code that initializes it when
Chandler starts.

>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/dev
>