Eclipse JDT Improvements

JDT adds a set of plug-ins for Java development to eclipsethat add the capabilities of a full-featured Java IDE. JDT plugins make available APIs so that they can be further stretched by other tool designers. Java Development Tool is supported by three pillars which are following:

1. Java Model: • Java Model – Concept and Design. • Java Model – Create, Access, Load Projects. • Traverse .jar File by Using Eclipse JDT. • Count total number of methods in a Java Project.

2. ASTParser – Parse projects, files, and methods: • Use ASTView to explore AST of a Java class • Parse Single .java files • Parse a Java Project • Parse a Java method • Parse Java statements • A complete standalone example of ASTParser

3. Java Search Engine: • A plain example • Search method references

Here are the points which can be used to improve Eclipse:

1. It can be improved by adding something like the Smalltalk Refactoring Browser.
2. Editor features should be added in order to be more attractive for visitors, riders and implementers.
3. Visitors will surely want to see the libraries of standard Java projects placed in a “Libraries” node similarly to the libraries of Web projects. It is irritating to set and unset filters to attain something similar.
4. Intellij is quite rocking to be here.
5. A dictionary should also be installed to correct spelling mistakes in the java documentation commentaries.
6. The XML editor, WTP, CDT, the visual editor, the IDL editor and all supplementary tools are required to be improved.
7. Profiler is lacking, should be improved too.
8. People will love to see a refactor from a named class to an anonymous class. Anonymous classes provide well encapsulation.
9. The code duplication examination options in IDEA are great.
10. Following are the features that can be much useful while working with grand workplaces:
• A view: a project depended graph.
• An “Open project and all referenced projects” as there is a close unrelated project feature.
• Create working set with referenced projects.
11. Imports – Auto insertion of imports allIntelliJ should be well because this is a major annoyance for the users.
12. Code Formatter – it should be good and it will be so, if you could translate to/from Check style configuration and have the formatter being sophisticated enough to say quick fix your code against a Check style configuration. The code formatter’s handling of comments also leaves much to be wanted.
13. Search -The results table should display a line for each match found to enable you to get an overview of the results without essentially needing to navigate into a file and to permit one to watch the results across files and also to be able to jump directly to a particular search result. This results table in common should be improved which would make all same features much more beneficial.
14. Working sets may really be advantageous in eclipse.
15. Quick marks–once more in IntelliJ style, the 2 plugins that aim to provide this have both caused many issues in the past, it should become a first class eclipse citizen.
16. Comparing it with “compare with clipboard” will be quite beneficial, if added.
Points mentioned above are the minor things that can make eclipse good to use.

Posted in Technology.

Leave a Reply

Your email address will not be published. Required fields are marked *