[jdt-core-dev] (no subject)

[Kirill Frolov <fkirill@xxxxxxxxx>]

Well, about code formatting and appropriate extentions. 
Formatters: 
1. I believe there should be separate formatters for javadoc and for java
code 
2. javadoc can potentially (via javadoc tags and some special tags) store
some kind of information, including meta-information, used by other tools
(for example, code generation options for ejb from home and remote interface
etc.) This (almost) approach is used in VAJ when VCE generated a private
static method, that contained only a comment. The same approach is used in
Together to store meta-information (there are no other options, since there
are no storable properties Together's resources can have) 

3. The javadoc comment should be formatted as well, because for example, if
pregrammer chooses that the code should be 80 chars wide, the comments
should still be readable and occupy no more then 80 chars. 

4. About my proposals about java code formatter I submitted an issue
<http://dev.eclipse.org/bugs/show_bug.cgi?id=6284>
http://dev.eclipse.org/bugs/show_bug.cgi?id=6284. It can be expanded with
IDEA's Java formatter features. 

5. besides, there should be a way for plugin to get information about java
code structure (not only meta-information like methods info). For example,
I'd like to count operations in some method or count how many instance
variables are being used in some method.

Extentions: 
1. Extention point giving control over javadoc comments and special tags in
code without direct manipulations with source. For example I'd like to write
a javadoc formatter that could format my comments some special way. Another
example, I'd like to add some custom tags with some view and and later view
should be able to retrieve these tags from code without parsing souce code.
Actually I have not many ideas how this could be used (I mean applications
of this mechanism). Any ideas? Welcome.

On the other hand, when my code is inside Eclipse I'd prefer to store all
the properties of the resources by means of the resources plugin (inside
.metadata folder), but when I import/export, there should be a mechanism to
store/retrieve resource's properties either within .java files or as a
separate properties file (or some kind of it). Anyway this extention point
should give plugins control over java source's custom tags and javadocs (in
particular)

I've got even better idea. We should give control over custom tags to
Import/Export extentions. 
And have an extention point giving access to java code structure (javadoc
and custom tags in particular). Extending these points there should be
possible to add/delete methods, attributes and so on (implementation of new
method wizard, new attribute wizard and so on)

2. Extention point providing extention of java formattng engine. There are a
lot to say, but many thoughts have already been posted.

Kirill. 


__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1