Closed mdoron closed 7 years ago
I've managed to do so, but I think it doesn't look good. I'm trying to do it with quick fix-like interface (similar to the Tippers in Spartan project).
We can now suggests fixes with the proper GUI (I left an example within SendTrace.java). Next step is actually allowing fixes in code.
In second thought, I want to see if I can improve this a little bit. I will keep this open for now.
@mdoron are you still working on this issue ?
@yonzarecki Yes but now this goes under research again, correspondingly to what was discussed with Yosi.
๐
So, short summary + update: At the beginning I thought we should add a small window to the eclipse plugin which will hold a simple explanation from the server about the cause for the bug we have. I wanted it to be over the lines which caused the exception. So the first lead was to implement something like we have in the Spartanizer project, using IMarkers etc. I implemented something simple to check if it's working and it was nice, but not enough. Then, @yossigil offered we won't use the markers, but something else, since this is not the right way to do such explanations. I searched a little bit and realized we should implement a Hover Help. So this is what I'm working on now - trying to understand how to do it the right way and add it to the project.
Update: I've decided to go deeper because I don't feel like I understand the core of eclipse plug-in dev. I have also looked on the internet and found some interesting material, but I will dive into those only after I'll feel comfortable with plug-in dev.
English will follow
ืืงืื stack-trace, ืืืงืืฆืื ืืืชืืืืื ืืฉืืจืืช ืืืชืืืืืช ืืื ืื ืืืืขืช ืืืืฆื ืืืฉืจืช ืืืื ืืฉืืืื. ืืืืงืจ ืืืฆืข ืืื ืืงืื ืืขืจืื ืืืฆื ืืืืฉ ืืฆื ืืคืืืืื.
ืืชืืืื ืืงืจืชื ืืช ื ืืฉื ื markerืื ืืืฆืืืชื ืืงืื ืืกืคืจ ืฉืืจื (ืืคืืื ืืืชืื ืืฉืืืื ืฉืงืืืื ื ืืืจืืช ืฉืื ืืฉื ืืื ืื ืคืืชื ืืืืืื ืืขืงืืืช ืืืจืื ืืืจืื) ืืืืฆืื ืขืืื ืืืืขืช ืฉืืืื. ืืืืจ ืืื ืืขืงืืืช ืืฉืืื ืขื ืืื ืื ืืืขื ื ืืืกืงื ื ืฉื markerืื ืืืงืืจื ืืืืขืืื ืืื ืื ืื ืฉื quickfix ืืืื ืื ืืื ืื ืื ืืืืืืง ืฉืื ืื ื ืจืืฆืื, ืื ืืื ืืืืขื ืืืชืจ ืืืืฉ ืชืืงืื ืืงืื, ืืืจ ืฉืื ืื ื ืื ืขืืฉืื. ืืขืงืืืช ืื ืคื ืืชื ืืืืงืจ ืฉื hover text ืืขืืืง ื lead ืืจืืื, ืืืืืืชื ืฉืืื ืื ืื ืฉื ืื ืฉืงืืจื ืื ืฉืื ืืฆืืืื ืืช ืืกืื ืขื ืืืืฉืื region ืื ืื ื ืืืืืื ืืงืื ืืืชื ืืื ืืืฆืข ืืฉืื. ืฉืืชื ืื ืฉืื ืื ื ืืฆื ืืื ืจืืฆืื ืืงืื ืืช ืืืชื ืืืืช ืฉื marker ืฉืืคืฉืจ ืืกืื ืืงืืืืช ืืกืืืืืื ืืขืืืื ืืงืื ืืืืฉืื ืืื-ืืื, ืืืฆื ืฉื ื ืื ืืืคืฉืจ ืืืืช ืืฆื ืฉื quick fix. ืื ืืฆืืชื ืื ืื ืื ืืืจ ืฉืืฉืื ืืื ืืฉื ืืื.
Get a stack-trace, and in the suitable files, in the suitable lines, put a message from the server regarding the exception. The research was done in order to get an estimation regarding the best way to implement it in the plug-in side
At first, I researched the Markers and succeed to get a line number and to put a message on it using the Markers. Afterwards, after a conversation with the instructor, we've reached the idea that the Markers are not intended for such cause, because we actually want to change code when we use them, so quickfix is not the precise mechanism we want to use. As a result a turned to research the Hover Text as main lead and I've discovered that in that mechanism you put your cursor on some Region and then we can get it and display a message. I've noticed that on one side we want the behavior of a Marker, and on the other side we don't want to actually enable a state a quickfix - in thus we want the Hover Text mechanism. I didn't find a mechanism that combine the best of both worlds.
I'd say this issue is finished, isn't it ? @mdoron
Definitely.
Introduction task which both me and @yosefraisman think is a good idea. The idea is just like the help in MATLAB open a small window, I want our site would open this way in the plugin.