tuxpaint-devel — General discussion list for Tux Paint developers

Re: [Tuxpaint-devel] Where are the current Tux Paint manuals?

[Bill K. <nb...@so...>]

On Mon, Mar 05, 2007 at 08:24:08PM -0800, Robert Elliott wrote:
> Where are the current manuals?   I have found the documents located at
> 
>      http://www.tuxpaint.org/docs/html/EXTENDING.html
> and
>      http://www.tuxpaint.org/docs/html/OPTIONS.html

Hi Robert!  Those should be the from the latest release (cur. 0.9.16).
The CVS repository would have the absolute latest, of course:

  http://tuxpaint.cvs.sourceforge.net/tuxpaint/tuxpaint/docs/


> but these still have old information. (The "Extending" page says starters
> are 192 pixels and 104 pixels less than the window size.)

Eep!  That should be 192 and 128, I believe.


>    Is there a WIKI site (such as Wikibooks) where people can contribute to
> the Tux Paint manual to keep it up to date?

Currently, no.  Right before our baby was born, my wife and I were posting
on the newly-created "tuxpaint-docs" list, a place for volunteers to come
together and help rewrite Tux Paint's docs... both in terms of content, and
format.

Been a pretty quiet list since the birth.  Cc'ing the list to hopefully
spark some activity/interest. :^)


>    (Note: "_mirror" works great for stamps but I cannot get "_flip" to work.
> Are you sure it really works?)

Hah!  Apparently, no!  Ack, sorry!  I'll file it as a bug over at SF.net
right now.

Thanks!

-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/

Re: [Tuxpaint-devel] [SDL] Full screen mode disabling screensaver?

[Torsten G. <wi...@sy...>]

Hello !


> Sounds like SDL is disabling screensaver while in fullscreen mode.
> Is that by design?  Any way around that?  Any reason to avoid turning on
> the screensaver?

+++

	/* Save DPMS and screensaver settings */
	X11_SaveScreenSaver(SDL_Display, &screensaver_timeout, &dpms_enabled);
	X11_DisableScreenSaver(SDL_Display);

+++

Yes it is disabled by SDL. Maybe to get sure not loosing context
or so.

> (Maybe I should add a simple screensaver to Tux Paint itself after
> an extended amount of inactivity...?)

You could make some adverts there for Tux4Kids :-)


CU

[Tuxpaint-devel] Full screen mode disabling screensaver?

[Bill K. <nb...@so...>]

Someone recently contacted me about Tux Paint with this problem:

  I'm running Tuxpaint 0.9.15b on Ubuntu 6.06.  It is
  running in full screen mode.  After the kids quit
  playing  with Tuxpaint (and leave it running) my
  screensaver fails to activate.  I looked in the
  configuration file but see no mention of any settings
  there.

Sounds like SDL is disabling screensaver while in fullscreen mode.
Is that by design?  Any way around that?  Any reason to avoid turning on
the screensaver?

(Maybe I should add a simple screensaver to Tux Paint itself after
an extended amount of inactivity...?)

-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/

Re: [Tuxpaint-devel] OK to subscribe tuxpaint lists to gmane?

[Bill K. <nb...@so...>]

Steinar - yes, I think it should be fine.  I believe the libSDL mailing lists
are gatewayed to Usenet via Gmane as well.  Some people prefer usenet or
forum interfaces over lists they have to subscribe to, so I think it's a
good idea.

tuxpaint-devel list -- anyone have any objections?

-bill!


On Sat, Feb 24, 2007 at 04:17:50PM +0100, Steinar Bang wrote:
> Hi!
> 
> Would it be OK if I asked that the tuxpaint mailing lists be
> subscribed to the mail<->news gateway at http://gmane.org/?
> 
> gmane is run by USENET veteran Lars Magne Ingebrigtsen, and takes care
> to be as non-intrusive to the mailing lists it gateways as possible,
> as well as providing heaps of spam prevention features (check the
> above mentioned web site for info on this).
> 
> Bonuses from your point of view would be a searchable, noise free (ie.
> no spam, unsubscribe, virus, or other cluttering messages) mailing
> list web archive, and the possibility to read the mailing list from a
> newsreader.
> 
> The web archive has two views.  A newsreader like web interface, and a
> blog-like interface with list-owner CSS customization possibilities.
> It can also send out the group as an RSS feed.
> See http://dir.gmane.org/gmane.discuss for an example of what's
> available. 
> 
> The newsreader interface does also have the noise level reduced, since
> all messages that get there will first has to pass a virus scanner,
> and then pass through SpamAssassin.
> 
> Thanx!
> 
> 
> - Steinar
> 
> 
> 
> 
> 

Re: [Tuxpaint-devel] Makefile updated to fix building for Maemo

[Alessandro P. <apa...@gm...>]

2007/3/12, Bill Kendrick <nb...@so...>:
>
> On Mon, Mar 12, 2007 at 10:56:43AM +0100, Alessandro Pasotti wrote:
> > I don't think I have CVS access to tp repositories, you can find the
> full
> > sources of my tp port here (it includes maemo hildon menus, icons and
> debian
> > stuff):



I will send you a tarball with only the files needed to build the deb.

A diff on the sources doesn't make sense, since my modifications (if I got
it right) are already in the trunk (they are more or less the same of the
OS2005 version) and the diff would be with an old tp version.



Give me your SourceForge username if you'd like.



el_paso


-- 
Alessandro Pasotti
w3:   www.itopen.it

Re: [Tuxpaint-devel] Makefile updated to fix building for Maemo

[Bill K. <nb...@so...>]

On Mon, Mar 12, 2007 at 10:56:43AM +0100, Alessandro Pasotti wrote:
> I don't think I have CVS access to tp repositories, you can find the full
> sources of my tp port here (it includes maemo hildon menus, icons and debian
> stuff):

Give me your SourceForge username if you'd like.


> http://www.itopen.it/wp-content/tuxpaint-0.9.15b-1_armel_src.tar.gz

You could also send a diff :)


> I think I forgot to add libsdl ttf dependency, but if text tool is removed
> maybe it is not needed anymore.

SDL_ttf is used to render all of the UI! ... text tool, or not!

Thx,

-bill!

Re: [Tuxpaint-devel] Makefile updated to fix building for Maemo

[Alessandro P. <apa...@gm...>]

I don't think I have CVS access to tp repositories, you can find the full
sources of my tp port here (it includes maemo hildon menus, icons and debia=
n
stuff):

http://www.itopen.it/wp-content/tuxpaint-0.9.15b-1_armel_src.tar.gz

I think I forgot to add libsdl ttf dependency, but if text tool is removed
maybe it is not needed anymore.


2007/3/12, Terje Bergstr=F6m <te...@te...>:
>
> Hi,
>
> I committed a Makefile patch to re-enable building latest tuxpaint for
> Maemo. I was supposed to do this earlier, but better late than never. Not=
e
> to others: Do not upgrade your Ubuntu to Feisty, because it breaks
> scratchbox.
>
> Alessandro, could you please commit your Debian control files to CVS or
> put them in some other public place. I would not like to recreate them to=
 be
> able to test latest tuxpaint on my N800. :-)
>
> Terje
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Tuxpaint-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
>
>


--=20
Alessandro Pasotti
w3:   www.itopen.it

[Tuxpaint-devel] Makefile updated to fix building for Maemo

[<te...@te...>]

Hi,

I committed a Makefile patch to re-enable building latest tuxpaint for
Maemo. I was supposed to do this earlier, but better late than never. Note
to others: Do not upgrade your Ubuntu to Feisty, because it breaks
scratchbox.

Alessandro, could you please commit your Debian control files to CVS or put
them in some other public place. I would not like to recreate them to be
able to test latest tuxpaint on my N800. :-)

Terje

[Tuxpaint-devel] Tux Paint runs on the B2 OLPC XO

[Albert C. <aca...@gm...>]

http://wiki.laptop.org/go/Tux_Paint

Be sure to view the second picture full-size. The diagonal lines are
not a camera-related artifact. The screen really does look like denim
cloth.

Re: [Tuxpaint-devel] hello, and hildon

[Alessandro P. <apa...@gm...>]

Sorry, I don't remember if the problem existed in 2005 edition, but since
they changed a lot of things in the 2006 release it's also possible the
problem arised in the 2006 edition.

BTW I've seen no code modifications that I've not (independently)
implemented in my port, in other words my OS2006 port and the OS2005 port
are almost completely equivalent in terms of code modifications (very few
lines indeed).

It's certainly more a problem of how the menu for hildon desktop is built
than a tuxpaint problem (many other ports are affected by the same issue),
see this post (the reply is form Eero Tamminem @ nokia . com):

> When the user press the hardware Home button, TuxPaint continues to run
> in the background and the user must kill it through a terminal with
> killall -9 tuxpaint
> or reset the device.
> I've tried unsuccessfully differente approachs (libosso), if you know
> how to solve this, please let me know.

Below is copy of my earlier mail to the devel list.
(I think the info is also in Maemo wiki somewere)
It tells how to get back to the application.


       - Eero

I spent a while debugging why I cannot switch back to SDL window
from which I've switched away, and noticed that it's actually
easy to fix.

Application switcher needs to know which window matches to which
.desktop file.  This is done using the standard WM_CLASS X property.
So, e.g. to be able to switch back to the Bomberman game, you
need to...

Add following line to Bomberman .desktop file for application switcher:
StartupWMClass=Bomberman

And ask SDL to use that WM_CLASS definition for the Bomberman game
window through an environment variable by adding following line
to the "launch-bomberman" script:
export SDL_VIDEO_X11_WMCLASS=Bomberman


I.e. only two lines need to be added and no actual code needs to
be changed!

---

Of course I tried this approach but it doesn't solve the problem.


-- 
Alessandro Pasotti
w3:   www.itopen.it

[Tuxpaint-devel] Where are the current Tux Paint manuals?

[Robert E. <r_e...@in...>]

Where are the current manuals?   I have found the documents located at

     http://www.tuxpaint.org/docs/html/EXTENDING.html
and
     http://www.tuxpaint.org/docs/html/OPTIONS.html

but these still have old information. (The "Extending" page says starters
are 192 pixels and 104 pixels less than the window size.)

   Is there a WIKI site (such as Wikibooks) where people can contribute to
the Tux Paint manual to keep it up to date?

   (Note: "_mirror" works great for stamps but I cannot get "_flip" to work.
Are you sure it really works?)

Robert Purser
 Wikiversity Instructor
  WikiU Film School

 r_p...@in...
http://en.wikiversity.org/wiki/filmmaking

[Tuxpaint-devel] Where are the current Tux Paint manuals?

[Robert P. C. U. <r_p...@in...>]

Where are the current manuals?   I have found the documents located at

     http://www.tuxpaint.org/docs/html/EXTENDING.html
and
     http://www.tuxpaint.org/docs/html/OPTIONS.html

but these still have old information. (The "Extending" page says starters
are 192 pixels and 104 pixels less than the window size.)

   Is there a WIKI site (such as Wikibooks) where people can contribute to
the Tux Paint manual to keep it up to date?

   (Note: "_mirror" works great for stamps but I cannot get "_flip" to work.
Are you sure it really works?)

Robert Purser
 Wikiversity Instructor
  WikiU Film School

 r_p...@in...
http://en.wikiversity.org/wiki/filmmaking

Re: [Tuxpaint-devel] hello, and hildon

[Bill K. <nb...@so...>]

On Mon, Mar 05, 2007 at 08:12:05AM +0100, Alessandro Pasotti wrote:
> The problem is somewhat more complex: it's ok that the home button drives
> the user to the desktop, it's wrong that the tuxpaint icon doesn't appear in
> the toolbar and the user cannot go back to tuxpaint.

Ok, thanks for clarifying.


> I tried several times to solve this issue (that happens also to other
> applications ported to the tablets) without success.

I thought Christian Hammond got that working in the OS2005 port...?

-bill!

Re: [Tuxpaint-devel] hello, and hildon

[Alessandro P. <apa...@gm...>]

2007/3/4, Bill Kendrick <nb...@so...>:
>
> On Sun, Feb 25, 2007 at 03:14:20PM +0100, Alessandro Pasotti wrote:
> > Mouse cursor can be easily avoided, it's just a matter of commenting a
> line
> > in the sources (or in the configuration file, cannot exactly remember
> where)
>
> I'll make a note to add a "--nomouse" option, which would be useful on
> other touchscreen devices.


Good!


<snip>
> > Other changes to the source are related to the screen size and disabling
> > text tools.
>
> The current version of Tux Paint supports pretty much any arbitrary
> screen size from 640-wide and up, and 480-tall and up.
>
> So on a 770, having a default config that sets it to 800x480 should be
> sufficient, wouldn't it?


Yes.


> Since AFAIK there is no GTK code in tuxpaint, there is no need to change
> to
> > hildon, the only good reason could be to implement text tools with the
> > hildon keyboard (and other hildon input methods).
>
> That'd be nice, down the road, if we can figure it out.
>
I also heard that there's a physical "Home" button on the device that
> the current (OS2006-compatible) release of TP does NOT recognize, so you
> have
> to go in and manually kill the app if you hit that button.  (This was not
> an
> issue in the build for OS2005.)



The problem is somewhat more complex: it's ok that the home button drives
the user to the desktop, it's wrong that the tuxpaint icon doesn't appear in
the toolbar and the user cannot go back to tuxpaint.

I tried several times to solve this issue (that happens also to other
applications ported to the tablets) without success.


-- 
Alessandro Pasotti
w3:   www.itopen.it

[Tuxpaint-devel] Tux Paint invited to Libre Graphics Meeting 2007, May 4-6 in Montreal, Canada

[Bill K. <nb...@so...>]

The Libre Graphics Meeting will be in Montreal, Canada this year:

  http://www.libregraphicsmeeting.org/

We've been invited to once again participate.  (Cedric Gemy was kind enough
to represent us in Lyon, France at last year's LGM.)

With a full-time job and a newborn, it's very doubtful I'll be able to
attend myself, but I wanted to extend the invitation to the other Tux Paint
developers and users.

Would anyone out here who is closer to Montreal like to attend on the
project's behalf? :)

Thanks!

-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/

[Tuxpaint-devel] No Text Tool (no fonts found?) on Mac OS X

[Bill K. <nb...@so...>]

Here's a bug recently submitted to SF.net:

  Text doesn't work at all
  http://sourceforge.net/tracker/index.php?func=detail&aid=1666078&group_id=66938&atid=516295

  Hello, I don't know if this is the same issue as the ASCII text thing
  someone emailed about, but on our computer the text button doesn't do
  anything. It flashes briefly when you click it, then the active button goes
  back to being the one which was active before you tried to select the text
  button. I'm running Mac OS X, v. 10.4.8, and the problem exists for the
  administrator and all other user accounts. Many thanks, Franklynw.

Another person emailed me about this same issue privately.  I've asked them
to run TP from the Mac's Terminal app, and send me any error output that
may come up.

In the meantime, any ideas?

-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/

[Tuxpaint-devel] Tux Paint cut-off print issue on Mac: works on in 640x480!?

[Bill K. <nb...@so...>]

I just got around to reading an email from January that said:

  The machines are OS X 10.3.9 with Tuxpaint 0.9.16. If you can give me any
  pointers or workarounds that would be cool! (Ok, I just found one. Set it
  to use a 640X480 window, and then nothing gets cut off.)

This is probably key to the printout issues...  is the Mac code assuming
a 640x480 canvas and scaling up?  (So in 800x600, for example, it gets
scaled TOO large?)

Thanks,

-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/

Re: [Tuxpaint-devel] A list of the Tux Paint canvas (and starters) size.

[Albert C. <aca...@gm...>]

On 3/4/07, Bill Kendrick <nb...@so...> wrote:
> On Sun, Mar 04, 2007 at 02:12:23PM -0500, Albert Cahalan wrote:
> > Maybe the answer is to run as 600x450, scaling the whole screen
> > up to 1200x900. The display is blurry anyway.
>
> Does the OLPC system handle this?  (e.g., if we have SDL ask it for
> a full-screen 600x450 display, will it scale it up?  Or will it end up with
> black borders?)

I was planning to handle it as Tux Paint updates the screen.
SDL would be unaware.

> Also, Tux Paint still needs tweaking before it can fit properly in <640 by
> <480.

Sure. The stamps and shapes can go.

Re: [Tuxpaint-devel] A list of the Tux Paint canvas (and starters) size.

[Bill K. <nb...@so...>]

On Sun, Mar 04, 2007 at 02:12:23PM -0500, Albert Cahalan wrote:
> Maybe the answer is to run as 600x450, scaling the whole screen
> up to 1200x900. The display is blurry anyway.

Does the OLPC system handle this?  (e.g., if we have SDL ask it for
a full-screen 600x450 display, will it scale it up?  Or will it end up with
black borders?)

Also, Tux Paint still needs tweaking before it can fit properly in <640 by
<480.

-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/

Re: [Tuxpaint-devel] A list of the Tux Paint canvas (and starters) size.

[Albert C. <aca...@gm...>]

On 3/4/07, Bill Kendrick <nb...@so...> wrote:
> On Mon, Feb 26, 2007 at 10:19:02PM -0500, Albert Cahalan wrote:
> > I'm wondering if this ought to be scalable in some way, either just the
> > non-drawing parts or the whole thing.
>
> I would like to make this more flexible, down the road, yes.
> (So you could have REALLY BIG buttons on a very high resolution screen,
> rather than having small buttons, and a ton of unused button slots.)
>
> For now, though, you're stuck with the 48x48s. :^/

Maybe the answer is to run as 600x450, scaling the whole screen
up to 1200x900. The display is blurry anyway.

Re: [Tuxpaint-devel] A list of the Tux Paint canvas (and starters) size.

[Bill K. <nb...@so...>]

On Mon, Feb 26, 2007 at 10:19:02PM -0500, Albert Cahalan wrote:
> I'm wondering if this ought to be scalable in some way, either just the
> non-drawing parts or the whole thing.

I would like to make this more flexible, down the road, yes.
(So you could have REALLY BIG buttons on a very high resolution screen,
rather than having small buttons, and a ton of unused button slots.)

For now, though, you're stuck with the 48x48s. :^/


<snip>
> There is also the matter of the beautiful Tux Paint appearance not
> being the specified style of ugly grey blocky shapes. Oh well though,
> there is not much sense using Tux Paint in the greyscale mode where
> the ugly style is kind of useful.

You could always replace the UI PNGs.  I was thinking, recently, that it'd
be nice to allow them to be themed, so you could have a high contrast
set of buttons, for low-sighted users, for example.

e.g.:  tuxpaint --uitheme highcontrast

where "highcontrast" is just the name of a subfolder in the UI data hierarchy.

-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/

Re: [Tuxpaint-devel] hello, and hildon

[Bill K. <nb...@so...>]

On Sun, Feb 25, 2007 at 03:14:20PM +0100, Alessandro Pasotti wrote:
> Mouse cursor can be easily avoided, it's just a matter of commenting a line
> in the sources (or in the configuration file, cannot exactly remember where)

I'll make a note to add a "--nomouse" option, which would be useful on
other touchscreen devices.


<snip>
> Other changes to the source are related to the screen size and disabling
> text tools.

The current version of Tux Paint supports pretty much any arbitrary
screen size from 640-wide and up, and 480-tall and up.

So on a 770, having a default config that sets it to 800x480 should be
sufficient, wouldn't it?


> Since AFAIK there is no GTK code in tuxpaint, there is no need to change to
> hildon, the only good reason could be to implement text tools with the
> hildon keyboard (and other hildon input methods).

That'd be nice, down the road, if we can figure it out.

I also heard that there's a physical "Home" button on the device that
the current (OS2006-compatible) release of TP does NOT recognize, so you have
to go in and manually kill the app if you hit that button.  (This was not an
issue in the build for OS2005.)

Thanks!

-bill!
bi...@ne...
http://www.newbreedsoftware.com/

Re: [Tuxpaint-devel] hello, and hildon

[Bill K. <nb...@so...>]

On Sun, Feb 25, 2007 at 02:05:44PM +0200, Terje Bergström wrote:
> I suggest we use the garage project Alessandro started to make the Maemo
> specific changes. Any changes that need to touch the tuxpaint code, should
> be committed to tuxpaint's CVS. Stuff like Debian control files, which are
> Maemo specific, could be hosted in the garage project's svn.

I'm happy having them in CVS as well.  We already have, for example,
an RPM .spec file.

-bill!

Re: [Tuxpaint-devel] A list of the Tux Paint canvas (and starters) size.

[Albert C. <aca...@gm...>]

On 2/26/07, Bill Kendrick <nb...@so...> wrote:

> In any case, the canvas size should be:
>
>   (window width - 192) x (window height - 128)
>
> The buttons are 48x48, and there are two columns of them on each side,
> so the canvas starts 96px in from the left, and ends 96px from the right.
>
> The Tux penguin text area, and color palette take up 128px at the bottom.

I'm wondering if this ought to be scalable in some way, either just the
non-drawing parts or the whole thing.

The OLPC XO uses a 7.5" 1200x900 display. For 1200x900 it's very blurry,
though it's fairly normal for a display of such physical dimensions.
(like TV, effectively somewhere around 400x300 to 693x520) Fine patterns
and thin lines along an upper-right to lower-left axis tend to show
severe color artifacts. The color gamut is also compressed, and usually
the display is run with 5 bits/channel.

There is also the matter of the beautiful Tux Paint appearance not
being the specified style of ugly grey blocky shapes. Oh well though,
there is not much sense using Tux Paint in the greyscale mode where
the ugly style is kind of useful.

Re: [Tuxpaint-devel] A list of the Tux Paint canvas (and starters) size.

[Bill K. <nb...@so...>]

On Sun, Feb 25, 2007 at 05:39:41PM -0500, Albert Cahalan wrote:
> On 2/22/07, Robert Elliott <r_e...@in...> wrote:
> 
> >    Please tell me if this is correct before I create starters at these
> > sizes. And if this info is correct, it should be added to the "Extending Tux
> > Paint" info page for people who want to create starters.
> 
> Tux Paint can be started in many other sizes, like these:
> 
> 666x555
> 640x1001
> 2560x1600

Indeed.  I THINK the docs have been updated since the last version to
cover this.  I've also updated Tux Paint Config to have two pulldowns...
one for width, one for height, and they both have the same list of
sizes, so you can easily do portrait vs. landscape.

In any case, the canvas size should be:

  (window width - 192) x (window height - 128)

The buttons are 48x48, and there are two columns of them on each side,
so the canvas starts 96px in from the left, and ends 96px from the right.

The Tux penguin text area, and color palette take up 128px at the bottom.


-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/