LogicLab allows you to define in the project the folder where the library collection (Package) is located (See article), in this way all the objects present in the various libraries become available in the project, simplifying development.
Elsist on the occasion of important additions/modifications in its libraries it releases new packages (our code Pck055xxxx) with the collection of all libraries inside. In this way you are sure of always having perfect alignment of all versions.
- All released packages are available for download from our site.
- This solution is not applicable to old projects with ppjs extension, in case save the project with the new plcprj extension.
Obsolete items
The evolution of the libraries leads to making obsolete some objects which are replaced by new, more performing versions. To allow the compilation of all programs even those dated, all obsolete objects are placed in the library eLLabObsoleteLib which is present in the distributed package.
Project source code
As described in this article, LogicLab allows you to download the source program to the device in order to have a copy of the project files. Naturally, even if compressed, the size of the project files is much larger than the executable file, and this increases both the time required for downloading and the space required on the device.
Now being able to have a homogeneous collection of libraries uniquely identified and always present in the distribution of Logiclab, it is useless to transfer the sources (even if encrypted) of the various libraries, so only the sources of the developed program will be transferred, considerably reducing both time and space necessary.
Libraries update
The libraries are constantly evolving, updating and/or adding new objects, but the collections (Packages) are only released on a scheduled basis. Between releases there may be library versions that will then be included in the next package version. During this period, a beta version of the package is released (recognizable by the code ending with "_") which contains the libraries under development, also recognizable by the code ending with "_".
Use the beta version of the package (Download) only if strictly necessary. If used, we recommend copying the package folder into your project and replacing the package path with the new beta version.
