tuxpaint-devel — General discussion list for Tux Paint developers

Re: [Tuxpaint-devel] Tux Paint on a plane

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

On Sat, Feb 24, 2007 at 10:49:52AM +0100, Karl Ove Hufthammer wrote:
> Anybody feel like sending an e-mail to these people to see if they would be 
> interested in Tux Paint?
> 
> http://www.linuxgamingworld.com/2007/01/virgin
> http://www.letvafly.com/mt/2007/02/want_your_game_featured_on_vir.html

Hey Karl.  I'm actually already in contact with the Red folks.
They sounded pretty excited to hear from me.  :)  Haven't heard anything
in a week or so, though, so I should probably ping them.  (And make sure
I haven't forgotten to reply to anything they've sent me since... new babies
are bad for email ;) )

Thanks!

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

Re: [Tuxpaint-devel] hello, and hildon

[Kees J. <kee...@gm...>]

> What are the advantages of using mud-builder instead of own packaging? As
> far as I've understood, mud-builder is great at building simple stuff with
> no Maemo specific changes. When the building has to be done in a customized
> way to make tuxpaint even run on Maemo, mud-builder is maybe not the optimal
> solution.
There is no immediate gain here if you know how to build for on
different maemo sdk's.
Also if you know how to signs the package and upload them to the maemo
reposiroty
I guess. Also once we have the patches into the official tuxpaint
there will be no gain in the mud paching system. I don't really mind I
think you are right in wanting to use the garage tuxpaint project.

> = Packaging =
> It's probably easier to start the packaging based on a stable version, so we
> could start with tuxpaint 0.9.16's source tar.gz package, make the needed
> changes to get it running well on 770 or N800, and then see how the changes
> could be merged to tuxpaint CVS. Probably the changes done on 0.9.16 are
> pretty easy to port to tuxpaint CVS.
>
> Maemo requires some special dependencies for packaging, so as an answer to
> Caroline, we cannot push that to Debian's tuxpaint package. In addition,
> Maemo is using older debhelper and some other tools.
correct

>
> = Hildonizing =
> I'm mostly worried about the mouse cursor. Otherwise I guess hildonizing
> will not be a big task. Mostly replacing some gtk calls with hildon calls.
> I'm not sure how file system differences etc. are going to affect.
>
> Hopefully most of the stuff can be done without touching the generic
> tuxpaint code. Compile time flags are not an optimal solution, but I guess
> they will do for now.
>
> How does that sound? I'm sending Alessandro a please-let-me-in email to get
> this started. I guess it's still best to keep the discussion in this mailing
> list.
Good thinking[tm]

I will try to looks if the freedesktop project keyboard layouts could
be used to display an onscreen keyboard

greetings

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

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

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

The existing layouts might need to change a bit. For example,
the OLPC XO is 1200x900 but as blurry as a TV.

Re: [Tuxpaint-devel] hello, and hildon

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

Jus a few comments

2007/2/25, Terje Bergstr=F6m <ter...@ko...>:
>
>
> There are at least two different types of tasks to do:
>
> =3D Packaging =3D
> It's probably easier to start the packaging based on a stable version, so
> we could start with tuxpaint 0.9.16's source tar.gz package, make the
> needed changes to get it running well on 770 or N800, and then see how th=
e
> changes could be merged to tuxpaint CVS. Probably the changes done on
> 0.9.16 are pretty easy to port to tuxpaint CVS.
>
> Maemo requires some special dependencies for packaging, so as an answer t=
o
> Caroline, we cannot push that to Debian's tuxpaint package. In addition,
> Maemo is using older debhelper and some other tools.
>
> =3D Hildonizing =3D
> I'm mostly worried about the mouse cursor. Otherwise I guess hildonizing
> will not be a big task. Mostly replacing some gtk calls with hildon calls=
.
> I'm not sure how file system differences etc. are going to affect.
>


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=
)

Hopefully most of the stuff can be done without touching the generic
> tuxpaint code. Compile time flags are not an optimal solution, but I gues=
s
> they will do for now.
>
> How does that sound? I'm sending Alessandro a please-let-me-in email to
> get this started. I guess it's still best to keep the discussion in this
> mailing list.
>
>
Other changes to the source are related to the screen size and disabling
text tools.

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).

Other changes for maemo packaging are done in the /etc/tuxp* file:
* store images in the mmc (and not in a hidden dir, otherwise users will
never find them anymore)
* disable printing
* hildon menu and icons
* disable cursor?

ToDo:
* text tool input
* fix the bug that don't show the application in the application bar (I
think is now fixed by kees in N800)
* change some tools to use integer math (no FPU on N770)
* implement the possibility to hide (via config file) the lower information
bar (so we have more space for drawings), this is a feature request from a
user, and I think it's a good idea
* package stamps
* package languages separately

Concerning mud yes or mud no, I'm agnostic but just a little bit lazy to
learn something new: I tried mud a week ago (trying to compile gdal) and
ended up compiling the entire world (CTRL+C after one hour or so).

If someone could help me/us start with mud, it could be an option, but I'm
not sure it is the best way to go.

Those are just a few ideas.

Comments are welcome.

BTW right now tuxpaint is already packaged and woks (with the a.m. bugs) on
both N800 and N770.

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

[Tuxpaint-devel] hello, and hildon

[<ter...@ko...>]

On 2/24/07, Kees Jongenburger <kee...@gm...> wrote:
>
> Hello Terje
>
> It looks like we are enough people who have a good interest in this
> project
> the mud builder builds tuxpaint from the tar.gz archieve.


What are the advantages of using mud-builder instead of own packaging? As
far as I've understood, mud-builder is great at building simple stuff with
no Maemo specific changes. When the building has to be done in a customized
way to make tuxpaint even run on Maemo, mud-builder is maybe not the optimal
solution.

I just tried to build tuxpaint from the debian repo and it required
> hevea and such for building
> how did you build it? I am quite sure the source debian will need to
> changes , the question is where to put these changes :p. I am off to
> fosdem are there tuxpaint developer going there?


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.

There are at least two different types of tasks to do:

= Packaging =
It's probably easier to start the packaging based on a stable version, so we
could start with tuxpaint 0.9.16's source tar.gz package, make the needed
changes to get it running well on 770 or N800, and then see how the changes
could be merged to tuxpaint CVS. Probably the changes done on 0.9.16 are
pretty easy to port to tuxpaint CVS.

Maemo requires some special dependencies for packaging, so as an answer to
Caroline, we cannot push that to Debian's tuxpaint package. In addition,
Maemo is using older debhelper and some other tools.

= Hildonizing =
I'm mostly worried about the mouse cursor. Otherwise I guess hildonizing
will not be a big task. Mostly replacing some gtk calls with hildon calls.
I'm not sure how file system differences etc. are going to affect.

Hopefully most of the stuff can be done without touching the generic
tuxpaint code. Compile time flags are not an optimal solution, but I guess
they will do for now.

How does that sound? I'm sending Alessandro a please-let-me-in email to get
this started. I guess it's still best to keep the discussion in this mailing
list.

Re: [Tuxpaint-devel] hello, and hildon

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

On 2/24/07, Kees Jongenburger <kee...@gm...> wrote:
>
> Hello Terje
>
> It looks like we are enough people who have a good interest in this
> project
> the mud builder builds tuxpaint from the tar.gz archieve.


What are the advantages of using mud-builder instead of own packaging? As
far as I've understood, mud-builder is great at building simple stuff with
no Maemo specific changes. When the building has to be done in a customized
way to make tuxpaint even run on Maemo, mud-builder is maybe not the optimal
solution.

I just tried to build tuxpaint from the debian repo and it required
> hevea and such for building
> how did you build it? I am quite sure the source debian will need to
> changes , the question is where to put these changes :p. I am off to
> fosdem are there tuxpaint developer going there?


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.

There are at least two different types of tasks to do:

= Packaging =
It's probably easier to start the packaging based on a stable version, so we
could start with tuxpaint 0.9.16's source tar.gz package, make the needed
changes to get it running well on 770 or N800, and then see how the changes
could be merged to tuxpaint CVS. Probably the changes done on 0.9.16 are
pretty easy to port to tuxpaint CVS.

Maemo requires some special dependencies for packaging, so as an answer to
Caroline, we cannot push that to Debian's tuxpaint package. In addition,
Maemo is using older debhelper and some other tools.

= Hildonizing =
I'm mostly worried about the mouse cursor. Otherwise I guess hildonizing
will not be a big task. Mostly replacing some gtk calls with hildon calls.
I'm not sure how file system differences etc. are going to affect.

Hopefully most of the stuff can be done without touching the generic
tuxpaint code. Compile time flags are not an optimal solution, but I guess
they will do for now.

How does that sound? I'm sending Alessandro a please-let-me-in email to get
this started. I guess it's still best to keep the discussion in this mailing
list.

Re: [Tuxpaint-devel] hello, and hildon

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

Yes, the cursor could be removed, I left it because I liked it, but it is
really unuseful.


2007/2/24, Terje Bergstr=F6m <ter...@ko...>:
>
> Hi,
>
> My first post, too. I tried to send this already from GMail, but it didn'=
t
> seem to appear in the list.
>
> >   I've just downloaded the sources from CVS.
> >   I'm the one who ported tp to OS2006 (Nokia 770 and Nokia 800 inetrnet
> tablets), not so much work indeed.
> >    Since Bill Kendrick told me that some hildonizations work has been
> done
> before (for OS2005 version of Nokia firmware) I've looked at the code.
> >    Well, I discovered that some makefile flags exists for Nokia 770 but
> no
> hildonizazion was done, it's just a few configuration change, exactly the
> same I did (in a very quick and dirty way) for OS2006.
> >    BTW having those flags is fine.
>
>
> I downloaded the sources and noticed, that they actually don't build. I
> made
> small changes to Makefile and got it to build and run in Maemo SDK fine.
> If
> there are no objections, I will commit my changes to Makefile to cvs
> tomorrow.
>
> My biggest change was not to overwrite stock CFLAGS, but just to
> append "-DNOKIA_770" to it by introducing similar flag set as with
> "NOSVG".
>
> I think the biggest challange with the already-packaged OS2006 version is
> the
> cursor. The cursor should be removed, as there is no mouse in OS2006. Wit=
h
> touchscreen the cursor just gets in the way.
>
>     Just a question: where can I find the DEBIAN control files in order t=
o
> make a debian package? Do I have to extract them for another tuxpaint
> debian
> package?
>
>
> I think the best bet would be to start with the Debian's tuxpaint package
> and
> work from there.
>
> Best regards,
> 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

Re: [Tuxpaint-devel] hello, and hildon

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

The NOKIA Internet Tablets run a debian-like system, but the packages do not
come from debian repositories.

The debian packages need some changes to adapt in the hildon framework
(menus, icons) and the sources need changes too.

The architecture is armel.

Regards.

2007/2/24, Caroline Ford <car...@go...>:
>
> Kees Jongenburger wrote:
> > Hello Terje
> >
> > It looks like we are enough people who have a good interest in this
> project
> > the mud builder builds tuxpaint from the tar.gz archieve.
> >
> > I just tried to build tuxpaint from the debian repo and it required
> > hevea and such for building
> > how did you build it? I am quite sure the source debian will need to
> > changes , the question is where to put these changes :p. I am off to
> > fosdem are there tuxpaint developer going there?
> >
> >
> Hi guys
>
> What is the connection between yourselves and Debian? I'm trying to
> understand so I can best answer your question.
>
> Are you running Debian on your tablets? Is there a Debian port for your
> tablets? The person you need to contact about the tuxpaint debian
> package is Ben Armstrong - sy...@sa... He's the Debian
> developer responsible for tuxpaint. (I've copied him into this email)
>
> To submit patches to the Debian packae I'd use their bug tracker. Ben
> will be able to help you better than I can.
>
> Caroline
>
>
>
> -------------------------------------------------------------------------
> 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=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Tuxpaint-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
>



-- 
Alessandro Pasotti
w3:   www.itopen.it

Re: [Tuxpaint-devel] hello, and hildon

[Caroline F. <car...@go...>]

Kees Jongenburger wrote:
> Hello Terje
>
> It looks like we are enough people who have a good interest in this project
> the mud builder builds tuxpaint from the tar.gz archieve.
>
> I just tried to build tuxpaint from the debian repo and it required
> hevea and such for building
> how did you build it? I am quite sure the source debian will need to
> changes , the question is where to put these changes :p. I am off to
> fosdem are there tuxpaint developer going there?
>
>   
Hi guys

What is the connection between yourselves and Debian? I'm trying to 
understand so I can best answer your question.

Are you running Debian on your tablets? Is there a Debian port for your 
tablets? The person you need to contact about the tuxpaint debian 
package is Ben Armstrong - sy...@sa... He's the Debian 
developer responsible for tuxpaint. (I've copied him into this email)

To submit patches to the Debian packae I'd use their bug tracker. Ben 
will be able to help you better than I can.

Caroline

[Tuxpaint-devel] Tux Paint on a plane

[Karl O. H. <ka...@hu...>]

Anybody feel like sending an e-mail to these people to see if they would be 
interested in Tux Paint?

http://www.linuxgamingworld.com/2007/01/virgin
http://www.letvafly.com/mt/2007/02/want_your_game_featured_on_vir.html

-- 
Regards,
Karl Ove Hufthammer

Re: [Tuxpaint-devel] hello, and hildon

[Kees J. <kee...@gm...>]

Hello Terje

It looks like we are enough people who have a good interest in this project
the mud builder builds tuxpaint from the tar.gz archieve.

I just tried to build tuxpaint from the debian repo and it required
hevea and such for building
how did you build it? I am quite sure the source debian will need to
changes , the question is where to put these changes :p. I am off to
fosdem are there tuxpaint developer going there?

greetings


On 2/24/07, Terje Bergstr=F6m <ter...@ko...> wrote:
> Hi,
>
> My first post, too. I tried to send this already from GMail, but it didn'=
t
> seem to appear in the list.
>
> >   I've just downloaded the sources from CVS.
>  >   I'm the one who ported tp to OS2006 (Nokia 770 and Nokia 800 inetrne=
t
> tablets), not so much work indeed.
> >    Since Bill Kendrick told me that some hildonizations work has been d=
one
> before (for OS2005 version of Nokia firmware) I've looked at the code.
> >    Well, I discovered that some makefile flags exists for Nokia 770 but=
 no
> hildonizazion was done, it's just a few configuration change, exactly the
> same I did (in a very quick and dirty way) for OS2006.
> >    BTW having those flags is fine.
>
>
> I downloaded the sources and noticed, that they actually don't build. I m=
ade
> small changes to Makefile and got it to build and run in Maemo SDK fine. =
If
> there are no objections, I will commit my changes to Makefile to cvs
> tomorrow.
>
> My biggest change was not to overwrite stock CFLAGS, but just to
> append "-DNOKIA_770" to it by introducing similar flag set as with "NOSVG=
".
>
> I think the biggest challenge with the already-packaged OS2006 version is=
 the
> cursor. The cursor should be removed, as there is no mouse in OS2006. Wit=
h
> touchscreen the cursor just gets in the way.

Re: [Tuxpaint-devel] hello, and hildon

[Terje <ter...@ko...>]

Hi,

My first post, too. I tried to send this already from GMail, but it didn't 
seem to appear in the list.

>   I've just downloaded the sources from CVS.
 >   I'm the one who ported tp to OS2006 (Nokia 770 and Nokia 800 inetrnet 
tablets), not so much work indeed.
>    Since Bill Kendrick told me that some hildonizations work has been done 
before (for OS2005 version of Nokia firmware) I've looked at the code.
>    Well, I discovered that some makefile flags exists for Nokia 770 but no 
hildonizazion was done, it's just a few configuration change, exactly the 
same I did (in a very quick and dirty way) for OS2006.
>    BTW having those flags is fine.


I downloaded the sources and noticed, that they actually don't build. I made 
small changes to Makefile and got it to build and run in Maemo SDK fine. If 
there are no objections, I will commit my changes to Makefile to cvs 
tomorrow.

My biggest change was not to overwrite stock CFLAGS, but just to 
append "-DNOKIA_770" to it by introducing similar flag set as with "NOSVG".

I think the biggest challange with the already-packaged OS2006 version is the 
cursor. The cursor should be removed, as there is no mouse in OS2006. With 
touchscreen the cursor just gets in the way.

    Just a question: where can I find the DEBIAN control files in order to 
make a debian package? Do I have to extract them for another tuxpaint debian 
package? 


I think the best bet would be to start with the Debian's tuxpaint package and 
work from there.

Best regards,
Terje

Re: [Tuxpaint-devel] Tux Paint startup at boot-up on a Mac

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

On Fri, Feb 23, 2007 at 01:24:31PM -0800, Matthew Helms wrote:
> Hi Bill,
> 
> This is probably not enough information to go on for  
> troubleshooting.  If it is not in a startup item then it should  
> generally not start up.  Start up items can be in the following places:

Thanks Matthew!  I've passed it along!  Hope it helps 'em :)

-bill!

Re: [Tuxpaint-devel] Tux Paint startup at boot-up on a Mac

[Matthew H. <mat...@ma...>]

Hi Bill,

This is probably not enough information to go on for  
troubleshooting.  If it is not in a startup item then it should  
generally not start up.  Start up items can be in the following places:

/Library/StartupItems
/Systems/Library/StartupItems

System Preferences, Accounts, Login Items (10.3, 10.4)
and I think System Preferences, personal, Login Items (10.2)

Also, I think Tux Paint launching on startup is a feature not a bug ;)

I hope this helps,
Matthew

On Feb 23, 2007, at 12:49 PM, Bill Kendrick wrote:

> I just received this question:
>
>> Every time i start my mac up Tuxpaint launches. it's not in my start
>> up items so wht does it do this?
>
> Anyone have any clue?  :^/
>
> Thanks!
>
> -- 
> -bill!
> bi...@ne...
> http://www.newbreedsoftware.com/
>
> ---------------------------------------------------------------------- 
> ---
> 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=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Tuxpaint-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel

[Tuxpaint-devel] Tux Paint startup at boot-up on a Mac

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

I just received this question:

> Every time i start my mac up Tuxpaint launches. it's not in my start
> up items so wht does it do this?

Anyone have any clue?  :^/

Thanks!

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

Re: [Tuxpaint-devel] hello, and hildon

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

Hi,

My first post, too.

I've just downloaded the sources from CVS.
> I'm the one who ported tp to OS2006 (Nokia 770 and Nokia 800 inetrnet
> tablets), not so much work indeed.
> Since Bill Kendrick told me that some hildonizations work has been done
> before (for OS2005 version of Nokia firmware) I've looked at the code.
> Well, I discovered that some makefile flags exists for Nokia 770 but no
> hildonizazion was done, it's just a few configuration change, exactly the
> same I did (in a very quick and dirty way) for OS2006.
> BTW having those flags is fine.


I downloaded the sources and noticed, that they actually don't build. I made
small changes to Makefile and got it to build and run in Maemo SDK fine. If
there are no objections, I will commit my changes to Makefile to cvs
tomorrow.

My biggest change was not to overwrite stock CFLAGS, but just to append
"-DNOKIA_770" to it by introducing similar flag set as with "NOSVG".

I think the biggest challange with the already-packaged OS2006 version is
the cursor. The cursor should be removed, as there is no mouse in OS2006.
With touchscreen the cursor just gets in the way.

Just a question: where can I find the DEBIAN control files in order to make
> a debian package? Do I have to extract them for another tuxpaint debian
> package?


I think the best bet would be to start with the Debian's tuxpaint package
and work from there.

Thanks in advance.
> --
> Alessandro Pasotti
> w3:   www.itopen.it
> -------------------------------------------------------------------------
> 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=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Tuxpaint-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
>
>

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

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

Tux Paint Developer List

   I am developing starters for kids to practice matte painting for motion
pictures using Tux Paint (on the Macintosh).  I find that some of the
information on the page "Extending Tux Paint" is incomplete or wrong.

   By measuring, I find that:

Wide view:
1. For the Tux Paint mode set to 640 by 480, the Tux Paint canvas is 448 by
376 pixels.

2. For the Tux Paint mode set to 800 by 600, the Tux Paint canvas is 608 by
472 pixels. (This is NOT 608 by 496 as listed in the "Extended Tux Paint"
info page for the correct canvas size for starters.)

3. For the Tux Paint mode set to 1024 by 768, the Tux Paint canvas is 832 by
664 pixels.

4. For the Tux Paint mode set to 1280 by 1024, the Tux Paint canvas is 1088
by 904 pixels.

5. For the Tux Paint mode set to 1400 by 1050, the Tux Paint canvas is 1208
by 904 pixels. (I am not sure why the Macintosh came up with such an odd
size.  Maybe my screen was too small.)

6. For the Tux Paint mode set to 1600 by 1200, the Tux Paint canvas is 1408
by 1096 pixels.

Portrait view:
1. For the Tux Paint mode set to 768 by 1024, the Tux Paint canvas is 576 by
904 pixels.

2. For the Tux Paint mode set to 1024 by 1280, the Tux Paint canvas is 832
by 1144 pixels.

   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.

   Note:  Both Tux Farmer and Nagasaki starters are off by at least one
pixel in size.  

Robert Elliott
 Wikiversity Instructor
  WikiU Film School
   r_e...@in...
    http://en.wikiversity.org/wiki/filmmaking

Re: [Tuxpaint-devel] hello, and hildon

[Caroline F. <car...@go...>]

Kees Jongenburger wrote:
> I  don't think this all is very interesting for tuxpaint developers. but..
> I would like to have a virtual keyboard so my kids can also type letters.
> are there people willing to create some graphics for that?
>
> greetings
>   
I'm working on sets of alphabet stamps currently which could be used. 
One question would be on keyboard layout as it would need to be 
localised - EN has qwerty, DE has qwertz etc

Caroline
> On 2/22/07, Caroline Ford <car...@go...> wrote:
>   
>> Alessandro Pasotti wrote:
>>     
>>> Just a question: where can I find the DEBIAN control files in order to
>>> make a debian package? Do I have to extract them for another tuxpaint
>>> debian package?
>>>
>>>       
>> They are done by Debian afaik - try packages.debian.org or
>> packages.ubuntu.com (Ubuntu is 'downstream' of  Debian  and generally
>> uses their packages unaltered. If it is altered it will have ubuntu in
>> the package name)
>>
>> Debian files are in the debian directory which is generally a patch to
>> the upstream tarball. You download the diff, the original tarball and a
>> dsc file which gives checksums etc.
>>
>> In Debian land tuxpaint is in 4 binary packages - tuxpaint,
>> tuxpaint-data, tuxpaint-stamps-default and tuxpaint-config. Currently
>> tuxpaint-data depends on tuxpaint-stamps and vice versa. In Ubuntu we
>> are looking at changing it so that tuxpaint-data only recommends the
>> stamps package as it is possible to run tuxpaint without the stamps
>> installed (and circular dependencies are horrible and break with gdebi)
>> (my bug - https://launchpad.net/bugs/82510)
>>
>> tuxpaint-stamps is a virtual package which is currently only provided by
>> tuxpaint-stamps-data but can be provided by other packages once the
>> stamps collection is split by theme.
>>
>> http://packages.debian.org/unstable/graphics/tuxpaint is the main binary
>> http://packages.debian.org/unstable/graphics/tuxpaint-data is the
>> architecture independent data
>> http://packages.debian.org/unstable/graphics/tuxpaint-stamps-default stamps
>> http://packages.debian.org/unstable/graphics/tuxpaint-config config
>>
>> Debian unstable currently has version 0.9.16 and 2006.10.21 for stamps.
>> Ubuntu Feisty will get 0.9.16, currently Ubuntu Edgy and Dapper have 0.9.15.
>>
>>
>>     
>
>   

Re: [Tuxpaint-devel] hello, and hildon

[Kees J. <kee...@gm...>]

Hello

I am very happy to get a chance to contribute to this great piece of software!

My involement in tuxpaint started because I wanted a tuxpaint for the N800.
I did this by putting a mud file in the mud builder
https://garage.maemo.org/plugins/scmsvn/viewcvs.php/trunk/packages/tuxpaint.xml?root=mud-builder&view=markup
The mud builder generates the debian /control and rules for us.
http://mud-builder.garage.maemo.org/index.php
The N700 is a pretty small (in terms of memory/cpu speed device) I
think we have different considerations when it comes to the
possibilities and I don't even thing there is a download stamps
package.

The maemo platform is debian based and we can use most of the other
debian source archives (we just need a good reson).

I think the current port works pretty well , it just needs a bit of love.
I propose to build the packages /debian things for the different maemo
platforms.

I  don't think this all is very interesting for tuxpaint developers. but..
I would like to have a virtual keyboard so my kids can also type letters.
are there people willing to create some graphics for that?

greetings

On 2/22/07, Caroline Ford <car...@go...> wrote:
> Alessandro Pasotti wrote:
> > Just a question: where can I find the DEBIAN control files in order to
> > make a debian package? Do I have to extract them for another tuxpaint
> > debian package?
> >
> They are done by Debian afaik - try packages.debian.org or
> packages.ubuntu.com (Ubuntu is 'downstream' of  Debian  and generally
> uses their packages unaltered. If it is altered it will have ubuntu in
> the package name)
>
> Debian files are in the debian directory which is generally a patch to
> the upstream tarball. You download the diff, the original tarball and a
> dsc file which gives checksums etc.
>
> In Debian land tuxpaint is in 4 binary packages - tuxpaint,
> tuxpaint-data, tuxpaint-stamps-default and tuxpaint-config. Currently
> tuxpaint-data depends on tuxpaint-stamps and vice versa. In Ubuntu we
> are looking at changing it so that tuxpaint-data only recommends the
> stamps package as it is possible to run tuxpaint without the stamps
> installed (and circular dependencies are horrible and break with gdebi)
> (my bug - https://launchpad.net/bugs/82510)
>
> tuxpaint-stamps is a virtual package which is currently only provided by
> tuxpaint-stamps-data but can be provided by other packages once the
> stamps collection is split by theme.
>
> http://packages.debian.org/unstable/graphics/tuxpaint is the main binary
> http://packages.debian.org/unstable/graphics/tuxpaint-data is the
> architecture independent data
> http://packages.debian.org/unstable/graphics/tuxpaint-stamps-default stamps
> http://packages.debian.org/unstable/graphics/tuxpaint-config config
>
> Debian unstable currently has version 0.9.16 and 2006.10.21 for stamps.
> Ubuntu Feisty will get 0.9.16, currently Ubuntu Edgy and Dapper have 0.9.15.
>
> Caroline
>
> -------------------------------------------------------------------------
> 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=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Tuxpaint-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
>

Re: [Tuxpaint-devel] hello, and hildon

[Caroline F. <car...@go...>]

Alessandro Pasotti wrote:
> Just a question: where can I find the DEBIAN control files in order to 
> make a debian package? Do I have to extract them for another tuxpaint 
> debian package?
>
They are done by Debian afaik - try packages.debian.org or 
packages.ubuntu.com (Ubuntu is 'downstream' of  Debian  and generally 
uses their packages unaltered. If it is altered it will have ubuntu in 
the package name)

Debian files are in the debian directory which is generally a patch to 
the upstream tarball. You download the diff, the original tarball and a 
dsc file which gives checksums etc.

In Debian land tuxpaint is in 4 binary packages - tuxpaint, 
tuxpaint-data, tuxpaint-stamps-default and tuxpaint-config. Currently 
tuxpaint-data depends on tuxpaint-stamps and vice versa. In Ubuntu we 
are looking at changing it so that tuxpaint-data only recommends the 
stamps package as it is possible to run tuxpaint without the stamps 
installed (and circular dependencies are horrible and break with gdebi) 
(my bug - https://launchpad.net/bugs/82510)
 
tuxpaint-stamps is a virtual package which is currently only provided by 
tuxpaint-stamps-data but can be provided by other packages once the 
stamps collection is split by theme.

http://packages.debian.org/unstable/graphics/tuxpaint is the main binary
http://packages.debian.org/unstable/graphics/tuxpaint-data is the 
architecture independent data
http://packages.debian.org/unstable/graphics/tuxpaint-stamps-default stamps
http://packages.debian.org/unstable/graphics/tuxpaint-config config

Debian unstable currently has version 0.9.16 and 2006.10.21 for stamps. 
Ubuntu Feisty will get 0.9.16, currently Ubuntu Edgy and Dapper have 0.9.15.

Caroline

Re: [Tuxpaint-devel] "Go download Stamps" note during installation process

[John P. <jo...@jo...>]

On Thu, Feb 22, 2007 at 11:07:56AM -0800, Bill Kendrick wrote:
><snip!>
> John - would it be difficult to add a clickable hyperlink (or perhaps
> a checkbox that opens a browser, similar to what we do for the README)
> that will make it obvious to people that they can (and should! ;^) ) go
> download the stamps, after the main app has been installed?
> 
Hi bill,

something like the README checkbox would be straight-forward.

There is a link in the 'Tux Paint' start-menu  group that points at the
web-site, but there is no obvious mention of the stamps there.

Where would be a good place to open in the browser?

This page is a possibility:
http://www.tuxpaint.org/download/windows/

but I guess it's still possible to miss that 'Rubber Stamps (optional)'
is something that really should be downloaded.

What about a page that explains why they are looking at it and what they
should do now :-)

Any ideas about what string should be next to the checkbox?

How about this:

  [X] View the README file
  [X] Launch Tux Paint Config
  [X] Optionally download the Tux Paint Stamps

cheers,
John.


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

[Tuxpaint-devel] "Go download Stamps" note during installation process

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

I've received numerous emails from people asking me why their copy of
Tux Paint doesn't have any stamps besides the few Tux ones included
in the main package.

Well, obviously, they didn't download the Stamps installer.
How could they have missed it on the website?  Well, they probably didn't
get Tux Paint FROM the tuxpaint.org website.  In many cases, they had
downloaded it from shareware sites such as CNet's Download.com, who
insist on mirroring a copy of the download file _themselves_.

So, people find Tux Paint (the app), and download it and run it, and then
dig up my email address in the documentation when they discover they're
missing stamps.

John - would it be difficult to add a clickable hyperlink (or perhaps
a checkbox that opens a browser, similar to what we do for the README)
that will make it obvious to people that they can (and should! ;^) ) go
download the stamps, after the main app has been installed?

Thanks!

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

[Tuxpaint-devel] hello, and hildon

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

Hello everybody,

This is my first post.

I've just downloaded the sources from CVS.

I'm the one who ported tp to OS2006 (Nokia 770 and Nokia 800 inetrnet
tablets), not so much work indeed.

Since Bill Kendrick told me that some hildonizations work has been done
before (for OS2005 version of Nokia firmware) I've looked at the code.

Well, I discovered that some makefile flags exists for Nokia 770 but no
hildonizazion was done, it's just a few configuration change, exactly the
same I did (in a very quick and dirty way) for OS2006.

BTW having those flags is fine.

Just a question: where can I find the DEBIAN control files in order to make
a debian package? Do I have to extract them for another tuxpaint debian
package?


Thanks in advance.
-- 
Alessandro Pasotti
w3:   www.itopen.it

[Tuxpaint-devel] Scaling bug for rubber stamps...

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

Tux Paint Developer List

   I am using v0.9.16 Macintosh (2006-10-18) and I found a bug in the rubber
stamp scaling routine for 600 by 800 screen size of Tux Paint.

   When using rubber stamps in the 1024 by 768 window size, the largest
magnification of a rubber stamps is about 125% of the screen height.
Everything seems to work OK with this window size.

   When you first open Tux Paint using a window size of 600 by 800, the
stamps are at full size which is the default which is about 125% of the
screen height (same as above).  However, once you begin changing the scaling
of the stamps by clicking in the scaling box (the box of verticle bars which
get progressively larger to the right), the rubber stamp now has a maximum
size of only about 95% of the screen.  That is, once you use the scaling
box, the maximum size never is 125% no matter what you do.  It is now only
95% of the screen height.

Notes:

(1)  I would prefer that the largest size of a rubber stamp is 150% of the
screen height for the 600 by 800 window.

(2)  I think the smaller sizes of rubber stamps is too small.  I believe
that you have set the scaling too small for the smaller sizes.

(3)  I wish there was some way to put rubber stamps on a page so that only
1/3 of the stamp is visible.  Currently, the lower limit is 1/2.

Robert Elliott (Purser)
 Wikiversity Instructor
  WikiU Film School
   r_e...@in...

Storyboard Artwork Project (for Tux Paint)
   http://en.wikiversity.org/wiki/Storyboard_Artwork_Project

which is part of Narrative Film Production
   http://en.wikiversity.org/wiki/filmmaking

Re: [Tuxpaint-devel] [Tuxmath-devel] Someone to represent Tux4Kids at FOSDEM?

[Holger L. <de...@la...>]

Hi,

On Thursday 15 February 2007 11:56, Bill Kendrick wrote:
> Anne-Marie from the KDE Edu project talked to me on #kde this evening:
>   I am doing an edu gathering at the KDE room on Sunday morning
>   http://fosdem.org/2007/schedule/events/kde_free_edu_software

I'll be at fosdem and definitly will try to attend her talk.

And, btw, some of us hang out on #tux4kids on irc.oftc.net.


regards,
	Holger