Shoutbox

incorporate a python scripting engine as well?
i know if it did i would script

but python needs to be installed... where as jscript is in windows

quote:

---

Originally posted by NanaFreak
but python needs to be installed... where as jscript is in windows

---

quite probably, it may be able to done just using certain dlls, or somehow integrated with plus?
yeah but i just though it might be a good idea as quite a popular language at the moment, not to mention very powerful.

i have a python25.dll which is used for py2exe which might work somehow

or.... how about patchou implements choice of WSH languages instead of just using jscript, and then you find a python WSH plugin (which i'm sure one exists, as there's one for PHP and stuff?)

quote:

---

Originally posted by ShawnZ
or.... how about patchou implements choice of WSH languages instead of just using jscript, and then you find a python WSH plugin (which i'm sure one exists, as there's one for PHP and stuff?)

---

But that would just complicate things so much, the great thing about the way things currently work is that most scripts will work on most people's computers, if you started adding things like what language it was made in, and do you have the right WSH plugin to use it, the whole thing becomes a lot more complicated, and most of Plus's users aren't that technically minded

quote:

---

Originally posted by saralk

But that would just complicate things so much, the great thing about the way things currently work is that most scripts will work on most people's computers, if you started adding things like what language it was made in, and do you have the right WSH plugin to use it, the whole thing becomes a lot more complicated, and most of Plus's users aren't that technically minded

---

actually, that'd be the easiest way to do it. it'd probably require only a very small change to plus!' code, whereas implementing a whole new scripting engine that uses a completely different API would take forever. if you're worried about users not having the language DLL, you could include it in your scripts and have a section in scriptinfo to register them or something.

quote:

---

Originally posted by ShawnZ
actually, that'd be the easiest way to do it. it'd probably require only a very small change to plus!' code, whereas implementing a whole new scripting engine that uses a completely different API would take forever. if you're worried about users not having the language DLL, you could include it in your scripts and have a section in scriptinfo to register them or something.

---

I was referring to having the option to have any language compatiable with WSH compatiable with plus. I think it should be kept to just javascript (or a select set of languages).

The idea that you could include the DLLs in the script and then register them during installation is even more ridiculous, there would be a ton of redundancy as every PHP script would include an extra DLL, or not every script would include the DLL and people would complain that a certain script doesn't work

Then when you come to installation, it's again, another thing to potentially go wrong. Especially for people who don't know much about computers (which is probably the majority of plus's users) and don't understand why a script wont work because they don't have a WSH plugin.

Right now, things "just work" and I don't think you should mess with that.

quote:

---

Originally posted by saralk
The idea that you could include the DLLs in the script and then register them during installation is even more ridiculous, there would be a ton of redundancy as every PHP script would include an extra DLL, or not every script would include the DLL and people would complain that a certain script doesn't work

---

because plus scripts can't already do that

oh wait, they can. you can register COM and .NET dlls to use in your scripts -- like xniff, etc. also, if you're going out of your way to install and code in a different language when you're developing the script, copying one DLL and adding a line to scriptinfo shouldn't be a problem.

quote:

---

Originally posted by saralk
Then when you come to installation, it's again, another thing to potentially go wrong. Especially for people who don't know much about computers (which is probably the majority of plus's users) and don't understand why a script wont work because they don't have a WSH plugin.

---

again, installation of a wsh plugin is just as complicated as registering a com object -- adding a few registry entries. and there are many more reasons scripts can fail to install than just this...

the choice of one language online was made for many resorts. It brings consistency, makes sure everybody gets the same help everytime and technically, it's more difficult that you would think to support many scripting language: each language has its own restrictions, for example, some allow you to pass variables by value, others by reference. I you chose a language that assumes the second, then you're screwed when you'll want to support a language that supports only the first.

Several thigns like that exist for every language and sticking to one language (here, JScript) helps make sure scripting is kept simple, efficient and optimised in its own environement. More choice is not always better.

You can always make your own script hosting script

I made one before that hosted Ruby scripts just as an experiment, basically you just create an instance of ScriptControl (ActiveX) and forward all the events and objects to it.