While the code editor in JMP works it is time to upgrade to a modern and feature rich code platform like visual studio Code or Eclipse. These will have better autocomplete, Github versioning, mass rename of a variables over multiple code files etc.
I love the the VSCode extension, it is really good and it should probably be the way forward. However the JMP side of the integration could use a little work to make the experience smoother:
1. When I hit escape within JMP it ends the link to VSCode in such a way that I have to restart JMP to be able to run scripts again. I had to rewrite my brain to no longer use escape to deselect in tables.
2. The log in JMP is no longer usable when running code from VSCode which eliminates all the recent additions to JMP that you could normally use to steal code (like the code to create a column or update a table). It also make debugging harder as the output available in VSCode doesn't usually include the location where the script breaks.
3. Typing in JMP when VSCode link is active becomes near impossible, so quickly testing a bit of code...making some changes in the table and testing it again becomes hard.
4. Adding in the link to the scripting index would be really nice to see working examples of functions.
As JMP is a VOC (voice of customer) driven company, it seems there is a strong argument against a new JSL editor which prevents the introduction. What are the arguments against a state of the art Script editor?
I'm the developer of the JSL for VSCode extension. Thank you for your feedback! Always feel free to open issues at https://gitlab.com/predictum/jsl-for-vscode/-/issues/new and I can try to make some improvements when I have the time. I've already opened up a few issues based on your comment.
1. When I hit escape within JMP it ends the link to VSCode in such a way that I have to restart JMP to be able to run scripts again. I had to rewrite my brain to no longer use escape to deselect in tables.
Running JMP from VSCode was tricky to set up and isn't ideal in how it works but to give you an idea of what's happening: there's always a JSL loop running in the background listening for commands from VSCode which hijacks your JMP session a bit. So I don't think we can stop escape from stopping the loop but we may be able to make it easier to reconnect so you don't need to restart JMP.
2. The log in JMP is no longer usable when running code from VSCode which eliminates all the recent additions to JMP that you could normally use to steal code (like the code to create a column or update a table). It also make debugging harder as the output available in VSCode doesn't usually include the location where the script breaks.
I wrote the code to connect to JMP before the niceties of the log existed so maybe there are some improvements that could be made here.
3. Typing in JMP when VSCode link is active becomes near impossible, so quickly testing a bit of code...making some changes in the table and testing it again becomes hard.
That's that background loop again which makes this tricky. But maybe a way to pause the connection to VSCode could help here.
4. Adding in the link to the scripting index would be really nice to see working examples of functions.
That should definitely be possible. Or to even have the examples integrated into VSCode somehow.
Hi @ben_ph , I love your extension and am really grateful for it. I just think that it should become a designed-in part of JMP instead of an addition that you have to make. Having said that: I understand your design choices and the consequences, but if you see a way to fix these points that would be fantastic. Let me know if you need some help testing!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.