Page 1 of 2

ReactOS Scripting Engines(e.g Python engine)

Posted: Sat Oct 06, 2012 4:54 pm
by erkinalp
Most people has known Windows has a scripting engine based on VisualBasic(VBScript) and one based on C and ECMAScript(JScript). ReactOS needs a scripting engine, doesn't it? First we should decide which scripting language(s) we incorporate into ReactOS. e.g:
Python, Perl, Ruby
By including these scripting we could also break the C hegemony of ReactOS.

Re: ReactOS Scripting Engines(e.g Python engine)

Posted: Sat Oct 06, 2012 6:18 pm
by alfanak.net
what about VisualBasic like langauge?

Re: ReactOS Scripting Engines(e.g Python engine)

Posted: Sat Oct 06, 2012 8:23 pm
by Z98
The by-default scripting engine in ROS will support the same languages as those included by default on Microsoft's Windows variants. Any others that a user wants, they are free to install themselves.

Re: ReactOS Scripting Engines(e.g Python engine)

Posted: Mon Oct 08, 2012 8:03 pm
by milon
I agree with Z98. It's better to maintain compatibility since that's the whole point of ROS. If we add additional scripting languages, then we break compatibility with Windows. It's better for users to add their own additional languages.

Re: ReactOS Scripting Engines(e.g Python engine)

Posted: Tue Oct 09, 2012 10:24 pm
by alexei
When ROS becomes compatible enough, end-users would be able to install WSH 5.6/5.7. So, it should be no problems with scripting.

Re: ReactOS Scripting Engines(e.g Python engine)

Posted: Wed Oct 10, 2012 7:03 pm
by milon
I think MS would frown on WSH being installed on ROS. We ought to provide our own scripting host, really. I don't think it's right to expect every user or company with ROS to break Microsoft's EULA. (I'm making the assumption that the EULA prohibits WSH being installed on non-Windows systems. I could be wrong.)

Re: ReactOS Scripting Engines(e.g Python engine)

Posted: Fri Oct 19, 2012 8:03 am
by alexei
There are WSH redistributables (5.6 and 5.7), wich are supposed to come to user as as supplement to some application.
If MS would try to disallow such applications to run on ROS it would be considered monopolistic and it would cost MS big $$.
In fact, suing MS in EU for prohibitive licensing may bring ROS a lot of money :)

Anyway, if you don't want to go this way, make WSH clone that would work with Sun (now Oracle) JVM.

Re: ReactOS Scripting Engines(e.g Python engine)

Posted: Sat Oct 20, 2012 2:29 pm
by erkinalp
alexei wrote: In fact, suing MS in EU for prohibitive licensing may bring ROS a lot of money :).
Legal but how much ethical(I think a compensation like this help ReactOS economically,but it may cause disapproval)?

Re: ReactOS Scripting Engines(e.g Python engine)

Posted: Mon Oct 22, 2012 5:13 pm
by milon
Suing another entity just because there's a chance of making money is highly unethical.

If that doesn't sway you, think pragmatically: Making an enemy out of MS would be a Very Bad Idea. We might (ha!) win the first battle, but we would lose the "war" that would follow. We would lose badly. MS knows how to use its money.

Re: ReactOS Scripting Engines(e.g Python engine)

Posted: Tue Oct 23, 2012 11:03 am
by PurpleGurl
milon wrote:Suing another entity just because there's a chance of making money is highly unethical.

If that doesn't sway you, think pragmatically: Making an enemy out of MS would be a Very Bad Idea. We might (ha!) win the first battle, but we would lose the "war" that would follow. We would lose badly. MS knows how to use its money.
I get your point. [Urinary skill competitions] are usually not a good approach to doing things. There have been things they have let slide so far. If you get on their bad side, they will likely throw as much mud as they can and see what sticks. Some companies when crossed have the policy of sue first and ask questions later. So we want to avoid all that drama. We just want a good open source OS that will run as much as what Windows will run as possible, not make trouble.

Yes, we need a good scripting host to be complete. There might even be open source projects already. But we have to get careful and not embed code that Microsoft is merely giving a free licensing grace period on. That is the problem with Mono and C#. They said it could be used free of royalties or licenses the first year, if I read and remember correctly. So you don't want to get stuck in a dependency on Microsoft code and then have them to change the license terms midstream.

Re: ReactOS Scripting Engines(e.g Python engine)

Posted: Sat Oct 27, 2012 12:31 am
by Acamapichtli
¿not LUA?, ¿Is there a problem with the MIT license?
some information

Re: ReactOS Scripting Engines(e.g Python engine)

Posted: Sat Oct 27, 2012 11:05 am
by zydon
Why not a combination of AJAX. CSS and JaveScript?

The opensource structure already on the Net, just make it natively available to ROS with an easy to learn and use version. What is left to do is to make a ROS scripting IDE to speed up the scripting project.

My guesses, that is what Android and Windows 8 does with the Java/Dalvik and HTML5 metro application.

Re: ReactOS Scripting Engines(e.g Python engine)

Posted: Sat Oct 27, 2012 6:44 pm
by Acamapichtli
zydon wrote:Why not a combination of AJAX. CSS and JaveScript?

The opensource structure already on the Net, just make it natively available to ROS with an easy to learn and use version. What is left to do is to make a ROS scripting IDE to speed up the scripting project.

My guesses, that is what Android and Windows 8 does with the Java/Dalvik and HTML5 metro application.
Is true, we should see the new type mobile technologies.
probably try a combination of several scripting languages​​,
especially those that consume the least resources possible to not affect the battery life of mobile devices and prevent overheating.

Re: ReactOS Scripting Engines(e.g Python engine)

Posted: Sat Oct 27, 2012 8:17 pm
by Z98
Reality check here, guys. The project's goals are to provide a compatible OS with NT5.2, not dump in something that not even Unix people use for scripting purposes.

Re: ReactOS Scripting Engines(e.g Python engine)

Posted: Sat Nov 03, 2012 8:56 pm
by zydon
ROS don't need a scripting engine. It need a visual app programming IDE and a compiler. Even a kid could write an application in ROS. A good example is App Inventor for Android. If something like that could be ported into ROS to take advantages of batch scripting and implemented Win32 libraries, a lots of times will be saved for ROS users to create productive applications. Probably, a ROS App market will follow later.