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?
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)
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.
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.