As the main goal set for this week in our meeting, @mdoron suggested we open an issue for suggestions regarding the future development of the plug-in this semester. We will be happy to receive suggestions from everyone in the comments.
[x] Implementation of #54 (launch configuration), which I think will be the critical mission of this semester.
[x] Restructure, remove old unused code.
[x] Support other IDE's (specifically IntelliJ)
[ ] Testing for user-input dependent behaviors (perhaps necessary for coverage goals)
[ ] Improve response time. This is somewhat unrelated to the plug-in specifically, as it has a lot to do with database and server, but here's an idea that is related: to speed up interaction with users, we can return an initial "reflex" response to the plug-in, before heavy computation begins on the website.
For example, the server could send back this quick reply: a solution to the most common trace with the same Exception type, which saves time, as it can happen before probing the larger, more complex database. With a quick response like that, the plug-in can display a window basically saying "This solution solves a similar common problem we found without looking too much, if you'd like, you can visit such and such webpage to find out more relevant problems and solutions."
After discussing this in our meeting, We think this functionality could be implemented using cache, instead of a separate index. This will make computation almost real-time, and we could address more than just the Exception type.
I'll edit this comment if I come up with more ideas.
As the main goal set for this week in our meeting, @mdoron suggested we open an issue for suggestions regarding the future development of the plug-in this semester. We will be happy to receive suggestions from everyone in the comments.