Working with Packages

www.altova.com Print this Topic Previous Page Up One Level Next page

Home >  User Reference > Mechanisms > Packages >

Working with Packages

Packages are stored on the server and are installed locally (on the client), on demand via the Authentic Browser GUI. Once a package is installed locally, it is activated on every startup until the user removes it.

 

 

 

Package management

Package management is an Authentic Browser functionality that gives the Authentic Browser user control over available packages. This functionality is available via the Package Management dialog.

 

To enable package management functionality, you must use the LoaderSettingsFileURL parameter in the HTML Page for Authentic Plug-in. This parameter specifies the URL of the LoaderSettings file for package management (which can reside at any accessible location):

 

In an HTML page for Internet Explorer, the LoaderSettingsFileURL parameter is used as a child PARAM element of the OBJECT element:

 
<OBJECT>

 ...

 <PARAM NAME="LoaderSettingsFileURL" VALUE="http://www.server.com/AuthenticFiles/XMLSpyPlugInLoaderSettings.xml"/>

</OBJECT>
 

In an HTML page for Firefox, the LoaderSettingsFileURL parameter is used as an attribute of the EMBED element:.

 

<EMBED

    ...

    LoaderSettingsFileURL="http://www.server.com/AuthenticFiles/XMLSpyPlugInLoaderSettings.xml"/>

 

The LoaderSettings file contains the definitions of the packages, along with the URLs of the respective packages. Given below is the listing of a LoaderSettings file.

 

 

 

Example of a LoaderSettings XML file

The document element of the LoaderSettings XML file is loadersettings (see listing below). This element can contain multiple child package and/or multiple zippackage elements.

 

The package element is used to reference the older .pck spelling packages and is used by Authentic Browser versions previous to version 2011r3. These Authentic Browser versions ignore the zippackage element.
The zippackage element is used to reference the .zip spelling packages and is used by Authentic Browser versions from version 2011r3 onwards. These Authentic Browser versions ignore the package element.

 

For more details about the spelling packages, see the section, Spellchecker Packages.

 

 

<?xml version="1.0" encoding="UTF-8"?>

<loadersettings>

 

 <zippackage mode="user_demand"        category="spelling">

         <packageurl>Portuguese (Brazilian).zip</packageurl>

         <description>Portuguese (BR) language pack.</description>

 </zippackage>

 

 <zippackage mode="user_demand"        category="spelling">

         <packageurl>Portuguese (Brazilian).zip</packageurl>

         <description>Portuguese (BR) language pack.</description>

 </zippackage>

 

 <package mode="user_demand" id="SentrySpellChecker_EAM_only"

         category="spelling" version="1">

         <packageurl>PlugIn/SentrySpellChecker_EAM_only.pck</packageurl>

         <description>Sentry Spellchecker (EN-US)</description>

 </package>

 

 <package mode="user_demand" id="SentrySpellChecker_EALL"

         category="spelling" version="1">

         <packageurl>PlugIn/SentrySpellChecker_EALL.pck</packageurl>

         <description>Sentry SpellChecker EN with Legal and Medical.</description>

 </package>

 

</loadersettings>

 

The following should be noted:

 

The location of a package must be specified as content of the packageurl child of the package or zippackage element. The location path can be absolute, or be relative to the HTML file that calls the LoaderSettings file. The package can be located anywhere on the server.

 

Removing a package from the XML file (by removing a package element) causes the package to not be available for installation on the client.

 

The mode attribute of the package element specifies the level of user influence over the decision to install the package. The following values may be used:

 

1.user: Causes the user to be asked at every Authentic Browser startup whether the package should be installed.
2.user_demand: Installs the package when this is specifically asked for by the user. The user specifically requests this by clicking either the toolbar button to spellcheck or to open the Package Management dialog.
3.force: Causes the package to be installed without notifying the user.

 

The content of the description child of package can be edited will be used as descriptive text in the package management dialog.

 

 

 

One-time installation of packages

If Authentic Browser is updated to a newer version, there is no need to reinstall a package that was previously installed on the client. The already installed package will be used by the new version. Authentic Browser on the client PC reads the LoaderSettings file on the server, retrieves package information from this file, and checks whether the package is locally installed.

 

Note:Spelling packages supported in version 2011r3 and later (.zip packages) use a different spellchecker than the spelling packages of previous versions (.pck packages). Authentic Browser versions from version 2011r3 onwards use either the .zip spelling packages. Older versions of Authentic Browser use the .pck spelling packages.

 

 


© 2018 Altova GmbH