According to Dick Middleton:
>
> To subscribers of the xforms list from Dick Middleton <dick@sqf.hp.com> :
>
> My suggestion is to use a naming convention which helps protect you from this
> sort of mistake. For example I prefix all my form files with D_ (for dialog)
> and files containing the supporting code I_ (for interface). All other code
> can then be safely named as you please. I'm sure there are many other
> possibilities.
I too have come up with a few conventions that help prevent me from
overwriting valuable files:
First off, I do all my work in C++ so I don't use the files that fdesign
spits out verbatim. The code that fdesign spits out is copied into the
create() member of each of my window classes. I agree this is tedious
but it works quite well after you get the hang of it. Anyway, since my
files end with .cc, the only chance I have or messing up a crucial file
is to accidentally overwrite a header file.
So, for each project, I create a subdirectory called "FD" that
contains the fdesign-related files. Since fdesign only operates within
the FD directories, there is no chance of fdesign overwriting one of
my other program files.
Finally, within the FD directory, I may have several .fd files. Before I
begin using fdesign to edit an existing .fd file, I always copy it to
"work.fd". When I'm done, I copy work.fd back to whatever it used to be.
This allows me extra "version control" above and beyond making frequent
backups of my code -- if something goes wrong during the fdesign session,
I can simply purge work.fd and repeat.
I agree wholehartedly with the backup concept. The way I implement it
is through a rudimentary sort of version control: I begin a project in
a v0.1 directory. After each significant change change to my code
(whether it's a fdesign change or otherwise), I increment the
version number, create a new directory and copy my files over. The
new directory becomes my work directory and the old directory is
tarred and gzipped. This way I have a complete history of my code
development in the event I want to see when a particular problem appeared
and I don't have to go through the trouble of setting up a sccs system.
Jimmie
-- Jimmie Mayfield "Hey brother can you spare a dime... mayfield@pa.uky.edu to get me off this slaughter line?" #include <disclaimer.h> http://www.pa.uky.edu/~mayfield _________________________________________________ To unsubscribe, send the message "unsubscribe" to xforms-request@bob.usuf2.usuhs.mil or see http://bob.usuf2.usuhs.mil/mailserv/xforms.html Xforms Home Page: http://bragg.phys.uwm.edu/xforms List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/