Re: Why are you on a *nix desktop?

"How hard is it? You can do CommandCalls and gather the messages back?"

I don't know enough about the mechanisms available (yet). I have to dig in a bit and see what the best option would be. Perhaps on the i side I could have a data queue that I could poll from the installer client that would give status updates, That could be relatively simple.

"I'd be very interested in hearing about your experiences."

I'll post back to you when I get something cobbled together. This isn't high on the list at the moment but there is a propriety application suite that runs on the i that I write custom applications for and for which I *used* have source for so I could tweak my RPG installer to work. However, about a year ago they changed ownership and made some updates for which I no longer have source code so I'm going to have to "roll my own" shortly. I'll let you know. An open source, i centric, "plug in" for IzPack might be a useful project

Pete

Thorbjoern Ravn Andersen wrote:

Pete Helgren skrev:

The biggest challenge is error feedback that makes it's way back to the user on the desktop: Firewall issues. Authority issues. Compiler and component (prerequisites) failures. The progress in the installation process. All that needs to be communicated back to the user in an intelligible manner.

How hard is it? You can do CommandCalls and gather the messages back?

Also, the installer needs to be something easy to script so that after the work is done to package it on the i there is just a minimum amount of stuff that needs to be scripted at the installer end to make it all work. IzPack seems pretty flexible and there might be some way to write some generic scripts that call the same routines on the i with the instructions being packaged and run at the i (in CL, probably).

I have just been musing about it today as I ran the ant scripts to build, jar and create the installer for tn5250j. Something I hope to look at soon.

I spent some time a while back to write some "build these Eclipse projects using ant and ant4eclipse" tasks. Those build.xml-files are rather nasty :)

I'd be very interested in hearing about your experiences. This might be a golden egg for deploying to remote servers for us too.