Milestone 1 javascript plugins infrastructure

[sieukrem]

No description provided.

[WinterSilence]

it's dirty & confused for "examples". why not use prototype & extended classes? If you want, I will help with this. But main problems it's:

1. debug() - week, console - not exists = need better reflection/debug function/class.
2. need minimal class pack: Fillesystem/File, CLI/Terminal, extended Editor (copy/past, find/replace) and GUI classes - abstract Menu, MenuItem, Form/Dialog.

just for examle: https://nwjs.readthedocs.io

[sieukrem]

@WinterSilence help is appreciated!

1. I agree
   • debug was useful at the beginning as there was no VS Debugger Support
   • console is not present
     My idea is first to setup minimal environment for easy development and deployment of plugins. So that such debugging functionality is provided by a plugin. Hence this milestone and PR
2. Classes you are talking about, are definitelly helpful, but before you can start it is importand to define what is their purpose. I would like to distinguish between functionality which is
   • Editor relevant and defines clear and easy to use API abstraction layer.
   • System relevant and reuses as much as possible concepts of Nodejs API due to profit from tonns of examples and documentation on the web. It is clear that only small piece of that is possible, but I am sure some parts of file access, process and console are feasible.

I started already with creating of system relevant functionality as part of this PR. For this purpose I introduced simple testing environment .

I would like if you could take care about e.g. fs or console. Create Issue as part of this Milestone, so that we can discuss on topic.