Re: [AD] 5.0.0 final release plan

[Matthew Leverton <meffer@xxxxxxxxxx>]

On Sun, Jan 2, 2011 at 11:06 PM, Thomas Fjellstrom
<tfjellstrom@xxxxxxxxxx> wrote:
>> On Sun, Jan 2, 2011 at 9:19 PM, Matthew Leverton <meffer@xxxxxxxxxx> wrote:
>> Oh, and I don't see any use for ALLEGRO_PROGRAM_PATH, considering
>> there is ALLEGRO_EXENAME_PATH.
>
> There was only one to begin with. I think theres a usecase for both. One is
> the dir the exe is in, the other is the full path to the exe (including the
> exe name).
>
I think PROGRAM_PATH probably became useful when SYSTEM_DATA_PATH
changed from program files to the user data folder. I just question
its current usefulness as a cross platform path, since it potentially
is meaningless inside an app bundle.

If there were something that represented the static program data
(e.g., APP_DATA_PATH), then I think the program path becomes totally
superfluous. You can easily chop the filename off of the EXE_PATH if
you really want it.

Regarding the patch, I would just do this:

* rename ALLEGRO_PROGRAM_PATH to ALLEGRO_APP_DATA_PATH. Warn in
documentation that it should be considered read-only.
* on OS X, add an extra check to see if running from an app bundle. If
so, return the bundled data folder location.
* change the demos to all use ALLEGRO_APP_DATA_PATH
* add more detailed documentation for all the path descriptions

With the exception of the home folder (which could be addressed
separately), I think all the other folder names are appropriately
named (or good enough) and have a reasonable implementation.

--
Matthew Leverton