Display About Third-Party Plug-In Versions

Having trouble to follow what version of which Plug-Ins (Wb, Goat, Mantis, ...) I am using.

I think I have seen a screenshot (by Danny..?) once, where it shows logos in the About-Window. I cant see them on my machine though.

Has this been changed? Is this a Bug?

Is there a different way to check third-party versions?

Replies to This Discussion

Permalink Reply by David Rutten on October 8, 2012 at 8:41am

Click on the little black icon in the upper left corner of the banner. But note, not all plugins add their icons to this repository.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by phillip on October 8, 2012 at 9:24am

Ah, I see. Thanks.

As you said, unfortunately I can only see some of the plug-ins.

So I guess for the others, the only option is to remember or check the edit date in the explorer?

Just out of interest:

I do not really understand the groups of the native components - e.g. Math seems to include a lot of other components as well, curve includes image gallery... what is behind this?

Permalink Reply by David Rutten on October 8, 2012 at 11:22am

I made it so that libraries that do not provide assembly information are still presented on the banner using an info-stub. So come the next version, all loaded plugins should appear on the banner.

It's a lot more work to add a new library than to just add a component to an existing library. Things like Image Gallery and LolCats are in curve simply because I didn't want to add a new library and because I wanted to write them in C#. There's sometimes no logic whatsoever to where a component is defined. It's also fairly irrelevant, as the only thing that matters is where an icon appears on the tabs, and those positions do not correlate with GHA files.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Andrew Heumann on October 8, 2012 at 12:10pm

are some of the libraries written in C# and others in vb.net?

Permalink Reply by David Rutten on October 8, 2012 at 1:07pm

Yes. VB.NET:

Grasshopper.dll
Mathematics.gha
Surface.gha
Triangulation.gha
Vector.gha
GalapagosComponents.gha
LegacyScript.gha
Script.gha
GrasshopperSDKDocDL.exe
GrasshopperImageStitcher.exe

C#:

GrasshopperPlugin.rhp
Curve.gha
Transform.gha
Galapagos.dll
Field.gha
GH_IO.dll
GH_IO_Viewer.exe
GH_Util.dll
TheSwarm.dll

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by phillip on October 9, 2012 at 1:43am

Interesting.

Is this because of different people working on the librarys, some things are easier to achieve in either way or what would be the reason, you are not using just a single language?

What would be your guideline if you start a new library?

Permalink Reply by David Rutten on October 9, 2012 at 4:23am

When I started Grasshopper (Explicit History rather) I only knew VB. These days I tend to pick C# when starting a new project because it makes it somewhat easier to share code with other McNeel employees, who tend to be more comfortable with C# instead.

I'm still somewhat miffed that VS can't handle both VB and C# code in the same project, or better yet, the same file.

David Rutten

david@mcneel.com

Poprad, Slovakia

RSS