Canmove, confirm, emeritus
1,093
edits
Changes
→Evaluating the Options
Therefore, the first step is to evaluate just how much work is likely required to merge the Orion input/rendering with the rest of Ace.
Julian Viereck's perspective:
''Background: Julian Viereck was a Bespin contributor early in the project. In 2010, he continued working on Skywriter and was full-time on the project and other developer tools during the summer. He contributed word wrap and code folding to Ace in 2011. Julian knows Ace about as well as anyone. What follows is a paraphrasing of some of his thoughts after taking a look at Orion.''
In a nutshell, Julian sees more work in taking Orion's rendering and input and merging that into Ace than adding some of Ace's nice features to Orion.
He thinks that we should talk with the Orion people to get them to follow the same syntax highlighting modes "standard" that Skywriter/Ace/CodeMirror had adopted.
Regarding other features:
* The Skywriter/Ace keyboard mapping code that Julian developed is abstracted and should be possible to port for use with Orion.
* Word wrapping would be tricky, but is not the most important feature in a code editor
* Ace's code folding logic code probably move to Orion
* Features like moving text with the mouse might require changes to contentEditable (he's not sure about that one)
* Features like highlighting every occurrence of the selected word should be possible.
== Next Steps & Open Issues ==
