Full Version: Nodebundle for playing with nodes

Show messages:  1-10  …  1731-1750  1751-1770  1771-1790  1791-1810  1811-1830  1831-1850  1851-1859

Thread Split: Some posts in this thread have been moved here

---

Thank you nkallen.
On Windows 10, got git installed, and did the first two steps done, the git clone... and git checkout...
Hung up on git commands.patch.

Very slow internet here. Cannot watch video until tonight.

Will try again tonight with fast internet, and watching video.
- Brian

My file explorer directory structure was temporarily messed up, I guess from git am --directory commands...
>>>After a reboot, the directory structure is back to normal. I'll have to follow the video directions for Windows 10.

- Brian

---

The other Readme file in elephant-0.1-alpha, refers to a third patch file,
git am --ignore-whitespace elephant.patch

It is confusing.
Will try again tonight...

- Brian

The second readme also has Win instructions...

---

Hi, I think following the video should be best, I'm still working on the README

---

Fantastic project nkallen, thank you for your hard work!
- Brian
(I edited my prior posts a bit.)

---

By following nkallen's video I was able to install the node graph. The program seems to work.
Also I had to put in my email address, and my username.

Unfortunately I did not understand about trial/, so do not have a backup of MoI, just the altered "master". Edit incorrect statement.
I guess I'll have to reinstall MoI4...
- Brian

MoI4 successfully reinstalled.

Edit, so trial\ refers to MoI 4.0 beta, not to the git "backup".

---

Does the result of this "new" NodeGraph is just modified Folders / FIles ?

So will be fine if we can just copy past these new Folder / Files
because this "Git" is very painful! Not yet success! Too much syntax errors, spaces, / , \ etc... a nightmare!
You lost me at video 3.2 minutes! :)

---

Hi,

The purpose of git is to keep copies of documents and manage different versions of them.

In the video when we do “git commit -m ‘Initial commit’” we make a backup of your moi folder before any changes are made. You can always go back to your initial commit no matter how many changes you make afterwards.

---

Yep but for old eyes like me it more easy to make something like this :)
for any Folders / Files who are changed by the nodegraph

NodeEditor_oldMax (so will not called by the program)
Nodegraph will called by the prog

and when i have finished I just rename
NodeEditor (so will called by the program
Nodegraph_old_nkallen (so will not called by the program)

that takes 3 seconds and not headaches! and no need to use Git :)
Of course if this sort structure is accepted by your "nodegraph" Folders / Files modified ...
and if you can provide the Folders/ Files modified!

---

I see that this is more painful than anticipated...

In the software industry / in open source/ among hobbyists, we almost always distribute source code using a version control system like git. It allows us to safely keep backups of files, and also easily upgrade to new versions. I would strongly encourage the moi community to consider using Github or something similar rather than passing around .zip files without any version history. There is a learning curve but it is a life-saver - I swear. You can ALSO produce easy-to-install zip archives, but code is happiest (and safest) when its in version control first.

Around 3.20 in the video, what I type is just to go to different folders on your hard drive. You can type:

cd /c
cd "Program Files"
cd "MoI 4.0 trial"

(Presumably you're not using the trial but I don't know the name of the non-trial folder on windows)

I have to ask Michael if I can distribute my changes as a .zip. For example, does the license permit me to distribute a modified version of Fillet.js? So far I'm using a .patch file which allows me to share my changes without ever distributing Moi3d's original source code.

---

I understand your point of view...so wait and see :)

during the video we have on begin Git line "1s" or "ls"... or ...other what is it exactly?

ps No trial is that in no Roaming folder

C:\Program Files\MoI 4.0

---

I type "ls" a lot which is lowercase LS

It means "list the files in the current directory".

I'm looking around and it seems like there's a program called TortoiseGit which is popular on windows and it looks easy to use. No typing commands. I'll play around with it and investigate. In the meantime, I've asked Michael what the license permits.

I'll be around in discord to help with step-by-step instructions.

---

ok! And one mystery resolved! :)

---

Hi,

Michael is ok with my distributing the source code via .zip file. (Thanks Michael!!)

I recognize this is easier than git. (But still -- git is awesome it's well worth learning even if you're not a programmer!)

https://github.com/nkallen/elephant/releases/tag/v0.1-alpha

You will need to download elephant.zip commands.zip and MainWindowLayout.xml

1. Unzip elephant.zip into AppData.
2. Unzip commands.zip into your main MoI executable folder (replacing the old commands/ folder BUT MAKE A BACKUP)
3. Replace ui/MainWindowLayout.xml with mine. BUT MAKE A BACKUP

This is I hope easier!

---

Hi Nkallen.

Thank you for your plugin, very interesting!

When cloning nodes from the widgets group through the context menu of the node, the program returns an error, the application screen shows which nodes cause the error.

Still, Git is primarily focused on programming, and it's easier for most people to use files in a folder.

Image Attachments:
rightButtonMouseCloneError.PNG 

---

Git resists ...

Image Attachments:
error.PNG 

---

so take the install by ZIP! :)

BOTTOM PAGE!!! https://moiscript.weebly.com/install-elephant.html

---

Everything is simple there, with Git there is a desire to understand:)

Image Attachments:
1.PNG 

---

This bug should be fixed. If you're using git, you can execute "git pull origin master" in the AppData/elephant directory. Otherwise, I'll bundle a new zip in a few days

---

I recommend everyone using this to add the following keybindings:

script:moi.ui.getUIPanel("moi://appdata/elephant/index.html").graph.showPreviousHistoryItem();
script:moi.ui.getUIPanel("moi://appdata/elephant/index.html").graph.showNextHistoryItem();

and bind them UpArrow and DownArrow

---

Show messages:  1-10  …  1731-1750  1751-1770  1771-1790  1791-1810  1811-1830  1831-1850  1851-1859