Improve the built-in script editor
in progress
l
lionel MAZEYRAT
I spend lots of time in script editor...
7.7 editor include very cool new features, but still need a few add !
- color marks for todo like in eclipse
- coor marks for found occurence of a find comment
- right click on function list to copy full function path
- auto comment, uncomment lines of code
- autocompletion for all packages
- ctrl mousewheel to increase text font size
Log In
e
eric.e.fredericksen
I see a lot of enhancements here that are obviously needed. I think first we need the editor to function properly. I notice many issues just in basic functionality like formatting, scripts that inexplicably stop working properly until the designer is restarted. Imports that were working but inexplicably are not found on next session. And this isn't just the script editor. Perspective also has an issue where even after a save the designer needs to be reloaded to pick up some changes. Pretty basic and maddening bugs if you ask me.
P
Paul Griffith
Merged in a post:
Scripting console improvments
R
Rudy Popeszku
I have been creating a lot of scripts lately using both the component script editor and the Script console. I feel that both built in editors are very basic and they need a lot more development. I also see that this has been a common complaint. The biggest problem I am having with the editors is that there is no intelligence or auto completion capabilities. I spend far too much time jumping between my browser researching variable and object definitions in the Ignition user manual and other sources. It is also the reason for some of the support ticket questions I have. If improving the editor is a long term project then maybe there should be an option to integrate with a more powerful 3rd party editor?
C
Chad Gregory
LSP support is a must, or even allow us to use something like VSCode to connect to the gateway and edit scripts
B
Bradley Phillips
This improvement will never be "complete" because people have become used to the excellent experience that you get from VSCode, Eclipse, PyCharm, etc, and since ignition is a scada and not an IDE, achieving the same feature set as one of these will require a huge amount of work.
Why not save yourself the work? vscode can be embedded in HTML + JS, you're already embedding chromium in the designer...
P
Paul Griffith
Bradley Phillips: Besides the fact that it's not quite as easy as "just drop in Monaco"... Chromium is only embedded in the Designer when you have Perspective installed, and JxBrowser also has a significantly different support matrix for OSes and architectures that base Java Swing happily supports. Switching the script editing experience over to require a platform JxBrowser supports is a non-starter from that angle.
My ultimate goal is to offer integration with the Language Server Protocol so that you can launch a script editing experience in a local instance of VSCode/PyCharm/Sublime/etc - recognizing the very true fact that we're never going to compete with dedicated IDEs across all features, but without requiring a heavy browser instance to be managed for basic designer functionality.
C
Chad Gregory
Bradley Phillips: I agree that Ignition is not an IDE but there are basic code editor features that the designer script editor lacks.
- Proper syntax highlighting
- Proper formatting (Like Prettier)
- Format on Save
- Multi-Cursor Support
- Better Intellisense/Autocomplete
L
Leonardo Mattioli
Fix comment, uncomment lines of code shortcut with different keyboard layout. In my case in Italian is not working. (or give us the possibility to costumize shortcuts)
P
Paul Griffith
Some additional improvements, including autocompletion for project library scripts, will be available in 8.1.19:
Y
Yuriy Burdak
Could be barking up the wrong tree here so correct me if I am wrong but, wouldn't a lot of suggestions in this thread automatically happen if a Language Server was implemented using LSP?
P
Paul Griffith
Yuriy Burdak: I spoke some on that here: https://forum.inductiveautomation.com/t/any-news-about-script-editor-improvments/53970/6?u=pgriffith
P
Paul Griffith
A first round of changes to the script editing experience is coming in 8.1.18:
B
Ben Newman
@Developers
Any Update on this?
C
Caleb Cain
An intellisense-like capability for Ignition scripting objects would be nice. It would make component/functionality discovery easier. For example:
Load More
→