Read/Writable folder in data/E2Expressions

[Filipe]

With user-defined functions coming (hopefully) soon, and a slew of other neat additions in the horizon, there's one small thing that I'd like to see added to E2 that I believe would open up a few new possibilities - implementation should be a 2 minute job, so it's really just a matter of everyone agreeing with it.

It's pretty simple: a specific folder inside data/Expression2 that would be accessible (read/write) to E2 file functions (or some sort of flagging system for folders)

The idea came to me while I worked on a sort of E2 extended preprocessor (in E2), where I wrote a fairly simple script that allowed the following syntax in E2 code:

(this is not what I'm suggesting, read above!)

@name Test
... some code ...
#!include "myProject/functions.txt"
... some more code ...

And a few other neat functions. The problem was that everytime I want to build/compile my project, I'm forced to copy all my files to data/e2files, run the expression, and then move it back to data/Expression2

There's countless other applications: compression, self-improving expressions, a new (optional) emphasis on project-oriented E2 development, to name a few.

So, what do you lads think?

[Colonel Thirty Two]

The problem is that the code is first uploaded to the server, and then preprocessed.

Of course, modifying E2 to preprocess/parse on the client would make this feasible, and would also improve performance.

[Filipe]

The problem is that the code is first uploaded to the server, and then preprocessed.

Of course, modifying E2 to preprocess/parse on the client would make this feasible, and would also improve performance.

You misread my post, and I can see why (my example could lead to some confusion). My suggestion is allowing E2 file-functions to access a special folder in the E2Expressions directory.

[Colonel Thirty Two]

I know, but I was referring to that.

[Filipe]

Oh, I know very well about the complications of integrating any sort of include function, my script merely emulates it by processing the whole e2 file locally

[Dav1d]

This isn't a bad idea, but can't you just have all your functions inside an e2 that's just used as a 'library' of sorts?
I think you can read and write to the "Expression 2" folder inside /data/ anyway, try using "../Expression 2/filename.txt" as the path, the ../ part just makes it go up a folder. (It works with playing sounds, at least)

[Filipe]

This isn't a bad idea, but can't you just have all your functions inside an e2 that's just used as a 'library' of sorts?
I think you can read and write to the "Expression 2" folder inside /data/ anyway, try using "../Expression 2/filename.txt" as the path, the ../ part just makes it go up a folder. (It works with playing sounds, at least)

File functions are locked to data/e2files, the data folder can possibly contain a alot of sensitive files, and it could be pretty terrible if a rogue script were to delete any of them.

[Drunkie]

I like this idea. You've got my vote.

[casino.doug]

same i would love to have this

[Whosdr]

Eh, I don't see why not.