Merge pull request #12 from QDucasse/master

Added all testcase=true	and inputFile:value=

Author: Ducasse

Chapters/12-Serving/serving.pillar

@@ -313,29 +313,29 @@ An encoding is a mapping between a character (or its code point) and a sequence
 
 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).
 
-[[[
+[[[testcase=true
 String with: (Character value: 65) with: (Character value: 66)
 >>> 'AB'
 ]]]
 
 
-[[[
+[[[testcase=true
 'AB' class.
 >>> ByteString
 ]]]
 
-[[[
+[[[testcase=true
 String with: (Character value: 16r5B) with: (Character value: 16r5D)
 >>> '[]'
 ]]]
 
 
-[[[
+[[[testcase=true
 String with: (Character value: 16rA9)
 >>>  the copyright character ©
 ]]]
 
-[[[
+[[[testcase=true
 Character value: 16rFC.
 >>> the u-umlaut character ü
 ]]]

book.pillar

@@ -4,25 +4,25 @@
 This part shows you how to get a simple Seaside application up and running
 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. 
 
-%${inputFile:Chapters/01-Pharo/Pharo.pillar}$
+%${inputFile:value=Chapters/01-Pharo/Pharo.pillar}$
 %should do a pass for Zinc, redo screenshots
-${inputFile:Chapters/02-Gemstone/Gemstone.pillar}$
+${inputFile:value=Chapters/02-Gemstone/Gemstone.pillar}$
 
 !! Gemstone version
 %Should add Gemstone chapter
 
 !Fundamentals
 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.
 
-%${inputFile:Chapters/02-RenderingComponents/RenderingComponents.pillar}$
+%${inputFile:value=Chapters/02-RenderingComponents/RenderingComponents.pillar}$
 %ready to review and fix figures
 
-%${inputFile:Chapters/03-CSS/css.pillar}$
+%${inputFile:value=Chapters/03-CSS/css.pillar}$
 %ready to review and fix figures
 
-%${inputFile:Chapters/04-Anchors/anchors.pillar}$
+%${inputFile:value=Chapters/04-Anchors/anchors.pillar}$
 
-%${inputFile:Chapters/05-Forms/forms.pillar}$
+%${inputFile:value=Chapters/05-Forms/forms.pillar}$
 
 
 ! Using Components
@@ -35,26 +35,26 @@ You will also see how a pre-defined component can be given different behaviour a
 
 Finally, you will see a discussion of ``Slime\'', which despite its name is an extremely useful library to check and validate your Seaside code.
 
-%${inputFile:Chapters/06-CallingComponents/callingComponents.pillar}$
-%${inputFile:Chapters/07-EmbeddingComponents/embeddingComponents.pillar}$
-%${inputFile:Chapters/08-Tasks/tasks.pillar}$
-%${inputFile:Chapters/09-Slime/slime.pillar}$
+%${inputFile:value=Chapters/06-CallingComponents/callingComponents.pillar}$
+%${inputFile:value=Chapters/07-EmbeddingComponents/embeddingComponents.pillar}$
+%${inputFile:value=Chapters/08-Tasks/tasks.pillar}$
+%${inputFile:value=Chapters/09-Slime/slime.pillar}$
 
 ! Seaside in Action
-%${inputFile:Chapters/04-ASimpleTodoApplication/ASimpleTodoApplication.pillar}$
-%${inputFile:Chapters/11-Sudoko/sudoko.pillar}$
+%${inputFile:value=Chapters/04-ASimpleTodoApplication/ASimpleTodoApplication.pillar}$
+%${inputFile:value=Chapters/11-Sudoko/sudoko.pillar}$
 %I would group the two example together
 
-%${inputFile:Chapters/12-Serving/serving.pillar}$
-%${inputFile:Chapters/13-Sessions/sessions.pillar}$
+%${inputFile:value=Chapters/12-Serving/serving.pillar}$
+%${inputFile:value=Chapters/13-Sessions/sessions.pillar}$
 
 
-%${inputFile:Chapters/14-RSS/rss.pillar}$
+%${inputFile:value=Chapters/14-RSS/rss.pillar}$
 %We should move it close to the Simple App
-%${inputFile:Chapters/15-REST/rest.pillar}$
-%${inputFile:Chapters/16-Deploy/deploy.pillar}$
+%${inputFile:value=Chapters/15-REST/rest.pillar}$
+%${inputFile:value=Chapters/16-Deploy/deploy.pillar}$
 
-%${inputFile:Chapters/17-JQuery/jquery.pillar}$
+%${inputFile:value=Chapters/17-JQuery/jquery.pillar}$
 
 
 !! Wish list of new chapter