Re: [AD] 5.0.0 final release plan

[Trent Gamblin <trent@xxxxxxxxxx>]

We can also make an ex_bundle if we want to show people how its done.

--
Trent Gamblin

On 2011-01-02, at 1:50 PM, Trent Gamblin wrote:

> On 2011-01-02, at 1:45 PM, Evert Glebbeek wrote:
> 
>> On 2 Jan 2011, at 13:12 , Peter Hull wrote:
>>> That looks OK for ALLEGRO_SYSTEM_DATA_PATH; a5teroids does work now
>>> with this patch *and* with al_get_standard_path(ALLEGRO_PROGRAM_PATH)
>>> replaced by al_get_standard_path(ALLEGRO_SYSTEM_DATA_PATH) in
>>> Game.cpp. However I don't know if this would break every other
>>> platform?
>> 
>> That's a good question.
>> It depends on how we think things should be organised in the demo program. I don't think ALLEGRO_PROGRAM_PATH is ever really intended to be used to locate game data in an actual program that people want to install (that's what the data paths are for), which essentially is what an application bundle is. However, the demo might be written with the idea that the executable and the data are placed in the same directory, in which case ALLEGRO_PROGRAM_PATH is what you want (even if it is bad style for a demo program without a big fat comment saying why you shouldn't do it that way and why we're doing it anyway). In that case, however, trying to stick everything in an application bundle is not appropriate because there you *don't* want to put everything in the same directory.
>> 
>> Any thoughts on this?
> 
> My first thought is, why put it in a bundle anyway? It's just a demo, not a real app. If I'm reading this
> right then ALLEGRO_SYSTEM_DATA_PATH will get the Resources/ directory in the bundle, so people wishing to
> make bundles can use that. It's unlikely that someone (besides us?) would deploy both a bundled and a non
> bundled version of their game both for Mac OS X.