eXept Software AG Logo

Smalltalk/X Webserver

Documentation of class 'stx_libcompat':

Home

Documentation
www.exept.de
Everywhere
for:
[back]

Class: stx_libcompat


Inheritance:

   Object
   |
   +--ProjectDefinition
      |
      +--LibraryDefinition
         |
         +--stx_libcompat

Package:
stx:libcompat
Category:
* Projects & Packages *
Version:
rev: 1.124 date: 2019/07/28 10:23:24
user: cg
file: stx_libcompat.st directory: libcompat
module: stx stc-classLibrary: libcompat
Author:
cg

Description:


Package documentation

This library contains compatibility classes,
which are useful when loading code from other Smalltalk dialects.

Some of the classes found here are simply empty, but mimic the class hierarchy of
corresponding frameworks in Squeak, VisualWorks, Dolphin or VisualAge Smalltalk dialects.

They usually only allow for an initial fileIn of such imported classes 
(by giving them a superclass to be loaded).
Importing then usually involves further rewrite and debugging - 
especially if the imported code is UI related. 
Non-UI code (model classes) often works out-of-the-box.


[primary maintainer:]
    cg


Class protocol:

description
o  excludedFromPreRequisites
list all packages which should be ignored in the automatic
preRequisites scan. See #preRequisites for more.

o  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.

o  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

description - actions
o  postLoadAction
invoked after loading a project

description - compilation
o  additionalDefinitions_nt_dot_mak

o  stcWarningOptions

description - contents
o  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,...

o  extensionMethodNames
lists the extension methods which are to be included in the project.
Entries are pairwise elements, consisting of class-name and selector.

description - project information
o  companyName
Return a companyname which will appear in <lib>.rc

o  description
Return a description string which will appear in nt.def / bc.def

o  legalCopyright
Return a copyright string which will appear in <lib>.rc

o  productName
Return a product name which will appear in <lib>.rc

description - svn
o  svnRevisionNr
Return a SVN revision number of myself.
This number is updated after a commit



ST/X 7.2.0.0; WebServer 1.670 at bd0aa1f87cdd.unknown:8081; Thu, 18 Apr 2024 13:43:51 GMT