# Any news about script editor improvments? **URL:** \ **Category:** Ignition\ **Tags:** ignition81, scripting\ **Created:** [December 9, 2021, 8:36pm UTC](https://forum.inductiveautomation.com/t/any-news-about-script-editor-improvments/53970 "2021-12-09T20:36:09Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [December 9, 2021, 9:42pm UTC](https://forum.inductiveautomation.com/t/any-news-about-script-editor-improvments/53970/6 "2021-12-09T21:42:06Z")
Right now, updating the built-in editors is in progress (awaiting QA). It’s far from complete, but it adds a lot of ‘smarts’ to basic stuff. Some of what I’d like to add will have to wait for 8.2, because of limitations in APIs such as third party scripting modules. I would _love_ to make the designer an [LSP](https://microsoft.github.io/language-server-protocol/) _client_, which would allow offloading a lot of tasks to external editors; but to do that we’d have to push designer-local resources to disk somewhere, and there’s some tricky complications there. Similar complications exist for pushing files to disk and opening in external editors; in addition, opening an external editor such as VS Code wouldn’t work perfectly without some doing because: 1. you wouldn’t have your project scripts in the right spots, and 2. you wouldn’t have autocompletion for any system functions, and 3. you wouldn’t have autocompletion for any Java libraries. Doing that properly might require the designer acting as an LSP **server** , which is also a big task. --- _[View the full topic](https://forum.inductiveautomation.com/t/any-news-about-script-editor-improvments/53970)._