Need to redesign scripting to use an "include" or some "global" vars

[vitrom]

Looking on a "standard" scripts i've found that a many parameters like zones gap, files masks etc. etc. are duplicated in the every script even of the same "category", for example "Sys disk" -- daily/weekly/monthly -- contains the same parameters except sorting method and something else.

It may lead to an useless moving of already optimized data when a user just forgot to change a value in the one of many scripts -- for example, daily and monthly defrag with a 1% gap and a weekly with a default 0,1% will result to a very big useless and time wasting shift.

IMO it's wrong and any reused variables needs to be moved out of scripts into the "Settings.myd" or "dailyconf.myd" or something like this and used in a scripts like a global variables.

--
xcuse me for my english but i hope i'm understandable.

[Darlis]

Your request is similar to the one in this thread: include file for SpaceHogs definition

I guess Jeroen's answer in that thread would also apply to this one. And of course you can change the scripts for yourself, if you think this could be a better solution. You can use SetVariable to define the global variables you need.

[vitrom]

Oops! Thank U very much! I didn't found it after textsearch over helpfile.

change the scripts for yourself, if you think this could be a better solution

I think it's the one only right solution (aka "reusing")

[poutnik]

I use for my system partition the only script with a Fileactions defined by macro : 

FileSelect      
   "FileSelection"
FileActions
   !Factions!
FileEnd

and calling the script with parameters, defining the actions.

E.g. my system custom weekly-like script is call by this command:

C:\Utils\dfrc.myd -m "Factions=Defragment(chunksize(64)) FastFill(WithShuffling)"