- Page 1 and 2: Smalltalk and Object Orientation: A
- Page 3 and 4: Chapter 7: Smalltalk Constructs Thi
- Page 5 and 6: The user interface construction fac
- Page 7 and 8: Preface 1. INTRODUCTION TO OBJECT O
- Page 9 and 10: 12.5 A CLASS SIDE METHOD...........
- Page 11 and 12: 27.3 VISUALWORKS WINDOW PAINTING TO
- Page 13: Part One Introduction to Object Ori
- Page 16 and 17: interfaces between different parts
- Page 18 and 19: een to ease the transition from one
- Page 20 and 21: encapsulation. Attempting to introd
- Page 22 and 23: is a controversial subject which is
- Page 24 and 25: will become second nature to many o
- Page 26 and 27: or return something. It has since b
- Page 28 and 29: defining the behavior of different
- Page 30 and 31: In time most developers start to ac
- Page 32 and 33: 2.4.3.4 Smalltalk environments are
- Page 34 and 35: 3. Constructing an Object Oriented
- Page 36 and 37: Wash wipe switch Wiper motor Relay
- Page 38 and 39: Point 2 above is more complicated.
- Page 40 and 41: services working? working? working?
- Page 44 and 45: 4. An Introduction to Smalltalk 4.1
- Page 46 and 47: • The idea of inheritance and sub
- Page 48 and 49: state of your development environme
- Page 50 and 51: 4.5.2.2 System Transcript The Syste
- Page 52 and 53: 4.6 Further reading A good paper gi
- Page 54 and 55: 5.3 Inspectors Another type of tool
- Page 56 and 57: • Correct it This allows the user
- Page 58 and 59: This dialog box indicates that New
- Page 60 and 61: Finally, you should see an inspecto
- Page 62 and 63: 6.2.1 Some terminology We will now
- Page 64 and 65: Object 1 name: 'John' age: 31 Class
- Page 66 and 67: The result of sending this method i
- Page 68 and 69: anObject MyCar totalNumber A capita
- Page 70 and 71: ounded round to nearest truncate ro
- Page 72 and 73: 1. instance variables - discussed a
- Page 74 and 75: Messages with one or more arguments
- Page 76 and 77: 8. An Example Smalltalk Class 8.1 I
- Page 78 and 79: You can now define the initialize m
- Page 80 and 81: 8.4 Creating an instance As was sug
- Page 82 and 83: Blocks are represented by square br
- Page 84 and 85: ifFalse: [.....] However, it is eas
- Page 86 and 87: assigned an initial value before th
- Page 88 and 89: • OrderedCollection. A collection
- Page 90 and 91: If you are confused by this descrip
- Page 92 and 93:
The OrderedCollection class can be
- Page 94 and 95:
10.9 Summary In this chapter you ha
- Page 96 and 97:
This is a very powerful class which
- Page 98 and 99:
provides any dimension size but req
- Page 100 and 101:
11.9 Iterating over collections A n
- Page 102 and 103:
An interesting exercise is to creat
- Page 104 and 105:
12. An Object Oriented Organizer 12
- Page 106 and 107:
Figure 12.3: Defining the initializ
- Page 108 and 109:
Figure 12.6: The newAddress:for: me
- Page 110 and 111:
The result of evaluating this code
- Page 112 and 113:
external device (including a file)
- Page 114 and 115:
You can also copy, move and delete
- Page 116 and 117:
13.4.2 Reading from BOSS You can ei
- Page 118 and 119:
14. The Magnitude Class Hierarchy 1
- Page 120 and 121:
Just as with the class Date, these
- Page 122 and 123:
15. Some More Tools of the Trade 15
- Page 124 and 125:
maintain a large number of images,
- Page 126 and 127:
Figure 15.3: The Change List tool T
- Page 128 and 129:
15.6 Summary In this chapter you ha
- Page 130 and 131:
130
- Page 132 and 133:
16.4 Object Oriented Analysis We sh
- Page 134 and 135:
for representing dynamic behavior i
- Page 136 and 137:
of appropriate classes and their in
- Page 138 and 139:
In the remainder of this chapter we
- Page 140 and 141:
classes, while object diagrams cont
- Page 142 and 143:
Car name hasEngine type Engine Golf
- Page 144 and 145:
compactness a tree structure can be
- Page 146 and 147:
Packages allow models to be structu
- Page 148 and 149:
Caller Phone Line Callee time calle
- Page 150 and 151:
• A conditional indicator. This i
- Page 152 and 153:
Operations can be of the following
- Page 154 and 155:
19. The Object Modeling Technique 1
- Page 156 and 157:
• Will the actor have to read/wri
- Page 158 and 159:
6. Verify that access paths exist f
- Page 160 and 161:
19.3.2.4 Identify attributes of obj
- Page 162 and 163:
20. More Object Modeling Technique
- Page 164 and 165:
Data flows are indicated by an arro
- Page 166 and 167:
20.3 Design phase The aim of the an
- Page 168 and 169:
20.3.1.8 Setting trade offs between
- Page 170 and 171:
made”. (However implementation st
- Page 172 and 173:
geographic information system. Thes
- Page 174 and 175:
a particular problem, the user gain
- Page 176 and 177:
Finally, it is interesting to note
- Page 178 and 179:
21.5.2 Adding an instance creation
- Page 180 and 181:
21.6 Summary In this chapter we exp
- Page 182 and 183:
22. Testing Object Oriented Systems
- Page 184 and 185:
people considered it suitable for c
- Page 186 and 187:
However, for the tester of the clas
- Page 188 and 189:
22.6.2 Extensibility of hierarchies
- Page 190 and 191:
23. Method and Class Testing 23.1 I
- Page 192 and 193:
23.1.6 Tracing a classes operation
- Page 194 and 195:
A good discussion of incremental te
- Page 196 and 197:
Temporary variables, which ar e loc
- Page 198 and 199:
The one exception to this rule are
- Page 200 and 201:
24.4 Methods 24.4.1 Naming methods
- Page 202 and 203:
• provide a more meaningful insta
- Page 204 and 205:
Part Five Graphical interfaces in S
- Page 206 and 207:
we cannot tell from this line alone
- Page 208 and 209:
dependents ObjectA ObjectB ObjectC
- Page 210 and 211:
(i.e. the changed message) and the
- Page 212 and 213:
| temp1 temp2| temp1 := DataObject
- Page 214 and 215:
• reusability of application and
- Page 216 and 217:
CheckButtonView class and its subcl
- Page 218 and 219:
How the update message is handled i
- Page 220 and 221:
26.4 Views and subviews In the exam
- Page 222 and 223:
26.6 Summary In this chapter you ha
- Page 224 and 225:
27.3 VisualWorks window painting to
- Page 226 and 227:
27.3.4 Widget layout control The wi
- Page 228 and 229:
Object ApplicationModel Statement F
- Page 230 and 231:
interface builder would be unable t
- Page 232 and 233:
While this may seem to be a complic
- Page 234 and 235:
Instance based reuse is more compli
- Page 236 and 237:
28. A Visual Organizer 28.1 Introdu
- Page 238 and 239:
the button. The selection colors ar
- Page 240 and 241:
28.3.3 The “aspects” protocol T
- Page 242 and 243:
we access the value holder using va
- Page 244 and 245:
29. Using a View Within a Window 29
- Page 246 and 247:
• Views control what is displayed
- Page 248 and 249:
29.4.1 Initialization 3. model: ini
- Page 250 and 251:
29.5 The classes involved This sect
- Page 252 and 253:
style := aSymbol Next we define an
- Page 254 and 255:
classVariableNames: '' poolDictiona
- Page 256 and 257:
Part Six Further Smalltalk 256
- Page 258 and 259:
30.3 VisualWorks memory management
- Page 260 and 261:
It is also possible to move objects
- Page 262 and 263:
31.3 Processes in Smalltalk For fur
- Page 264 and 265:
processes, all three processes will
- Page 266 and 267:
This is a very simple algorithm, bu
- Page 268 and 269:
32. The Metaclass Framework 32.1 In
- Page 270 and 271:
In addition a metaclass cannot be a
- Page 272 and 273:
Behaviour Behaviour class ClassDesc
- Page 274 and 275:
that no distinction is made between
- Page 276:
276
- Page 279 and 280:
to team development. At present if
- Page 281 and 282:
Compatibility (or code generation)
- Page 283 and 284:
Thanks mostly to Java, object techn
- Page 285 and 286:
eturn operator in a method. Thus al
- Page 287 and 288:
34.3 Classes and methods 34.3.1 Def
- Page 289 and 290:
This repeatedly eval uates the Smal
- Page 291 and 292:
Bibliography [Acron and Walden 1992
- Page 293 and 294:
[Krasner a nd Pope 1988] G. E. Kras
- Page 295 and 296:
Index ; ; 81 ^ ^ 67 A Abstract clas
- Page 297 and 298:
OLE................................