Search the Community
Showing results for tags 'marionette'.
Found 78 results
I'm curious to know if its possible to display values generated by a Marionette network in the OIP. I've experimented a little with the Marionette OIP controls and I am able to display static info using Marionette.WidgetType.TextStaticParam. I've created a couple of simple custom nodes for Maker Info and Object Name and I'm able to essentially trick Marionette into displaying this info for Marionette Objects (image below). But what if I wanted to display the area of an object generated by a Marionette Object in a static manner like what you see with a regular VW object. Is this possible? Is there a way to feed a variable from a network back to the OIP? I know I can easily display something like this as text on the drawing but I'd like it in the OIP. Thanks, Kevin OIP Example.vwx
I used Fundamentals this am on behalf of a client who has a strong interest in trying Marionette to replace the many Vector Scripts he has created and used for many years. Sadly Marionette is not available in Fundamentals. Given that you have the ability to do scripts in that version would it not be logical to have Marionette there as well.
Marionette was introduced with the intention that non-programmers could learn to use it without having any previous programming knowledge. Personally, I have not found that to be the case. This may be partially because Marionette is still very new and not fully documented, but even if it were, it seems like Marionette's current implementation requires quite a bit of programming knowledge as evidenced by many of the threads in this Marionette forum. It is not in any way user-friendly or intuitive for the 'programming newbie'. Watching any of the thousands of tutorial videos on Grasshopper or Dynamo won't get you very far with Marionette. The written content and presentation on the Vw Dev Wiki has always been intended for a target audience of developers and programmers. It requires a good working knowledge of VS and Python to understand any part of it, and probably most Vw users have no need to ever visit it. In addition to being very 'code heavy', the Dev Wiki is also very 'text heavy', without many pictures or diagrams. Graphically, it is the exact opposite of what the training material for a graphical scripting language like Marionette should look like. Just providing a single-page listing the name and simple description of each node is not enough (especially since it's the same info that you get by clicking on the Node's OIP 'Description' button). We need to have examples of how to use each node including what are its accepted inputs and its expected outputs. The Marionette - Implement a Node page, which I believe is intended to be 'Introductory 101' level, is very heavy into required programming with lots of Python code. Personally, I did not find that page to be very intuitive or helpful; I became lost before I even started. The six Introductory video tutorials posted here are a good start - and certainly more of these videos will be welcome, but... What I think is needed is a separate, dedicated 'Marionette Primer' website along the lines of the Dynamo Primer. Simply putting more info on the Dev Wiki is not the best way to further expand knowledge about Marionette.