Separate Laubwerk Plants and Python folders #20
Labels
enhancement
New feature or request
Comments
|
The current Add-on preferences panel provides a single Laubwerk Install Path to configure. To address this issue, the proposed fix would be to include two paths to configure, one for Plants and one for Python. |
dvhart
added a commit
that referenced
this issue
Jun 15, 2020
The Laubwerk Plant Kits allow the user to specify different locations for the Plants and the Python Extension. Allow for this by specifying the two paths individually in the Addon Preferences, rather than assuming a single top level Laubwerk install path. To be able to check the two paths and provide meaningful error messages in the preferences panel, convert the ThicketStatus object from an enum to a simple object with several bool members. Change the lbw_sdk_valid semantics to mean the laubwerk module was successfully loaded. Drop the rebuild_db state as this is equivalent to the ready state. Simplify installation for the common case by providing default paths for both Windows and Mac (Darwin) users via the platform.system() call. Fixes: Issue #20: Separate Laubwerk Plants and Python folders Signed-off-by: Darren Hart <dvhart@infradead.org>
dvhart
added a commit
that referenced
this issue
Jun 15, 2020
The Laubwerk Plant Kits allow the user to specify different locations for the Plants and the Python Extension. Allow for this by specifying the two paths individually in the Addon Preferences, rather than assuming a single top level Laubwerk install path. To be able to check the two paths and provide meaningful error messages in the preferences panel, convert the ThicketStatus object from an enum to a simple object with several bool members. Change the lbw_sdk_valid semantics to mean the laubwerk module was successfully loaded. Drop the rebuild_db state as this is equivalent to the ready state. Simplify installation for the common case by providing default paths for both Windows and Mac (Darwin) users via the platform.system() call. Fixes: Issue #20: Separate Laubwerk Plants and Python folders Signed-off-by: Darren Hart <dvhart@infradead.org>
|
The experimental v0_3_1-alpha2 release contains the lbw-paths branch including the updated preferences panel show below:
|
dvhart
added a commit
that referenced
this issue
Jun 21, 2020
The Laubwerk Plant Kits allow the user to specify different locations for the Plants and the Python Extension. Allow for this by specifying the two paths individually in the Addon Preferences, rather than assuming a single top level Laubwerk install path. To be able to check the two paths and provide meaningful error messages in the preferences panel, convert the ThicketStatus object from an enum to a simple object with several bool members. Change the lbw_sdk_valid semantics to mean the laubwerk module was successfully loaded. Drop the rebuild_db state as this is equivalent to the ready state. Simplify installation for the common case by providing default paths for both Windows and Mac (Darwin) users via the platform.system() call. Fixes: Issue #20: Separate Laubwerk Plants and Python folders Signed-off-by: Darren Hart <dvhart@infradead.org>
dvhart
added a commit
that referenced
this issue
Jun 21, 2020
The Laubwerk Plant Kits allow the user to specify different locations for the Plants and the Python Extension. Allow for this by specifying the two paths individually in the Addon Preferences, rather than assuming a single top level Laubwerk install path. To be able to check the two paths and provide meaningful error messages in the preferences panel, convert the ThicketStatus object from an enum to a simple object with several bool members. Change the lbw_sdk_valid semantics to mean the laubwerk module was successfully loaded. Drop the rebuild_db state as this is equivalent to the ready state. Simplify installation for the common case by providing default paths for both Windows and Mac (Darwin) users via the platform.system() call. Fixes: Issue #20: Separate Laubwerk Plants and Python folders Signed-off-by: Darren Hart <dvhart@infradead.org>
|
Resolved in release v0_3_1. |
|
hi, how do i fix this, theres an error turning on the add on Latest from GitHub (for testers and developers) |
|
i've downloaded the latest laubwerk 1.0.34 and i install it with custom, it seems it doesn't compatible in my pc? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
John Payne reports that attempting to change the installation path of a Laubwerk Plant Kit on Windows will install the Plants at the specified destination, but the Python SDK is still installed in "C:\Program Files".
If this is by design, the Thicket Add-on preferences may need to allow specifying the Plants and Python folders individually, rather than assume they both exist under a common Laubwerk installation path.
Need to confirm intent with Laubwerk.
The text was updated successfully, but these errors were encountered: