Interesting! and this online Nodes prog could export too?

I suppose yes! ;)
"Easily export your piece of work at any time. Embed it into your website or use it for any kind of creative installation."

Ok, thank you for the link.

I am attempting to simulate the Explodemove of two Voroni patterns extruded as Pilou's demo below, but with a new node on the NE (node editor, elephant some call).

Ref:
http://moi3d.com/forum/index.php?webtag=MOI&msg=10470.4

The problem that is happening with my NE code is, everything is exploding when it should stay as a solid when moved.

If the objects are defined and applied, then the explodeMove is executed from the command line, it works fine.

The factory API for explodeMove is being guessed at by trial and error. Mostly error.

factory('explodemove', objects, distance, point);

Is there an additional parameter that says to keep the objects solid and not explode?

Thank you,
Wayne

Here are the differences between the two results.

The command line keeps all the objects together.
The NE code takes all the solid objects and separates them.

Hi Wayne, inputs for the ExplodeMove factory go like this:

Index 0 : "Objects" - object list of objects to explode.
Index 1: "Scale factor" - numeric value for scale factor.
Index 2: "Origin" - optional origin point for scaling.

- Michael

Hi Michael,

Thank you for the quick reply. The input parameters you provided are as expected. This leads to additional code is required to filter the objects types and keep the closed objects together. Back to coding...

Thank you,
Wayne

Draft of a 3D log spiral node.
For 2D, set zFactor to zero.
This is just an alpha version with little testing.
I want to add arcLength output...
(Code came from powerConeSpiral script.)

- Brian

Ok, I had to do some deep searches for an answer to my problem. Found the solution to my objects exploding in a rarely referenced documentation by Max Smirnov.

Here he explains the essence of the multi-Process syntax for a node setup:
http://moi3d.com/forum/index.php?webtag=MOI&msg=7713.395

My solution is to simply add a + to the Long mode so the array is processed as one element.

Wow, Thank you Max for that post!

Wayne

Final result of solution:

Good find Wayne.

Was wondering what Lont+ meant.
(I did read that post by Max 5 years ago, but never really grasped it.)

Did a slight upgrade of alpha logSpiral node.
But see that Karsten? already did a curve length node.
So (at least some?) MoI curves have a .length property, so I do not have to re-calculate the arcLength...

- Brian

Cool adaptation! :)

My old experiments.

Cool try! :)

As per Barry's suggestion, here is a kludged together Macro, using the Concat node, renamed, to enable the creation of a macro node with several lines of text.

Highlight the completed text macro in the nodeeditor canvas, and EXPORT it to the Macro directory, with desired name.
Saving it saves the DocText macro as a node program, so Loading it with Load erases the current canvas screen.
The DocText macro may be entered into a new screen through the right click Macro menu.
Do NOT get the DocText macro with the Load button.
Saving it saves the DocText macro as a node program, so Loading it with Load erases the current canvas screen.
The Macro menu seems to lack a scrolling bar, so space may be limited???

This whole Macro Save vs Export vs Load, versus macroLoad is confusing. There should be a SaveMacro button, and a LoadMacro button? And Macro scroll?
Also, every node Program would need to have its own text macro saved???

Well it is an experimental kludge...I cannot spend any more time on it.

I'm sure Max could do something really good...

- Brian

A few simple tests:
It seems that only one master DocText Macro is needed.
The Macro can be right click MacroSelected to the canvas multiple times, and each canvas copy can have its text modified in different ways, and the canvas .nod program saved in a node program.

But the modifications permute the order of the text lines, which is not good.

- Brian

Edit: Macro Import can import the DocText file from some other directory.

Note, the order of the text lines can be changed by Max' addition a few years ago of the ability to Alt+Drag the input Dots to the Macro. (I had forgotten this.)

Brian & Barry,

Litegraph.js the foundation for NodeEditor contains a "Panel" node (see image below),
which I imagine is for notes within a node circuit. Unfortunately it does not appear to be functional.



Litegraph demo can be found here:
https://tamats.com/projects/litegraph/editor/

James
https://www.instagram.com/nodeology/

Thank you James.
So I finally found the WidgetPanel code here:
litegraph.js zip is at github.

litegraph.js-master>src>nodes>interface>WizardPanel().

It states "Non interactive panel".
So my guess is that it is just a pretty box, which does not have any text ability. (???)
There are a couple of other programs using litegraph, that may use the box, with additions, to display graphics(?)

- Brian

There is a LiteGraph used in blokist.gitlab.io, but I cannot find out where to download it. gitlab site does not recognize blokist.

- Brian

Brian,

Sorry, only include the cascading menus in the image in my last post
to reveal the location of "Panel" node. I should have checked that each tier
of the activated menu items remained highlighted: Add Node/Widget/Panel

The other element in litegraph demo that would be useful in NE is "Add Group"
Groups may be individually named and nodes are within the group border can then
be moved around the canvas as a block.


James
https://www.instagram.com/nodeology/