New major version is coming up!
Quote from luishp on August 13, 2021, 11:23 amWe are very close to release a new VisualNEO Win major version with a bunch of new commands and functionalities. Meanwhile we have just updated the documentation. Please take a look and let us know if everything is understandable and clear to you. These are the main sections with changes:
Embedded Files:
Improved information with screenshots.
Predefined Global Variables:
There is a new [MimeStream] Global variable.
https://winhelp.visualneo.com/PredefinedGlobalVariables.htmlFile Related Commands:
New Commands: FileToMimeStream, IniKeyDel, IniRead, IniReadKeyList, IniReadSectionList, IniWrite, UnZipToFiles, UnZipToMimeStream, UnZipToString, ZipDeleteFiles, ZipGetComment, ZipFiles, ZipFileList, ZipMimeStream, ZipRenameFile, ZipSetComment, ZipString
https://winhelp.visualneo.com/Files1.htmlThank you!
We are very close to release a new VisualNEO Win major version with a bunch of new commands and functionalities. Meanwhile we have just updated the documentation. Please take a look and let us know if everything is understandable and clear to you. These are the main sections with changes:
Improved information with screenshots.
Predefined Global Variables:
There is a new [MimeStream] Global variable.
https://winhelp.visualneo.com/PredefinedGlobalVariables.html
File Related Commands:
New Commands: FileToMimeStream, IniKeyDel, IniRead, IniReadKeyList, IniReadSectionList, IniWrite, UnZipToFiles, UnZipToMimeStream, UnZipToString, ZipDeleteFiles, ZipGetComment, ZipFiles, ZipFileList, ZipMimeStream, ZipRenameFile, ZipSetComment, ZipString
https://winhelp.visualneo.com/Files1.html
Quote from Andy Marshman on August 13, 2021, 1:26 pm@luishp I've had a quick check through and it all reads clearly to me.
Looking forward to the release.
Regards
Andy
@luishp I've had a quick check through and it all reads clearly to me.
Looking forward to the release.
Regards
Andy
Quote from Vadim on September 3, 2021, 3:36 pm@luishp
Wonderful, useful additions! Thank you so much!!!
- I suggest the "Use relative path and wildcards" checkbox be enabled by default. Newbies always run into the problem of transferring a project to another computer. Hard paths are more of an exception, so relative paths should be enabled by default. It seems to me that way.
- Regarding online help. I don't know if there is such a possibility - to forbid google to automatically translate text in square brackets (see screenshot) as well as command names. So that global variable names and command names stay in English when translating the rest of the text to another language.
- I want more information about MimeStream. When is it preferable to use it instead of Embedded? How is base64 encoding useful?
Wonderful, useful additions! Thank you so much!!!
- I suggest the "Use relative path and wildcards" checkbox be enabled by default. Newbies always run into the problem of transferring a project to another computer. Hard paths are more of an exception, so relative paths should be enabled by default. It seems to me that way.
- Regarding online help. I don't know if there is such a possibility - to forbid google to automatically translate text in square brackets (see screenshot) as well as command names. So that global variable names and command names stay in English when translating the rest of the text to another language.
- I want more information about MimeStream. When is it preferable to use it instead of Embedded? How is base64 encoding useful?
- You need to login to have access to uploads.
Quote from HPW on September 3, 2021, 6:29 pmHello,
I want more information about MimeStream. When is it preferable to use it instead of Embedded? How is base64 encoding useful?
You do not use it instead of Embedded. You embedd files when you want them in a save place and when they never change on runtime. Or when you want somthing to extract to filesystem on the first run of your app.
Mimestream's are a generic way to store binary data in text-based neoscript variables.
At least a similar way as the internet protocols handle binary data.
When you load a binary file into memory you get an amount of bytes as a memorystream.
You get the same bytes in memory when you decode the mimestream to a regular memorystream.
I introduced mimestreams over 10 years back in my plugins hpwImage/hpwUtility when I want to transport binary data between 2 plugins or a plugin and neobook.
With the latest release we get first uses of nativ support of mimestreams in VNW for imagedata.
And with the new zip-support the use of mimestreams gets much more usefull.
In-memory processing of binary data can be get much more usefull, when more plugins or objects gets enabled to use this option. It is a open standard and freeware libs exist for encoding/decoding.
Regards
Hans-Peter
Hello,
I want more information about MimeStream. When is it preferable to use it instead of Embedded? How is base64 encoding useful?
You do not use it instead of Embedded. You embedd files when you want them in a save place and when they never change on runtime. Or when you want somthing to extract to filesystem on the first run of your app.
Mimestream's are a generic way to store binary data in text-based neoscript variables.
At least a similar way as the internet protocols handle binary data.
When you load a binary file into memory you get an amount of bytes as a memorystream.
You get the same bytes in memory when you decode the mimestream to a regular memorystream.
I introduced mimestreams over 10 years back in my plugins hpwImage/hpwUtility when I want to transport binary data between 2 plugins or a plugin and neobook.
With the latest release we get first uses of nativ support of mimestreams in VNW for imagedata.
And with the new zip-support the use of mimestreams gets much more usefull.
In-memory processing of binary data can be get much more usefull, when more plugins or objects gets enabled to use this option. It is a open standard and freeware libs exist for encoding/decoding.
Regards
Hans-Peter
Quote from Vadim on September 3, 2021, 9:14 pm@hpw
Thank you so much for your comments and especially for developing VNwin!!!
Thank you so much for your comments and especially for developing VNwin!!!