XWidgetSoft Forum

Feature Request: incorporate ECMA 1.4 javascript
Page 1 of 1

Author:  yereverluvinuncleber [ 2017年 Mar 11日 04:42 ]
Post subject:  Feature Request: incorporate ECMA 1.4 javascript

Xwidget, the desktop widget design tool, uses a primitive emulation of javascript as its scripting language (along with an approximation of vbscript) however, neither of these implementations is anywhere near complete. The scripting in the Xwidget engine is a bespoke implementation and as such is merely some glue between the IDE and the cores to allow users to customise the extra functionality that is provided by 'cores' or external data sources.

This is an unsatisfactory approach that means the scripting language will never receive the development it really requires leaving the scripting methods as the poor relation with regard to developing actual programs. Without the ability to extend widgets ourselves through scripting, more cores need to be written to allow access to new and fresh data sources but these are closed-source and written in C++ and without the main developer being available 100% of the time the existing cores will degrade over time (generally stop working in relation to their changing data sources) and new cores have been proven to be very slow to arrive.


If the xwidget environment is ever going to be considered as a serious contender for real widget development it MUST incorporate one of the main javascript engines that are available that follow ECMA standards as defined by the ECMA body: https://en.wikipedia.org/wiki/ECMAScript

If Tony, the Xwidget designer was to incorporate such a 3rd party open source engine (there are several available that others incorporate into their engines) and simply make the additional xwidget functions available to it (via cores) then it would allow developers to use either xwidget's cores or build their own functionality in javascript. It would open the xwidget engine to the world of javascript that is already extant. Hundreds, if not thousands of javascript programs would then be able to run within xwidget. Potentially, most if not all the code that you create for Xwidget would become available to the web.

It frustrates me that Tony set out to create a partial simulation of javascript rather than implementing an existing open source engine. If he had done then most of the limitations that xwidget is experiencing would have been overcome as you could have called upon off-the-shelf functionality to solve any coding problem encountered.

Feature Request: incorporate ECMA 1.4 javascript (or later version) into the new Xwidget 2.0 environment and watch Xwidget mature into a real widget programming environment.

http://duktape.org/ Duktape is such an embedded environment usable from C++. It would truly transform Xwidget from a toy to a serious tool.

Author:  digigamer [ 2017年 Apr 13日 02:23 ]
Post subject:  Re: Feature Request: incorporate ECMA 1.4 javascript

XWidget depends on Windows Script Host (which unfortunately supports ES 3) There is no way to replace it. What you can use is write ES5/6/7 code and use a transpiler like babel and compile it to ES3 compatible code.

Xwidget can however replace the javascript engine (V8, the one that runs in Google Chrome is really easy) but it will render a whole class of widgets unusuable, i.e, the ones that depend on Microsoft ActiveX.

Author:  yereverluvinuncleber [ 2017年 Apr 20日 03:25 ]
Post subject:  Re: Feature Request: incorporate ECMA 1.4 javascript

I hear what you are saying with regard to ActiveX Digigamer. It is complex.

I am just thinking of cross-platform compatibility and code re-use.

Other widget engines use alternative javascript engines but manage to expose the activeX APIs successfully. Obviously this does not allow cross-platform compatibility but would retain the windows functionality.

Page 1 of 1 All times are UTC - 8 hours
Powered by phpBB® Forum Software © phpBB Group