I am curious as to the strategy experienced scripters use when trying to
interface with the filesystem through the web document. This for scripters
who try to write web documents acting as applications (HTA?) which are
opened on the localhost, and so there is no question regarding security
here once the user accepts that the downloaded document represents no
threat.
For instance, some scripters are used to Unix style function calls
(opendir, readdir, etc) and prefer to use such an interface. They would
then create a library of wrapper code with calls specific to the multiple
or major systems they wish to target (say either a Unix-type or Windows-
type).
With Unix-type systems however, there is no real concept of drives except
to mount a physical drive within the hierarchy as a (sub)directory path.
In this case, perhaps it is preferable to write script in which the
interface is entirely via Microsoft's FileSystemObjec t methods, and then
writing wrappers for those methods in the case where the filesystem is
actually a Unix/Linux-type system. This might especially be true for
coders who like the Open/Save As... type dialogs presented by Windows, and
so they are willing to do handstands and somersaults to present a graphical
interface with graphical web browsers.
I would like to know what approach those of you have tried or prefer for
cases where you wrote documents that open/save to the filesystem.
Comment