Managing WORKFLOW (IP ENG.) 1) SYS CALLING XYS SCRIPT FILES?

[jcadbiz]

DESKTOP INFORMATION ENGINEERING

Hi guys, I need to integrate XYplorer into a unified universal desktop management suite for general use. I have some patent value to add to it.



So, I need to create a directory on the desktop (or in a sub dir to XYplorer is fine) to hold a stash of scripts that I can name at will through the system, and that will execute when I run or open them also thru the system. IOW,

. . . . 1) Can I make run-time executables out of the XYS FILES?
. . . . 2) Are there any workarounds even if not, and
. . . . 3) Any discussion of it?

So you know: I see this as break it, if I don't make it, so I am determined to make it work (if possible.)
I found this original discussion on scripting (2008) http://www.xyplorer.com/xyfc/viewtopic. ... executable

Apparently at that time at least, no one considered the scripting component as in any way separate from the GUI. The GUI is a wonderful addition - but I wouldn't want to be forced to use it just to invoke a script. I should be able to run a script from any system command line with something as minimal as: "Xyplorer.exe -scriptname.xys" -- or even just "scriptname.xys" - or of course directly with a double click - nothing new here.

Thanks for jumping on it.

Keywords: executable, runtime, compiler, compiled

[admin]

tip: caps off.

[Stefan]

Hi jcadbiz, welcome.

Please try if this works for you:

Execute an script one-liner:

Code: Select all

XYplorer.exe   /win=min   /ini=commandline.ini     /script=" ::msg 'Welcome to XY!';   #191; "

Execute an script file:

Code: Select all

XYplorer.exe   /win=min   /ini=commandline.ini     /script="temp\jcadbiz";

Data\Scripts\temp\jcadbiz.xys

Code: Select all

msg "Hello";
  #191;

#191; is the command for "File > Close without saving"


See XYplorer help for more info > Configuration > Command Line Switches


-----------------------------------------------------------------------------------
@Don

/script
For example
XYplorer.exe /script=test

But didn't works for me without quoting the script name:
XYplorer.exe /win=min /ini=commandline.ini /script=c; //only open new XY only
XYplorer.exe /win=min /ini=commandline.ini /script="c"; //works
-----------------------------------------------------------------------------------

[admin]

-----------------------------------------------------------------------------------
@Don

/script
For example
XYplorer.exe /script=test

But didn't works for me without quoting the script name:
XYplorer.exe /win=min /ini=commandline.ini /script=c; //only open new XY only
XYplorer.exe /win=min /ini=commandline.ini /script="c"; //works
-----------------------------------------------------------------------------------

Works fine here.

[jcadbiz]

-----------------------------------------------------------------------------------
@Don

/script
For example
XYplorer.exe /script=test

But didn't works for me without quoting the script name:
XYplorer.exe /win=min /ini=commandline.ini /script=c; //only open new XY only
XYplorer.exe /win=min /ini=commandline.ini /script="c"; //works
-----------------------------------------------------------------------------------

Okay, I get: XYplorer.exe /win=min /ini=commandline.ini /script="c"; //works
But it starts a new iteration of XY, even with "allow multiple instances" off (/config/starup & exit)
so... I am officially half way there.



So to be clear: is there a switch to use a running iteration of XY GUI?
I see it . . . working on it . . .
/help/config/command line switches/keeping a single instance

follow up:
Okay, using in the RUN CL: "XYplorer.exe /win=min /script="testmenu""
It works, but the /win=min switch has no effect - the GUI is being restored. It has to stay out of sight for this. Any ideas?
The "keeping a single instance" reference says the intended behavior is "this path is opened in a new foreground tab of the previous instance. . . ." WHICH - is no good for this.

. . . ALSO NOTE that double clicking on a script file directly from anywhere should at least optionally RUN the macro - instead it goes to the macro in the GUI, and when clicked from inside the GUI does the same - so no net change. ANY IDEAS HERE?

(I'm thinking that it would profit XY mightily to put out a GUI-LESS interpreter for free - and to separate the interpreter code from the GUI so the GUI doesn't have to even run unless called. But - just an idea.)

[CodeLobster]

i like the idea of xy runtime mini apps.

a bell rings and it tolls me the prediction i made in another thread of 20 h running that ended in

58 h as the light version took 5 would end up in far less time if the script routines were running

on top of a dedicated, revised and exclusive engine.

yes i agree it is too much for a file manager but its stuff like that that are making my

contractors purchasing dept to perhaps finally spend some bucks in a few more licenses.

+1 count me in

[jcadbiz]

High Priests of Xy:

I'm just a wee bit out of my strength, but having included simplified syntax in my CTO "coursework" for wikis and every other place where they appear, your implementation is "Stupid Simple." Cudos. In this desktop niche, I think it has the potential to be the Porsche of the industry.

I also see that as a talent. And talent as the true strength (you probably don't.) But you should. And I think you should pursue this manifestation as a priority.

. . . . "Tool. Fire. Wheel."

Right now, that's my conclusion. Unless you can convince me otherwise, I'll be following up as a recruiter for the association.

Meanwhile - let's hack a way to keep the GUI minimized for the one-way (so far) we can "execute" a script file.