Hi pior.

About the claims to the node editor. Michael explained so that it is clear through a language translator, we use what we have and rejoice.
Yes, it is not perfect, but it grew on the enthusiasm of two people and was supplemented by the rest of the participants of this forum.

And it's all free. And this is the link that James made to put everything in order. It's all in English.

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

@ Prior
Thx for all the advices!
All was made on the fly on a moment of inspiration ... a challenge : translate all Nodes inside the Node Editor itself in French! The funny of this it's that is working for the most current nodes! :)
After the documentation was just a personal notebook checklist memo pad!
(like all my site :)
First for my own practical use...then available for all... but after some years it's appears that is too times consuming !
So following numerous new nodes are not done!
It's was just a base!
And alas due the actual war Max's work is broken!
Sure maybe organisation is maybe a little tricky but it's mine first for my personal speedy use!
If you want make another one don't hesitate! :)
Happy Elephant discovery!

Hello !

Well first of all thank you for all the efforts that obviously went into it, as it looks like it covers pretty much everything.
Depending on how useful the Node Editor turns out to be for my own uses I might end up making a simplified, linear PDF version out of these help pages for easy reading. I'll let you know if that happens.
Regarding maintenance : well, even the most appropriate solutions for the authoring of such pages (like the very popular ReadTheDocs Python generator) can quickly become a pain as soon as the technical aspects (building the pages) gets in the way. So yeah as said I feel like the most streamlined solution is just a good old PDF with a bunch of pictures generated from a text document - just like the UE Compendiums really :)

Anyways, time to learn some node stuff now.

Here's a PDF combining all the help pages I've found, organized linearly. This is very raw as page breaks happen in unexpected places but it does the job of putting everything in one place as opposed to having to click many links. I quickly removed as much fluff as possible (like the repeating groups of links), hopefully without accidentally removing something important. Let me know if I forgot a page or some important ressource.

https://drive.google.com/file/d/1oRpUDw3nsM56R9iha9_vMDMccJCdDtLP/view?usp=sharing

And a source .ODG if anyone is brave enough to get in there and sort the layout :D
https://drive.google.com/file/d/1jbgjPUY9SLsKmEP4oQsRgLboPinfmPCk/view?usp=sharing

It would be interesting to also add some of the images and node networks by @Nodeology, so if anyone as them downloaded already let me know and I'll add them. Or, feel free to add them yourself and re-host.

Best,

P.O.

Hi pior,

Thank you for your work.

For 3840 X 2160 display resolution, the Font is way too small for myself. Zooming in does not help much.

Is there an easier Font to read? I dislike the Font, but do not know which font would be better.

Never used .odg file format. Loaded Libre Office, which promptly crashed on the .odg file...
I've never used Libre Office before...
Is there a better XML editor?
Is there an XSLT stylesheet for the XML document?

- Brian

@Prior
Cool work with my base Elephant Node Editor site! ;)

Hi Brian.

Brian, WM : FWIW it was generated by simply performing a "print to PDF" on all the individual web pages, then stitched together using GiosPDFSM, and then basic edits were done in LibreOffice. All that to say that I didn't do anything about font size and left it all as it was, since styling is less important than content :)

As for sources of inspiration for visual styling, the UE4 Blueprint Compendiums mentionned earlier would probably be a good starting point ; as well as any PDF export from any documentation site made with ReadTheDocs. Here's an example : https://docs.readthedocs.io/_/downloads/en/latest/pdf/
(I personally strongly dislike ReadTheDocs when it comes to *writing* documention, it's just painful and annoying. But the output itself is really quite clean visually.)

As for opening the .ODG : on my end I am using LibreOffice 7.2.7.2.

FP : no problemo, I needed to do it anyways in order to be able to parse through it all without losing my sanity :D Great work again on all the examples, it looks like everything is well covered really.

Thank you, pior, for the explanations. (And WM as well.)
My past attempts to use MS Word for anything have been very unfruitful, and very awkward.

- Brian

i see the exact same thing. the 0.97 install seems to be missing something. did i miss a step?

Hi mike,

re:
> i see the exact same thing. the 0.97 install seems to be missing something. did i miss a step?

Can you maybe describe a bit more about what problem you're seeing?

Is it that the CustomUI "NodeEdit" button is showing a blank window?

- Michael

yes, exactly

it is that the CustomUI "NodeEdit" button is showing a blank window

i installed this version of the nodeeditor

https://moiscript.weebly.com/biblio-elephant.html
https://moiscript.weebly.com/install-elephant.html

https://moiscript.weebly.com/uploads/3/9/3/8/3938813/nodeeditor_1.zip

@'y'@ 0.97

Hi mike,

re:
> i installed this version of the nodeeditor

Do you possibly have the .zip file name in the path?

Like nodeeditor_1\nodeeditor\index.htm ?

If so then it won't find it because it's looking for

moi://appdata/nodeeditor/index.html

and you've instead got

moi://appdata/nodeeditor_1/nodeeditor/index.html

If that isn't it please show a screenshot of where you have it installed to.

- Michael

sure, thanks

here is my screenshot

Hi mike, that sure looks correct.

I think maybe that nodeeditor might be an old version from moi v3 that is expecting to be put in the "c:\Program Files" install folder instead of in appdata.

Try with this one instead:
http://moi3d.com/forum/index.php?webtag=MOI&msg=9358.10

- Michael

great thanks,

that works -- awesome :)