|
|
| (45 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | == Automatic Method Ordering ==
| |
| | | | |
| − | Coding conventions as discussed, for example, in Clean Code recommend that methods should be ordered in the sequence they get called. This drastically improves the readability of your code, since the amount of jumps in code required to understand the code are reduced to a minimum. Manual ordering is an annoying and time consuming task. So we want you to automate this task by implementing an Eclipse Code Style.
| |
| − |
| |
| − |
| |
| − | == Collecting relevant items while developrs traverse APIs ==
| |
| − |
| |
| − | While developers learn how to solve a specific task they need to learn about the given API. Assuming they found a starting point they have to figure out if there are additional things they must know about or which would help them. This is something every developer will be confronted with again and again. What we can do is to store what a developer was looking at, so we can extract interesting points and show them others which hit the same starting point. So what we finally want to have is an Eclipse plug-in collecting information about API traversal and a view that shows the collected data, so that others can see information like “Developers who looked at this method also looked at…”
| |
| − |
| |
| − |
| |
| − | == Local Code Search ==
| |
| − |
| |
| − |
| |
| − |
| |
| − | == Flexible Configuration of Content Assist lists ==
| |
| − |
| |
| − | The preference page for the Eclipse Completion Engines currently allows you to enable multiple engines on the ''default'' tab. But for cycling multiple tabs it is only possible to have one engine on each cycling tab. As Code Recommenders adds multiple engines, we faced the problem that we must aggregate our engines to provide useful configurations to developers. This change is filed and accepted as feature request by the JDT team. There are some adapted screenshots attached to the feature request to give a hint of how this could be implemented: https://bugs.eclipse.org/bugs/show_bug.cgi?id=340876
| |
