quote:
Originally posted by Jaguar
1. Plus! can execute a .lnk file with the scheduler already.. so there would be no need to make up a new file. The advantage of having it a .lnk file is that it's totally Window compatible.
Scheduler does use shell indeed to execute everything, nice
. Any extension can be made windows compitable without much work. My point is that .lnk is meant to be purely a shortcut to another file. A .lnk file itself doesn't contain any other data besides the name and location of the file it should execute, optionally it can has one or more comman line switches.
So when you use pure .lnk you can only store the whole "script" in the shortcut itself by using the command line switches, or have the "script" stored somewhere else and make the .lnk shortcut refer to this. Both methods have downsides:
- .lnk is used, also by by non-plus! users, when they doubleclick these Plus! "scripts" Windows will still try to execute, causing errors.
- The actual "scripts" themselves have to be stored somewhere anyway, when they are stored somewhere in seperate files people can exchange them with eachother on MSN and sites which will boost popularity big time. Ofcourse you can store the "scripts" in .lnk files too, but it must be on one command line, which will be very messy with bigger "scripts", also see point above here.
quote:
Originally posted by Jaguar
2. & 4. Why would you want other people to be able to run commands on your computer?
Many reason, ever did scripting in mIRC or simulair? It's great to have automatic response to certain message/commands. But i understand such things might be to advanced to create in a plugin, certainly for a new plugin.
quote:
Originally posted by Jaguar
3. Plus! already has a delay funtion in quick texts so you could just use that. (I can't remember the command.)
That's true, forgot about that for a moment (even while i was the one requesting it once
).
quote:
Originally posted by Jaguar
5. The whole point is making them .lnk files so Windows and other programs can use them.
I understand and agree with that. My main point is just that:
- It's not a good idea to store the actual "script" code in a .lnk file
- I think the "scripts" should be stored in seperate files (with other extensions then .lnk) so people can send them to eachother, publish them on sites and such. If you store the "scripts" in either registry, one big file or some kind of database type you would have to import/export "scripts" first which makes it less simple to use.
To be able to run "scripts" from any program there should be something that handles them from command line. Something like:
code:
"C:\Program Files\Messenger Plus! 3\Plugins\scriptlauncher.exe" -run c:\Program Files\Messenger Plus! 3\Plugins\somescript.mps
Took .mps as extension for the file that contains the "script" code (
Messenger
Plus!
Script).
quote:
Originally posted by Stigmata
code:
private sub Form_Load(command as string)
if command = "status=busy" then
messengerapi.mystatus = 2
else
Msgbox "Command Not Reconised"
end if
end sub
Nice, but i prefer pure simple syntax as Jaguar showed in his picture, altough it would require way more programming to be able to use advanced functions in simple syntax mode.
/ 
