Class: stx_libview

• Inheritance
• Description
• Class protocol
  • description
  • description - compilation
  • description - contents
  • description - project information

Inheritance:

   Object
   |
   +--ProjectDefinition
      |
      +--LibraryDefinition
         |
         +--stx_libview

Package:

stx:libview

Category:

* Projects & Packages *

Version:

rev: 1.112 date: 2023/11/29 09:06:41

user: stefan

file: stx_libview.st directory: libview

module: stx stc-classLibrary: libview

Description:

Package Documentation

This library contains low level interfaces to the underlying graphic system
and representations of windows, fonts, colors, bitmaps etc.

It does not contain medium level widget classes or applications/tools,
but instead provides a device- and operating system independent layer on top of which
GUI frameworks can be built.

It currently supports X11 and Windows-API. 
Native OSX support may be an option if there is sufficient demand for it 
(i.e. someone is willing to pay for its development).


[primary maintainer:]
    cg

copyright
COPYRIGHT (c) Claus Gittinger / 2006 by eXept Software AG
             All Rights Reserved

This software is furnished under a license and may be used
only in accordance with the terms of that license and with the
inclusion of the above copyright notice.   This software may not
be provided or otherwise made available to, or used by, any
other person.  No title to or ownership of the software is
hereby transferred.

Class protocol:

 excludedFromPreRequisites

binaryStoreBytes - sent by XWorkstation >> #selectionBuffer:as:

 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 only built, not forced to be loaded when a package is loaded;
for those, redefine #referencedPrerequisites or #mandatoryPreRequisites.

 additionalBaseAddressDefinition_bc_dot_mak

this is an optional definition, which (if present) may speed up the dll-loading a little
on win32 systems.

 additionalDefinitions_bc_dot_mak

(comment from inherited method)
allows for additional definitions/rules to be added to the bc.mak file.
Subclasses may redefine this.

 additionalDefinitions_make_dot_proto

 additionalRules_bc_dot_mak

(comment from inherited method)
obsolete - kept for compatibility with old project files

 additionalRules_make_dot_proto

(comment from inherited method)
allows for additional rules to be added to the make.proto file.

 localDefines_unix

 localIncludes

 stcOptimizationOptions

 stcWarningOptions

 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.

 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