With IzPack there are two ways to implement custom actions. The third step, the reporting phase, is normally represented by a panel that reports the result state of the installation (OK, or not OK) and a simple good bye message. In IzPack there are already some common actions, for example "file transfer", "parse" or "execute". There are actions intended to be reused, so called common actions, and actions for one special purpose only, so called custom actions. Each of this subsequent steps are denoted as actions. files will be copied to the installation destination or some short cuts will be registered. During this step the state of the locale machine will be changed, e.g. If all needed data is collected the second step will be perfomed, let us call it the action phase. the destination path - different input panels are involved. But mostly - depending on to the information, e.g.
In general nothing will be changed on the system until all needed data is obtained.
Typically this is done by typing all neded data into one or more panels, if a GUI is used, or automatically by reading the data from a config file. The first step, let's call it the data collection phase, is getting specific data needed for the installation process. In general the installation procedure is separated into several steps. Learners can use existent custom actions but should not implement them as exercise.
Custom actions are not a good starting point for learning java. The implementation of custom actions presume knowledge of java.
0 kommentar(er)
