Want to set-up One pub install (.exe), and 'run many'

Lar_123 · **Posted:** January 14th, 2009, 11:12 am

After following thread below, I decided I want to pursue the approach mentioned. Goal would be that User does one install of a Full OpusPro publication, and I provide three "modules".

from: viewtopic.php?t=3311&start=15
Dave Emberton wrote

Quote:

There is another possible solution. If you set the publish option for "Create executable and data files", you'll get an .exe and .ilm file.

The .exe files are all the same, so it is possible to use the same .exe for many different publications and pass the .ilm file as a parameter.

I'll be using a DB. Probably one common database for all 3 'modules'. Could store names or codes for .ILM files (modules) there. But I am confused a bit... where or how to "pass the .ilm file as a parameter".

Can someone outline how to set this up? More importantly, I want to understand what this looks like for the User. (I'm hoping User will see only 1 Pub in the Windows taskbar)

I'm thinking it's a small 'dialog' Pub with a ListBox showing the 3 choices. Is it required then to have an action to "Launch" chosen pub and Exit current one?? Any better ways to do this?

Thanks.

mackavi · **Posted:** January 14th, 2009, 3:01 pm

As Dave points out you can launch an .ILM file using the EXE by passing it as a parameter. This is because if you publish with data files then the EXE created is simply the IO player found in the Opus directory (check the MD5s)

Basically, what you're doing is working the same way as a Plexus publication and personally I would actually publish to Plexus (discarded the HTML) and launch the file with IO Player via Windows Run.

ILMPlay.exe Untitled1.ilm

Where ILMPlay.exe is DW's player or your EXE and Untitled1.ilm is the published data file (s) including any necessary path.

Although, I've never done this - my attempted solution would be to create a menu publication with the separate EXE (player) and data file. If run, the player should launch any ILM with a same name as the EXE by default thus launching your menu.

The menu would need to read the files in a specific folder and display this as the available modules. Then because your EXE is actually a player, I'm guessing that if you now launch the EXE but this time with the parameter of the chosen module it will run the ILM. Simply specify the close on launch option to have only one program running.

Personally, this method is reasonable for Mike's problem if the publications are distinct but if these 'modules' form part of a cohesive unit then Opus is better suited to using the update function and designing the initial EXE as the module manager. Opus has all the tools necessary to work with new pages / chapters if added dynamically using updates and is more than capable of creating a full LMS.

Mack

Lar_123 · **Posted:** January 15th, 2009, 12:59 am

Mack wrote:

Quote:

ILMPlay.exe Untitled1.ilm

Where ILMPlay.exe is DW's player or your EXE and Untitled1.ilm is the published data file (s) including any necessary path.

Thx. Clears that up. Now seems 'obvious', and warrants at least a virtual-DUH. :oops:

So can we confirm or clarify some of this? Here's what I think you've outlined,
A -- the User launches an installed 'application', PubMaster_Menu.exe
which is what you suggested here:

Quote:

create a menu publication with the separate EXE (player) and data file. If run, the player should launch any ILM with a same name as the EXE by default thus launching your menu.

Then
B -- when User chooses 'Module B' from "Menu", the OpusScript might be look like this:

Code:

//modified from Help file example for LaunchFile()
var Fname = SYSTEM_PROGRAMS_DIR + "\\InstalledFolder\\PubMaster_Menu.exe"
var Params = "Module_B.ilm"
LaunchFile(Fname,Params)
wait(0.1)
ReallyExitPublication()

However I don't understand 'Windows run'.

Quote:

launch the file with IO Player via Windows Run.

As for the 'Modules' being distinct vs. cohesive, I'm thinking it is more 'distinct' eBooks. Working inside one rules out jumping around in another. These Modules do share a common design/look, and structure, however.

This is really encouraging --- what can be done. So many choices. Thanks for the help.
Larry

mackavi · **Posted:** January 15th, 2009, 10:29 am

Windows Run - EG - Click start and then the run box or in your case - enter the program to be run in the Vista run / search bar.

I check the idea above and it does work.

Create the menu publication as a normal Opus publication using the launch to execute itself with the ILM of choice as the parameter.

Then create your ebooks. Publish this as Web Publications and keep just the ILM file.

Mack

Lar_123 · **Posted:** January 15th, 2009, 11:29 am

Mack, thanks.

Your answer provides me some confidence to proceed in this direction.

Right now I am laying out the sqlite DB, so will not test the .exe/.ILM approach until next week perhaps. However, I did want to confirm this method so I can anticipate dovetailing it in the DB.

Quote:

Windows Run - EG - Click start and then the run box or in your case - enter the program to be run in the Vista run / search bar.

Okay, I take it this is a neat way to test it when needed. But I expect the User to do an Install of the default Pub and just click on a shortcut Icon to run it. Sorry if I belabour the point.

Since you've reminded me of the Opus update route, I've modified my DB structure to allow that approach as well, and map to Opus Chapters.

Cheers,
Larry

Digital Workshop

Want to set-up One pub install (.exe), and 'run many'

Who is online