AutomatedInstallData vs. InstallData

[David Ngan]

What is the practical difference between using AutomatedInstallData and InstallData? Why are there two "install data" objects? InstallData extends AutomatedInstallData and they are both singletons, right? If I add an item to the InstallData object, will it be accessible from the AutomatedInstallData object (and vice versa)? Why do some methods get passed the AutomatedInstallData object (such as executeAction() in panel actions) while an InstallData object is passed in for things like the constructor for custom panels?

[ZellKries]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi I'm not a master in the subject but I think the main difference between then is that the install data is the one that the installer will use and modify trough the installation, and the automated data will be like the event mirror so then IzPack generate the atuomatic xml installation file (so it can be runned in diffent pc with the same installation settings).

Reggards,

Kries

> Date: Fri, 23 Oct 2009 16:01:26 -0700
> From: dngan@...
> To: user@...
> Subject: [izpack-user] AutomatedInstallData vs. InstallData
>
>
> What is the practical difference between using AutomatedInstallData and
> InstallData? Why are there two "install data" objects? InstallData extends
> AutomatedInstallData and they are both singletons, right? If I add an item
> to the InstallData object, will it be accessible from the
> AutomatedInstallData object (and vice versa)? Why do some methods get passed
> the AutomatedInstallData object (such as executeAction() in panel actions)
> while an InstallData object is passed in for things like the constructor for
> custom panels?
> --
> View this message in context: http://www.nabble.com/AutomatedInstallData-vs.-InstallData-tp26034411p26034411.html
> Sent from the izpack - users @ codehaus mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

---

[Kjell Braden-5]

Hi,

CHRISTIAN EMAI ANASAGASTI wrote:
> Hi I'm not a master in the subject but I think the main difference between then is that the install data is the one that the installer will use and modify trough the installation, and the automated data will be like the event mirror so then IzPack generate the atuomatic xml installation file (so it can be runned in diffent pc with the same installation settings).
>
> Reggards,
>
> Kries
>

Definitely not. See below.


David Ngan wrote:
> What is the practical difference between using AutomatedInstallData and
> InstallData? Why are there two "install data" objects? InstallData extends
> AutomatedInstallData and they are both singletons, right?

As you noticed, InstallData extends AutomatedInstallData. Seeing that
the automated installer is headless, and looking at the code of
com.izforge.izpack.installer.InstallData it becomes pretty obvious that
the InstallData adds GUI stuff (specifically: GUIPrefs, the current
Panel and some Colors).
I'm not sure what you mean by singleton here.

> If I add an item to the InstallData object, will it be accessible from the
> AutomatedInstallData object (and vice versa)?

As you are writing to the 'user' list, what do you mean by "add an item
to the InstallData object"?

> Why do some methods get passed the AutomatedInstallData object (such as
> executeAction() in panel actions) while an InstallData object is
> passed in for things like the constructor for custom panels?


Because some methods will be run in both the headless ("Automated") and
the usual GUI installer and some methods will be run in the GUI
installer only (the constructor on IzPanel and it's subclasses for example).


-Kjell

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email