DEV02 - Create WarpIN Packages the smart way
Exploiting the power of true XML
Christian Langanke for netlabs.org
Overview
- Introducing WarpIN
- Cause for changing WarpIN
- Former AMP4ECS scripting
- Limitations of WarpIN Scripting
- Creating an alternative: mkwpi
- mkwpi XML - features/element overview/using includes
- Long-term goals for mkwpi
- My WarpIN feature wishlist
Introducing WarpIN 1/2
- XML script defines for a WPI file, including one or more packages
- installation commands to be executed per package
- create Workplace Shell objects
- add items to CONFIG.SYS
- execute programs after installation
- prompt for variable values
- sequence of pages to be shown during installation
- REXX functions to be executed during installation
- other/external packages as prerequisite
- installation commands to be executed per package
- the WarpIN compiler assembles the resulting WPI package from
- the script
- the files for the components
Introducing WarpIN 2/2
- on installation
- text can be displayed to be accepted
- packages can be (de)selected for installation
- files can be installed
- Workplace Shell objects can be created (forced or optionally)
- CONFIG.SYS can be modified (forced or optionally)
- the installations
- are logged to a local database
- can be verified and can be deinstalled without the installer package
Cause for changing WarpIN
- review of the former AMP4OS2 project, now AMP4ECS
- assembles Apache, PHP, MySQL, PHPMyAdmin to one WPI file
- complex build scenario: three WPI files (AMP4ECS13/20/22) were
built out of the components, where some components were used twice
AMP4ECS Apache PHP MySQL phpMyAdmin V13 1.3.37 4.3.10 4.1.7b2 2.6.4 V20 2.0.59 4.3.10 4.1.7b2 2.5.7-pl1 V22 2.2.4 5.2.1 5.0.41 2.10.1 - implemented by a long script and command file per package
- lots of redundant data - including text and commands for packages
- result: changes to the packages were not applied correctly to all required places
Former AMP4ECS scripting
Limitations of WarpIN Scripting
- missing features for WarpIN and WarpIN compiler for complex projects
- no support for user variables (REXX workaround only)
- no include feature (redundancy is unavoidable for complex projects)
- no automatic handling for remote source files (auto-download)
- no language support (REXX workaround only)
- WarpIN implements no detailed XML element hierarchy
- some elements contain assembled string data instead of sub elements, like: CREATEOBJECT, EXECUTE
- Conclusions
- WarpIN is suitable for smaller projects, but may not be flexible enough for larger or more complex ones
- long WarpIN scripts are not well readable due to improper modelling of the XML language
Creating an alternative: mkwpi
- complete replacement of WarpIN compiler not feasable now
- learning curve for that is high (at least for me)
- for now the upcoming preprocessor mkwpi
- introduces a new input format: mkwpi XML
- generates the WIS script and the WPI package file out of the XML data
- implements new features for build of the WPI package
- download required files from a remote URL automatically
- offer a more flexible notation for source files
- does not break backwards compatibility
- is implemented in REXX
- though: cannot extend WarpIN with some other required features
(see my wishlist below)
mkwpi XML - features
- implements a proper XML element structure
- is parsed by a true XML parser (libxml)
- is validated using XML Schema validation
- will cover all features of the current WarpIN compiler
- implements new elements per project and/or package to
- include package definitions in project definitions
- inline in one XML file
- included from another file
- generate pages automatically - no more coding of a page sequence
- include package definitions in project definitions
mkwpi XML - element overview
mkwpi XML - using includes
Long-term goals for mkwpi
- be a prototype and set a standard for a new WarpIN input format and new WarpIN features
- offer a method to let power users add new features to their WarpIN packages
- implement a DLL plugin interface to allow calls to user DLLs
- extend the mkwpi XML schema to allow user defined XML extensions to control the plugin DLLs
- Note: this requires to
- incorporate the mkwpi approach into the WarpIN compiler WIC
- implement the plugin interface to WarpIN
- Benefit:
- builders of WPI packages can extend WarpIN to their needs
- these extensions can be added to upcoming WarpIN versions with little efforts
My WarpIN feature wishlist
- implement all new features of mkwpi :-)
- PREEXECUTE command - allows exit installation on error of sniffer program
- extension of EXECUTE command - allow to hide called programs
- implement language support for the script (text defined by the package)
- on installation download and install remote files defined in a WPI package
The Author
- Name: Christian Langanke
- email: cla@clanganke.de
- homepage: http://www.clanganke.de
- with free programs for OS/2 and eComStation
- my PGP key
- Member of Team OS/2 Germany
- OS/2 user since 1990 from OS/2 V1.2 on
My projects and activities
- author/inventor of projects
- netlabs.org support activities
- The Voyager Project (Design, Promotion)
- Generic MAC Wrapper driver (Release Management)
- Port of WPA supplicant (Maintenance)
- planning or supporting events of
- Team OS/2 Germany local fairs
- netlabs.org developer Workshop 2008
- Warpstock Europe events
The End
Thank you very much for your your attention!