Talk:Tux Paint

From OLPC
Revision as of 12:51, 26 January 2008 by AlbertCahalan (talk | contribs) (2.5 year old tux user)
Jump to: navigation, search

Tantrum

Are you seriously going to throw a tantrum over the GUI? What happened to the dedication you had when you started? --Basique 15:02, 27 June 2007 (EDT)

I think calling tantrum is silly. To the developer: If you don't want to use the full Sugar-style interface, don't! One of the marking features of tuxpaint is the colored-cartoonish interface and talking tux, and I agree that it just wouldn't be tuxpaint otherwise. I think tuxpaint is really nice, my nephews have had fun with it in the last 2 years, and I would love to see it available to kids owning XO's, in whatever shape it takes.HoboPrimate 16:36, 27 June 2007 (EDT)
Call it that if you wish, but I don't see how I'm supposed to deal with undocumented volatile interfaces. Reverse engineering can be fun at times, such as when an "enemy" has provided a binary blob. It's not fun when a "friend" has dumped a huge pile of barely-commented Python at me and called it documentation, with things changing as I work. In the former case I find a challenge. In the latter case I only find misery. There are small signs that the documentation situation might be changing, so there is hope. It's still completely stupid and absurd that a normal 1200x900 full-screen app can't just run though. BTW, because of the hardware spec change, I no longer have any idea how Tux Paint will perform on the production machines. This matters because a full-featured Tux Paint is right about at the limit; I do not wish to chop out features unless required. Much of my early effort was wasted on chopping out features while the hardware spec change was still secret. AlbertCahalan 00:17, 13 August 2007 (EDT)

demo/example app

There is a simple demo/example app (plain C and Xlib) linked from my user page. If that were to work OK with Sugar, then there would at last be code that people could learn from. Tux Paint and other native apps would become much easier to port. AlbertCahalan 00:17, 13 August 2007 (EDT)

update : remove CVS dirs

the current -1.xo contains the CVS directories in every subdir; you may want to remove them and repackage. --Sj leave me a message 23:47, 30 December 2007 (EST)

Oh, and this is just awesome; as is the "sugarize" activity. --Sj leave me a message 23:53, 30 December 2007 (EST)

Nifty!

I've been looking forward to this. Thanks!  :) MitchellNCharity 11:04, 2 January 2008 (EST)

Adding collaboration

It appears the sugar api is stabilizing somewhat. So it might be plausible to consider adding collaboration and other sugarization, with less cruft and pain that previously required. There are a couple of trac tickets re improving/simplifying the api for collaboration, but I was unable to find them just now to check their status. Things will no doubt continue to improve, and so at some point, should eventually become straightforward. MitchellNCharity 11:20, 2 January 2008 (EST)

Please start by describing how sharing ought to work. Is simultaneous editing actually desirable? (never minding that it may be very difficult to implement) Is there something else that makes more sense? AlbertCahalan 21:49, 7 January 2008 (EST)

I'd be interested in helping with such sugarization given some pointers.... PDS

canvas size

Tux Paint normally only supports one canvas size. This is because many children struggle with scrolling and zooming, and because any dead space on the screen might be confusing. Any ideas for providing the features without causing trouble for the little ones? Note that there are some Tux Paint users who have yet to meet their second birthday. AlbertCahalan 21:58, 7 January 2008 (EST)

2.5 year old tux user

My daughter is an older tux paint user (by some standards) at 2.5 years old - tux is her favorite thing to do on the XO. The rest of the apps are good, but a bit beyond her as of yet. As there are kids in her daycare in Canada that function on her level at age 4, i suspect there are those in the developing world especially who function at the same level as my daughter at age 6. (but that will change for some of them because of this _education project_:) that said, i can see tux has a place on the XO just as it is - and i encourage the developer to continue to resist features that may complicate things for this user group. Keep up the good work!

Now my wish list - 1. a way to disable the frame that comes when the mouse hits the top corner 2. something isn't right with the scroll buttons for the stamps. it gets stuck on I think. 3. how about a way to toggle through the stamps/colours/etc using arrow keys (next to the monitor, not on the keyboard) this might be friendlier to little fingers as the stamp buttons are a little small (even for me). 4. the final wishlist is actually directed at the OLPC foundation itself - my girl is constantly trying to press the buttons on the screen - how about a touch screen? (I know, i know, budgets  :)

The frame causes problems for my daughter too. She is 2.5 years old, rather bright, and not very experienced with computers.
Scrolling is normally done with a scroll wheel, but the XO has none. The button sizes were originally done for a 640x480 screen, where they were huge.
Hopefully the game button presses are passed through the SDL library somehow. If not, getting at them will be difficult.
Touchscreens have been planned, but I hope it never happens. Sunlight-readable mode won't work well if the screen is all scratched up. Screens will tend to break if kids are encouraged to poke at them.