Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: How does one use an on-disk editor for poweron files #4

Open
nackler opened this issue Feb 21, 2024 · 2 comments
Open

Question: How does one use an on-disk editor for poweron files #4

nackler opened this issue Feb 21, 2024 · 2 comments

Comments

@nackler
Copy link

nackler commented Feb 21, 2024

My poweron files are stored inside my bank core system. When I edit them I am using a built-in editor inside the bank's core system. I don't think the files reside on my local disk at all.

It would seem to me that in order to use another editor, such as VS code, I would need to export the poweron files to my machine, then import them back into the banking system when I'm done editing them. That round trip takes some of the excitement out of using a plugin like this.

What is your workflow?

@cainfe
Copy link
Contributor

cainfe commented Feb 22, 2024

What I do is develop my PowerOn code in VS Code and copy and paste the code into the PowerOn Specfile in Symitar. It's a bit tedious but I find it worth it to have the features VS Code brings.

If your core system was hosted in house I wonder if you could directly (and securely) access the hosts filesystem from VS Code but I don't have any experience with that.

@nackler
Copy link
Author

nackler commented Feb 22, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants