Having recreated my module after JetGroovy 1.5 eradicated it in favor of an entirely new one, I'm back to working. Already I've noticed some things about which I'd like to give some feedback:
- Navigation Bar
-- This is nice, but it takes up more space than I'd like it to. I'd like to see it shrunk (borders could easily be reduced), possibly relocated outside the text editing area (e.g., to the button bar) or made optional or movable to the bottom of the text editing area.
-- It would be nice to integate TagLibs into the selector. While they aren't technically part of the tuple <Domain, DomainController, DomainView, DomainTest, DomainControllerTest>, when their name fits the pattern, they could be included in the tuple.
-- Likewise, it would be nice if Services were accessible there.
-- Definite assignment check ("Variable 'something' might not be assigned") is sometimes incorrectly raised.
-- "Cannot apply default constructor for class 'DomainClass'": The Grails data-binding constructor for domain classes should be known by this inspection.
- Iconography / Graphics
-- The asterisk in the editor tab overlaps the padlock icon.
-- The extra border within the text area of Domain classes that accommodates the tabs at the bottom (to select Text or "domain class dependencies") causes the JetGroovy Navigation Bar and its contents to reposition slightly (but very noticeably). It's border should adjust to the difference so its contents do not appear to shift around when one moves between Domain and non-Domain classes.
-- As JetGroovy gets more complex, I think it is going to be necessary to give users control over its features. E.g.: Colors (comments are colored differently, now); Navigation bar characteristics, etc.
-- The access level check found a missing "public" keyword in years-old Java code.