[Sugar-devel] [IAEP] Paint improvements?

[Aleksey Lim]

On Thu, Jul 09, 2009 at 12:07:11PM -0400, Ton van Overbeek wrote:
> On Thu, Jul 9, 2009 at 11:46 AM, Aleksey Lim<alsroot at member.fsf.org> wrote:
> > On Thu, Jul 09, 2009 at 07:28:09AM -0500, David Farning wrote:
> >> On Wed, Jul 8, 2009 at 5:41 PM, Aleksey Lim<alsroot at member.fsf.org> wrote:
> >> > On Wed, Jul 08, 2009 at 06:26:00PM -0400, Caroline Meeks wrote:
> >> >> Nod, I've done that for Memorize and maybe we will for Paint too.  It will
> >> >> take some thought to get it right and I've got a lot on my plate right now.
> >> >> Worth it if it turns into code but right now I'm wondering what is the best
> >> >> path forward? Sugarizing Tux, Improving Paint or adding features to Colors?
> >> >> It mostly depends on what programmers out there are interested.
> >> >
> >> > If Tuxpaint satisfies all needs and new features list for Paint and
> >> > Colors! is not short, I guess its much easier to add save-to-journal
> >> > feature to Tuxpaint.
> >> >
> >> I am in occasional contact with Bill Kendrick the lead developer for
> >> tuxpaint.  I try to reach out to him and the rest of the tuxpaint team
> >> to work more closely with Sugar Labs.
> >
> > The save-to-journal feature shouldn't be a problem(since this will be
> > local change in Tuxpaint's code).
> >
> > The relly hard problem is sharing mode in Tuxpaint.
> >
> > There is a ticket for this reason - #887
> >
> > --
> > Aleksey
> 
> As someone who has hacked on Albert Cahalan's original XO-1 port of Tuxpaint
> (see the tuxpaint entry on http://wiki.laptop.org/go/Activities/All)
> I'd be glad to help
> with further sugarizing tuxpaint.
> What I did was to adapt it to the rainbow requirements for the XO-1 (store
> data in the right directories, etc.) and proper startup from the ring.
> No integration with the journal or implementation of sharing.
> 
> Note that a full installation of tuxpaint is very big, due to all the
> examples and translations. Probably too big for a 1G stick SoaS.
> 
> Aleksey, what are your ideas about integration with the journal? Provide
> a python glue layer? Or implement it directly in C?

I kept in mind implementing it in Tuxpaint's code in C, since DS API is just
dbus API(the good example is etoys) but I didnt think about it yet.

> Anyway, let me know what I can do.

maybe implementing save-to-Journal feature ;)

if you are interested in sent me your nick on git.sl.o and I'll add you
to commiter list of http://git.sugarlabs.org/projects/tux-paint.
I keep upstream code in "upstream" branch(now its 0.9.20), you would
want to switch it to new release or trunk, then just rewrite upstream
branch(I guess its not worth keeping all upstream commits)

-- 
Aleksey