guttormvik
Member²
I'm having a hard time getting used to the way you display results now.
It has a set of drawbacks, and I don't really see any benefits.
Drawbacks:
* It is harder to use the result of one statement to build another statement
* It doesn't fit well with executing parts of a statement. ( You still don't support it, and I assume the mismatch is part of the reason?)
* It is harder to answer the question : "What did I just do"? (ie did I execute all, selection or current statement)
Even though the result tabs in pl/sql developer can be a bit annoying (mostly when one statement takes a long time and it, and all statements after it pings..)
I think I prefer them over the current solution.
I would suggest:
* Stop tracking statements in the margin as code is written.
* When code is executed, show statements in the margin and produce result tabs.
-> The statements that are marked in the margin is always what I last ran
* Have a soft binding between statement and result tab:
* When opening a result tab, highlight the corresponding statement but don't move the cursor (maybe use the margin to highlight it)
* When clicking in statement text, don't switch result tab. (Possibly highlight the tab heading?)
* Optionally, open the result tab when you click on a statement in the margin
-> I can use the result from one statement to build another, and still have a clear mapping between each statement and its result
It has a set of drawbacks, and I don't really see any benefits.
Drawbacks:
* It is harder to use the result of one statement to build another statement
* It doesn't fit well with executing parts of a statement. ( You still don't support it, and I assume the mismatch is part of the reason?)
* It is harder to answer the question : "What did I just do"? (ie did I execute all, selection or current statement)
Even though the result tabs in pl/sql developer can be a bit annoying (mostly when one statement takes a long time and it, and all statements after it pings..)
I think I prefer them over the current solution.
I would suggest:
* Stop tracking statements in the margin as code is written.
* When code is executed, show statements in the margin and produce result tabs.
-> The statements that are marked in the margin is always what I last ran
* Have a soft binding between statement and result tab:
* When opening a result tab, highlight the corresponding statement but don't move the cursor (maybe use the margin to highlight it)
* When clicking in statement text, don't switch result tab. (Possibly highlight the tab heading?)
* Optionally, open the result tab when you click on a statement in the margin
-> I can use the result from one statement to build another, and still have a clear mapping between each statement and its result
