"My index html is lang.set("FR");" <<This is correct.>>
"My lang.js is var lang = { LANGUAGE: "FR" } " <<<This is "incorrect." Leave it as: var lang = { LANGUAGE: "EN" }>>>
I temporarily went to MoI Options, and edited the moi.ini file to read, under [UI] as Language=French
With index html: lang.set("FR");, and leaving your lang.js as downloaded, with var lang = { LANGUAGE: "EN" }
no other modifications were needed to get French Node language.
There is no need to add the French words to the EN section, lines 159+ in your post.
- Brian
(These are my personal observations and tests and opinions:-)
@Max: Sure!
Here the complete folder nodeeditor who is working! (so with 2 "French dictionnaries" as shown on my image above inside the file lang.js) http://we.tl/TwsT35rm6z till 12 may 2016
Of course all translations of nodes and other things are not yet made! (All is in Wip building)
but with this yet made and this curious lang.js all works fine in French!
One more node added - TextArray
It converts text data to pointarray. For each point can be set upto six values: x, y, z, x-rotation angle, y-rotation angle, z-rotation angle.
Thank you for this French package. But I would like to give you a couple of advices for a future releases.
- I found few backup files and obsolete nodes in your package. It will be better if you will use my latest packages as is. Just add translation to lang.js. The next version will switch language automatically depending of the interface settings. So no need to change lang.set parameters.
- Don't translate strings like Basic/Constant, Factories/Circular Array etc. It's a waste of time, because it is just a debug info, which shouldn't be translated. I'll remove it in the future.
P.S. I'll fix that "Clean" bug in the next beta release. Don't fix it directly by changing the word in .js file.
Just made a significant changes in translation engine to stop that translation hell. Now all labels and node titles are stored in .nod files with english names (with the exception of manually renamed nodes). The script will make all translations on the fly.
Waiting for a bug reports :)
<< I found few backup files and obsolete nodes in your package.
Normal : I increase the dictionnary with the new names without erasing old ones (difficult to see what are they)! :)
<< - Don't translate strings like Basic/Constant ... I'll remove it in the future.
Cool to know!
v.0.55 (it may be buggy)
- Changed translation engine
- Added timer features (double click on background to show node timers)
- Added Line node
- Added TextArray node.
Each line => point: [x] [y] [z] [xAngle] [yAngle] [zAngle]. Use space or ; as separator.
Example:
Hello Max,
thank you for that great work. - your speed is incredible.
As mentioned, I am working on a pushFrame-function. Here is my first working code with some reworked nodes to test it. Please let me know if you want to improve and integrate it, or we should use an external way.
In a short test I can't run the circle-node?
By the way I made another cursor. The original crosshair has in my opinion not enough contrast. It is a simple PNG which can changed with a simple graphic prog. Activation for those who also need more contrast: open litegraph.css in the css directory and change cursor: crosshair; to cursor: url(./crosscursor.png) 16 16, crosshair; put the crosscursor.png in the same directory.
infonodes.js