| Prev | Next | Start of Chapter | End of Chapter | Contents | Glossary | Index | Comments | (14 out of 23)

M

master dialogs
master KBs
using for parallel development
memory
detecting and preventing overload
guidelines for using
leaks
minimizing by
hiding attribute displays
hiding name boxes
minimizing non-functional items
selecting efficient data structures
minimizing use of
preventing leaks by
avoiding random name generation
creating and deleting objects
memory meters
menu entries
menu specifications
menus
creating, using GMS
messages
avoiding using error
declaring as superior class of objects
localizing
subclassing
meters
method hierarchies
methods
See also attributes
benchmarking results for
comparing with procedures
conventions for
coding
indentation
naming
creating
describing object behaviors, using
documenting protocols of
guidelines for using
hierarchies
implementing optional procedure arguments, using
inheriting, using multiple inheritance
initiating processing for
keeping together with class definitions
object-oriented design technique
overriding inherited
subclassing
Microsoft
COM
Dynamic Data Exchange (DDE)
middleware
communicating, using
See also distributed object standards
mission-critical applications
modular knowledge bases
definition of
modularization
See also modules and module prefixes
benefits of
designing reusable modules
encapsulating modules
introduction to
managing multi-module applications
organizing workspaces
selecting module scope
software development standard
using standard G2 utilities
module hierarchy
definition of
module prefixes
benefits of
costs of
using
modules
architectures
four-layer
four-layer, two-module
communications handling in
conflicts
class-qualified attributes
preventing
user mode
creating
APIs for
GUIs for
definition of
dependent
designing reusable
determining how data is used in
encapsulating
using proprietary restrictions
using public and private naming conventions
using user modes
error handling in
functional
guidelines for creating
hiding violations of modularity in
independent
inheriting across
attributes
rules
subclasses
user menu choices
initializing
limiting
dependencies between
scope of
localizing
managing multiple
organizing
functionally
structurally
workspaces in
prefixes for
referencing private knowledge across
release manager
restricting references between
rules of modularity
saving
separating
GUI from core
into layers
settings for
structural
supporting testing
by organizing
by using proven
verifying modularity of
version control for
multiple inheritance
effects of
guidelines for using
linearizing class hierarchy
using
multi-threaded processing
See also single-threaded processing
allowing communications between processes
examples of
implementing
using procedures
using rules
maintaining atomicity, using
| Prev | Next | Start of Chapter | End of Chapter | Contents | Glossary | Index | Comments | (14 out of 23)

Copyright © 1997 Gensym Corporation, Inc.