Luis,

I seems like a watered down version of PanelingTools needs to be
compiled specifically for GH.  Then again I wonder if David has any
thoughts about porting Rhino plug-ins into GH...  Both easier said
than done.

It's interesting that PanelingTools uses history.  I never realized
some plug-ins might be using history in the background, but of course
that makes perfect sense.

Anyway, keep us posted on any progress.  It sounds like your doing a
great job of figuring out what the issues are.

-taz

On Apr 27, 1:44 am, fraguada <[email protected]> wrote:
> In some correspondence with Rajaa, it was explained to me that
> Paneling Tools was history enabled to a certain extent.  I tested this
> out and indeed  this worked.  So, as a preliminary connection, one
> could try communicating between paneling tools and grasshopper through
> this method.  Well, a quick experiment showed that making a reference
> to some flat panels did not work.  It seems Paneling Tools is
> destroying the geometry with each change to the underlying geometry.
> Meaning, yes, it is history enabled, you can change the underlying
> surface, etc and things update, but Grasshopper looses the reference,
> so each time one changes, one must reapply the reference in GH.
>
> Another note, the geometry generated in paneling tools is a bit
> curious.  From what I noticed, surfaces are trimmed or untrimmed, but
> not totally one or the other.  It would be great if everything was
> untrimmed, esp things like triangular panels.
>
> Recently with a client we set up a process to analyze some paneling
> tools geometry with GH.  In the end it worked quite well, but for
> someone just learning these tools, it was many steps to go through
> because of the couple of issues we found.  In any case, it became very
> clear that a seamless marriage between the two systems would be quite
> powerful.  I can imagine thats easier said than done ;)
>
> luis
>
> On Apr 26, 10:22 pm, taz <[email protected]> wrote:
>
> > I'm just bumping this thread.  Command line macros in a VB component
> > could be a good temporary way to use PanelingTools in GH.
>
> > This is the visose example of using functions from the Pointset
> > Reconstruction plug-in.
>
> >http://groups.google.com/group/grasshopper3d/browse_thread/thread/c81...
>
> > -taz
>
> > On Mar 25, 11:30 am, Rajaa <[email protected]> wrote:
>
> > > Hi,
>
> > > At some point we hope to migratePanelingToolsfunctions directly into
> > > Grasshopper or facilitate a more smooth integration.
>
> > > In the meanwhile and for those of you interested in the joint between
> > > the PT & GH, I posted two examples to show how to go between the two.
> > > It basically involves creating a custom select/bake components to
> > > extract/attach serialized names to grid points. Here is the link to
> > > the 
> > > samples:http://en.wiki.mcneel.com/default.aspx/McNeel/PanelingToolsAndGrassho...
>
> > > Let me know what you think.

Reply via email to