Skip to content

Commit 797bfde

Browse files
author
QDucasse
committed
Added all testcase=true and inputFile:value=
1 parent 53d2e3e commit 797bfde

File tree

2 files changed

+23
-23
lines changed

2 files changed

+23
-23
lines changed

Chapters/12-Serving/serving.pillar

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -313,29 +313,29 @@ An encoding is a mapping between a character (or its code point) and a sequence
313313

314314
In the latest version of Pharo, the ==Character== class represents a character by storing its Unicode. Since Unicode is a superset of latin1, you can create latin1 strings by specifying their direct values. When a ==String== is composed only of ASCII or latin1 characters, it is encoded in a ==ByteString== (a collection of bytes each one representing a character).
315315

316-
[[[
316+
[[[testcase=true
317317
String with: (Character value: 65) with: (Character value: 66)
318318
>>> 'AB'
319319
]]]
320320

321321

322-
[[[
322+
[[[testcase=true
323323
'AB' class.
324324
>>> ByteString
325325
]]]
326326

327-
[[[
327+
[[[testcase=true
328328
String with: (Character value: 16r5B) with: (Character value: 16r5D)
329329
>>> '[]'
330330
]]]
331331

332332

333-
[[[
333+
[[[testcase=true
334334
String with: (Character value: 16rA9)
335335
>>> the copyright character ©
336336
]]]
337337

338-
[[[
338+
[[[testcase=true
339339
Character value: 16rFC.
340340
>>> the u-umlaut character ü
341341
]]]

book.pillar

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -4,25 +4,25 @@
44
This part shows you how to get a simple Seaside application up and running
55
in less than 15 minutes. If you’re new to Pharo, have a look at the Pharo by Example Seaside Chapter. You can also have a look at the excellent Pharo Mooc *http://mooc.pharo.org*. Watch the first video and the development session about the counter.
66

7-
%${inputFile:Chapters/01-Pharo/Pharo.pillar}$
7+
%${inputFile:value=Chapters/01-Pharo/Pharo.pillar}$
88
%should do a pass for Zinc, redo screenshots
9-
${inputFile:Chapters/02-Gemstone/Gemstone.pillar}$
9+
${inputFile:value=Chapters/02-Gemstone/Gemstone.pillar}$
1010

1111
!! Gemstone version
1212
%Should add Gemstone chapter
1313

1414
!Fundamentals
1515
In this part we will introduce you to the manipulation of basic elements such as texts, anchors and callbacks as well as forms. It presents the notion of ''brushes'' that is central to the Seaside API. Understanding these concepts will be fundamental to your use of Seaside.
1616

17-
%${inputFile:Chapters/02-RenderingComponents/RenderingComponents.pillar}$
17+
%${inputFile:value=Chapters/02-RenderingComponents/RenderingComponents.pillar}$
1818
%ready to review and fix figures
1919

20-
%${inputFile:Chapters/03-CSS/css.pillar}$
20+
%${inputFile:value=Chapters/03-CSS/css.pillar}$
2121
%ready to review and fix figures
2222

23-
%${inputFile:Chapters/04-Anchors/anchors.pillar}$
23+
%${inputFile:value=Chapters/04-Anchors/anchors.pillar}$
2424

25-
%${inputFile:Chapters/05-Forms/forms.pillar}$
25+
%${inputFile:value=Chapters/05-Forms/forms.pillar}$
2626

2727

2828
! Using Components
@@ -35,26 +35,26 @@ You will also see how a pre-defined component can be given different behaviour a
3535

3636
Finally, you will see a discussion of ``Slime\'', which despite its name is an extremely useful library to check and validate your Seaside code.
3737

38-
%${inputFile:Chapters/06-CallingComponents/callingComponents.pillar}$
39-
%${inputFile:Chapters/07-EmbeddingComponents/embeddingComponents.pillar}$
40-
%${inputFile:Chapters/08-Tasks/tasks.pillar}$
41-
%${inputFile:Chapters/09-Slime/slime.pillar}$
38+
%${inputFile:value=Chapters/06-CallingComponents/callingComponents.pillar}$
39+
%${inputFile:value=Chapters/07-EmbeddingComponents/embeddingComponents.pillar}$
40+
%${inputFile:value=Chapters/08-Tasks/tasks.pillar}$
41+
%${inputFile:value=Chapters/09-Slime/slime.pillar}$
4242

4343
! Seaside in Action
44-
%${inputFile:Chapters/04-ASimpleTodoApplication/ASimpleTodoApplication.pillar}$
45-
%${inputFile:Chapters/11-Sudoko/sudoko.pillar}$
44+
%${inputFile:value=Chapters/04-ASimpleTodoApplication/ASimpleTodoApplication.pillar}$
45+
%${inputFile:value=Chapters/11-Sudoko/sudoko.pillar}$
4646
%I would group the two example together
4747

48-
%${inputFile:Chapters/12-Serving/serving.pillar}$
49-
%${inputFile:Chapters/13-Sessions/sessions.pillar}$
48+
%${inputFile:value=Chapters/12-Serving/serving.pillar}$
49+
%${inputFile:value=Chapters/13-Sessions/sessions.pillar}$
5050

5151

52-
%${inputFile:Chapters/14-RSS/rss.pillar}$
52+
%${inputFile:value=Chapters/14-RSS/rss.pillar}$
5353
%We should move it close to the Simple App
54-
%${inputFile:Chapters/15-REST/rest.pillar}$
55-
%${inputFile:Chapters/16-Deploy/deploy.pillar}$
54+
%${inputFile:value=Chapters/15-REST/rest.pillar}$
55+
%${inputFile:value=Chapters/16-Deploy/deploy.pillar}$
5656

57-
%${inputFile:Chapters/17-JQuery/jquery.pillar}$
57+
%${inputFile:value=Chapters/17-JQuery/jquery.pillar}$
5858

5959

6060
!! Wish list of new chapter

0 commit comments

Comments
 (0)