On Fri, Nov 7, 2008 at 5:24 PM, Eben Eliason <[EMAIL PROTECTED]> wrote: > Subclassing makes sense to me (though I'm "just a designer", so don't > give me too much weight.) It seems that we could create a > CollaborativeActivity subclass, and perhaps even subclass that if > there are several common "types" of collaboration with different > setups. The easier it is for someone to get started with a > collaborative code base, the better, in my opinion.
One of the 0.84 goals for Activity is to reduce the amount of code we import and run when the activity doesn't use all the class functionalities. Also we want modules to be imported more lazily. I'm sorry that I don't have a clear direction to point you to yet, I need to think about it more carefully, I just started measuring this week. But I thought it was worth to point this out... Marco _______________________________________________ Sugar mailing list [email protected] http://lists.laptop.org/listinfo/sugar
