eXept Software AG Logo

Smalltalk/X Webserver

Documentation of class 'ApplicationModel':

Home

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

Class: ApplicationModel


Inheritance:

   Object
   |
   +--Model
      |
      +--ApplicationModel
         |
         +--AbstractFileApplicationNoteBookComponent
         |
         +--AbstractFileBrowser
         |
         +--AbstractLauncherApplication::PackageLoadDialog
         |
         +--AbstractLoggerSettingsApplication
         |
         +--AbstractSettingsApplication
         |
         +--AbstractSettingsApplication::ToolboxSettingsAppl::ClassToolSetting
         |
         +--ApplicationWithFileHistory
         |
         +--BookmarkBar
         |
         +--BookmarkListEditor
         |
         +--DidYouKnowTipViewer
         |
         +--Dolphin::Shell
         |
         +--EventMonitor
         |
         +--FileBrowserV2SettingsDialog
         |
         +--HTMLDocumentViewerApplication
         |
         +--MemoryMonitor
         |
         +--MultipleItemSelectionWidget
         |
         +--PerforceSourceCodeManagementSettingsAppl::ManagerPerModuleApp
         |
         +--PrintAbortDialog
         |
         +--PrintingDialog
         |
         +--ProcessMonitorV2
         |
         +--SettingsDialog
         |
         +--SimpleDialog
         |
         +--SystemBrowser
         |
         +--ToolApplicationModel
         |
         +--Tools::AbstractTestRunner
         |
         +--Tools::BreakpointBrowser
         |
         +--Tools::Browslet
         |
         +--Tools::BrowsletCanvas
         |
         +--Tools::ChangeSetBrowser2::ChangeEditor
         |
         +--Tools::ChangeSetDiffTool
         |
         +--Tools::InlineMessageDialog
         |
         +--Tools::Inspector2
         |
         +--Tools::LintRuleDetail
         |
         +--Tools::MethodRewriter
         |
         +--Tools::NavigatorModel
         |
         +--Tools::ProjectCheckerBrowser
         |
         +--Tools::SmalltalkDiffTool
         |
         +--Tools::SourceCodeManagerConfigurationTestTool
         |
         +--Tools::SpecialCodeView
         |
         +--Tools::StringSearchTool
         |
         +--Tools::TagsBrowser
         |
         +--Tools::TestRunner2::ResultList
         |
         +--Tools::TextDiffTool
         |
         +--Tools::WebBrowserPage
         |
         +--URITransmissionServiceAppl
         |
         +--URITransmissionServiceAppl::URIDialog
         |
         +--V::ApplicationCoordinator
         |
         +--VersionDiffBrowser

Package:
stx:libview2
Category:
Interface-Framework
Version:
rev: 1.425 date: 2018/05/24 12:51:36
user: cg
file: ApplicationModel.st directory: libview2
module: stx stc-classLibrary: libview2
Author:
Claus Gittinger

Description:


Since many ST-80 classes are subclasses of ApplicationModel, this class
is provided here to allow easier porting of ST-80 code.

It does not (currently) provide all functionality and is NOT
compatible to the corresponding ST80 class; therefore, manual
changes have to be made to get those applications to run under ST/X.
(but at least, this enables you to fileIn that code and have a superclass
 for them)

As time goes by, ST/X applications are going to be converted to
become subclasses of this abstract class - see Launcher for a
first concrete example.


ApplicationModel is prepared to build a view from a windowSpec, as
created by the windowBuilder. If your subclass does not provide such
a spec, you should at least redefine:

    #openInterface   - to create a topview and open it

you may want to redefine:

    #closeRequest    - to catch window closing
    #focusSequence   - to define a sequence for focus-stepping


Once the interfaceBuilder is finished & released, subclasses can
alternatively provide the spec via a #windowSpec method.

The classResources have been put into this class to allow ST/X
applications (which used to be subclasses of StandardSystemView)
to migrate smoothly into ApplicationModels (which is better design ...).


[Instance variables:]
    resources    ResourcePack       language string translation

    builder      WindowBuilder      a builder who knows how to create
                                    a window hierarchy from a specification


Notice: this class was implemented using protocol information
from alpha testers and PD code - it may not be complete or compatible to
the corresponding ST-80 class. If you encounter any incompatibilities,
please forward a note to the ST/X team.


Related information:

    StandardSystemView
    WindowGroup
    DeviceWorkstation

Class protocol:

accessing
o  application

o  applicationName
the name as shown in an about box or in the deployed package.
If there is an application definition in my package, ask that one.
Otherwise, return my name.

active help
o  flyByHelpSpec
obsolete: only provided for backward compatibility.
default is: take the oldStyle help-spec (should be redefined by concrete class).

o  helpSpec
default is: no help-spec (should be redefined by concrete class if help is wanted).

bindings
o  actionFor: aKey
sent by the builder to ask for an actionBlock for
a Button. The argument, aKey comes from an UI-spec
for a buttons #action property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
actionBlocks from a Dictionary or whatever.
Typically, a block is returned there.

o  actionFor: aKey withValue: aValue
sent by the builder to ask for an actionBlock for
a Button which passes a value to the actionMethod.
The argument, aKey comes from an UI-spec
for a buttons #action property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
actionBlocks from a Dictionary or whatever.
Typically, a block is returned there.

o  aspectFor: aKey
sent by the builder to ask for an aspect (a data model).
The argument, aKey comes from an UI-spec
for a components #aspect property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
holders from a Dictionary or whatever.
Typically, a valueHolder is returned there.

o  clientFor: aKey
sent by the builder to ask for an application provided
subcanvas's application.
The argument, aKey comes from an UI-spec
for a subcanvas's #client property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
appModels from a Dictionary or whatever.
Typically, an applicationModel is returned there.

o  colorFor: aSymbol
sent by the builder to ask for an application provided color.
The argument, aKey comes from an UI-spec
for a widgets #*Color property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
holders from a Dictionary or whatever.
Typically, a color is returned there.

o  componentFor: aKey
sent by the builder to ask for an application provided
component.
The argument, aKey comes from an UI-spec
for a viewHolders #view property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
holders from a Dictionary or whatever.
Typically, a view is returned there.

o  fontFor: aSymbol
sent by the builder to ask for an application provided font.
The argument, aKey comes from an UI-spec
for a widgets #*Font property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
holders from a Dictionary or whatever.
Typically, a font is returned there.

o  labelFor: aKey
sent by the builder to ask for an application provided
label for a component.
The argument, aKey comes from an UI-spec
for a components #label property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
labels from a Dictionary or whatever.
Typically, a string is returned there.

o  listFor: aKey
sent by the builder to ask for an application provided
holder for a list.
The argument, aKey comes from an UI-spec
for a listWidgets #list property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
holders from a Dictionary or whatever.
Typically, a list-holding model (SelectionInList) is returned there.

o  menuFor: aKey
sent by the builder to ask for an application provided
holder for a menu.
The argument, aKey comes from an UI-spec
for a widgets #menu property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
holders from a Dictionary or whatever.
Typically, a menu or a menu-holding valueHolder is returned there.

o  specificationFor: aKey
sent by the builder to ask for an application provided
specification for a subcanvas or subspecification.
The argument, aKey comes from an UI-spec
for a subcanvases #specification property (minorKey).
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
interfaceSpecifications from a Dictionary or whatever.
Typically, an interfaceSpecification is returned there.

o  specificationFor: aKey application: app onDevice: deviceOrNil
sent by the builder to ask for an application provided
specification for a subcanvas or subspecification.
The argument, aKey comes from an UI-spec
for a subcanvases #specification property (minorKey).
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
interfaceSpecifications from a Dictionary or whatever.
Typically, an interfaceSpecification is returned there.

o  subApplicationFor: aKey
sent by subCanvas to ask for an application inside itself.
The argument, aKey comes from a TabList-specs majorKey.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
an application from a Dictionary or whatever.
Typically, an ApplicationModel subinstance is returned there.

o  visualFor: aKey
sent by the builder to ask for an application provided
image or element for a label.
The argument, aKey comes from an UI-spec
for a widgets #label property, if LabelIsImage is turned on.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
images from a Dictionary or whatever.
Typically, an image is returned there.

change & update
o  update: something with: aParameter from: changedObject
flush resources on language changes

defaults
o  defaultExtentFor: anApplicationClass
return a default extent for an app-class or nil.
If the user has the corresponding userPreference set,
previous extents are remembered (at close time)
and used as default for the next opening.

o  defaultHttpServerPort
this is only used for web-applications

o  defaultIcon
default is: no icon (should be redefined by concrete class if an icon is wanted).

o  defaultIconForAboutBox
the icon to be shown in my about-this-app dialog

o  defaultServiceLinkName
old web server interface - remove me

** This is an obsolete interface - do not use it (it may vanish in future versions) **

o  labelAt: aKey
default is: no label (could be redefined by concrete class ).

o  labelAt: aKey ifAbsent: aBlock
default is: no label (could be redefined by concrete class ).

o  labelAt: aKey put: aValue
not yet implemented

o  labels
not yet implemented

o  visualAt: aKey
default is: no visual (could be redefined by concrete class ).

o  visualAt: aKey ifAbsent: aBlock
default is: no visual (could be redefined by concrete class ).

o  visualAt: aKey put: aValue
not yet implemented

o  visuals
not yet implemented

font helpers
o  resolveFont: aSelector
resolve the font descriobed by aSelector.
Delegate to a WindowBuilder, whuch may forward to self fontOn:

font specs
o  buttonFont
that is a symbolic font

o  buttonFontBig
that is a symbolic font

o  buttonFontSmall
that is a symbolic font

o  inputFont
that is a symbolic font

o  inputFontSmall
that is a symbolic font

o  labelFont
that is a symbolic font

o  labelFontBig
that is a symbolic font

o  labelFontSmall
that is a symbolic font

o  listFont
that is a symbolic font

o  listFontSmall
that is a symbolic font

o  menuFont
that is a symbolic font

o  textFont
that is a symbolic font

o  textFontBig
that is a symbolic font

o  textFontSmall
that is a symbolic font

help
o  aboutImage
bitmap image or nil for an about box for this application.

o  aboutThisApplicationLabel
label for an about box for this application.

o  aboutThisApplicationText
text for an about box for this application.

o  documentationPath

history
o  forgetDefaultExtentFor: anApplicationClass
forget the remembered last extent for some application class.
This is sent by the UIPainter, when a windowspec is saved,
to bring up the application with its possibly changed default extent

o  forgetRecentlyOpenedApplications

o  recentlyOpenedApplications

o  rememberRecentlyOpenedApplication
support for the launcher's ''open recent...'' menu function.
It is questionable, if dialogs should also be remembered
(although it might be convenient dor developers)

initialization
o  initialize
ApplicationModel initialize

instance creation
o  new
return a new initialized instance

o  onDevice: aDevice
return a new initialized instance, which shall open its interface on aDevice.

private
o  bigFontFor: aFont

o  selfResponsibleFor: aKey

o  smallFontFor: aFont

queries
o  interfaceSpecFor: aSelector
return an interface spec

o  isAbstract
self isAbstract

o  isVisualStartable
return true, if this application can be started via #open.
(to allow start of a change browser via double-click in the browser)

o  shouldRememberLastExtent
to be redefined by concrete applications:
if true is answered, the application's extent is remembered on close
and used as a default when opened the next time

resources
o  classResources
if not already loaded, get the classes resourcePack and return it

o  classResources: aResourcePack
allow setting of the classResources

o  flushAllClassResources
flush all classes resource translations.
Needed after a resource file / language setting has changed.

o  flushClassResources
flush classes resource string translations.
Needed whenever a resource file / language setting has changed

o  resources
return the application's resources -
that's a ResourcePack containing national language strings

o  updateClassResources
update my classResources

startup
o  open
create an instance of the application and open its view.
Sorry, but for visualworks compatibility, the builder is returned,
not the application instance
usage example(s):
     Launcher open

o  openAt: aLocation
create an instance of the application and open its view
at some position.

o  openDialogInterface: anInterfaceSymbol
create an instance of the application and open a view as
specified by anInterfaceSymbol.

o  openDialogInterface: anInterfaceSymbol withBindings: bindings
create an instance of the application and open a view as
specified by anInterfaceSymbol.

o  openDialogInterfaceSpec: anInterfaceSpec
create an instance of the application and open a view as
specified by the given spec.

o  openDialogInterfaceSpec: anInterfaceSpec withBindings: bindings
create an instance of the application and open a view as
specified by the given spec.

o  openDialogSpec: aSpec
create an instance of the application and open a view as
specified by aSpec.

o  openDialogSpec: aSpec withBindings: bindings
create an instance of the application and open a view as
specified by the spec.

o  openInterface: anInterfaceSymbol
create an instance of the application and open a view as
specified by anInterfaceSymbol.

o  openInterface: anInterfaceSymbol at: aPoint
create an instance of the application and open a view as
specified by anInterfaceSymbol.

o  openLauncherOnInitializedDisplayNamed: displayName
Smalltalk secureFileIn:'display.rc'.

o  openModal
create an instance of the application and open its view modal

o  openOn: anApplicationModel
send an open message to the argument, anApplicationModel.
I don't really understand what this method is useful for ...

o  openOnDevice: aDevice
create an instance of the application and open its view
on ANOTHER device.
For more info, read the document on multiple display
support and the documentation of the DeviceWorkstation class.
usage example(s):
     Launcher openOnDevice:Display

o  openOnXScreenNamed: aScreenName
create an instance of the application and open its view
on some X display screen. The argument aScreenName must be
a valid x-display name (i.e. of the form '<host>:<screenNr>' as in 'foo:0').
For more info, read the document on multiple display
support and the documentation of the DeviceWorkstation class.
usage example(s):
     Launcher openOnXScreenNamed:'sgi:0'
     Launcher openOnXScreenNamed:'foo:0'
     NewLauncher openOnXScreenNamed:'dawn:0'
     NewLauncher openOnXScreenNamed:'bitsy:0'
     SystemBrowser openOnXScreenNamed:'dawn:0'
     SystemBrowser openOnXScreenNamed:'bitsy:0'
     SystemBrowser openOnXScreenNamed:'localhost:0'

o  openWithSpec: aSpecSymbol
ST80 compatibility:
mhmh - what is the difference to #openInterface ?

startup-web applications
o  addRequiredForeignServicesTo: anHTTPServer
a hook to allow web apps to register additional services;
typically: file services to deliver bitmaps

o  initialPageSpec
this is only required for web-applications

** This method raises an error - it must be redefined in concrete classes **

o  pageSpec
this is only used for web-applications

o  pageSpecs
this is only required for web-applications

** This method raises an error - it must be redefined in concrete classes **

o  startAsWebService
this is not yet a public interface. For internal exept use only.
Start a web service for myself on the default webService linkURL.
The webService will create new instances of me for incoming sessions.
Answer the webService.
usage example(s):
     self startAsWebService

o  startAsWebService: linkName
this is not yet a public interface. For internal exept use only.
Start a web service for myself on link, an URL.
The webService will create new instances of me for incoming sessions.
Answer the webService.
Start a HTTP server, if not already running
usage example(s):
     self startAsWebService:'hello'
     UBS::UBSUsecase startAsWebService:'uuu'

o  startAsWebService: linkName inServer: httpServer
this is not yet a public interface. For internal exept use only.
Start a web service for myself on the default webService linkURL.
The webService will create new instances of me for incoming sessions.
Answer the webService.
Start a HTTP server, if not already running
usage example(s):
     self startAsWebService:'hello'
     UBS::UBSUsecase startAsWebService:'uuu'

o  startAsWebService: linkName onPort: httpPort
this is not yet a public interface. For internal exept use only.
Start a web service for myself on the default webService linkURL.
The webService will create new instances of me for incoming sessions.
Answer the webService.
Start a HTTP server, if not already running
usage example(s):
     self startAsWebService:'hello'
     UBS::UBSUsecase startAsWebService:'uuu'

o  startAsWebService_old
this is not yet a public interface. For internal exept use only

o  startInPortalService: aPortalServiceOrSession
this is not yet a public interface. For internal exept use only
usage example(s):
     PortalTests::TestApplication1
	startInPortalService:
	    (HTTPPortalService allInstances select:[:s | s httpServer port = 8080]) first

o  webServiceLinkName
the link name, under which instances of myself are found in the httpServer


Instance protocol:

Compatibility-VW
o  mainWindow

accessing
o  application
application knows about interfaceSpecs, menuSpecs etc.
Usually this is my class.
This may be redefined in subclasses

o  builder
return the applications builder; this one has more information
about views, components etc.

o  builder: aBuilder
set the applications builder. Normally, you should not set it
directly, but depend on the default builder, as created when the application
was created.

o  componentAt: name
return a component identified by its name

o  device

o  masterApplication
return the master application, in which I am embedded, or nil, if I am the topmost application.
Useful for embedded sub applications to access outer windows and/or bindings from the master

o  masterApplication: anApplication
set the value of the instance variable 'masterApplication' (automatically generated)

o  resources
return the application's resources -
that's a ResourcePack containing national language strings.
If I have a masterApplication, those resources are returned.

o  resources: aResourcePack
set the application's resources - usually this is done automatically,
except for manually built dialogs

o  topMasterApplication
return the topmost master application. Useful when nested subapplications are used

o  topView
SimpleView compatibility - answer my topWindow

o  window
return my topWindow - or nil, if I have no window (yet)

o  window: aTopView
set my topWindow.
As a side effect, this creates a dummy builder if non has yet
been built. This prevents non-GUI-Painter apps from failing later,
when the builder is accessed.

o  windowGroup
return the applications windowGroup
usage example(s):
"/ So it lost its windowGroup.
usage example(s):
"/ applications may (and do) run in a separate windowGroup
usage example(s):
myWindow windowGroup:wg.

o  windowTitle: aString

binding access
o  actionFor: aKey
sent by the builder to ask for an actionBlock for
a Button. The argument, aKey comes from an UI-spec
for a buttons #action property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
actionBlocks from a Dictionary or whatever.
Typically, a block is returned there.

o  actionFor: aKey withValue: aValue
sent by the builder to ask for an actionBlock for
a Button which passes a value.
The argument, aKey comes from an UI-spec for a buttons #action property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
actionBlocks from a Dictionary or whatever.
Typically, a block is returned there.

o  actionFor: aKey withValue: value1 withValue: value2
sent by the builder to ask for an actionBlock for a Button which passes two values.
The argument, aKey comes from an UI-spec for a buttons #action property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
actionBlocks from a Dictionary or whatever.
Typically, a block is returned there.

o  aspectFor: aKey
sent by the builder to ask for an aspect (a data model).
The argument, aKey comes from an UI-spec
for a components #aspect property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
holders from a Dictionary or whatever.
Typically, a valueHolder is returned there.

o  aspectOrNil: aKey forSubApplication: aSubApp

o  aspectValueFor: aspectKeySymbol
fetch an aspect's value
same as (self aspectFor:aKey) value

o  aspectValueOr: default for: aspectKeySymbol
common helper - fetches the aspect value;
if it is nil, return a default.

o  clientFor: aKey
sent by the builder to ask for an application provided
subcanvas's application.
The argument, aKey comes from an UI-spec
for a subcanvas's #client property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
appModels from a Dictionary or whatever.
Typically, an applicationModel is returned there.

o  colorFor: aKey
sent by the builder to ask for an application provided color.
The argument, aKey comes from an UI-spec
for a widgets #*Color property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
holders from a Dictionary or whatever.
Typically, a color is returned there.

o  componentFor: aKey
sent by the builder to ask for an application provided
component.
The argument, aKey comes from an UI-spec
for a viewHolders #view property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
holders from a Dictionary or whatever.
Typically, a view is returned there.

o  fontFor: aKey
sent by the builder to ask for an application provided font.
The argument, aKey comes from an UI-spec
for a widgets #*Font property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
holders from a Dictionary or whatever.
Typically, a font is returned there.

Use #resolveFont:, if you are not a builder!

o  labelFor: aKey
sent by the builder to ask for an application provided
label for a component.
The argument, aKey comes from an UI-spec
for a components #label property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
labels from a Dictionary or whatever.
Typically, a string is returned there.

o  listFor: aKey
sent by the builder to ask for an application provided
holder for a list (for example, a popUpLists list).
The argument, aKey comes from an UI-spec
for a listWidgets #list property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
holders from a Dictionary or whatever.
Typically, a list-holding model (SelectionInList) is returned there.
If the instance does not provide a value, a corresponding aspect
is asked for. If that fails as well, the app class is asked as a last
chance.

o  menuFor: key
Sent by the builder to ask for an application provided
holder for a menu. The argument, `key`, comes from an UI-spec
for a widgets #menu property.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
holders from a Dictionary or whatever.
Typically, a menu or a menu-holding valueHolder is returned there.

o  specificationFor: aKey
sent by the builder to ask for an application provided
specification for a subcanvas or subspecification.
The argument, aKey comes from an UI-spec
for a subcanvases #specification property (minorKey).
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
interfaceSpecifications from a Dictionary or whatever.
Typically, an interfaceSpecification is returned there.

o  subApplicationFor: aKey
sent by subCanvas to ask for an application inside itself.
The argument, aKey comes from a TabList-specs majorKey.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
an application from a Dictionary or whatever.
Typically, an ApplicationModel subinstance is returned there.

o  visualFor: aKey
sent by the builder to ask for an application provided
image or element for a label.
The argument, aKey comes from an UI-spec
for a widgets #label property, if LabelIsImage is turned on.
Here, a corresponding message is sent to myself,
which ought to be defined in the application subclass.
Alternatively, a subclass may redefine this method, to provide
images from a Dictionary or whatever.
Typically, an image is returned there.

building
o  allButOpen
create my views from the windowSpec, but do not open the main window.

o  allButOpenFrom: aSpec
create my views but do not open the main window.
The argument is a spec which defines the interface.

o  allButOpenInterface: aSymbol
create my views but do not open the main window.
The argument specifies a selector of a method,
which when sent to myself should return a spec.
Notice, this returns the windowBuilder.

o  buildSpec: specToBuild asSubCanvasWithBuilder: aBuilder
build a subcanvases spec into aSubcanvas

o  buildSubCanvas: spec withBuilder: aBuilder
build a subcanvases' spec into aSubcanvas

o  buildSubCanvas: spec withMenu: withMenuBoolean withBuilder: aBuilder
build a subcanvases' spec into aSubcanvas

component manipulations
o  components: aSymbolOrArray do: aBlock
evaluate aBlock for all components listed aSymbolOrArray.

o  disable: aSymbolOrArray
disable the components whose id's are aSymbolOrArray.

o  enable: aSymbolOrArray
enables the component(s) identified by aSymbolOrArray.

o  invalidate: aSymbolOrArray
invalidates the component(s) identified by aSymbolOrArray.

o  makeInvisible: aSymbolOrArray
makes the components whose id's are aSymbolOrArray invisible

o  makeReadOnly: aSymbolOrArray
make all components identified by aSymbolOrArray read only
(for editText components).

o  makeVisible: aSymbolOrArray
makes the components whose id's are aSymbolOrArray visible

o  makeWritable: aSymbolOrArray
make all components identified by aSymbolOrArray writable
(for editText components).

copying
o  postCopy
(comment from inherited method)
release dependents after copying

o  postDeepCopy
(comment from inherited method)
allows for cleanup after deep copying.
To be redefined in subclasses.

debugging
o  inspectorExtraAttributes
( an extension from the stx:libtool package )

delayed actions (enqueue)
o  delayedUpdate: something with: aParameter from: changedObject
support for delayed updates -
subclasses which invoke #enqueueDelayedUpdate:with:from: (from #update:with:from:)
must also redefine this method, and perform the actual update there.

o  enqueueDelayedAction: aBlock
This will enqueue a delayed action - the application-process will
eventually execute aBlock.
Useful for synchronization

o  enqueueDelayedUpdate: something with: aParameter from: changedObject
support for delayed updates - to be invoked from a concrete classes
#update:with:from: method.
This will enqueue a delayed update, and resend #delayedUpdate:with:from:
whenever the receiver is handling events.
Especially useful, if many updates arrive at high frequency, to avoid
multiple redraws.

o  enqueueMessage: selector
enqueue a message without arguments to be sent to myself later,
when my process is back in its eventLoop. Also, filter duplicates.
This is useful, to buffer redraws and avoid flicker due to multiple
redraws (especially in browsers, when reacting on changeMessages resulting
from changes made in other browsers)

o  enqueueMessage: selector argument: arg
enqueue a message without arguments to be sent to myself later,
when my process is back in its eventLoop. Also, filter duplicates.
This is useful, to buffer redraws and avoid flicker due to multiple
redraws (especially in browsers, when reacting on changeMessages resulting
from changes made in other browsers)

o  enqueueMessage: selector arguments: argumentArray
enqueue a message to be sent to myself later,
when my process is back in its eventLoop. Also, filter duplicates.
This is useful, to buffer redraws and avoid flicker due to multiple
redraws (especially in browsers, when reacting on changeMessages resulting
from changes made in other browsers)

o  enqueueMessage: selector for: someone
enqueue a message without arguments to be sent to someone later,
when my process is back in its eventLoop. Also, filter duplicates.
This is useful, to buffer redraws and avoid flicker due to multiple
redraws (especially in browsers, when reacting on changeMessages resulting
from changes made in other browsers)

o  enqueueMessage: selector for: someone argument: arg
enqueue a message without arguments to be sent to someone later,
when my process is back in its eventLoop. Also, filter duplicates.
This is useful, to buffer redraws and avoid flicker due to multiple
redraws (especially in browsers, when reacting on changeMessages resulting
from changes made in other browsers)

o  enqueueMessage: selector for: someone arguments: argList
enqueue a message to be sent to someone later, when my process
is back in its eventLoop. Also, filter duplicates.
This is useful, to buffer redraws and avoid flicker due to multiple
redraws (especially in browsers, when reacting on changeMessages resulting
from changes made in other browsers)

o  enqueueMessage: selector with: argument
enqueue a message with one argument to be sent to myself later,
when my process is back in its eventLoop. Also, filter duplicates.
This is useful, to buffer redraws and avoid flicker due to multiple
redraws (especially in browsers, when reacting on changeMessages resulting
from changes made in other browsers)

o  enqueueMessage: selector with: argument1 with: argument2
enqueue a message with one argument to be sent to myself later,
when my process is back in its eventLoop. Also, filter duplicates.
This is useful, to buffer redraws and avoid flicker due to multiple
redraws (especially in browsers, when reacting on changeMessages resulting
from changes made in other browsers)

drag & drop
o  canDropObjects: aCollectionOfDropObjects
drop manager asked if a drop is possible
- should be redefined by apps which can do it, to return true

o  canDropObjects: aCollectionOfDropObjects in: aComponent
drop manager asked if a drop is possible
- should be redefined by apps which can do it, to return true

o  canDropObjects: aCollectionOfDropObjects in: aComponent at: position
drop manager asked if a drop is possible.
Should be redefined by apps which can do it, to return true

o  dropObjects: aCollectionOfDropObjects
drop manager wants to drop.
This is ony sent, if #canDrop: returned true.
Must be redefined in order for drop to work.

** This method raises an error - it must be redefined in concrete classes **

o  dropObjects: aCollectionOfDropObjects in: aComponent
drop manager wants to drop.
This is ony sent, if #canDrop: returned true.
Must be redefine in order for drop to work.

o  dropObjects: aCollectionOfDropObjects in: aComponent at: aPoint
drop manager wants to drop.
This is ony sent, if #canDrop:in: returned true.
Can be redefined in apps which return true to #canDrop.

o  droppedFile: aFilename in: aComponent
ignored here - only sent by textView components, sometimes

easy bindings
o  registerInterestIn: aValueModel using: aSelectorOrArray
Register interest in a change in aValueModel using information in aSelectorOrArray.
aSelectorOrArray can be one of three things:

1) nil in which case no interest is registered
2) a selector in which case the receiver is understood to be self
3) an Array in which case the size is two where the first element is the
message to be sent and the second element is the receiver.

o  valueHolderFor: aSelector initialValue: anObject
Return a ValueHolder on anObject.

o  valueHolderFor: aSelector initialValue: anObject changeMessage: aSelectorOrArrayOrNil
Return a ValueHolder on anObject. aSelectorOrArrayOrNil is the change information
for the ValueHolder. This argument is either a Symbol or an Array of two elements.
If it is a Symbol, then it is the change message and the interested object is understood
to be the receiver. If it is an Array, then the first element is the change message and
the second element is the interested object.

forced actions
o  doAcceptByReturnKey

o  doCancelByEscapeKey

help
o  aboutImage
bitmap image or nil for an about box for this application.

o  aboutThisApplicationLabel
label for an about box for this application.

o  aboutThisApplicationText
text for an about box for this application.

o  activeHelpViewFor: text onDevice: aDevice
redefinable to allow for applications to provide their own active help
(aka tooltip) bubble window

o  flyByHelpDependsOnPositionIn: aView
subclasses where the help-text depends upon the pointer position might
want to redefine this

o  openAboutThisApplication
opens an about box for this application.
Can be specialized by redefining #aboutThisApplicationText
and #aboutThisApplicationLabel

o  openHelpViewOnFile: pathToHelpText
open a help viewer (as opened by the help buttons).
The argument is a relative path within the help directory
(but a file under the current directory is tried first)

o  showActiveHelp: aHelpText for: view
This is invoked from the activeHelp event listener, to display some popup-help
for a component. If false is returned, the help manager will pop up
some active help bubble; if true is returned, it will assume that the
help text has been already displayed and will not do any further actions.
Here, we accept the help text, and push an event into out own input
queue, so that the help text will be displayed asynchronously by myself,
vis the #showHelp:for: method.
This can be redefined in concrete classes to handle active help differently.

o  showHelp: aHelpText for: view
actual method which is supposed to display the help text.
Should be redefined in concrete classes, to put the help text
into some info label, or the windows title bar.
Here, the help text is ignored.

o  showingHelp
return true, if the activeHelp manager should invoke my #showHelp:for:
method, when the mouse pointer is moved over my widgets.
The default here is true, however, the #showHelp:for: methods are empty.
These should be redefined to put the help text into some info label,
or into the view's title bar.
You may also redefine the showingHelp/showingHelp: methods, to
remember the flag setting.

help texts
o  basicHelpTextForKey: aKey
flyByHelp interface: return some short help text for a key.
key is the symbol associated with some widget or menu item.
Return the original (english) text as written in the helpSpec;
needs to be translated as per language

o  helpSpec
activeHelp interface: return some short help text for a widget component

o  helpTextFor: aComponent
activeHelp interface: return some help text for a widget component

o  helpTextFor: aComponent at: aPoint
if not redefined by subclass, fall back to general method

o  helpTextForKey: aKey
flyByHelp interface: return some short help text for a key
key is the symbol associated with some widget or menu item.
(from my helpSpec); return a language variant (if available)

o  helpTextForKey: aKey row: aRowNr
Special interface for DataSet - get the active help text for a specific row

hooks
o  aboutToOpen: whichTopView
the topView is about to be opened.
This is sent by whichTopView, right before its really open
(i.e. finally visible)

o  commonPostBuild
a common hook for postBuildWith: and postBuildAsSubcanvasWith:.

o  commonPostOpen
a common hook for postOpenWith:, postOpenAsSubcanvasWith: and postOpenAsDialogWith:.
Notice: redefined methods should do a super send.
otherwise resources might be undefined.

o  commonPreBuild
a common hook for preBuildWith:, preBuildAsSubcanvasWith: and preBuildAsDialogWith:.

o  commonPreOpen
A common hook for preOpenWith:, preOpenAsSubcanvasWith: and preOpenAsDialogWith:.

o  postApplicationProcessCreate: newProcess windowGroup: newGroup
this is sent whenever a new application is launched from this app,
which forks its own windowGroup process. Allows for process group management,
or process-global exception handlers to be installed.
Nothing done here - to be redefined in concrete applications

o  postBuildAsSubcanvasWith: aBuilder
this is sent after an interface is built from a spec as subcanvas,
and the appModel is the same as the topWindow's application.
Can be redefined in subclasses for additional setup after
the subcanvas' view has been built, but not yet opened.

o  postBuildDialogWith: aBuilder
this is sent after an interface is built from a spec as dialog with me
as a source (for aspects) i.e. via openDialogInterface:.
Can be redefined in subclasses for additional setup after
the dialog's view has been built, but not yet opened.

o  postBuildWith: aBuilder
this is sent after an interface is built from a spec,
but only iff the appModel is not the same as the topView's app
(i.e. if it is not a build for the same appModel again).
In that case, postBuildAsSubcanvasWith is invoked.
Can be redefined in subclasses for additional setup after
the view has been built, but not yet opened.

o  postOpenAsSubcanvasWith: aBuilder
this is sent after the application's window is opened inside another application.
Can be redefined in subclasses for actions after showing the canvas view.

o  postOpenDialogWith: aBuilder
this is sent after the applicationÄs window is opened as a dialog with me
as a source (for aspects) i.e. via openDialogInterface:.
Can be redefined in subclasses for actions after opening a dialog view.

o  postOpenWith: aBuilder
this is sent after the application's main window is opened.
Can be redefined in subclasses for actions after opening the view.

o  preBuildAsSubcanvasWith: aBuilder
this is sent before an interface is built from a spec as a subcanvas,
and the appModel is the same as the topWindow's application.
Can be redefined for apps which need to be informed about that.

o  preBuildDialogWith: aBuilder
this is sent before an interface is built from a spec as a dialog with me
as a source (for aspects) i.e. via openDialogInterface:.
Can be redefined for apps which need to be informed about that.

o  preBuildWith: aBuilder
this is sent before an interface is built from a spec,
but only iff the appModel is not the same as the topView's app
(i.e. if it is not a build for the same appModel again).
In that case, preBuildAsSubcanvasWith is invoked.
Can be redefined in subclasses.

o  preOpenAsSubcanvasWith: aBuilder
this is sent before the applications window is opened inside another application.
Can be redefined in subclasses for actions after showing the canvas view.

o  preOpenDialogWith: aBuilder
this is sent after the applications window is opened as a dialog with me
as a source (for aspects) i.e. via openDialogInterface:.
Can be redefined in subclasses for actions after opening a dialog view.

o  preOpenWith: aBuilder
this is sent before the applications main window is opened.
Can be redefined in subclasses for actions right before opening the view.

initialization
o  addTopViewsToCurrentProject
add all of my topViews to the current projects list of views.
This allows hiding views on a per-project basis.
Applications which do not want to be switched with projects
(such as the Launcher), may redefine this to a noop.

o  basicInitialize
initialize the application.
Since ST-80 applications seem commonly to redefine #initialize
without doing a super initialize, the real initialization is
done here ...

o  initialize
nothing done here;
but can be redefined in concrete applications

o  initializeDevice

o  initializeResources
initialize the applications resources (NLS support).

o  initializeScreenDevice

o  setDevice: aDevice
set the device (i.e. some Screen), where the application shall open its view(s).
The default device (if not set here) will be the current screen.

opening
o  hideWindows

o  open
open a standard interface.
Sorry, but for visualworks compatibility, the builder is returned,
not the receiver.

o  openAndWaitUntilVisible
open a standard interface, and wait until my window is visible

o  openAs: windowType
open a standard interface as slave, partner, dialog, popUp, undecorated etc.
Sorry, but for visualworks compatibility, the builder is returned

o  openAsSlave
open a standard interface as slave.
Notice: there is still a need to make the current window a master
(see code and comments in WindowBuilder >> openAt:withExtent:andType:)
usage example(s):
     WorkspaceApplication new openAsSlave.

o  openAt: aPoint
open a standard interface at some point

o  openAtPointer
open a standard interface at the current pointer position.
Sorry, but for visualworks compatibility, the builder is returned

o  openInterface
open a standard interface.

Subclasses which do not have an interfaceSpec
should redefine this method and create & open their view(s) there.
(see Launcher as an example).

Sorry, but for visualworks compatibility, the builder is returned

o  openInterface: aSymbol
open a specific interface.

The argument, aSymbol specifies which interface. The concrete
application subclass must provide a method with that name,
which must return an interfaceSpec.
This is forwarded to the builder to create the views.
Typically, applications only use one interface, returned by the #windowSpec method.

Sorry, but for visualworks compatibility, the builder is returned

o  openInterface: aSymbol as: windowType
open a specific interface in a special mode.

The argument, aSymbol specifies which interface.
The concrete application subclass must provide a method with that name,
which must return an interfaceSpec. This is forwarded to the builder to create the views.
Typically, applications only use one interface, returned by the #windowSpec method.
The windowType can be any of #slave, #partner, #dialog, #popUp etc.

Sorry, but for visualworks compatibility, the builder is returned

o  openInterface: aSymbol at: aLocation
open a specific interface at a location in default mode.

The argument, aSymbol specifies which interface. The concrete
application subclass must provide a method with that name,
which must return an interfaceSpec. This is forwarded to
the builder to create the views.
Typically, applications only use one interface,
returned by the #windowSpec method.

o  openInterfaceAs: windowType
open a standard interface in a special mode.

The windowType can be any of #slave, #partner, #dialog, #popUp, #undecorated etc.

o  openInterfaceAt: aLocation
open a standard interface.

o  openInterfaceModal
open a standard interface as a modal dialog.
Sorry, but for visualworks compatibility, the builder is returned

o  openInterfaceModal: aSymbol
open a specific interface as a modal dialog.
The argument, aSymbol specifies which interface. The concrete
application subclass must provide a method with that name,
which must return an interfaceSpec. This is forwarded to
the builder to create the views.
Typically, applications only use one interface,
returned by the #windowSpec method.

o  openInterfaceModal: aSymbol at: location
open a specific interface modal at some screen location.
The argument, aSymbol specifies which interface. The concrete
application subclass must provide a method with that name,
which must return an interfaceSpec. This is forwarded to
the builder to create the views.
Typically, applications only use one interface,
returned by the #windowSpec method.

o  openModal
open a standard interface as a modal dialog

o  openModalAtPointer
open a standard interface modal at the current pointer position.
Sorry, but for visualworks compatibility, the builder is returned

o  openOnDevice: aDevice
open a standard interface on some other device

o  openSpec: anInterfaceSpec
open a view as specified in anInterfaceSpec.

o  openSpec: anInterfaceSpec withBindings: bindings
open a view as specified in anInterfaceSpec.

o  openSpec: anInterfaceSpec withBindings: bindings modal: modal
open a view as specified in anInterfaceSpec.

o  openSpecModal: anInterfaceSpec
open an interface spec modal

o  openWindow
open the window
- assumes that the builder has already setup the interface.
usage example(s):
openWindow.

o  openWindowAs: windowType
open the window - assumes that the builder has already setup the interface.
The windowType can be any of #slave, #partner, #dialog, #popUp etc.

o  openWindowAs: windowType at: originOrNil
open the window - assumes that the builder has already setup the interface.
The windowType can be any of #slave, #partner, #dialog, #popUp etc.

o  openWindowAt: aPoint
open the window
- assumes that the builder has already setup the interface.

o  openWindowAtCenter
open the window centered on the screen
- assumes that the builder has already setup the interface.

o  openWindowModal
open the window as a modal dialog
- assumes that the builder has already setup the interface.

o  openWindowModalAt: aLocation
open the window as a modal dialog
- assumes that the builder has already setup the interface.

o  openWithExtent: extPoint
open a standard interface with given extent

o  opened: whichTopView
the topView has been opened.
This is sent by whichTopView, when its really open
(i.e. finally visible)

o  showWindows

o  unhideWindows

opening-dialogs
o  openDialog
open my window as a modal dialog
- assumes that the builder has already setup the interface.

o  openDialogAt: aPoint
open my window as a modal dialog
- assumes that the builder has already setup the interface.

o  openDialogAtPointer
open my window as a modal dialog
- assumes that the builder has already setup the interface.

o  openDialogInterface: aSelector
open a dialog

o  openDialogInterface: aSelector withBindings: bindings
open a dialog, given a spec-selector

o  openDialogInterfaceSpec: aSpec withBindings: bindings
open a dialog, given a spec

o  openDialogModeless
open my window as a modal dialog
- assumes that the builder has already setup the interface.

o  openDialogSpec: aSpec withBindings: bindings
open a dialog

o  openDialogSpecModeless: aSpec withBindings: bindings
open a dialog, but without blocking the caller

opening-webInterface
o  addToService

o  createWebBuilder
create a Web-UIBuilder if not already present

o  defaultPageSpecName

o  defineInterface
define a standard interface.

Subclasses which do not have an interfaceSpec
should redefine this method and create their page there.

o  defineInterface: aSpecSymbol
define an interface.

o  defineInterfaceFrom: aSpec
define an interface (setup a page), given a spec.

o  httpServerPort
on which port will a HTTP server be started

o  initializeAsWebServiceOnWebDevice: webDevice

o  initializeWebServiceDevice
no real device here; instead, we need a web service in which I register.
The device is a dummy one, to make the protocol transparent & compatible

o  pageSpecs

o  service

o  service: something

o  serviceLinkName

o  startAsWebService
self new startInWebService

o  startInPortalService: aPortalServiceOrSession

o  webBuilderClass
return the UIBuilder class for me.
This method can be redefined if (eventually) there are
spec readers for other UI languages (motif UIL ?)

o  webLink
if nil is returned, I will install my page(s) right under the serviceLink (i.e. /portal/nn).
Otherwise, they will be under (i.e. /portal/link/nn)

o  webLink: something

private
o  builderClass
return the UIBuilder class for me.
This method can be redefined if (eventually) there are
spec readers for other UI languages (motif UIL ?)

o  createBuilder
create a WindowBuilder if not already present

queries
o  defaultWindowExtent
return my default window extent or nil.
Return nil if the defaul extent should be computed by other means.

The code here asks for the last extent of an instance of this class.

o  defaultWindowSpecName

o  defaultWindowType
Applications come up non-modal, by default

o  graphicsDevice
return the device I want to open my views on.
The default (if not created with #onDevice:) is the currently
active screen.

o  interfaceSpecFor: aSelectorOrSpec
return an interface spec.
Here, the query is forwarded to my class.
Can be refefined in subclasses which want to provide per-instance specs.

o  isOpen
answer true if the application's window is open

o  isShown
answer true if the application's window is shown

o  isWebService

o  processName
return a name to be shown for me in the process monitor

o  resolveClassNamed: something inClass: aClass
return the class from something, a class, symbol, string or nil.
first we are looking in the namespace of the application, then in the
current namespace and finally in Smalltalk

o  resolveFont: something
resolve the font. Delegate to windowBuilder

o  resolveName: something
return the class from something, a class, symbol, string or nil.
first we are looking in the namespace of the application, then in the
current namespace and finally in Smalltalk

o  resolveName: something inClass: aClass
return the class from something, a class, symbol, string or nil.
first we are looking in the namespace of the application,
then in the current namespace and finally in Smalltalk

o  selfResponsibleFor: aKey
internal: return true, if I am to provide a value for some aspect.

** This is an obsolete interface - do not use it (it may vanish in future versions) **

o  shouldRememberLastExtent
to be redefined by concrete applications:
if true is answered, the application's extent is remembered on close
and used as a default when opened the next time

o  topApplication
return the top-master application

startup & release
o  applicationWindowClass
return the class used for my (top-) windows

o  close
this is sent by my topView when about to be closed
by the program (not by the windowManager).
Notice, that we get a closeRequest message if closed by the windowManager,
which can be rejected by the app (or confirmed via a dialog)
Could be redefined in subclasses.

o  closeDownViews
close down the application's view(s)

o  closeRequest
this is sent by my topView when about to be closed by the windowManager.
Could be redefined in subclasses to suppress close or confirm.
usage example(s):
a closeRequest (although, it is supposed to

o  closeRequestFor: aTopView
this is sent by any of my topViews when about to be closed by the
windowmanager. For backward compatibility with single-view applications,
this is forwarded here to a simple (non topView-specific) closeRequest,
effectively closing all of my views.
MultiView applications should redefine this method if closing of individual
views closing is to be caught and/or should not close all of them.

o  doAccept
this is invoked by the Return-Key (if returnIsOK) or
the ok-button (if any), IFF the application has been
opened modal (i.e. as a dialog).

o  doCancel
this is invoked by the Escape-Key (if escapeIsCancel) or
the cancel-button (if any), IFF the application has been
opened modal (i.e. as a dialog).

o  releaseAsSubCanvas
a subcanvas is closed or switching to a new application.
Can be redefined to perform a self release in this case.

o  rememberLastExtent
remember my current extent for the next open

o  restarted
sent by my topWindow, when restarted from an image.
Nothing done here, but can be redefined to perform any actions
required to reset the application after an image-restart.
(for example: check if application files are still around, restart
subprocesses etc.).

o  saveAndTerminateRequest
some windowManagers send this to shut down an application
and have it save its state for restart.
Can be redefined in subclasses

o  saveAndTerminateRequestFor: aTopView
some windowManagers send this to shut down an application
and have it save its state for restart.
Can be redefined in subclasses

testing
o  isApplicationModel

translating
o  translateString: aString
translate aString to the current language.
We use the resources as default.
Subclasses may redefine this to use another mechanism

o  translateString: aString with: anArgument
translate aString to the current language.
We use the resources as default.
Subclasses may redefine this to use another mechanism

user interaction & notifications
o  beep
output an audible beep or bell on my screen device

o  beepInEditor
output an audible beep or bell on my screen device.

beep to wakeup the user after some error/not found condition in an editor.
Use this ONLY to beep in response to a bad user operation (not system failure beeps).
Can be disabled via the settings if too annoying

o  information: aString
like Object's information, but translates the string via the
resourcePack, thus giving a translated string automatically

o  informationTranslated: aString
like Object's information, but translates the string via the
resourcePack, thus giving a translated string automatically

o  informationTranslated: aString with: anArgument
like Object's information, but translates the string via the
resourcePack, thus giving a translated string automatically

o  notify: aString
like Object's notify, but translates the string via the
resourcePack, thus giving a translated string automatically

o  openDocumentationFile: aFilename

o  restoreCursors
restore the original cursors in all of my views

o  showCursor: aCursor
set all of my views cursor to aCursor.
It can be restored with #restoreCursor.

o  warn: aString
like Object's warn, but translates the string via the
resourcePack, thus giving a translated string automatically

o  warn: aString translate: aBoolean
like Object's warn, but optionally translates the string via the
resourcePack, thus giving a translated string automatically

o  warn: aString with: arg
like Object's warn, but translates the string via the
resourcePack, thus giving a translated string automatically

o  warn: aString with: arg1 with: arg2
like Object's warn, but translates the string via the
resourcePack, thus giving a translated string automatically

o  warn: aString with: arg1 with: arg2 with: arg3
like Object's warn, but translates the string via the
resourcePack, thus giving a translated string automatically

o  warn: aString with: arg1 with: arg2 with: arg3 with: arg4
like Object's warn, but translates the string via the
resourcePack, thus giving a translated string automatically

o  warn: aString withArguments: argArray
like Object's warn, but translates the string via the
resourcePack, thus giving a translated string automatically.
Also translates \'s to newLine.

o  withCursor: aCursor do: aBlock
evaluate aBlock, showing aCursor in my topView and all of its subviews.
Return the value of aBlock.

o  withExecuteCursorDo: aBlock
evaluate aBlock, showing an executeCursor in my topView and all of its subviews.
Return the value of aBlock.

o  withReadCursorDo: aBlock
evaluate aBlock, showing a readCursor in my topView and all of its subviews.
Return the value of aBlock.

o  withVisibleCursor: aCursor do: aBlock
evaluate aBlock, showing a waitCursor in my topView and all of its subviews.
Return the value of aBlock.
Ensure, that the cursor is visible by the user for a minimal amount of time.

o  withWaitCursorDo: aBlock
evaluate aBlock, showing a waitCursor in my topView and all of its subviews.
Return the value of aBlock.

o  withWaitCursorVisibleDo: aBlock
evaluate aBlock, showing a waitCursor in my topView and all of its subviews.
Return the value of aBlock.
Guarantee, that the cursor is visible by the user for a minimal amount of time.

o  withWriteCursorDo: aBlock
evaluate aBlock, showing a writeCursor in my topView and all of its subviews.
Return the value of aBlock.

window events
o  clientMessage: msgType format: msgFormat eventData: msgData
a client message - very X-Window specific and only useful for special applications.
Subclasses prepared to receive them should redefine this method

o  copyDataEvent: parameter eventData: msgData
a client message - very Win32 specific and only useful for special applications.
Subclasses prepared to receive them should redefine this method

o  delayedAutoRaiseEventFor: oneOfMyViews
called with a delay by the focusIn code, iff the userPref setting is active.
Some (a small number only) may want to prevent autoraise in certain situations
- for example, if one view is controlling another.
These get a chance to redefine this method

o  dispatchEvent: event
dispatch a user-pushed event.
This allows for events for an appModel to be pushed into the event queue
the same way as events for a view are pushable.

o  dispatchEvent: evType arguments: evArgs withFocusOn: focusView delegate: doDelegate
dispatch a user-pushed event.
This allows for events for an appModel to be pushed into the event queue
the same way as events for a view are pushable.

o  dispatchEvent: ev type: evType arguments: evArgs withFocusOn: focusView delegate: doDelegate
dispatch a user-pushed event.
This allows for events for an appModel to be pushed into the event queue
the same way as events for a view are pushable.

o  dispatchEvent: event withFocusOn: focusViewOrNil
dispatch a user-pushed event.
This allows for events for an appModel to be pushed into the event queue
the same way as events for a view are pushable.

o  dispatchEvent: event withFocusOn: focusViewOrNil delegate: doDelegate
dispatch a user-pushed event.
This allows for events for an appModel to be pushed into the event queue
the same way as events for a view are pushable.

o  noticeOfWindowClose: aWindow
sent when a topView or applicationSubView has been closed.
Can be redefined in subclasses for cleanup.

o  noticeOfWindowOpen: aWindow
sent when a topView or applicationSubView has been opened.
Can be redefined in subclasses.

o  processApplicationCommand: command with: argument
a message from a secondary application instance (the exe has been started again).
Typically, the command is one like 'openPath:', as generated in StandaloneStartup.

o  processOpenPathCommand: argument
a message from a secondary application instance (the exe has been started again)
to open another window on document as found in the pathName argument.
Left blank (i.e. ignored) here, but can be redefined to open up another application
editor window if supported.

o  processShortcut: aKeyEvent
a shortcut key event as forwarded from the keyboardProcessor - if there is the
shortcut key defined, process the shortcut and return true - otherwise false.

o  requestForWindowClose
the applicationWindow wants to know, if a close
is ok. Return false if not.

o  showActivity: someMessage
some activityNotification shalt be communicated to
the user. Forwarded from the topView and ignored here.
Can be redefined in concrete applications to show the
message either in some infoView (infoLabel as in Windows)
or in the title area (as done in the browsers)

o  windowEvent: anEvent from: anApplicationWindow
dummy: windowEvent forwarding is not yet implemented



ST/X 7.1.0.0; WebServer 1.663 at exept.de:8081; Wed, 12 Dec 2018 21:23:54 GMT