Split plugins as well?

tim Rowledge tim at rowledge.org
Thu Oct 20 17:05:34 UTC 2005


On 20-Oct-05, at 1:48 AM, Cees De Groot wrote:

> On 10/20/05, tim Rowledge <tim at rowledge.org> wrote:
>
>> This is an illustration of the simple truth that a trivial
>> hierarchical separation isn't adequate for all cases. The answer is
>> that the Files team will have to negotiate with the VM team to agree
>> on the relevant apis.
>>
>
> That's one option. Is there anything big against the other option,
> that the VM team 'lets go' of individual plugins? I mean, less work
> for them! ;)

I think the practical issues would probably prevent that working. The  
plugin code for many plugins has strong tie-ins to platform files and  
all of them have to live cleanly in the VM code world. There are a  
few I could imagine splitting out ok (modulo both sides actually  
managing to work together successfully) such as the crypto, klett,  
replugin and a few other possibles. These have no platform dependence  
and aren't core system parts, so it might work. On the other hand,  
keeping them in the one place would mean they get compiled every time  
and that might help with keeping them up to date.


tim
-- 
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim





More information about the Squeak-dev mailing list