Writing a competent code editor is a big job, and would likely violate Oildrop's easy-auditability goal. As such, the reccommended usage pattern is to write a userscript in a text editor or the browser console, then copy it into Oildrop's new script dialogue.
However, adding a code editor is only a problem if it runs at the same privilege level as Oildrop. One way to make the devleopment workflow easier would be adding integration with a third-party, web-based javascript editor. The user could navigate to that site, write their code in it's window, and then press a "load from page" button in the Oildrop popup. This would provide most of the convenience of a builtin editor, but could be accomplished with probably fewer than twenty lines of code!
Writing a competent code editor is a big job, and would likely violate Oildrop's easy-auditability goal. As such, the reccommended usage pattern is to write a userscript in a text editor or the browser console, then copy it into Oildrop's new script dialogue.
However, adding a code editor is only a problem if it runs at the same privilege level as Oildrop. One way to make the devleopment workflow easier would be adding integration with a third-party, web-based javascript editor. The user could navigate to that site, write their code in it's window, and then press a "load from page" button in the Oildrop popup. This would provide most of the convenience of a builtin editor, but could be accomplished with probably fewer than twenty lines of code!
Possible candidates: