-
Notifications
You must be signed in to change notification settings - Fork 26
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
GH_UI_overhaul #169
GH_UI_overhaul #169
Conversation
@obucklin cool! can you attach a Rhino+GH doc which demonstrates the new UI? |
yeah where do I do that? |
you can zip them and drag and drop onto the main PR comment |
OK Done. Also ready for review. Thanks!! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the new flow! left first round of comments.
Please run invoke format
and invoke lint
and fix any issues.
@@ -167,6 +167,14 @@ def __init__(self, beam): | |||
self.processings = [] | |||
self._et_element = None | |||
|
|||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to many spaces around method, run invoke format
@@ -167,6 +167,14 @@ def __init__(self, beam): | |||
self.processings = [] | |||
self._et_element = None | |||
|
|||
|
|||
def reference_surface_from_beam_face(self, beam_face): | |||
""" Finds the reference surface with normal that matches the normal of the beam face argument""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Parameters
and Returns
missing in docstring
|
||
|
||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lots of spaces. run auto-formatter
src/compas_timber/ghpython/components/CT_Joint_Rule_Topology/code.py
Outdated
Show resolved
Hide resolved
src/compas_timber/ghpython/components/CT_Joint_Rule_Topology/metadata.json
Outdated
Show resolved
Hide resolved
def comply(self, beams): | ||
try: | ||
return set(self.beams) == set(beams) | ||
except KeyError: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When is a KeyError
raised?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm good point. what kind of error should we raise? maybe comply should check for topo match...?
…compas_timber into compas_fab_test1
…compas_timber into compas_fab_test1
args = {"cutoff": Cutoff} | ||
options = JointOptions(FrenchRidgeLapJoint, **args) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like FrenchRidgeLapJoint
doesn't take a parameter cutoff
:
def __init__(self, beam_a=None, beam_b=None, gap=0.0, frame=None, key=None): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There's a couple of issues still open (rule priorities), but I think we can address them in other PRs since this one is big enough.
Pending the build (Actions) all completing fine, and assuming the concept is OK with everyone (e.g. @jonashaldemann) I say we can merge this.
This is a major rework of the Grasshopper UI.
I added two new Joint Rule components:
-TopologyRule allows users to define a joint type to be applied on a detected topology. This has default joints in case none are defined
-DirectRule allows users to directly define joints between a pair of beams.
I changed the Category rule component to take JointOption components as input instead of text tags.
I changed the Automatic rules component to process the new rule types. The rules are applied such that Direct rules override all other rules, and category rules override topology rules.
I added JointOptions class to connections/joint.py which is a container for joint type and kwargs for specific joint parameters
I added JointOption GH components for each implemented joint type, which act as the input to define joint type in the Rule components
I changed JointDefinition class, Assembly GH component, and Automatic Rules GH component to allow kwargs passthrough for joint parameters
What type of change is this?
Checklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.CHANGELOG.md
file in theUnreleased
section under the most fitting heading (e.g.Added
,Changed
,Removed
).invoke test
).invoke lint
).compas_timber.datastructures.Beam
.GH_UI_Sample.zip