Hey David Admittedly, I didn't get your angle at first. It seems like you're trying to streamline the creation of definitions, limit the number of components used. That could be fine, but that amount of streamlining may stifle some people (make it too easy...). Much of the parametric creativity comes in the more explicit connections. Centroids, though, are always helpful and bounding box seems like the logical place to put it for connecting, positioning and general organization.
While I'm here, I thought I could give a little wish list: --Right now I'm working with surfaces boxes in designing facades, and would eventually like to get dimensions for the adjusted modules for fabrication (length of brep edges, volume, area, etc.) Perhaps that's more than just a wish list item... ;-) --multi preview toggle, so we don't have to go to each component. --Previously opened definitions aren't queued in the "recent files" pull down menu; only what has been opened in a current session. That would be cool to have. --Something like labels or titles to label sections of a definition. Like completely dumb stickies with a couple different colors. Great for organization, explanation and sharing of info. That's all for now. Thanks again. rob On Jan 24, 11:13 am, Rchitekt <[email protected]> wrote: > David, > You beat me to it :) > > On Jan 24, 8:09 am, Rchitekt <[email protected]> wrote: > > > Hi Bas, > > I think David was after something slightly different. I'm pretty sure > > he was asking about specific translation conversions. Meaning, if a > > component wants a Brep for the input and you give it a surface, the > > surface will be converted into a Brep on the fly. The same is true > > for a Curve and a Number. If the component you are working with wants > > a Number input, and you happen to give it a curve, it will > > automatically translate that and output the Curve length as a number. > > There are lots of autoconversions going on, and I think he's asking > > whether or not we have a preference for some of the new conversion > > structures. > > And you should be able to get the length, breadth, and height of a > > bounding box through using the Box Components (Surface/Analysis/Box > > Components). > > Best, > > Andy > > > On Jan 24, 5:35 am, bas <[email protected]> wrote: > > > > Hi David, > > > > I would appriciate such basic functions. Midpoint of a line or curve > > > would be a function I will often use. The Volume centre is now > > > possible via Volume, but this is slowing down the script due to the > > > volume calculation. I would like to add: length, breadth and hight of > > > a bounding box. > > > > Cheers, > > > Bas > > > > On Jan 23, 7:33 pm, David Rutten <[email protected]> wrote: > > > > > Does it make sense to anyone to have default conversions for: > > > > > Curve -> Point (start point? mid point? end point? centre of > > > > bounding box?) > > > > Surface -> Point (centre of bounding box? centre of UV domain?) > > > > Brep -> Point (bounding box centre? Volume/Area centroid?) > > > > Mesh -> point (?) > > > > Box -> Point (... etc. etc.) > > > > Twisted Box -> Point > > > > Generic Geometry -> Point > > > > > And, if so, how would you expect it to work? > > > > > Thanks, > > > > David > > > > > -- > > > > David Rutten > > > > [email protected] > > > > Robert McNeel & Associates
