You have also this one where all is explained! Maybe more shortly! ;)
French on left, English on the right!
https://moiscript.weebly.com/biblio-elephant.html

Due the war all links from Max Smirnov are not accessible! :(
So take the James all in one !

Hi, Michael.

Thank you for showing me the right and official direction. There's no particular project at the moment, rather I just want to 'doodle' with it to familiarize the concept and workflow.


Pilou, thank you for the additional info.



Cheers!

Hi Elang,
I would suggest reading the MoI Wiki on the nodeeditor, and Macro information, and becoming familiar with the numerous "non-visible" features.
...selecting groups of nodes and moving them, quick copy of a node, Info box, etc. Ctrl-C, right click, ..., Run, Stop, resetting output nodes. Accessing Documentation...

Also entering some of the working nodes, such as in Pilou's documentation, and James posts, etc.

Perhaps avoid some of the old node program examples, with red nodes, which are missing, or not up to date.

Also, for Windows, create a Library directory for quick access to the MoI / AppData / Roaming > Nodeeditor directory.
Also create a NodePrograms directory, for saved node programs.

I prefer the Light color node canvas.
Set up a MoI keyboard shortcut to the Light canvas.
Also do a shotcut key for the "dark" canvas, to allow the opening of a second canvas, if desired.
There is a third canvas theme by James...

To the degree possible, I prefer a grid-like arrangement of nodes, with data flow mostly from left to right on the canvas.
(Rather than creating a "rat-nest" of wires.)

- Brian

I like the nodeeditor program a lot. It is not perfect. Sometimes nodes fly off. Spacing of nodes can be a bit variable. Macro list does not scroll.
Run can cause different behaviours. I still get confused saving vs exorting a macro... Then there is the Multiplexing stuff...

No one is making extensions>Documentation>EN (or >FR) files, for the nodeeditor. Have not seen any other languages, except maybe RU.


We can hope for future improvements ???

Hi Elang,

re:
> There's no particular project at the moment, rather I just want to 'doodle' with
> it to familiarize the concept and workflow.

If you have no specific goal in mind then probably you don't need to learn the node editor.

The node editor is an alternative way to construct models by using a type of visual programming language.

When using it you will be constructing a model by setting up a series of instructions rather than using the regular drawing tools.

It's primarily of use for certain specialized types of models that involve some kind of repetitive pattern that would be awkward to draw directly.

If you don't need to construct that particular kind of specialized model type then you would not really gain any benefit from using the node editor.

- Michael

Hi, Brian

Thank you very much for the insight. I'll make sure to follow through.

Sincerely.

Thank you for your response, Michael.

The fact that I don't have a specific goal doesn't imply I'm unaware of how valuable the node editor is. I'm sure it'll be useful (I'd prefer to say "mandatory") to model recurring patterns and the like, especially if there's a lot of room for changing the object on the fly.

To acquaint myself with the tool, I'd want to doodle with it (modeling and altering recurrent patterns model).

Cheers!

Hi Elang, if the node editor would be useful for you but you're having difficulty getting started with it, you might have more success using the Grasshopper node system in Rhino instead. There are a lot more supporting materials like training videos and books and such for that system.

- Michael

Hello there, Michael...

I manage to make it work somehow.



Now is the time to learn more about it and play with it.

Cheers!