[sugar] Modularizing activities

Marco Pesenti Gritti mpgritti
Wed May 7 16:19:30 EDT 2008


On Wed, May 7, 2008 at 10:17 PM, Bernie Innocenti <bernie at codewiz.org> wrote:
> [cc += sugar]
>
>  Marco Pesenti Gritti wrote:
>
> > I like these ideas very much... I'm not sure about the separation of
> > sugar core and activities though. I tend to think we should have a
> > unified release process for them (at least on the short time) and
> > having two different trac would probably make it harder.
> >
>
>  The Linux kernel keeps all drivers in the tree because this is
>  the only way you can quickly change internal interfaces without
>  the burden of backwards compatibility.
>
>  Xorg modularized too much, and now every time they refactor the
>  server all drivers break and some remain broken for 6 months or
>  longer.
>
>  Sugar might be different: there could be very little shared code
>  between the shell and the activities.  Communication is mostly
>  dbus based, and protocols are notoriously much easier to keep
>  stable than APIs.

I expect API to change quite a bit for a while (in a compatible way).

>  All considered, I think that keeping a core group of activities
>  with the rest of Sugar would be a good idea.  This is also what
>  KDE and Gnome do.

I agree.

Marco



More information about the Sugar-devel mailing list