I agree that splitting surfaces rather than trimming them is a much easier task. Not having to worry about which results to keep frees things up significantly I put together a quick attempt at this with a scripting component a while back. I haven't done that much testing with it, but maybe it will be helpful too you.
http://www.box.net/shared/nduj84b2v7 I don't believe that GH requires you to know the science of anything. What it does require is that you understand each of the steps and operations that are being performed. I've seen a lot of questions or "reports" about how GH isn't reacting how they think it should, when in reality it is reacting based on the organization and structure of the data that it is given. GH has a specific system by which it performs these given operations. With out it, it would fall apart. I understand that you can use GH without knowing or understanding that system, but it does explain why certain things are done the way they are. I personally see that important to using the tool effectively and getting the most out of it. I also don't see this as something that is centered around programming or requires any programming knowledge. I completely understand that professionals may not have the time to dive into GH as much as they should, but I personally believe that this is a problem with the profession. Architecture completely undervalues the ability to use tools effectively and efficiently, both in education and practice. The reality is that knowing how to use a tool (whether its AutoCAD, Rhino, GH, or anything else...parallel bar, french curves) is important. It can dictate what you can actually achieve with a given tool, how useful it is to the rest of the process, and how long it actually takes you to achieve your task. I'm not saying that an architect should know and understand how to WRITE the tool, just how to use it effectively. I'll leave it at that for now, but that's my take on it. Best Regards, Damien On Apr 13, 11:05 am, dodo <[email protected]> wrote: > Hi everyone, > > thanks for the feedback to my question. > > For the trimming, I agree it is hard to make GH decide on which > surface to keep and which to discard. But I guess GH doesn't need to > discard anything. I just need to be able to split the surface, output > a list of resulting surfaces and then I keep on routing the output > that I need further into my component tree. I just extract the item > that i need from the list. Maybe there would be a way to turn off the > display for the resulting surfaces that I don't want to use or see. > > So for my wish, I guess I change my wish to splitting surfaces rather > then trimming. If that would be possible to do, that would be great. > > I guess there are a lot of people who will use GH for its history and > evaluation capabilities, rather than the programming. These days there > are a lot of discussions going on that dive very deeply into > programming using the VB script component. Which is great, but for me > my biggest wish is to use GH without knowing how to programm. A lot of > professional just don't have the time to learn programming and people > are not using scripting so often in everyday business that you keep > forgeting how you did it. That is why GH is so important for pople > like me who are professionals with no time on their hands, but like to > use the advances of what GH prividing to rhino. > > We need a tool like GH, but we just don't have the time to dive into > the science of it. GH is so easy and intuitve right now, please keep > it that way, otherwise GH will become tool for a few people. I like > the tree and branch component. I can't think of a better or more > grafical way to make a difficult subject become so intuitiv to use. > > Thanks David and everyone making this technology available. > > Oliver > > On Apr 13, 4:21 pm, damien_alomar <[email protected]> wrote: > > > The question with splitting becomes how to you specify which region to > > keep and which region to "throw away". When you perform this > > operation in Rhino a mouse click tells Rhino which regions to > > disregard. So how would one perform that mouse click in GH? A UV > > point would be a decent idea, but then that would work for only > > surfaces, not Breps I guess the best way would be to provide a point > > and whichever region its closest to it would be trimmed away. Its not > > 100% reliable, but it could potentially work. > > > There's no need for the Boolean2Objects command equivalent in GH > > because the functionality is there. That command allows you to toggle > > through the different boolean possibilities (A+B, A-B, B-A, A&B), but > > after that, it just performs the given operation (union, difference, > > intersection). All you need to do is understand which operation you'd > > like, and then you can use that particular component. > > > Best, > > Damien > > > On Apr 12, 2:11 pm, Josh7777smith <[email protected]> wrote: > > > > I definitely agree that the trimming functions are limited... On > > > several occasions I have had to bring the function back 3 or 4 steps > > > to split the curves first and reroute those into my function... Also, > > > the boolean2objects commands are completely missing from Grasshopper, > > > is this just due to limitations of explicit history? I use this > > > function in rhino quite a bit, and would very much like to not have to > > > bake all of my objects before being able to further manipulate them... > > > > Thanks, > > > Joshua > > > > On Apr 11, 4:14 am, dodo <[email protected]> wrote: > > > > > /// happy eastern /// everyone, > > > > > Hi David, I was wondering if it will be possible to implement cutting > > > > and spltting of surfaces. Maybe it is allready possible, and I missed > > > > it? I am one of the users who is using GH also for modelling task. May > > > > example is always, if i want to modell a simple computer mouse, I can > > > > extrude all the muose outlines front and side, then the surfaces > > > > overlap and I trim of the edges. In rhino this is history supported up > > > > to the trimming part, I hope it will be supported in V5. Is it > > > > possible to to that in GH, I mean trim surfaces with lines or > > > > surfaces? > > > > > We are using GH for our 3d architectural shape creation, cause it s > > > > great to evalute cost sqm and masses while you editing the basic > > > > shape. It only woks as long you can do it with boolean operations > > > > though. We need to cut and split surfaces sometimes though, Is it > > > > allready possible or will surface cutting and splitting be > > > > incorporated? > > > > > /// thanks and frohe ostern /// > > > > > Oliver
