Tom, You might like to do your development/testing online in a separate directory (or virtual host, if you can). This is mostly for after you've released something that is being used. It's a safer way to develop - you won't have to worry what you "break" when you save a file that might contain a syntax error. Then, get into the habit of copying data into the "live" directory from your development/testing area(s), or use CVS for revision control.
I do a lot of development this way. Because it's online, you can jump from computer to computer. Also, the development/testing enviroment(s) are so similar to the live environment that you won't have to worry about compatibility issues between them. Good luck! Mary On 4/30/07, Thomas Haws <[EMAIL PROTECTED]> wrote:
I guess I neglected to say I am still Windows-bound. That's still no excuse for not setting up a local development environment, but the fact I jump from computer to computer is a good excuse. Here's what I think I will be happy with for the moment: 1. Install WinSCP and Notepad++ (my current editor of choice) on each computer. Edit files remotely almost as though they were local. WinSCP allows me to double-click on remote file(s) to edit it/them, then save and test without closing my editor. 2. Make a pseudo-menu cheat sheet for vi survival that looks and thinks like a Windows/Mac application. Put it on the web so I can always access it in the rare case I need to vi. Tom _______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
-- Mary Shaw Internet Consultant http://www.stitchsoft.com
_______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
