XY Macro Recording aka Scripting for the Newbies

[SkyFrontier]

It's widely known among forum regulars that I simply *love* XY scripting. But I'm always concerned on how the novices can take full advantage of XYplorer firepower the soonest they can.

Months ago (when I had more spare time) I tried to elaborate a way a meta-script could lead the user to either perform common actions for which s/he would be expected to write scripts but due to to her/his current lack of knowledge s/he couldn't, or to deliver a final script based on a series of questions such meta-script presented the user. My own lack of sc html knowledge compromised the project (see http://www.xyplorer.com/xyfc/viewtopic.php?f=7&t=10275 with Stefan's collaboration for some reference), so it ended into the drawer.

...but what about an XY own Macro Recording capabilities? Recent File Operations (v12.30) is a step and I think that Undo/Redo (v8.60) is another. Many actions can be triggered by just using simple sequences of command IDs (v6.80). Start XY Macro Rec, log each and every commands performed since then, give a cool interface to save such a sequence once stopped under a familiar name, a nice button to re-run last executed/recorded macro (able to run on single or multiple files and a gentle warning to prompt if original recorded action was performed on files only, folders only or files+folders but current run makes it different - basic error check, you know...) and voilá - quick scripting for the masses!

__________________
Logged command IDs could be automatically commented, making the learning easier:
#163; // Copy Here

[kunkel321]

... and voilá - quick scripting for the masses!

Heck ya! Do it!
It might be nice if XY had a type of "scratch pad" where bits of code could get sent to. For example if I copy a particular file, that might not constitute a full macro-worth of actions. As such I wouldn't want it sent as an .xys file in the scripts folder--I've got enough half-baked junk in there already.

[PeterH]

... in the scripts folder--I've got enough half-baked junk in there already.

"Junk" and XYscript folder :-( I know that problem!

But you know you can make some organization here - with subfolders of the script folder?
For example I have
- a subfolder \test for scripts I'm just testing
- a subfolder \system for scripts to organize XY
- a subfolder \sub for kind of subroutines that are only called from other scripts

So if I need my subroutine "debug" from any script, I just:
load "sub\debug";

This way I can keep the number of files in the main script folder small and more easy to handle...

[SkyFrontier]

Good news, everyone!

Sammay & I Dev Team is working on an old project of mine, an early (but never implemented) stage of the Themes* auto-generating scripts. It's a semi-auto-scripter, question-driven, command-sequencer which will introduce new users to the wonderful world of scripting, generating actually working scripts out of sketches. It may also help XYperienced users to better understand the problems newbies may have.

An alternative to Macro recording, in the meantime it doesn't come to play (IF it comes, someday).

All the heavy work may be Sammay's, this time.

No ETA is given, but we're already discussing the better model to accomplish it.

Stay tuned.

______
*
RthemeL - aRtistic Theme Loader, our first and great team-up
XYstylEZ - 1170 Themes Pack, plus Loader/Deletion Tool
XYstylEZ - Visual Themes for your XYplorer, made easy