[Prev][Next][Index][Thread]
Re: FileMaker under Executor
Clifford T. Matthews writes:
> FileMaker and a few other programs (Finale comes to mind)
> want to write scratch files at the top of the "volume" that
> they're found on. If you run them on a Mac, and you have a
> hard drive named "Disk", and you have FileMaker in a
> subdirectory named "FileMaker", the scratch files get
> written in "Disk" and not "FileMaker".
>
> I've spent a bit of time thinking about a way to trick these
> aberrant programs, but haven't figured out anything
> yet.
>
I would like to define "drives" for Executor - similar to SoftPC. That
way, I can have a shared system "volume" in
/LocalApps/Executor.app/ExecutorVolume, and then personal "volumes,"
say, ~/Library/ExecutorVolume and /. That way, if a program wants to
write to the top of the volume, it will write it to the top of that
defined volume (and in most cases,
/LocalApps/Executor.app/ExecutorVolume).
I find myself trying to manuever in those awkward Mac open panels too
much; I wish I could hit ~username/filename and so on. The Mac file
interface wasn't intended for the huge number of subdirectories so
pervasive in UNIX. How about drag and drop filenames into the dialog
boxes? :-)
While I'm at it, why not have HFS_XFer be a NeXTSTEP app? Does it
*have* to be a Mac one? If it was a native NS app, it would be faster,
have a better GUI, and (maybe) could run alongside of Executor. As it
stands, running the two at the same time seems to really slow down the
system, and I get occasional file corruptions.
Happy New Year!
---
Bill Chin, NeXTSTEP Developer, PRC Inc.
VP Communications, Washington Area NeXT Users Group
Association of NeXTSTEP Developers International Technical Staff
bchin@nextsrv1.andi.org - NeXTmail welcomed