On Fri, 5 Jul 2002 12:27:10 +0100, Carlos wrote: > > Code style by project would be useful. Projects may have very different > origins and very different styles.
I would find it much better to apply different styles to different source paths (aka "sub-projects") or much better: to apply different styles to different packages. > Having several named code styles (company, jdk, apache, etc) and choosing > which code-style a project uses would be useful. > > I don't see much use for this within a project . Editable files within the > project should all have the same code style. Small correction: "... within a sub-project ...". > For non editable files (library sources should always be read-only for > eample), the only problem I see is tab size. Applying my default tab size > (4) for the jdk sources makes them almost unreadable. Very annoying, indeed. Why isn't SUN able to run a tool for converting tabs to spaces over the code before releasing it? (And it would be good for SUN to check its JavaDocs. IDEA always finds a lot of bugs in it.) > If the tab size could be specified for each library, the code would be > readable. No need to reformat anything. > > Also, an option to make libraries/sourcepaths unchangeable by idea would be > useful - sometimes I find myself editing files in wrong projects by > mistake - switch editor, paste. oops, wrong file:). > > Carlos Tom _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
