Hi, Jussi,
I just noticed the configuration settings on the workspace config FTP tab dialog. This is 3.97n beta12. Are these settings accessible to macros at all? I've been planning to implement a couple of those as global setting strings for use in some macros I've written, but if these settings are available and accessible I'd prefer to use them.
Another question - since there are FTP settings at both the workspace and "global" level, which has priority? I would assume workspace if present, but just checking...
Finally, the examples on the FTP tab use my directory structure from an earlier question. Having my name there is not a problem, but I'd probably prefer that the company name (Peterson) was NOT there.
Thanks,
Bill
Workspace FTP Config Items
Hi Bill,
No.
I suspect what you want is a few new macro function, something like:
These functions would then use the global FTP options to connect to the server.
The Workspace FTP features are just used be the workspace. This feature is there to upload/download all the files in the workspace.
This feature was added many years ago on the request of a user.
In that time I have only used this feature once or twice and I have always found it a bit tricky to set up and use
I personally think it is another one of those Zeus features that should not be there, but rather it should get added by the user via macro scripting.
Because in it's current form it is too restrictive.
I think you will find this is only happening because it is your workspace
The examples on the FTP tab are fully dynamic and are created based on the details of the current workspace
Cheers Jussi
Are these settings accessible to macros at all?
No.
I've been planning to implement a couple of those as global setting strings for use in some macros I've written, but if these settings are available and accessible I'd prefer to use them.
I suspect what you want is a few new macro function, something like:
Code: Select all
upoad_ftp_file("local file", "remote file")
download_ftp_file("local file", "remote file")Code: Select all
Another question - since there are FTP settings at both the workspace and "global" level, which has priority? I would assume workspace if present, but just checking...The Workspace FTP features are just used be the workspace. This feature is there to upload/download all the files in the workspace.
This feature was added many years ago on the request of a user.
In that time I have only used this feature once or twice and I have always found it a bit tricky to set up and use
I personally think it is another one of those Zeus features that should not be there, but rather it should get added by the user via macro scripting.
Because in it's current form it is too restrictive.
Finally, the examples on the FTP tab use my directory structure from an earlier question.
I think you will find this is only happening because it is your workspace
The examples on the FTP tab are fully dynamic and are created based on the details of the current workspace
Cheers Jussi
Hi, Jussi,
Yes, a couple of built-in macro functions like that would be useful to me. .NET makes writing an FTP program pretty easy, and then I have completely control of the mapping between local and remote names. But it would definitely be cleaner to not have to system() to some external program.
The other complication I have is that the AS400 is an EBCDIC machine, while of course the PC is ASCII. Again, this is pretty easy to handle with the .NET FTP support and stream encoding, but since it's not an especially common thing I hesitate to ask. Maybe the issue here is that the FTP support doesn't negotiate or ask for encoding, it just transfers. I do know that when I use the FTP client in Windows, the translation just happens. So there may be something built in to the protocol that I don't know about that does that negotiation and translation, but that I'm expected to implement for myself when using the .Net system.net functions.
But I'd hate to add to the list of stuff that there just cause one vocal user asked.
Bill
Yes, a couple of built-in macro functions like that would be useful to me. .NET makes writing an FTP program pretty easy, and then I have completely control of the mapping between local and remote names. But it would definitely be cleaner to not have to system() to some external program.
The other complication I have is that the AS400 is an EBCDIC machine, while of course the PC is ASCII. Again, this is pretty easy to handle with the .NET FTP support and stream encoding, but since it's not an especially common thing I hesitate to ask. Maybe the issue here is that the FTP support doesn't negotiate or ask for encoding, it just transfers. I do know that when I use the FTP client in Windows, the translation just happens. So there may be something built in to the protocol that I don't know about that does that negotiation and translation, but that I'm expected to implement for myself when using the .Net system.net functions.
But I'd hate to add to the list of stuff that there just cause one vocal user asked.
Bill