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

New hook for launching v2.0 plugins #197

Open
ryanfobel opened this issue Nov 30, 2016 · 1 comment
Open

New hook for launching v2.0 plugins #197

ryanfobel opened this issue Nov 30, 2016 · 1 comment

Comments

@ryanfobel
Copy link
Contributor

ryanfobel commented Nov 30, 2016

MicroDrop v1.0-style plugins based on PyUtilib are launched by importing the plugin's root directory. The proposed v2.0 plugin framework aims to be language agnostic, and therefore we need a new method for launching plugins. One option could be to use a hook script -- e.g., on_plugin_start.bat (Windows) or on_plugin_start.sh (Linux/Mac OS) -- similar to the on_plugin_install scripts already in use.

If we do decide to go this route, we will also need to figure out what (if any) arguments should be passed to this script. For Python-based plugins, we somehow need to pass the path to the Python executable and we would probably need something similar for other interpreted languages. One option would be to store these paths in some kind of "environment definition" file that could be accessed via the hook scripts, e.g.:

python_path = x
node_js_path = y
java_path = z
@cfobel
Copy link
Contributor

cfobel commented Dec 7, 2016

We could adopt the same approach as used in Conda build. Conda build uses environment variables to pass context to the build script (i.e., bld.bat).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants