Re: [Tuxpaint-devel] Stamps installer on Windows

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

On Wed, Sep 14, 2005 at 07:49:17PM -0700, Mark K. Kim wrote:
> <snip bill's comments>
> 
> If we make this change, that means the new stamps can't be installed on
> the older TuxPaint versions, right?  How can we resolve this problem
> elegantly?  A few options come to mind:
> 
I hadn't considered backwards compatibility. As it happens the old
stamps have this data layout anyway, so they will work if installed in
the application directory.

It is only an issue if the stamps are installed for the current user
only, which isn't supported by the old version.

>   1. The Stamps installer checks for the TuxPaint version, tell
>      the user to upgrade.
>
I will put a warning box in.

>   2. The Stamps installer checks for the 'data\' path, install
>      one path above it if it doesn't already exist.  Make sure
>      new versions of TuxPaint creates the empty 'data\' path
>      upon installation.
> 
Doesn't work for stamps in zip archives, which some people prefer. It
seems to be good practice for the installer to behave in as simple a
manner as possible, although a variety of technical 'bodges' came to my
mind also :-)

>   3. Warn the user on the stamps download page.
> 
Good idea.

>   Etcetera...
> 
> Also, let's make sure this is *the* TuxPaint path to use for all future
> Stamps (and fonts) installations.  Otherwise we'll have to deal with this
> backwards-compatibility issue again when we change our minds about the
> canonical path.
> 
I've only added paths to be examined so backwards compatibility has been
preserved.

The previous versions saved pictures and scanned directories in the
application directory(!) unless the 'savedir' option was used. That no
longer happens and isn't an option (except by using 'savedir').

I haven't given any thought to updating an existing installation beyond:

 - backup your paintings
 - un-install the old version
 - install the new version
 - move paintings to the new user data directory (which won't be created
   until the program has been run once by the end user)

Automating this would be more complex than the rest of the installer!
It could be done when the new version of Tux Paint is run for the
first time though ....

I'm going to go ahead and add the additional paths for stamps, brushes
and fonts,

cheers,
John.


> Otherwise it sounds like a good solution to me.
> 
> -Mark
> 
> 
> -- 
> Mark K. Kim
> AIM: markus kimius
> Homepage: http://www.cbreak.org/
> Xanga: http://www.xanga.com/vindaci
> Friendster: http://www.friendster.com/user.php?uid=13046
> PGP key fingerprint: 7324 BACA 53AD E504 A76E  5167 6822 94F0 F298 5DCE
> PGP key available on the homepage
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. 
> Download it for free - -and be entered to win a 42" plasma tv or your very
> own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Tuxpaint-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
>