Using an Installer for plugins

[jorm]

I just installed the nullsoft installer, and wrote a quick installation script for xrecord and fastfind. Easy to use.

When you use the installer for xrecord it now
1. creates the rectracker.mdb if it does not already exists.
2. creates the default priorityrecordings.xml if it does not already exists.
3. and handles the shutdown and restart of the recording service because of the fast find dll in the root directory.

If you want to try it out (at your own risk) I have done it about 6 times no problems yet.

http://www.bladerhq.com/pmwiki/pmwiki.ph...in/XRecord

If developers are interested I will post my script.

Jrock if you need want I can write ones for cdk scheduler and guide2j as well.

The installer itself.
http://nsis.sourceforge.net/home/

Easy to use frontend
http://hmne.sourceforge.net/

[reboot]

Is it hard coded to the default install path, or can one manually select the install?

Why don't you write an installer, that includes all the best plugins, all in one package?
I'm sure lots of people would like a hassle free way of getting all the goodies, then disabling what they don't want in config, if necessary.
Weather, FindFast, Xrecord, Theatre, Guide2J, RenameRecording, RecTracker, ComSkip, BleepBloop, CheckEmail, Diskspace, DVDRipper, the "My" series (all), RSS Reader, Shutdown, and Solitaire are my choices

[jorm]

It is not hard coded. It reads the gbpvr path from the registry and installs to that location.

That is a good idea, one plugin pack. The problem is that bladerse has been running out of bandwidth and making a big file might cause even more problems for him.

[Jeff]

I would be interested in seeing the script and creating install scripts for the new weather plug-in and the video archive plug-in.

Jeff

[reboot]

You create it, and we'll debug it, and I'll host it (providing it's under 5 meg), with a direct link from the Wiki, so his bandwidth doesn't get used.

[jorm]

I am posting the install script on wiki under xrecord you can open it with notepad or install the apps.

[jorm]

As for the plugin pack. We should probably use individual installers first. And then build a installer that includes all of the others and invokes them one by one.

[reboot]

If you want to write a separate installer for each plugin...
I would think it easier to bundle them ALL. Let the user decide what to use, either through the installer as an option (tickboxes), or config.

[Jeff]

The problem with bundling them all is that they are not all released under the same schedule nor is the list of files required by each plug-in constant from release to release.

Jeff

[jrockintuitive]

Jorm I do appreciate that offer... and please do create the install program for me.

A few more weeks and I will be back in business.