Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Milestone 1 javascript plugins infrastructure #91

Draft
wants to merge 14 commits into
base: master
Choose a base branch
from

Conversation

sieukrem
Copy link
Owner

@sieukrem sieukrem commented Jun 9, 2020

No description provided.

Copy link
Contributor

@WinterSilence WinterSilence left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Owner Author

@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.

@sieukrem sieukrem force-pushed the milestone-1-javascript-plugins-infrastructure branch from 880612e to a016a51 Compare June 13, 2020 00:12
@sieukrem sieukrem force-pushed the milestone-1-javascript-plugins-infrastructure branch from e671122 to 7022188 Compare June 13, 2020 21:02
@sieukrem sieukrem force-pushed the milestone-1-javascript-plugins-infrastructure branch from b2b286e to 4e7629a Compare June 14, 2020 18:26
@sieukrem sieukrem force-pushed the milestone-1-javascript-plugins-infrastructure branch from 4e7629a to 239e59d Compare June 14, 2020 19:17
@sieukrem sieukrem linked an issue Jun 14, 2020 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement installation of plugin listed in the repository
2 participants