[sugar] code contributions to Sugar (was Re: Sugar Clock)

Eben Eliason eben.eliason
Wed Oct 15 11:56:07 EDT 2008

On Wed, Oct 15, 2008 at 4:30 AM, Tomeu Vizoso <tomeu at tomeuvizoso.net> wrote:
> On Tue, Oct 14, 2008 at 9:27 PM, Benjamin M. Schwartz
> <bmschwar at fas.harvard.edu> wrote:
>> P.S. I think this is a good example of why contributing to Sugar is
>> necessarily hard.  Many small technical contributions from the community
>> require significant policy decisions by the leaders.  When Sugar's
>> subsystems are as mature and rationalized as the kernel's, then perhaps we
>> will be able to add small components without needing big decisions, but
>> that point is still years away.
> Anybody has ideas about how we could improve this? One thing that may
> help is the recent refactoring that Marco made in the shell. Adding a
> clock widget to the frame is now a matter of dropping a .py file in
> the extensions/deviceicon directory. What else needs to happen?

Are you sure that's all? ;)  We should likely support dropping in a
directory as well, so that an icon can be packed in along with the
.py.  We don't want every extension to require the author to hack
artwork also.  Icons should only be in artwork if they are a) part of
the core OS or b) potentially useful to many activities. Extensions to
the devices, the home layouts, control panel modules, and anything
else that we'd like to support should include all necessary components
in a self-contained way.

But this is a great start!

- Eben

> Regards,
> Tomeu
> _______________________________________________
> Sugar mailing list
> Sugar at lists.laptop.org
> http://lists.laptop.org/listinfo/sugar

More information about the Sugar-devel mailing list