|
Class: stx_goodies_communication
Object
|
+--ProjectDefinition
|
+--LibraryDefinition
|
+--stx_goodies_communication
- Package:
- stx:goodies/communication
- Category:
- * Projects & Packages *
- Version:
- rev:
1.47
date: 2019/08/01 09:37:57
- user: cg
- file: stx_goodies_communication.st directory: goodies/communication
- module: stx stc-classLibrary: communication
Package documentation:
This library contains utilities for various communication protocols and file formats:
DNS, FTP client and server, HTTP client, JSON encoding,
SunRPC, Rest client, SFTP client, SMTP and Telnet client and server.
description
-
excludedFromPreRequisites
-
TestCase - superclass of RegressionTests::FTPClientTest
-
mandatoryPreRequisites
-
list packages which are mandatory as a prerequisite.
This are packages containing superclasses of my classes and classes which
are extended by myself.
They are mandatory, because we need these packages as a prerequisite for loading and compiling.
When loading whole packages,
mandatoryPreRequisites will be automatically loaded
BEFORE this packet has been loaded.
This method is generated automatically,
by searching along the inheritance chain of all of my classes.
Please take a look at the #referencedPreRequisites method as well.
-
referencedPreRequisites
-
list packages which are a prerequisite, because they contain
classes which are referenced by my classes.
These packages are NOT needed as a prerequisite for compiling or loading,
however, a class from it may be referenced during execution and having it
unloaded then may lead to a runtime doesNotUnderstand error, unless the caller
includes explicit checks for the package being present.
When loading whole packages,
referencedPreRequisites will be automatically loaded
AFTER this packet has been loaded.
This method is generated automatically,
by searching all classes (and their packages) which are referenced by my classes.
Please also take a look at the #mandatoryPreRequisites method
-
subProjects
-
list packages which are known as subprojects.
The generated makefile will enter those and make there as well.
However: they are not forced to be loaded when a package is loaded;
for those, redefine requiredPrerequisites.
description - compilation
-
additionalDefinitions_bc_dot_mak
-
description - contents
-
classNamesAndAttributes
-
lists the classes which are to be included in the project.
Each entry in the list may be: a single class-name (symbol),
or an array-literal consisting of class name and attributes.
Attributes are: #autoload or #<os> where os is one of win32, unix,...
-
extensionMethodNames
-
lists the extension methods which are to be included in the project.
Entries are 2-element array literals, consisting of class-name and selector.
A correponding method with real names must be present in my concrete subclasses
if it has extensions.
description - project information
-
companyName
-
Return a companyname which will appear in <lib>.rc
-
description
-
Return a description string which will appear in nt.def / bc.def
-
legalCopyright
-
Return a copyright string which will appear in <lib>.rc
-
productName
-
Return a product name which will appear in <lib>.rc
|