>
>Also, is it best to keep an alias of the folder(s) that I will be moving
>things to and from?  There will be at least one source folder and possibly
>many folders to move things into.  Pathnames would work but aren't what I
>want to do at all.  Pathnames are bad :)  I'd like to go for maximum
>usability and least user set up and maintainance.  That's why I figure
>aliases are the way to go.  Here again, I have no experience so if someone
>would be kind to point out a starting place I'd be forever grateful.

I can't resist jumping in here.  I have some experience in moving files 
between folders, volumes, servers, etc.  Here is one situation that I 
have encountered:

You app makes an alias to the "Plug-ins" folder.
The user renames the "Plug-ins" folder to "Disabled Plug-ins".
The user creates a new "Plug-ins" folder.
Your app now starts moving items to "Disabled Plug-ins" because thats 
where the alias will point!

Heres the solution I used:
Find the application using the desktop database (This will also allow you 
to warn the user if he has multiple copies of the app on his drive(s))
Make an alias to the app.
When you need to move things, get the path to this app using the alias, 
then extend the path by appending "Plug-ins:" to then end of it.  You 
could also just open a working directory to that folder if it makes it 
easier for you.

Partial Paths are a much more dependable solution than either full 
pathnames or a complete alias.  This will also mean that the user need 
not find the app on his drive for you, yet will be free to move 
everything around without affecting your app.

Jamin