Names of design patterns appear in small capitals: e.g., ADAPTER. Page numbers in bold indicate the definition
of a term. Numbers in italics indicate a diagram for the term.
Letters after a diagram's page number indicate the kind of diagram:
a "c" denotes a class diagram, an "i" denotes an interaction diagram,
and an "o" denotes an object diagram. For example, 88co
means that a class and object diagram appears on page 88.
F
- FACADE
185
- compared with MEDIATOR
193,
282
- in catalog summary
8
- use in Choices
192
- Facade
- participant of FACADE185c,
187,
187c
- facade
185
- FACTORY METHOD
107
- in catalog summary
8
- language-specific variants
112
- parameterized with product identifier
110
- used to implement ABSTRACT
FACTORY
90,
91,
110
- used to create an iterator
258
- FileStream
183,
183c
- FLYWEIGHT
195
- combined with COMPOSITE167,
200
- combined with INTERPRETER247
- combined with STATE
308
- in catalog summary
9
- Lexi's use of
39
- participant of FLYWEIGHT198,
198co
- flyweight
196,
196o
- managing shared
200
- FlyweightFactory
204
- participant of FLYWEIGHT198co,
199
- FontDialogDirector
274,
274o,
275ci
- Foote, Brian
353
- forwarding requests
229
- framework
26,
360
- compared with design patterns
28
- documenting with patterns
27
- graphical editor
117
- see Bedrock
- see Choices
- see ET++
- see HotDraw
- see MacApp
- see NEXTSTEP
- see NeXT AppKit
- see RApp
- see RTL Smalltalk compiler
- see Unidraw
- trade-offs associated with
27
- Fresco
344
- friend class
360
- used to grant Iterator privileged access to
collection
262
- used to support Memento287
- functor
242
- future cash flow
323