Skip to content

Commit 099dadf

Browse files
authored
Merge pull request #136 from LNUitTutor/patch-7
Update Commander.md - catch #s
2 parents 4e75b2b + cabd509 commit 099dadf

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

Chapters/Commander2/Commander.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ As a general design advice, do not define application logic in a command. A comm
8585
#### SaveMailCommand
8686

8787
```
88-
MailClientCommand << SaveMailCommand
88+
MailClientCommand << #SaveMailCommand
8989
slots: {};
9090
package: 'CodeOfSpec20Book'
9191
```
@@ -118,7 +118,7 @@ In the previous command class, we did not implement `NewMailCommand >> canBeExec
118118
#### SendMailCommand
119119

120120
```
121-
MailClientCommand << SendMailCommand
121+
MailClientCommand << #SendMailCommand
122122
slots: {};
123123
package: 'CodeOfSpec20Book'
124124
```
@@ -147,7 +147,7 @@ SendMailCommand >> canBeExecuted
147147
#### DeleteMailCommand
148148

149149
```
150-
MailClientCommand << DeleteMailCommand
150+
MailClientCommand << #DeleteMailCommand
151151
slots: {};
152152
package: 'CodeOfSpec20Book'
153153
```
@@ -176,7 +176,7 @@ DeleteMailCommand >> canBeExecuted
176176
#### FetchMailCommand
177177

178178
```
179-
MailClientCommand << FetchMailCommand
179+
MailClientCommand << #FetchMailCommand
180180
slots: {};
181181
package: 'CodeOfSpec20Book'
182182
```
@@ -436,7 +436,7 @@ MailClientPresenter >> buildFormatMenuWith: presenter
436436
yourself
437437
```
438438

439-
Now that the command tree for the menubar is defined, we can use it. In Chapter *@cha_mailapp@*, we defined `MailClientPresenter >> #initializeMenuBar`. We can replace it by:
439+
Now that the command tree for the menubar is defined, we can use it. In Chapter *@cha_mailapp@*, we defined `MailClientPresenter >> initializeMenuBar`. We can replace it by:
440440

441441
```
442442
MailClientPresenter >> initializeMenuBar
@@ -456,7 +456,7 @@ As you can see in Figure *@WithMenuBar@*, the first menu in the menubar shows a
456456

457457
We can achieve the same grouping with commands. Commands can be managed in groups and such groups can be turned into corresponding menu item sections.
458458

459-
Let's make the required changes to the method `MailClientPresenter class >> #buildMessageMenuWith:` that we introduced before.
459+
Let's make the required changes to the method `MailClientPresenter class >> buildMessageMenuWith:` that we introduced before.
460460

461461
```
462462
MailClientPresenter class >> buildMessageMenuWith: presenter
@@ -481,7 +481,7 @@ An important message is `beDisplayedAsGroup`. It indicates that in a menu, the n
481481

482482
![Nested menu with the mouse pointing at its name.%width=60&anchor=WithNestedMenu](figures/WithNestedMenu.png)
483483

484-
In our case, we do not want a nested menu. We want a separate section in the menu. With the implementation of `MailClientPresenter class >> #buildMessageMenuWith:` above, we see a menu as shown in Figure *@MenuWithGroup@*. As in Chapter *@cha_menus@*, now there are two groups of commands, separated by a line.
484+
In our case, we do not want a nested menu. We want a separate section in the menu. With the implementation of `MailClientPresenter class >> buildMessageMenuWith:` above, we see a menu as shown in Figure *@MenuWithGroup@*. As in Chapter *@cha_menus@*, now there are two groups of commands, separated by a line.
485485

486486
![Menu with a separate group. %width=60&anchor=MenuWithGroup](figures/MenuWithGroup.png)
487487

0 commit comments

Comments
 (0)