Hey, I'd like to discuss a possible Install.pyw.
(and Uninstall.pyw as well).
Should it be included in the core .zip, or packaged seperately? I am actually inclinced to include this.
Specs:
An install package should:
1. Install the drpython folder to an appropriate standard location on a user's machine:
Windows: Program Files/drpython
Linux: /usr/local/drpython (with a link in /usr/local/bin).
Mac: ?????
2. Install the drpython prefs folder
Linux/Mac: ~/.drpython
Windows: userdire/drpython
3. Allow the user to install plugins from the zip files.
In regards to 3:
I am thinking having plugin writers include a
".drpy.plugin" file (eg "SearchInFiles.drpy.plugin),
that can be read, and will include the plugin file to be installed (.py, etc).
If this file is found, it will install (directly, not via index) the plugin, and run any .install script found.
If not, it will prompt the user to select the .py file to install.
What thoughts?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey, I'd like to discuss a possible Install.pyw.
(and Uninstall.pyw as well).
Should it be included in the core .zip, or packaged seperately? I am actually inclinced to include this.
Specs:
An install package should:
1. Install the drpython folder to an appropriate standard location on a user's machine:
Windows: Program Files/drpython
Linux: /usr/local/drpython (with a link in /usr/local/bin).
Mac: ?????
2. Install the drpython prefs folder
Linux/Mac: ~/.drpython
Windows: userdire/drpython
3. Allow the user to install plugins from the zip files.
In regards to 3:
I am thinking having plugin writers include a
".drpy.plugin" file (eg "SearchInFiles.drpy.plugin),
that can be read, and will include the plugin file to be installed (.py, etc).
If this file is found, it will install (directly, not via index) the plugin, and run any .install script found.
If not, it will prompt the user to select the .py file to install.
What thoughts?