allow for local addons to be specified via absolute paths #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this is a PR to work through getting local addons to work in the gui.
I am allowing them to be specified at the command line via absolute paths which get converted to relative paths to the project in the command line tool as the project is generated (ie, if you have a folder called localAddons in the root, and you pass in -a"/users/......./ofxTemp" it will be like adding ../../../localAddons/ofxTemp to your project) . On the gui side, it's much easier to take a relative path to OF for the local addon (or absoute path) and store it internally as an absolute path....
I've added support in settings.json and in the gui now, just working on storing and passing through the right things, and on dealing with parsing addons.make on import.
as I get stuff to work, I'll check it in...