Mimestreams and Data - Forum

Forum Navigation
You need to log in to create posts and topics.

Mimestreams and Data

I'm just beginning to play with the new mimestream features and would appreciate some clarification.  Could someone explain to me the difference between an embed and a mimestream variable?   Both house the data for access and so I know I'm missing something ;-)

Thanks

Hello Robert,

>embed and a mimestream variable

There are no embed or mimestream variables. All variable are text.

The minestream content represents some binary data in base64 encoded text-format.

Both are storage methods. The embed data is readonly and is stored on compiletime.

Embed files are read by a special SDK Api (OLE) call by commands and plugins.

Mimestreams can be read/write or dynamicly created.

You can mix both technologies is some manner.

You can store a zip in embedded and read content from the zip to a mimestream-variable. But  no way to save back then on runtime.

So you can leave the zip (also renamed to other extension) external and have the data read to variable (for text) or mimestream (for binary).

Regards

Hans-Peter

 

luishp, Vadim and 2 other users have reacted to this post.
luishpVadimCN_Icemanrcohen

Thanks for the clarification Hans.

Have a great holiday!

I am able to convert a file to Mimestream, but ... what is the method to return the data to it's original file?   I must be missing something....

Thanks

Hello,

Not sure what you mean exactly. Dependes on the sort of file you use.

When you have a specific file format you need an app/plugin to load that mimestream and is able to do a LoadFromStream into an object.

So a bitmap can be loaded into an ImageWindow.

In hpwImage you can load an image from a Mimestream and save it to back a real bitmap-file.

So first the code has to decode the MimeStream into a binary memory stream and then the code has to understand/load that binary stream.

Regards

Hans-Peter

 

rcohen has reacted to this post.
rcohen

Thanks @hpw,

I was then trying to use it for something that it wasn't intended for.  I swapped that out for a mime64 solution.

Thanks for the clarification.

I must say, I'm missing the boat regarding how to then use Mime streams towards something advantageous.  To be able to load an image using a mime streams only in Neo is a nice trick, but how does this offer an advantage?   I'm obviously missing something ;-0 (wouldn't be the first time) ;-)

Thanks Hans

Hello,

My real excamples for mime-streams are:

Use an embedded zip for data-storage: Only one embedded file entry and a internal file system with pathes with simple maintainance.

General support for file access from an encrypted zip data-container without accessing local file system.

hpwImage's load and save from/to mime-streams.

hpwScreenShot (hpwUtility) with mimestream-support.

hpwKnobCreate (hpwUtility) with mimestream-support.

 

There might be more usefull uses. ;-)

Regards

Hans-Peter

 

rcohen has reacted to this post.
rcohen

@hpw,

Understood.   Thanks for the further explanation.

I recall using free DB plugin back when to package media in blob fields with a search ability.   I see where this here can eliminate the need for such.

Thanks Hans