I don’t think the API programmers should get scared just yet, but is there a day coming when visual programming will completely replace custom code? Julien seems to think so:
“I firmly believe Dynamo could be used for many many purposes, and addin-like behavior is one… Definitions are easy to share and update. Users can tune them with only some basic Dynamo skill. It is not the same with addins. It is a lot of work to manage and deploy. And users will not be able to tune things. Same thing for macros.”
This topic is somewhat of a work in progress (I know Julien and a few others have been chasing how to make this happen nicely). Lev Lipkin made a comment on the thread, which reads a bit like a how-to, but to my knowledge it is probably more of a wishlist at this stage.
Permalink Reply by Lev Lipkin Dynamo when working on Vasari beta 3 has node “Face From Points” (which needs n x m grid of points) and “Replace Solid Faces” (which would keep adjacent faces as bounds of the resulting Solid). Resulting solid could be put into Form using “Bake Solid as Revit Element” node. Hope this might help.
EDIT The merging of DesignScript and Dynamo was confirmed by Ian Keough:
@lukeyjohnson not much news here. Dynamo and Design Script have merged. It’s called Dynamo, but has the DS virtual machine. — Ian Keough (@ikeough) November 1, 2013
There is some interesting “fluidity” of language in discussing DesignScript, Dynamo, Revit and Vasari in the following two class descriptions of AB2551… I guess all will be revealed at the AU class on Thursday, Dec 5, 8:00 AM – 9:30 AM.
From this: snapshot of the page as it appeared on 22 Oct 2013 12:40:35 GMT
From the github page: uses a python script to automatically generate Revit journal files. When run, these journal files handle opening a specified model, instigating the testing plugin, and running the specified test. This document outlines the components of the Dynamo Revit Test Framework and provides examples of how to run NUnit tests against Revit from the command line. … results file is a proper nunit results file and should be able to be parsed as such by continuous integration systems like Jenkins, etc.
These fractals can both be drawn by emulating a pen: we keep track of the direction the pen is facing, and we can make the pen draw lines of a certain length in its current direction. We can turn the pen, and we can draw with the pen. These can be emulated with Transformations: turning applies a rotation to the pen’s transformation, and drawing adds a translation (and the end point of the draw operation can be stored as an XYZ for creating line geometry later).
From Zach Kron’s buildz blog: Peter Boyer, Matt Jezyk, and I did a presentation on getting started with Dynamo, and I have posted the step by step instructional on the GitHub wiki. If you are just looking to get started, or have mastered the initial concepts, this pdf can help. Starting from the basics of how to launch and make a point, through formulas and custom nodes.
The lessons are: -Getting Around in Dynamo: Installation and Interface -Create a Point, or, “Hello World!” -Creating and Laying Out Geometry on Lines, Grids and Lattices -Synchronizing Family Instance Parameters -Doing Basic Math with the Formula Node -Attractors: creating relationships between elements -Using Revit Geometry in Dynamo and Placing Adaptive Components -Using Python to Build a Sine Wave in Dynamo -Using Custom Nodes and Recursion to Create a Fibonacci Sequence