| Re: [AD] SF.net SVN: alleg:[13892] allegro/branches/4.9/src/macosx/system.m |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Hm, but from where Allegro will know where app was installed? If in
config, such information is already possible to obtain.
On 14 November 2010 23:35, Thomas Fjellstrom
<tfjellstrom@xxxxxxxxxx> wrote:
> On November 14, 2010, Michał Cichoń wrote:
>> That would be ALLEGRO_INSTALL_PATH which have no sense since Allegro
>> knows nothing about installation process.
>
> I don't see why it can't export that info. It also doesn't care about temp
> files, or in fact, any of the paths. Its purely a convenience function for
> people using allegro. And some might wish to actually know that info. We have
> no way of knowing.
>
>> On 14 November 2010 08:11, Thomas Fjellstrom
>> <tfjellstrom@xxxxxxxxxx> wrote:
>> > On November 13, 2010, Elias Pschernig wrote:
>> >> On Sat, 2010-11-13 at 19:07 +0100, Michał Cichoń wrote:
>> >> > Is the ALLEGRO_PATH a path to the file or directory? I think both.
>> >> >
>> >> > More proper names for _PATH variables are:
>> >> > ALLEGRO_TEMP_DIR_PATH
>> >> > ALLEGRO_DATA_DIR_PATH
>> >> > ALLEGRO_SYSTEM_SETTINGS_DIR_PATH
>> >> > ALLEGRO_USER_DATA_DIR_PATH
>> >> > ALLEGRO_USER_SETTINGS_DIR_PATH
>> >> > ALLEGRO_USER_HOME_DIR_PATH
>> >> > ALLEGRO_EXENAME_PATH
>> >> >
>> >> > Suffixing with _DIR_PATH should solve all doubts.
>> >>
>> >> They sound a bit strange, so not sure it's really needed for the one
>> >> exception we have.
>> >
>> > Indeed. I see no reason to insert _DIR.
>> >
>> >> > Also ALLEGRO_APPLICATION_PATH is suits better than ALLEGRO_EXENAME_PATH
>> >> > IMHO.
>> >>
>> >> I can only agree to that though.
>> >
>> > But that is sensible. Unless we wanted to export the path to where
>> > applications install to.. (/usr/bin? /Applications? C:\Program Files?) I
> guess
>> > it really depends.
>> >
>> > --
>> > Thomas Fjellstrom
>> > tfjellstrom@xxxxxxxxxx
>> >
>> >
> ------------------------------------------------------------------------------
>> > Centralized Desktop Delivery: Dell and VMware Reference Architecture
>> > Simplifying enterprise desktop deployment and management using
>> > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
>> > client virtualization framework. Read more!
>> > http://p.sf.net/sfu/dell-eql-dev2dev
>> > --
>> > https://lists.sourceforge.net/lists/listinfo/alleg-developers
>>
>>
>>
>>
>
>
> --
> Thomas Fjellstrom
> tfjellstrom@xxxxxxxxxx
>
> ------------------------------------------------------------------------------
> Centralized Desktop Delivery: Dell and VMware Reference Architecture
> Simplifying enterprise desktop deployment and management using
> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end
> client virtualization framework. Read more!
> http://p.sf.net/sfu/dell-eql-dev2dev
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
--
thedmd, Michał Cichoń
Artifex Mundi
michcic@xxxxxxxxxx
http://www.artifexmundi.com