Software packages overview
The software in WordFrame Integra platform is organized in so called software packages. The package manager enables you to install, uninstall or update those packages, while complying strictly with the dependency policy of the software package developer.
It automatically checks and synchronizes its package collection from the software repositories it is subscribe to. You should regularly update your system in order to apply important security and bug fixes.
Each software package has the ability to be signed by its vendor in which case its integrity and vendor could be guaranteed.
Disclaimer: Not signed software packages or packages signed by not trusted vendors can cause system malfunction or security breach. WordFrame team and ITBrix as a company, advices you strongly to install only packages that are properly signed and developed by vendors that are approved as trusted by the WordFrame team.
packages can be categorized in five types, based on their purpose:
- application packages
- provide the ability of web applications to be created, updated and deleted as modules on top of the WordFrame Integra platform. These packages include library files and business logic; scripts for creation, update and deletion of databases and database tables; list of all other packages that are required to be modified and how; information about what kind of user interface must be constructed in the public part of the system, for the users to be able to interact with the application.
- webframe packages
- templates, that provide an ability of webframes to be created, updated and deleted. The webframe is a presentational block for the user interface that resides in specified page region. The webframe pack includes not compiled and open source .ascx files. It can include images, flash, movies, audio and everything that is needed from the webframe to provide its functionality.
- user interface packages
- language packages
- provide language localization by application basis. They do not need to be instantiated in order to be used. If you attempt to uninstall a language package that is used by a master page, the uninstall job will fail with an error. The package includes an XML file with key <-> resource pairs in it. They could be partially customized be overwriting the pairs from the corresponding page in the Builder's section.
- utility packages
- provide some extra functionality, libraries or resources that are need from the applications and must have its own update and dependency list. The package may contain any file type.
Last edited by georgeatha on 28 Sep 2010 | Rev. 10 |
This page is public
Filed under: Software management