Groovy tab in Project Properties is only available once Groovy is enabled. Groovy is only enabled (as far as I am aware)
when I create one of the samples from the Groovy support. So, the user must create a Groovy sample before being able to
use Groovy in their own projects, which is counter intuitive.
Actually, I was wrong. Ergonomics is actually a BIG improvement for workflow with Groovy. Why? Because now there is no
need to check the checkbox in the Project Properties... because Ergonomics sets everything up when a Groovy file is
created by the user. Therefore, a few less steps in the tutorial. Thanks.
Actually there never was a need to check the checkbox first (at least both 6.5 and 6.7). Creating the groovy file was
enough. Ergonomics' job is to delay the load of groovy modules to that moment.