-
Notifications
You must be signed in to change notification settings - Fork 4
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
Integrating file transfers via FileTransfer2 #8
Comments
I've been pondering how to do it for a very long time. I think I could tie into the task system but I'm still not sure how to set up the transfer information. Maybe I can parse the APW file and use information from in there. I'm still learning how to tie into VSCode API stuff. |
Could consider constraining initial feature scope to transfer only the TKN file created by the last successful compile? .jar and other files would need to be transferred manually, but as those are not typically modified using VSCode or NetLinx Studio, perhaps thats acceptable. This would require a method to track the TKN file name between the compile and transfer task, and a mechanism to specify the transfer target (maybe the workspace/folder settings)? |
An alternative perhaps simpler approacher could be to use a file transfer list file ("ftlfile"), which the user would edit as part of the VSCode workspace, and could be passed to FTCon as an argument;
|
Can you think of a way to initiate file transfers in VSCode via FTCon included in FileTransfer2? This would deliver a further integrated dev environment, and benefit those with a remote deploy workflow.
See below sample console output (which works fine, if just a little manual).
The text was updated successfully, but these errors were encountered: