Hi David, I haven't been pestering you on these forums for a while since I lost the access to the Windoz workstation I was using (I'll have tis corrected shortly because i have a shiny new MBP). I couldn't resist commenting on this discussion though. I Played around a bit With a fun little visual programming environment called star logo TNG. It is developed by MIT's Scheller Teacher Education Program. It is intend to teach children about programming and agent based modelling. The way they approached the Interface was completely different to any other visual programming environment I've seen (this is important since the interface of a visual programming language is effectively equivalent to a text based languages syntax and grammar.) In SLTNG Different blocks snap together in different ways. Blocks have different input and output shapes and these logically correspond to what blocks connect to what. for example a loop block needs a condition to evaluate so it has a space where a logic block can be inserted. logic blocks have a specific shape and only they will click into that particular place.
I'm happy with the basic strategy of GH but it example blocks which attach and so i thought it might be useful if your interested in this leach block idea. http://education.mit.edu/drupal/starlogo-tng Cheers, Dieter Toews On Sep 30, 5:53 am, David Rutten <[EMAIL PROTECTED]> wrote: > Distractions? :) > > It sounds like having 'leech objects' that attach themselves to > regular components/parameters and somehow alter the properties might > be quite an interesting approach. It might even be a solution for > visual Conditionals and Loops. Now you've got me thinking....... > > -- > David Rutten > Robert McNeel & Associates > > On Sep 30, 12:01 am, taz <[EMAIL PROTECTED]> wrote: > > > David, > > > No, I wouldn't say I'd find it necessary. > > > When I put together the pdf I thought (in the case of an exploding a > > box) some may want the individual components results to display > > differently as direct output. That could still easily be done with > > an 'attach' color component just like for meshes. > > > Don't let me distract you with too much talk of colors since I know > > that's farther down the list. > > > taz > > > On Sep 29, 11:37 am, David Rutten <[EMAIL PROTECTED]> wrote: > > > > Taz, Visose, > > > > that indeed sounds like an easy fix. I'mnottoo fond of this > > > particular solution since it might involve some data duplication (the > > > display code still tends to duplicate data in order to prevent null > > > points during viewport redraws, but this is something I'm looking > > > into). > > > > Taz,doyou really need this kind of control on a per-parameter basis? > > > Would it be enough to be able to 'attach' some sort of properties > > > override object to an entire component? > > > > -- > > > David Rutten > > > Robert McNeel & Associates > > > > On Sep 28, 1:14 am, visose <[EMAIL PROTECTED]> wrote: > > > > > What taz explains about the layers parameter and component is exactly > > > > what i visualized that didn't seem to require a big change in how > > > > grasshopper works, just another component. Add rhino layers as another > > > > type of object to be able to link from the rhino model just as curves, > > > > points, etc. The next best thing would be to link materials, and be > > > > able to change some of it's basic properties through grasshopper. I've > > > > read that the main users of grasshopper are architects. Architecture > > > > isnotonly geometry, but also texture, light and color. Make that > > > > parametric too, please ;)- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > > - Show quoted text -
