Later in 2023, we’re going to introduce a new feature of EasyMorph Desktop – the File Browser app. Our goal is to make EasyMorph the most convenient tool for everyday work with data. Therefore we’re envisioning the Desktop as an integrated suite of tools to browse, organize, retrieve, and transform data. After the Catalog, the File Browser is another step in that direction.
The initial functionality will be somewhat basic - browsing, uploading, downloading, and deleting. More operations, like folder renaming, will be added later and will simultaneously appear as new commands in the respective actions.
Some file/folder operations may not be available in some remote file stores if they are not supported by the available APIs provided by the vendors.
How does it look to you? Feel free to share your opinion in the comments below.
I don’t know yet. We’ll see when it’s ready. I suppose if a folder is available in Windows, EasyMorph should be able to handle it. The File Browser will use under the hood the same drivers as used by EasyMorph actions. So if a VM folder is available in an action, it will be available in the File Browser.
It really looks awesome ! And it also includes the feature we wanted, ie the possibility to download a whole folder where you can have the project but also the import and export files, ie the whole pack.
Will it convert EBCDIC char to ASCII while downloading, as WinSCP and FileZilla do ? That would allow to get data directly from a sequential file from a mainframe computer !
In my last job, because of this functionality, we had to use WinSCP (using the EasyMorph command action) to download the EBCDIC from the Mainframe to our office, then use EasyMorph to convert the sequential text file into a dset file. It didn’t work otherwise because the EBCDIC end line (CR) character was not recognized.
In my case, it didn’t work when I downloaded the Mainframe file with the File Transfer Action, and then treated it with the Import Plain Text (since it is a sequential text file) with the encoding set to EBCDIC - because of the unrecognized end line character. (ref: How to read EBCDIC files - #2 by Nicolas )
I do not work there anymore, but did I try ! (It would have been some sort of a revolution to be able to import the whole Mainframe sequential file right into Easymorph)
I’m sure anyway that this File Browser will be a great addition to EasyMorph, though !