smart0036 / tesv-snip

Automatically exported from code.google.com/p/tesv-snip
0 stars 0 forks source link

[TESVSnip] Generate backups of the original plugin before any change is made. #11

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
I think we should add a function similar to xEdit in which any time you save 
your plugin, the previous state of it is saved as it is before touching 
anything.

We could create an Snip History folder next to the exe, and before the plugin 
being edited is saved, just copy the current status to the folder with a its 
file name appended with date and time.
Delete comment Report abuse Comment 1 by project member danielhmpdx16, Aug 19, 
2012
This function exists, but may not occur when you have indicated.  Also I would 
like the backup folder to be where the executable it located.
Delete comment Report abuse Comment 2 by project member danielhmpdx16, Aug 19, 
2012
I didn't notice your other note for a history log.  Can  issue38  be merged 
with this one?
Delete comment Report abuse Comment 3 by project member danielhmpdx16, Aug 19, 
2012
If no edit occurs then it should not save a file.
Delete comment Report abuse Comment 4 by project member danielhmpdx16, Aug 19, 
2012
I also noticed that the backup file is saved where the original plugin is and I 
think there is another .esp file saved where the executable is.  I'd like the 
History Log, the .bak files, and the .esp/.esm files to be in separate folders. 
 I'd like the folders to be easily accessed from the File menu please.
Delete comment Report abuse Comment 5 by project member danielhmpdx16, Aug 26, 
2012
Describe the desired look and feel.

I'd like to have a history log for the changes made to the plugin saved in a 
separate folder.  I would like to have an option to close the session, or close 
the log file without closing the plugins.

Outline the goals/benefits of the enhancement

The history log could be used for version tracking but may have other benefits 
I can't think of at the moment.

What is the expected output?

Saves a log file with a Julian Date plus a truncated Plugin Name no longer then 
30-40 chars.  Having the ability to close the log file could be used for 
testing to indicate that at some point the plugin worked and a new plugin was 
introduced.

This also could be used for version tracking once certain plugins have been 
modified, and a new plugin is brought into Snip

Please provide any additional information below.

I would like the history folder to be where the executable it located.

You should be able to view the Log in Snip opening in another window that is 
superimposed over Snip, and can be sent to the background or foreground as 
needed.

Original issue reported on code.google.com by danielhmpdx16@gmail.com on 22 Sep 2012 at 11:55