close Warning: Can't synchronize with repository "(default)" (/var/svn/tolp does not appear to be a Subversion repository.). Look in the Trac log for more information.

Changes between Version 4 and Version 5 of Packages


Ignore:
Timestamp:
Feb 5, 2016, 12:54:29 PM (9 years ago)
Author:
Pedro Gea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Packages

    v4 v5  
    2626== Introduction ==
    2727
    28 Bla bla bla ...
     28The idea of a package comes from the concept of modularity and the possibility of loading and
     29distributing a whole module as a unit. A TOL package is essentially no more than a NameBlock
     30distributed in an .oza file.
     31
     32In the TOL programming frame, we identify the package with the NameBlock that contains
     33the set of classes, structurs, variables, functions and definitions. This is distributed and loaded as
     34an unit of the TOL package system.
     35
     36Looking more from a distribution-focused point of view, a package is a compressed file
     37(specifically a .zip file) that contains the nameblock serialisation (an .oza file). This is
     38accompanied by other complementary resources that can be: files containing icons or images,
     39documentation, libraries of compiled functions (written in C++ and distributed in .dll or .so files)
     40and even uncompiled TOL code ( .tol files) by way of example.
     41
     42== Names and versions ==
     43
     44A TOL package is identifed by its name and version.
     45
     46The name of the package matches with the name of the nameblock that represents it. It generally
     47follows a CamelCase structure.
     48
     49The version consists of integers. The first (the high version number) shows if there has been an
     50important change in the structure and functionality; one which could break the compatability
     51with the user-code in use. The second however (the low version number) shows that changes
     52have been made to the package that maintain package-use compatibility. These changes could
     53be corrections or the inclusion of new functionalities.
     54
     55The package identifier is created by linking the name and two version numbers
     56<name>.<version.high>.<version.low> with a full-stop (.).
     57For example, the identifier {{{GuiTools.3.5}}} makes reference to version 3.5 of GuiTools, which
     58includes utilities for TOLBase graphical integration.
    2959
    3060== TolPackage ==