Can you elaborate?
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog
Fabrizio...@tidalwave.it - mobile: +39 348.150.6941
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
It would help in that I can set up a macro to call the formatter and the
organize imports, then save. It's still not what Eclipse offers, e.g.
you can't format just changed lines and I don't think NetBeans covers
all of the more advanced things such as adding finals. But I should try
such a setup, I don't really know why I didn't come up with it myself.
But even if it works: I think NetBeans should emphasize code hygiene
more. Being able to write a macro for it is better than having to write
a plugin, but it still is a conceptual burden and it won't be trivial to
spread across a project. With the Eclipse approach the Save Actions can
be configured as part of the project's configuration, then any developer
on the project will automatically use them (assuming you check in your
Eclipse config, but in an Eclipse shop that makes sense).
Of course the problem is that you can't default to anything because
whatever you chose as default >95% of the audience will disagree :-)
Peter
like a user DAO or DTO that might be used in almost all
the features?