hey all,
me and my friends making game using JMonkey
now we are struggling at GUI part , any easy Tutorial about Nifty? … and if we design our GUI in Nifty Editor how to implement that in JMonkey
ps : we tried to add Nifty Libraries in jMonkey , but it says " Doesn’t exist"
any help ?
thanks in advance
There is a handbook for nifty that was useful while I used nifty.
Although I personally would suggest switching to lemur, it’s much easier to use and the methods remind me of Swing a lot (so I don’t have to learn twice 
).
Please specifiy on “doesn’t exist”, maybe a screenshot?
There are some tutorials in the wiki. You could start here:
https://jmonkeyengine.github.io/wiki/jme3/advanced/nifty_gui.html
The manual of NiftyGUI can be downloaded here:
https://netcologne.dl.sourceforge.net/project/nifty-gui/nifty-gui/1.3.2/nifty-gui-the-manual-1.3.2.pdf
Well, it seems that you didn’t add the nifty library to your classpath.
You can add the library in the project properties:
it worked , THANK YOU VERY MUCH 
if you have any tips to learn NIFTY " fast " without any complicated tutorial , to implement simple GUI , i’ll be very THANKFUL
Then have a look at the wiki tutorial I posted above. For more detailed tutorials you have the manual. But there can also be found some documentation on GitHub.
I’m curious what this means.
Guava version 12 or later
• slf4j version 1.7.5 or later, plus an adapter for your preferred logging framework. (At minimum, you will need the API jar, something like: slf4j-api-1.7.5.jar)
•(optional but highly recommended) Groovy version 2.1.9 or later. This is only need if you want to use the style language support and in the end you only need groovy-all.jar. (For example: groovy-all-2.1.9.jar)
So, the complaint is that the SDK already has the half-dozen nifty jars built in and Lemur doesn’t?
Got it.
I make no judgment, just answer the question.
Just want to note that - although not a complete solution - tools such as ProGuard actively remove unused classes. It might be something people didn’t realise existed or was possible, so thought I’d just chime in.
Quote from ProGuard’s FAQ: R.E. “What is Shrinking?”
Java source code (.java files) is typically compiled to bytecode (.class files). Bytecode is more compact than Java source code, but it may still contain a lot of unused code, especially if it includes program libraries. Shrinking programs such as ProGuard can analyze bytecode and remove unused classes, fields, and methods. The program remains functionally equivalent, including the information given in exception stack traces.
And I’ll just throw this in here for whomever may be interested.