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

Integrating file transfers via FileTransfer2 #8

Open
niekgroot opened this issue May 3, 2020 · 3 comments
Open

Integrating file transfers via FileTransfer2 #8

niekgroot opened this issue May 3, 2020 · 3 comments

Comments

@niekgroot
Copy link

niekgroot commented May 3, 2020

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).

PS C:\Program Files (x86)\AMX Control Disc\FileTransfer 2> .\FTCon.exe ‘\Programming\home.tkn' 172.16.1.220 -Boot
    
FTCon [Version 1.1]
(C) Copyright 2005 AMX Corp.

Attempting to Send File-home.tkn
Transferring home.tkn
266021 of 266021
Transfer Complete
Attempting to Send File-empty.src
Transferring empty.src
246 of 246
Transfer Complete
PS C:\Program Files (x86)\AMX Control Disc\FileTransfer 2>
@sentry07
Copy link
Owner

sentry07 commented May 3, 2020

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.

@niekgroot
Copy link
Author

niekgroot commented May 3, 2020

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)?

@niekgroot
Copy link
Author

niekgroot commented May 3, 2020

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;

PS C:\Program Files (x86)\AMX Control Disc\FileTransfer 2> .\FTCon.exe
    
FTCon [Version 1.1]
(C) Copyright 2005 AMX Corp.

Not enough arguments

FTCon "apwfile" ["projid"] ["sysid"]
FTCon "axwfile" ["projid"] ["sysid"]
FTCon "ftlfile" -Send|-Receive
FTCon "file" commsetting [mapping] -Send|-Receive
       -Boot -Axcess -Optimize -TPD=BIF -KPB=GF -User="username:password"

apwfile     APW file to send
axwfile     AXW file to send
ftlfile     FTL file to send

(...)

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