Database Encryption
Robert Brenstein
rjb at rz.uni-potsdam.de
Sun Jan 5 17:52:00 EST 2003
>But will be good for MC developers if you will give them built-in methods to
>convert them into MAC and windows native paths.
The conversion function is quite trivial and needed only when opening
databases with Valentina, so it is used only by a small fraction of
MC users. Within MC, one always uses the unix-style paths and MC self
handles the system-specific conversions internally.
>Robert, I do not see sense, why on e.g. Windows, Valentina must wait for
>UNIX path....for all other products we have for each platform NATIVE path,
>Because for example in REALbasic, from OpenDialog is returned Windows path,
>And Valentina need Windows path to send it to Windows system functions.
You are right. Valentina is largely used as a plugin or library, so
it is not possible for it to support platform-independent filepaths
in a consistent manner.
>This DO NOT make any problems for development of cross-platform code.
>As you know REALbasic, Director, Java, C++ all they perfectly work in
>cross-platform way with Valentina, and again, developers do not have
>problems with conversion of paths as you think, because paths self come from
>system's Open Dialog.
First, Open Dialog in MC returns Unix-style paths, so things are
consistent for people working with MC. Second, Ruslan, open dialog is
not the only source of the file paths. Third, remember that MC
scripts work normally with no changes under Mac, Windows, and Unix,
so if one needs to do any filepath manipulations, one does not need
to have three branches of code to handle platform variations. Think,
for example, about extracting the name of the database file from a
filepath.
>And ONLY Metacard developers, as far as I see, have headache with conversion
>of paths...at least if they work with Valentina.
Nee, no headache. A few lines of code written once as a
general-purpose function and re-used for ever and ever.
Robert
More information about the metacard
mailing list