Digital Workshop

My most basic question here is this: what is a good strategy for keeping the Plexus Plug-in updated...
[Lar Edit:] I say 'Plexus Plug-in' above & below, but I don't know what I am talking about. I am confusing Plexus with IO Opus Player... "full standalone player" and further with the [b]"executable" generated in Publishing.[/b]. Let me take this up below in a 'Reply post' March 26th.
a) packaging the Plexus Plug-in with the "install" or prompt for download, or...
b) if one is already installed, setting up a way to verify/compare what is the most current Plug-in ?

FYI, I think my particular scenario is to have one executable player, and several .ILM packages (cumulatively adding ILMs over time)

I am assuming I will use both EnigmaProtector and AdvancedInstaller (Stephen's and Mackavi's recommendations respectively). Then there is the whole issue of DRM (digital rights mgmt) which Stephen has highlighted recently -- so trying to figure out where that fits in.

Some questions I am 'facing':
1. the Plexus Plug-in question --- how do you get a User to update the Plexus plugin when it is revised? e.g., maybe replace with 'newer' on the next purchase/install?
2. do you have any advice, or links/overviews, regards specifying Install Directories. We've had some discussions here: viewtopic.php?t=3129&highlight=vista+install+path
I am trying to get an overall picture and understanding of where things are going.
-- where to put multiple ILMs and their individual sets of content files
-- where to put a common/central DB file

3. (more of an anticipation question) If I use 'installer' and 'protector', and want to update one particular .ILM -- what tool governs that update process? e.g., Opus update feature, EnigmaProtector (EP), an Overinstall/Upgrade.
( at Stephen's advice, I will query EP support regarding their capabilities.)

I am not looking for a specific answer. I'd be happy with some advice as to things to consider and best-practices. Hopefully this is an open-ended discussion that may benefit many others.

apologies in advance -- I know I am throwing out a lot at one time. It is just reflecting the scope of what I am facing.

Hi Lar

I'm not even sure I really understand what you are talking about here, so I will be tuning in and listening hoping to learn something - and there seems to be so much to learn about as well.

Cheers

Graham

Thanks Graham.

At its most simple, it is a question of the consequences of installing Pub data files and ILM files in directories other than C:\Program Files

Common paths for Vista and beyond seem to be:
C:\Program Data
C:\Users\User01\Documents
C:\Users\User01\NewPubFolder
C:\Users\User01\App Data\AlsoPubFolder

(so far, ignoring Default and Public paths under c:\Users)

I am nearly tempted to remove my question as I realize it is 'twisted' around a huge set of conditions to consider. But let's let it float here a bit.

I am truly a novice for this back-end stuff... distributing and installing, maintaining and updating.

so reframing the questions:
Q2 - where to install .ILM files (when separate from .exe)
Q2 - where to install sqlite.DB which is common to multiple .ILM files

Q1 - was... does the Plexus Plugin (or player .exe) ever need to be updated? How?

Q3 - is a bit more involved. How to deliver changes and updates (probably straight forward until one deploys EnigmaProtector)

Any bits of wisdom appreciated. TIA

All of these questions apply to Client machines (and is not about OpusPro program or Editor)

Okay, let me restate part of this where I was/am confusing these components:
* Plexus Plug-in ( which I think is: ILM5.ocx )
* IO Opus Player "full standalone player" ( which I now think is: ILMPlay.dll and ILMPlay2.dll )
* "executable" as discussed below/see quote ( ?? )

David Emberton post Dec 22, 2008:
That is what I want.

So I am trying to sort out the installs and follow-on purchases of extra Pubs (as ILM files + External Files), as well as fixes/updates....

When a Customer installs that "separate executable", I thought that would reside in C:\Program Files\Larry_Branded_App\
as a programXYZ.exe ---- true?


Part of my confusion is related in reading Emberton post Dec 21 08, talking about the Plexus plug-in... and the player

In the above mentioned Common FIles path, there are mostly DLLs and OCX files.

So if and when I can get to understand those (plug-in, full player, executable...), I want to determine how and where to "install" .ILM files (and external files/data sets) initially and for subsequent purchases of add-on modules.

More 'clear' for what I'm asking I hope. All replies appreciated.


for reference I viewed/quoted these:
viewtopic.php?t=3311
viewtopic.php?t=1742 (in 2006)

Hi Lar,

The file(s) containing the data are the *.ilm ones. These can be launched from the 'desktop' using the executable (exe) which can be standalone or wrapped to include the data.

They can also be launched using the OCX / DLL (depending on browser) from the Firefox / IE / Chrome / Etc. See the HTML file that is published with the web publication.

You can also interchange the ilm from a web / 'desktop' publication and launch using either method.

The path for the ilm needs to specified when you launch the EXE or the HTML file. The default for the 'desktop' is the same folder, but can be changed.

As for where to installed, then under Vista+, EXEs should be in the program files folder and the ilms if updated should be in the programdata or user data folders depending on who should have access.

If you intend on updating the EXE then do it properly using an installer, preferable - MSI based. As for when to update the EXE - this is simply dependant on the version the ILMs were published with. IE don't use an Opus 6 EXE to run an Opus 7 publication. I don't know whether the EXE bit actual does change, DW can confirm, but it seems common sense!

Then simply update the ILMs using either the update option or publish as standalone and distribute in the method that suits.

As for Enigma Protector, I won't answer this - as I don't like the program or concept.

Mack

Mack,

Thx. I think you have either directly answered many of my 'doubts', 'fogs', and uncertainties... or have at least pointed the way ahead. I will have to review and see what remains to cover.

Thanks. I didn't know how to treat the ILMs. Most likely I will plan on \Program Data and give the Customer some guidance to maintain backups. My ILMs will serve mostly as layouts/containers, and will have the logic and controls. Much of the rest is external.

Good to know. However, this project cannot use web-based or Flex given the feature limits.

Now that I can put the plug-in and the player 'out of the picture', installing and updating seems more straight forward. I can appreciate that I'll need a 3rd party Installer. ( It seems update of main EXE will be infrequent. Good. )

I will have to get hands-on here... and just experiment, and test, methods for updating ILM packages. Maybe OpusPro's native installer/updater will work -- as incremental updates if I make each ILM "updatable" to begin with. I expected that that option/feature would not be available for "separate exe & ILM".

Maybe I can do without EnigmaProtector. Certainly simplifies the mix w/o it. I am just concerned about cracking and pirate copies of ebooks (ILMs). Also, am not ready to bear heavy expense for complete server solution for registration/control. Will need some tool or service for it.

All things considered, this is making much more sense now. So thanks again.