RPG Next Gen

RPG Next Gen Editor is a lightweight RPG editor solely based on the Eclipse platform. It has some basic plugins which among other things provide a tree view on the QSYS filesystem. The focus for the editor lies on small size and speed. The goal for this project is a feature complete RPG free-format editor which can be used to develop small to midsized projects for even the most advanced programming style.
| Tasklist |

FS#109 - Integrate compile listing with source code editing

Attached to Project: RPG Next Gen
Opened by Jim Rothwell (jwrothwell) - Wednesday, 19 August 2009, 20:28 GMT+2
Last edited by Mihael Schmidt (Mihael) - Wednesday, 19 August 2009, 21:12 GMT+2
Task Type Feature Request
Category Editor
Status Unconfirmed
Assigned To No-one
Operating System All
Severity Medium
Priority Normal
Reported Version 0.5
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Tie compile listing to source code so that clicking on an error in the listing takes you to corresponding source line. Alternatively, show compile errors in source code, above or below the code in error, with facility to jump to next error.
This task depends upon

Comment by Mihael Schmidt (Mihael) - Wednesday, 19 August 2009, 21:18 GMT+2
There is already a view "Compile Result" which can be shown with "Window -> Show view -> RPG Next Gen -> Compile Result" which shows the compile result of the current source activated in the editor. And double click on a compile result entry takes you to the source. If the error is based on a copybook the source of the copybook will be opened and the error highlighted.
Comment by Mihael Schmidt (Mihael) - Wednesday, 19 August 2009, 21:20 GMT+2
I would love to implement the errors also as markers which would be seen on the vertical ruler next to the editor area but markers are only supported for classes which implement IResource and we can't do that because we are not using a local file in the workspace.
Comment by Mihael Schmidt (Mihael) - Wednesday, 19 August 2009, 21:24 GMT+2
Show errors below the code line: IMO this is the badest alternative that exists and LPEX has an even worse implementation of this kind of error feedback. It really sucks in LPEX. But this is just my opinion.

If there is somebody who also likes the LPEX way of giving error feedback can make a contribution to the editor but I won't spend any resources on it. There are other tasks which results in more productivity than implementing this (like Content Assist #22).
Comment by Mihael Schmidt (Mihael) - Wednesday, 19 August 2009, 21:27 GMT+2
Show next error: Sounds nice but actually how should that work?

I double click on en entry and the line in the editor is highlighted. What now?

If I add an icon on which the user can click to get to the next error he can also double click on the next error. Key Binding to get to the next error. Ok that makes more sense if I don't use the mouse that much and want to stick to the keyboard.

Any ideas? Suggestions?
Comment by Jim Rothwell (jwrothwell) - Wednesday, 19 August 2009, 21:32 GMT+2
I only offered the suggestion of including the errors in the source as an alternative, in case that would be easier to implement. I agree with you that that's not the optimum solution. And I'm sorry I didn't find the Compile Result view before posting the request - I probably spent more time going thru all the existing tasks to make sure I wasn't duplicating a request.
Comment by Mihael Schmidt (Mihael) - Wednesday, 19 August 2009, 21:39 GMT+2
No offense meant.

Loading...