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.
- Eben On Fri, Nov 7, 2008 at 7:41 AM, Morgan Collett <[EMAIL PROTECTED]> wrote: > I want to push some of the code required for sharing into > sugar-toolkit, for example: > > def _list_tubes_reply_cb(self, tubes): > for tube_info in tubes: > self._new_tube_cb(*tube_info) > > If I put this directly into sugar.activity.activity.Activity, then all > activities will gain the code which might impose some overhead. > > Alternatively I can subclass Activity to SharableActivity or something > like that, and add the telepathy/tubes helper code in there. > > Thoughts? > > Regards > Morgan > _______________________________________________ > Sugar mailing list > [email protected] > http://lists.laptop.org/listinfo/sugar > _______________________________________________ Sugar mailing list [email protected] http://lists.laptop.org/listinfo/sugar
