#1
|
|||
|
|||
Wouldn't it be nice to have a 'Save Script As..." function?
Right now it seems that to create a new backup script that is based on one of supplied scripts, I have to create a new script and then include one of the general ones and add my modifications. While this works, it would be conceptually cleaner if there was a 'Save Script As...' command.
|
#2
|
||||
|
||||
No. The whole idea of including a base script (as opposed to modifying an existing one) is that changes we make in future versions are automatically reflected in the included versions.
__________________
--Dave Nanian |
#3
|
|||
|
|||
Quote:
In other applications, when you select to create a new script, one is given a list of options to choose from (either via a dialogue box with several 'buttons' or via a dropdown menu, the equivalent of your base scripts). In SD, the hierarchy between 'scripts' and 'script commands' is rather unclear to me. It seems everything is a script and that hierarchy does not matter. But what happens if script A says exclude folder X and script B (set to include script A) says include folder X? Furthermore, it seems settings and scripts are saved independently from each other (with scheduled copies at least being based on scripts). And do settings actually save the options? Or what else do they save? So, what happens if you have a scheduled copy that runs fine on its own is using a smart copy and then for a different operation you change from smart copy to erase & copy? Will this affect the scheduled copy? Or does the scheduled copy include the settings that were active when it was created? |
#4
|
||||
|
||||
Yes, they're purposefully separate. Settings reference volumes and scripts, and contain the various options. They can also reference shell scripts.
Scheduled copies are copied to their own location and those settings are separate. When we had an installer, the "standard scripts" folder was read-only so you couldn't change them. But, you can include your own scripts, too - ours are on the "same level" as yours in the "rights" sense. The idea, though, is to use the tool properly - and I do document that in the User's Guide. Yes, many improvements could be made in the scripting area...and many others. The question is taking the engineering time available and applying it to areas that benefit the most users, which doesn't necessarily mean the parts of the design that are objectively the "worst" (but not necessarily used much).
__________________
--Dave Nanian |
#5
|
|||
|
|||
Quote:
Quote:
|
#6
|
||||
|
||||
Yes, if you want to save a general setup, you'd save the settings.
Also, recreating a recovery partition, as we've likely discussed in the past, is pretty easy...
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Converting an Apple script to a shell script ... | rlesperance | General | 2 | 06-27-2010 06:35 PM |
Booting from backup | guruuno | General | 27 | 10-16-2009 11:53 PM |
Do shell script erroring? | Budgie | General | 1 | 02-08-2006 04:50 PM |
Scheduled Custom Script Uses Wrong Script? | Dasman | General | 1 | 12-08-2005 01:55 PM |
Error: No space left on device | tradervic | General | 11 | 06-29-2005 04:50 PM |