Installer

[Papillon]

Ok, I'll set something up.

Is the current prototype something you can work with ? Or do you need more information on the files ?
_________________
Papillon

[Via Con Diablos]

The current prototype should be fine. I should be able to post a version of the installer within a day of the server side file being in place.

It will check that file, download the version of nwnx4 listed in the file, and then set it up.

[Papillon]

[Via Con Diablos]

I think so, I'll give it a shot when I get home from work tonight and see how it goes.

[Via Con Diablos]

Seems like the nwnx download plugin doesn't like that format. It errors out stating that the server did not specify the content length. I'm guessing due to it being dynamically generated through the cms.

If you need, I could probably host the file and build a php interface for you to update it.

[Papillon]

Ok, then please try this link:

http://nwnx.org/fileadmin/current.txt
_________________
Papillon

[Via Con Diablos]

Sorry for the lack of an update. The download plugin with nsis doesn't like the php fed downloads. I'm checking into a few other options (InnoSetup, Installshield, writing a new downloader plugin) and will hopefully have something soon.

[Papillon]

Stupid downloader plugin I hope there will be a solution, since I'd really like to count the downloads the installer makes.
_________________
Papillon

[Papillon]

Any news on the installer ? Is there something I can do to help you ?

If the automatic download feature is to complicated, you might want to consider creating a normal, monolithic installer.
_________________
Papillon

[Via Con Diablos]

I've got a working example, with the downloader, excluding one small bit.

The nwnx.ini and xp_*sql.ini have no section identifiers. Would it be overly much trouble to get a
[main]
added to the top of each file?

To see it in (almost) action
setup.exe

[Papillon]

I just tried it, looks good ! Would it be possible to have a "No DB" option on the database selection screen ?

I could add that section to the ini file, but then I would have to change the source code as well... it's not a problem of course - if the installer absolutely needs it, I can put everything in a [main] section.
_________________
Papillon

[Via Con Diablos]

Yes, it'd be easy to add in a no db section as well.
Adding the [main] section would be perfect if it's not too much trouble. Unfortunately InnoSetup (which I finally went with for the installer...works much better than NSIS) requires a section of some sort of the ini file. I tried leaving it blank, but it wouldn't compile.

[Via Con Diablos]

Oh one other question. When you add a new version of NWNX to the download page, will the link change?
Right now it is http://www.nwnx.org/typo3conf/ext/nf_downloads/pi1/passdownload.php?downloaddata=7
Is it possible for you to keep that link the same when you update to a newer version?

[Via Con Diablos]

Alright, I've got a fairly functional installer working.
It will download the plugins you specify (currently only three) and set them up.
It doesn't do much for validation yet, but that will be coming soon.

Plugin creators: I'm trying to think of a way to automatically create setup pages in the installer for new plugins. This would require an additional INI on your end, that the installer could read, and then create the needed info in the installer.

Any feedback on the current revision would be appreciated.

http://www.twilightlegacy.ca/NWNX4Setup.exe

[Papillon]

Impressive! This is a really, really fine installer !

Here are some small issues that I've found during my tests:

- It says it will install prototype 1.06. Is that hardcoded?
- nwn2temp: Maybe add a note that leaving this empty will not change the default NWN2 already uses
- gamespy watchdog ("how often should the gamespy..."): It's not clear what the unit is (seconds).
- The mysql page is missing an option to set the schema (db) name.
- (possibly irrelevant, since there is now a GUI): The Desktop .lnk does not include the -interactive command line switch.
- my nwnx.ini ended up with a double module specification: parameters = -module mymodulefile -module mymodulefile

I think 1.08 will have an installer .

Could you post an example ini file for setting up a plugin installer page ? Maybe for one of the DB plugins, for illustration purposes.
_________________
Papillon