He was probably joking, of course. Satire is difficult to transmit through the web. Here's the thread: http://groups.google.com/group/grasshopper3d/browse_thread/thread/3af2a4b27bb000de We were trying to come up with a method of blending lists in gh. I came up with a solution, but then someone posted a scripted solution. I jokingly said that was cheating. David then said that. The fun part was trying to figure it out with the available components, scripting was the easy way out. Of course few people use grasshopper for recreational purposes, so whatever solution is more efficient should be desired.
> Components are one thing, but the data within the components are what really count. So in this case for example, the explode component would be inefficient since it carries the useless overhead of the exploded lines, but what would be the real difference between the divide curve component solution and the scripted solution? The component is more cpu intensive? There must be a line drawn somewhere between ease of use and wasting valuable memory and processor cycles. On Jan 10, 11:14 pm, damien_alomar <[email protected]> wrote: > Components are one thing, but the data within the components are what > really count. A solution that winds up creating more objects will be > more intense to calculate and memory wise as well. Each component has > a copy of the data that goes into it, so the same number of components > with a bunch of boolean values are going to be much less intense than > the same number of components with bReps going through them. > > I'm a little surprise to hear that David said that. Until he's able > to add every little thing thats available in Rhino is available in GH, > then there's always going to be someone saying "but what about this", > and even still there will be those kind of requests. The scripting > components allow people who feel like getting into it to add stuff > that they need. I've had projects where what I've needed is so > specialized, asking David for it would be almost ridiculous and was > completely solved by working it out in a scripting component. I think > the tools that I would consider "missing" from GH are fairly few and > the overall capabilities are almost overwhelming. To consider GH a > failure in any sense would be selling David's efforts way short. > > -Damien > > On Jan 10, 8:51 am, visose <[email protected]> wrote: > > > In this case however both methods (scripting/non scripting) use the > > same number of components. :P > > But yeah, using this workarounds you'll eventually run into problems. > > I just post them for people that are still uncomfortable with > > scripting, that's why some chose to use this plugin i guess. > > David also mentioned once that every time someone has to solve > > something by scripting he feels like a failure. I wouldn't go that > > far. > > > On Jan 10, 3:13 am, damien_alomar <[email protected]> wrote: > > > > Yea that certainly works, but after putting together some pretty > > > complex GH projects, I try to take any steps out if I can as it makes > > > the definition less intense in terms of what it takes to actually > > > calculate the solution. Also, things can get really cluttered really > > > quick, so keeping fewer components out there is better for > > > organization as well. > > > > As it stands, that method works for polylines, but nothing else. You > > > could use the component that I posted with any curve that has a nurbs > > > form to extract the control points. > > > > Best, > > > Damien > > > > On Jan 9, 8:13 pm, visose <[email protected]> wrote: > > > > > > However, you may just > > > > > want to extract the the points of your polyline and then rebuild the > > > > > curve either with those points as control points or as an interpolated > > > > > curve. That's not available either, > > > > > Actually, it is available (if the source is a polyline, that is). > > > > There are at least two methods of doing this with standard components: > > > > 1) Use the 'explode' component to output the polyline's vertices. > > > > 2) Use the 'divide curve' component with the 'split segments at kinks' > > > > option enabled and 'segments' as 1. > > > > > On Jan 10, 1:23 am, damien_alomar <[email protected]> wrote: > > > > > > Well, there's no rebuild component, although I think there should be. > > > > > From a polyline is a little weird though as most of the time > > > > > rebuilding doesn't lead to a solution that's of any real use (straight > > > > > lines to curvy lines has no real "conversion"). However, you may just > > > > > want to extract the the points of your polyline and then rebuild the > > > > > curve either with those points as control points or as an interpolated > > > > > curve. That's not available either, but I had something lying around > > > > > that I modified to extract control points from a curve. See if that > > > > > will allow you to do what you're looking for. > > > > > >http://grasshopper3d.googlegroups.com/web/extractPolylinePts.ghx?hl=e... > > > > > > Best, > > > > > Damien > > > > > > On Jan 9, 5:33 pm, stigvg <[email protected]> wrote: > > > > > > > hi,, sorry to be unclear,,, what I want is just to rebuild the > > > > > > degree > > > > > > of a curve inside grasshopper,, > > > > > > > On Jan 9, 11:24 pm, klint <[email protected]> wrote: > > > > > > > > Not exactly sure what you mean, but in the params tab you have the > > > > > > > Line parameter which represents a list of 3d lines. > > > > > > > > /Lars > > > > > > > > On 9 Jan, 22:04, stigvg <[email protected]> wrote: > > > > > > > > > Hi there > > > > > > > > > I have a set of curves with straight lines only: I would like to > > > > > > > > rebuild those lines in grasshopper, but can not find the tool > > > > > > > > to do > > > > > > > > that,, can you help me,,? > >
