Forum for XYplorer Users and Developers
https://www.xyplorer.com/xyfc/
Shouldn't it be called /exec= or /script= to better show what it's for?admin wrote:Not implemented. Maybe later I can add a switch /load=[xys file]...
Yes, /script= looks good.PeterH wrote:Shouldn't it be called /exec= or /script= to better show what it's for?admin wrote:Not implemented. Maybe later I can add a switch /load=[xys file]...
And didn't we talk about an initial script? Then calling xy with a .ini containing an initial script could achieve the same.
(But I think both could be helpful.)
Just curious: what kind of script is that? Backup?timhatz wrote:It would be nice to have another switch to tell the system to not show the gui, so it just stays hidden while it executes, and then unloads from memory nicely when the script finishes.
tim
I see. I'm not very fond of this kind of automatic stuff. Too dangerous, too robotic. Think of freaking robots in science fiction...timhatz wrote:For an example it would be nice to automate the delete of files older than 10 days in a folder based on a filter.
Without having to run it manually.
Just for the example, I do have something like that myself (Note: this is a simple copy/paste, I haven't had the time to use the "new" loops/etc) :admin wrote:But, with a little effort, you could do it with scripting: A script that runs a number of other scripts once per day. So all you'd have to do is press a button once, and then all your daily one-time routines would be performed. If you press again, the button would know (INI storage) that he did the job already today and do nothing. The later, if we have CEA, you could tie this button to any event (e.g. startup). That way, using XY (and triggering that event) would ensure the jobs get done.
Code: Select all
"Do cron jobs : doCron"
global $CRON_list;
sub _ensureXY;
self $base, base;
$today = <date dd/mm/yyyy>;
getkey $lastrun, "LastRun", "Settings", "$base.ini";
// if we already ran today, we stop here
end ($lastrun == $today),,1;
status "Processing cron jobs for today ($today)...",,progress;
getkey $CRON_list, "list", "Jobs", "$base.ini";
$CRON_list = "$CRON_list,";
// adds a last coma to make things easier to work with on loop
setting "AllowRecursion", 1;
sub ($CRON_list != ",") ? "_cronLoop" : "_nothing";
setting "AllowRecursion", r;
//
// done for today!
setkey $today, "LastRun", "Settings", "$base.ini";
status "Cron jobs for today ($today) completed";
"_cronLoop"
global $CRON_list;
self $base, base;
// "extracts" first element on list
strpos $p, $CRON_list, ",";
substr $id, $CRON_list, 0, $p;
substr $CRON_list, $CRON_list, $p + 1;
//
// get definition of the cron job, and run it if condition evaluates to true -- simple as that!
getkey $condition, "Condition$id", "Jobs", "$base.ini";
getkey $script, "Script$id", "Jobs", "$base.ini";
load (eval($condition) ? $script : 'call'),,s;
//
end ($CRON_list == ""),,1;
sub _cronLoop;Code: Select all
[Settings]
LastRun=23/09/2009
[Jobs]
list=1,2
Condition1=1
Script1=load 'dailyScript';
Condition2=<date w> == 2
Script2=load 'weeklyScript';