Yeah, not very modest. But here's one thing I'd love to see for function report() : an additional parameter to be a |-separated list of source items. That way, instead of having to go to a location and select files, we could just put their names in! Awesome, plus we can do items on multiple locations without running search, or use it as function to test whether or not a file/folder exists with something like
Code: Select all
msg (report("{Name}",,"C:\file.txt") == "") ? "File is missing!" : "File exists!";Code: Select all
report("{Fullname} - {Size}<crlf>", , "C:\WINDOWS\*.dll|C:\WINDOWS\system32\*.dll/mod,d");Or: To Infinity And Beyond!
I'll repeat TheQwerty's idea of a function html() to show a window with HTML content, because it'd be pretty cool. It should probably work with a file path/name to load up or raw content (HTML code) directly. It'd be nice to generate reports and show them directly in XY without having to save them and open a browser, or be able to use things like color, bold, italic, etc to show results of a script execution...
Also, noticed I said function? -- Yeah, because I'm already dreaming of it like so : by default (user clicks "Ok") it returns nothing ("woohoo!", Homer says), but the HTML code would support things (in links) like "xys::42" or "xys::foo bar" and, when clicked, it would close the window and the function would then return whatever was specified (42, foo bar) That way our scripts could have different actions based on what the user clicked, which would be kick-ass (especially for a few scripts of mine!) and a nice way to allow show a list of multiple choices with easy selection, instead of using input with "enter 1 for foo, 2 for bar, 3 for foobar, ..." -- and I'm not even talking about using javascript to "hack" a form and create a hidden xys::link with results of a selection made of checkboxes, etc and generate a click on it! Oh God, I can already see how much easier it'll make my scripts, a real single configuration dialog instead of an endless succession of pop-ups and a list of IDs to be remembered...
Excuse me while I'm drooling at the endless mind-blowing possibilities...
(Seriously, I hadn't fully realized what this would allow one to do until last night when I first drafted this, and I couldn't sleep thinking of what it would allow us to do. I think this just became my #1 wish/dream/bribe/whatever it takes
I know it's been mentioned before, but it'd be cool if open/openwith/run would support to wait for the process to be over. I'm pretty sure that can be done through APIs, and it would allow to automate a bunch of tasks a lot more than showing a pop-up that says "Press OK when <app> is done..." which also requires to check in to press OK every so often.
XY could simply show a little modal window (to block XY usage in the mean time, of course, that's the plan) with a little "Please wait..." message (unless there's/as well as, an optional short text from script, to describe what's going on), and a button to "Abort" -- to abort process (if that can be done, send a Kill message or something?) and abort script execution, so we can get XY back in case something goes wrong.
I know there's the case of errors, etc but I still think this would be very useful, and if one doesn't feel comfortable without error return code one can either use a msg to manually allow (or not) to continue script execution, or rely on LOG file that can now be read from scripting...
lol, now things get heavy, so hang on! I'd like a new function strrepeat(<string>, <nb>) that would return a concatenation of <string> repeated <nb> times.
Also, to actually be big, if toolbars work so well it's because catching colorful icons is much easier/faster than reading text, and that's why it would really be nice to have the ability to use icons on script files -- specifying on the caption/label line the path/file,index to the resource.
Oh yeah, and dual pane, too!
XYplorer Beta Club