Database Encryption
Ruslan Zasukhin
sunshine at public.kherson.ua
Tue Jan 7 09:45:00 EST 2003
on 1/7/03 2:26 PM, Robert Brenstein at rjb at rz.uni-potsdam.de wrote:
>>> It does: what you're confused about is what "native" means. Those old
>>> things that start with a drive name and are delimited with colons are
>>> obsolete MacOS 7/8/9 format paths. The way of the future is UNIX paths.
>>
>> Me confuse ?
>>
>> Okay, assume a developer develop with help of MC 2.4.2 CARBON his own Carbon
>> app, which must work on MacOS 9 and X. This is standard expectation from
>> Carbon app.
>>
>> Such Carbon app, must not work etc directory, because it NOT exists on
>> classic. Otherwise you simply mix apples with bananas.
>>
>
> Sorry to say but you are wrong, Ruslan, although you appear to be
> right. Think of filepaths in MC not as Unix filepaths but as MetaCard
> universal filepaths which just happen to look like Unix paths.
>
> As I and others wrote, it is a convention that works quite well for
> great majority of MC users and people who use Valentina or encounter
> other specific situations where they need true native paths just
> handle them accordingly.
>
> There is really no point to argue this any further. Just accept it.
> It's too bad that it is technically not feasible for Valentina to use
> such an approach self.
Hi Robert,
Guys, in fact this is not a problem to me at all.
If MetaCard community fell this is good then this is good.
And since as Scott have mention there are simple ways to build native paths,
then more no problems here.
--
Best regards,
Ruslan Zasukhin [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com
To subscribe to the Valentina mail list
send a letter to valentina-on at lists.macserve.net
-------------------------------------------------------------
More information about the metacard
mailing list