Hi I second to all Asa points > 13. This one is tough... Grasshopper should be a part of Rhino so that > every action taken in Rhino had a node representation...
>Yeah, I'd love for this to happen, but it would require a rewrite of >all of Rhino. Almost all 20 developers working for 4 years, and that's >not to mention the hundreds of plugins written by other companies... I >think it's safe to say this is not going to happen. >Perhaps the History feature in Rhino itself will become a bit more >flexible and accessible, which will allow me (but only to a degree) to >'read' the history record and convert known History tags into >Grasshopper components. mmm... any development in that direction is good, but I think that sooner or later it will have to come to that... I have another tough one.... Multiple definitions per Rhino file... maybe each Object/block could have a grasshopper definition with its own remote control... this could allow to have dynamic components like sketchup only waaay much more powerful. And this way you could make definitions at different levels... it could appear as a block node in the main definition and it would behave like a cluster (not like clusters today, but as what cluster will be)... Frane
