Using the document where the user writes his code to diplay the evaluation result is wrong, and it's the source of several UEX issues (e.g., caret position not set at the right place #25). IMO, the right way to fix this is to split the editor into two separate views:
A left one used by the user to write code, and
right one to show the evaluation result.
Simple and clean.
With the splitted view then we should also have automatic folding/unfolding of the evaluation result based on the expression selected in the left editor (with some highlighting, similar to what diff tools do). Isn't that nice? ;-)
Using the document where the user writes his code to diplay the evaluation result is wrong, and it's the source of several UEX issues (e.g., caret position not set at the right place #25). IMO, the right way to fix this is to split the editor into two separate views:
Simple and clean.
With the splitted view then we should also have automatic folding/unfolding of the evaluation result based on the expression selected in the left editor (with some highlighting, similar to what diff tools do). Isn't that nice? ;-)