Re: [Shapefusion-devel] names

[Gregory S. <wo...@tr...>]

On Dec 2, 2007, at 6:36 PM, Tito Dal Canton wrote:

> Another planned feature is to look in different places for that file.
> For example, the MacOS X build should look inside the application  
> bundle
> rather than /usr/local/share/shapefusion, and the Windows build could
> look in the directory containing the executable. But more important,
> precedence will be given to a similar file in the user's home  
> directory
> (.shapefusion/DefaultNames.txt or similar), so one will be able to  
> give
> meaningful names for her own scenario in a simple and consistent way.

The Mac OS X convention would be  ~/Library/Application Support/ 
ShapeFusion, rather than .shapefusion. There's a similar convention  
in Windows (I'd have to look it up).

Chances are, though, it would make more sense to look in the  
directory containing the executable; since this is a Marathon shapes  
editor, and we're all used to keeping scenarios in their own folders,  
with Forge and Anvil in them. For instance, I could have 3 different  
ShapeFusions, one for M1A1, Infinity, and Tempus Irae. I don't want  
them all to use the strings in ~

> The only drawback I can think of is that a 'make install' step is now
> required in linux, to make sure the file is there. But we can also  
> tell
> the user "put that default file in ~/.shapefusion" in the README.

I suggest not requiring a default. Build the Infinity names into the  
executable, so no text file is needed unless custom names are used.  
This is how Aleph One works with its MML strings.

FWIW, most Linux users are probably accustomed to having a make  
install, and may get confused if it's not present!

Gregory