Would you like to see File I/O functions in MQ Scripts?

BlueSkies · Post by **BlueSkies** » Fri Jun 27, 2003 3:02 pm

Just curious to see what the demographics are on this topic.

By File I/O functions, I mean the ability to open text files, retreive data, write data, etc. while in MacroQuest.

L124RD · Post by **L124RD** » Fri Jun 27, 2003 3:20 pm

Salutations,
If file IO comes about, I would like to see:

/macro somethin.mac
Warning: somethin.mac reads/writes the following files:
..\iofiles\bazaar.txt
c:\windows\explorer.exe
MQ paused, to accept, un pause the macro, otherwise use /endmacro.

so that we don't have any wonderful MQ viruses going around... I think this was the original problem with encoding macros so their not human readable (came up at one point iguess). but, ya konw , I expect that all of you who read these forums are more mature then that, but I can't say anything for macro's retreived outside of the forms.

Valerian · Post by **Valerian** » Fri Jun 27, 2003 3:24 pm

While you're at it, include .ini file support as well, so you could have somemac.mac, and it can read/write settings from/to somemac.ini... or any .ini format file... would probably be easier to use the ini format for certain things, since there are already fairly flexible APIs to use 'em.

BlueSkies · Post by **BlueSkies** » Fri Jun 27, 2003 3:46 pm

Good points, both of you. :) I'll keep these in mind when I start working on this.

Losingteam · Post by **Losingteam** » Fri Jun 27, 2003 5:03 pm

I might be illiterate, or whatever. But I don't understand this I/O thing you speak of. All I ever knew I/O to stand for was on and off. Regardless, if this I/O thing will help in even the slightest way, I give a major gratz and good luck to you for working on it.

BlueSkies · Post by **BlueSkies** » Fri Jun 27, 2003 5:08 pm

I/O stands for Input / Output. Basically, I want to implement File Manipulation in MacroQuest.

AlphaBeta · Post by **AlphaBeta** » Fri Jun 27, 2003 5:53 pm

Losingteam you'r confusing I/O with binary numbering of 1's and 0's hehe

Jalapeno · Post by **Jalapeno** » Sat Jun 28, 2003 9:46 pm

File I/O to me is an obvious benefit to writing scripts. It opens up a world of possibilities. One of which is recording and playing back PATHs. =)

I vote yes for file I/O... Since I'm working with BlueSkies on implementing it anyway. =p

fryfrog · Post by **fryfrog** » Sun Jun 29, 2003 10:51 pm

a POSSIBLE solution to the abuse of file i/o is only allow writing to a sub-directory that was SPECIFICALLY designed for this (perhaps /Macro/ or some subfolder of /macro). sort of a chrooted or jailed environment. it could also be done in such a way that mq could be configured to allow write elsewhere, but not configured in such a way by default (if you follow my idea) :)

Valerian · Post by **Valerian** » Sun Jun 29, 2003 10:54 pm

there's now .ini file I/O, and it may not need to go any further than that... *shrug*

BlueSkies · Post by **BlueSkies** » Sun Jun 29, 2003 11:32 pm

Val -- Jala and I have come to the same conclusion. .INI File I/O is really all that's needed for MQ's purposes, at this time. I see no need to implement any other forms.

And fry -- The only way File I/O can be abused is if people don't review the script they're about to run. And, honestly, I don't understand why anybody would run a script they didn't look over, even if they don't know the slightest thing about MQ script.
Besides, if we limit it to a directory inside the MacroQuest folder, there'd be no way to manipulate the EQ INI files or the Bazaar INI files, which I suspect will get someone going. :)

fryfrog · Post by **fryfrog** » Mon Jun 30, 2003 4:46 am

blah blah blah, it all comes down to me should have read all the threads in the forum before posting :)

the ini read/write sounds very useful.

BlueSkies · Post by **BlueSkies** » Mon Jun 30, 2003 6:11 am

Hehehe :)

It happens, fry.

No worries.

AarynD · Post by **AarynD** » Tue Jul 15, 2003 4:47 pm

Great Job guys!

I think this is one of the top new features of MQ, as it singlehandedly opens up an entire world of possiblities from with a MQ macro.

- Aaryn