150
script editor improvments
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
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...
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:
C
Caleb Cain
An intellisense-like capability for Ignition scripting objects would be nice. It would make component/functionality discovery easier. For example:
K
Kamen Krastev
Variable suggestions, method suggestions would be nice!
P
Paul Mangels
Want to +1 several of the suggestions here. A lot of this seems like basic stuff for a Python editor, and I also would be happy just having an external editor to use.
- Auto-complete/IntelliSense for custom functions. It is super annoying to have to manually copy or type paths. If the function is available from the scope I'm working in. If I can call the function, I should be able to auto-complete it (for example, global scripts in a tag script, etc).
- Basic copy-pasting. I don't know what exactly is happening under the hood, but copying and pasting code results in incorrectly tabbed/formatted code 95% of the time. It's not a big deal for a couple lines of code, but any decently long script it is a serious inconvenience and potential source for errors.
I do also agree that the most complete solution is probably to allow easy integration with an external editor (VS Code is my personal preference) rather than a la carte adding these to the Ignition editor.
B
Ben Newman
Honestly a better approach would be to just have a feature that will allow us to connect an external python editor to the Gateway.
VS Code
PyCharm
Notepad++
Atom
Sublime
Etc.
B
Bradley Phillips
Ben Newman: i totally agree
B
Bradley Phillips
Ben Newman: could even be a plugin for vscode
B
Bradley Phillips
Ben Newman: César Román wrote this https://github.com/ignition-api/stubs, and the files are on-disk in the data folder of the gateway, so you can get pretty darned close by using the stubs and editing outside of ignition, the downside is you can't test (but you can mock the stubs and write tests)
You'd also have to write a little script or something to remove the hash from the resource.json file
Load More
→