| Re: [AD] Allegro 4.3 Settings/Conf API |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Allegro 4.3 Settings/Conf API
- From: Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx>
- Date: Thu, 17 Nov 2005 07:59:26 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=ujxFiDo9sndGdHKE4ze2B39luaEEd7HWQXqHNRrNt0VzmoKnaAax9hVYGTPJgBE2Kq37pw8Dc3w3k0985kTwWTPVvgRQocgf7Umt/2wxgKs2Rv0baw/BmLJJpk3DS/jeSW5vElX4IXlAw6nU1LMeGJXqxr3VlEPz8Y913QwQCQg=
On November 17, 2005 07:10 am, Vincent Penecherc'h wrote:
> > That is the general idea, but you still have to accept paths
> > given from the
> > user, or a platform specific dialog perhaps?
> >
> > >This is a separate issue from the canonical path list though.
> >
> > In my view, they should be together. File handling is file handling.
>
> Yes, you do have a point.
To be a little more precise (I'm tired...) each platform could, and should
provide a two methods, one to convert to the "allegro path format" and ont to
convert from it. Though this is a little different from the normal "driver"
setup we currently use, because these "methods" may have to be available on
all other platforms. Now, while typing that I've come to realize that at the
most one (platform format to allegro format) will be needed out side of its
native platform, if not none... But hey, I said I was tired ;)
--
Thomas Fjellstrom