Hi,
Thank you for your enquiry.
As you may be aware, when you publish an executable in Opus, the publication data file is combined with a file named ilmplay.exe (located in C:\Program Files\Opus Pro 04\Players\win32). This 'player' file is the same for every publication and contains all of the code necessary to run your publication data on the end-users system. This player file adds an overhead of around 1.5 MB to any published file.
The iO-plugin essentially installs this player file onto the end-user's system, so when they visit your iO-based web publication, they only need to download the publication data and the previously-installed plug-in will run the publication.
Publishing a project as an 'iO plugin based standalone publication' creates an executable which does not contain the player file and is therefore substantially smaller than a normal standalone publication. For example, publishing a blank, single page publication as a standalone publication results in a file weighing in at 1.56 MB, whereas publishing an iO based standalone publication results in a file size of 78 KB.
This is obviously very useful when distributing publications on small storage media such as floppy disks or business card CDs or sending publications by e-mail for review. If the client has not previously downloaded the iO-plugin, they will be prompted to download this from our web site (using the same interface shown on web publications) and once the plug-in is installed, they will be able to view the publication (and any future iO-based publications) without delay.
I hope this helps. Please do not hesitate to contact me if you have any further queries.
Kind regards,
_________________ Robin Garrett
Digital Workshop Technical Support
For this message Robin Garrett has been thanked by : mackavi
|