Hi Andre
I'm not sure about this, since I haven't used the plugin .exe option, but here's a guess:
the players in Opus, upon publication, take up "overhead" in terms of Mb's, so if you use a regular .exe standalone, it will have its Mb size inflated by the players. If you use the plugin .exe option, it omits the players with their Mb "overhead."
For example, a pub I'm currently developing if published as a standalone .exe has a size of 2.12 Mb, wheras if I publish it as a plugin .exe, it is 315 Kb instead.
However, the person viewing the plugin .exe version who does not already have the plugin installed will need to either download the plugin or find it as a separate file elsewhere. You can check with DW, but I think you may be able to package the plugin set-up along with the main plugin .exe. Of course, adding it like this may assure a path to find it but doesn't save on the total size.
The other difference between the HTML-web version and the plugin .exe versions are that the web one will use a web browser like IE to open, whereas, the plugin .exe one, I think, opens simply standalone in Windows.
Other Forum colleagues with more experience than I can correct my guess, if inaccurate and supplement the answer.
But, hopefully this will help.
Kind Regards,
_________________ Stephen
|