[Design Change Request] npmjx mechanism

[enricogior]

How npmjx works is not documented. There are actually two npmjx modules, one is just a proxy module that points to the real npmjx module. When you run the "jx npm install" command, jx.exe executes the lib/jx/_jx_install.js script (that is embedded in jx.exe) that downloads the proxy module using a hardcoded url. The proxy module in turn downloads the real npmjx module (using another hardcoded url). The proxy module contains the tar.gz module that is required to expand the real npmjx module.

There are some problems with the current way this mechanism work:

• code duplication: lib/jx/_jx_install.js and tools/npmjx/index.js do the same thing, they download modules from the cloud.
• both scripts contain hardcoded urls (this problem is already tracked by https://github.com/thaliproject/jxcore/issues/8) .
• nothing guarantees that the two modules don't get out of sync pointing to old/wrong urls.
• the current naming and location is confusing: the proxy module lives in tool/npmjx, it should not be named npmjx and since it's not a tool, it should be in the deps/ folder.
• the proxy module seems to be required only in order to download the tar.gz module, therefore why not change the proxy module to just contain the tar.gz code and let the _jx_install.js script do all the heavy lifting of downloading the tar.gz module and the npmjx module.

[enricogior]

It is not documented how the npmjxv311.jx lib is created (npmjxv311.jx is the proxy module used by the "jx npm install" command) The command to create it is:

from the jxcore project root:
cd tools/npmjx/
jx compile npmjx.jxp