algorithmic modeling for Rhino

I am thinking about doing a patreon supported weekly show where I describe a component or make something cool and describe how.

I made a lot of videos several years ago that translated Daniel Shiffman's Nature of Code into Python in Grasshopper. I am getting back into grasshopper and looking for a way where I can make grasshopper videos in a way that it makes sense for me to do so.

Let me know if these kind of videos would be helpful to the community. Or if anyone has any ideas about how I can put my grasshopper skills to good use.

Views: 380


You need to be a member of Grasshopper to add comments!

Join Grasshopper

Comment by Kim hauer on November 23, 2015 at 10:10am

Hi Jake

From personal experience I know its a lot harder to make an instructional video, then it is to watch one. I applaud your efforts, and I hope you continue on this journey. 

Comment by Pieter Segeren on November 21, 2015 at 4:56am

Hi Jake, I can't say if new users will be interested or not (I hope so), but I do have some feedback for you.
The black viewport background makes it hard to see (on my screen at least) the points and curves being drawn. I would use components with icons on them (see my arguments here). I would try to avoid to construct a point from coordinates to then deconstruct that point into its coordinates, that seems superfluous, and to me at least - bad practice. Also I would try use the correct naming: i.e. not call the graph mapper curve handles 'circles'. Hope this contributes something.

Comment by Jake Hebbert on November 19, 2015 at 8:06pm

Hey Daniel,  Thanks for the feedback.  It interests me to know what people want so your reply was great.

My basic thinking about the layout of the video right now is:  

1. A short intro

2. Description and demonstration of the component

3. Example

This way if people just want a description of the component they can stop watching before the example section.

For this video I explained the example I made at the end.  So maybe that is a waste of time?  Maybe it is better if I show an example and then post pictures of the components. That might be easier for people to build it themselves and get a deeper understanding.

I agree that it is best if there is only one idea covered per video and I will try to do that in the future.

I think that the winform with a fragmented video tutorial is a good idea but for me right now would be too hard to setup.  

I think my videos will have to be within the 6-8 minute range, but I will try and we can see what will happen.  (I originally had another example in the video above but it made the video 15 min and I thought that was way too long).


Shout out to NARUTO. Its been awhile. Hello.

Comment by Daniel González Abalde on November 19, 2015 at 6:58pm

Hi Jake,
I do not understand spoken English so I can not comment about your video, but this subject interests me.

I think we need a program to teach gh kindly. The new users are quickly saturated and that limits learning, too many plants in a pot. So I think that, for the beginner, at the stage of knowing the environment/components, it is preferable to throwing many seeds, but the plants grow slightly. Ie, talking of many components, but without going deeper into them, only what is necessary. Thus I believe that acquire a small base of the possibilities of gh, what to do with the components, but not force them to hold a lot of data in the head, because there are already too many basic components. And above all, do it fast, light, entertaining.

Who needs Legos having Grasshopper? :)

I think the most friendly way to do this would be with short videos (or other animations), of 1 or 2 min, very short, or even, if possible, make a form/window for the canvas containing videos of 10-30 seconds, accompanied by text, so that's a step by step, the user sees a short video and realizes himself, then press the play and displays the following minivideo. This could give all the necessary information of a component, but it is the user who sets the rhythm, their rhythm. This approach should also contain little/a bit of text, because if too most probably will not be read or read quickly through. Simplicity, one shot, sexy, and next thing.

Well, maybe this approach (using a winform with a fragmented video tutorial to explain a component step by step) is not the most appropriate, or perhaps more complex to develop this mold, but I definitely think that any learning is welcome/helpful, definitely.

Comment by 筑梦NARUTO on November 19, 2015 at 6:49pm

Thank you Jake, this will be a great work




© 2022   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service