commit 980e3e4c195172780d89aedffbb4bd7633860802
parent 2efb84a0a4565e8b9a4336eef31a94091b923880
Author: Marcello Stanisci <marcello.stanisci@inria.fr>
Date: Wed, 16 Nov 2016 01:14:21 +0100
zipping samples
Diffstat:
2 files changed, 11 insertions(+), 5 deletions(-)
diff --git a/Makefile b/Makefile
@@ -9,6 +9,7 @@ all: $(SUBDIRS)
$(SUBDIRS): graphics
cp -t $@/doc graphics/arch.png
cd $@/doc/; texi2pdf tutorial.texi
+ cd $@/doc/; zip samples.zip ../*.$@
graphics:
cd graphics; dot -Tpng arch.dot > arch.png
diff --git a/php/doc/tutorial.texi b/php/doc/tutorial.texi
@@ -115,7 +115,6 @@ The Taler software stack for a merchant consists of four main components:
The following image illustrates the various interactions of these
key components:
-@c FIXME, hangs the compilation: @center @image{arch, 3in, 4in}
@image{arch, 3in, 4in}
@@ -127,9 +126,6 @@ directly communicate with the exchange, and also does not deal with
sensitive data. In particular, the merchant's signing keys and bank
account information is encapsulated within the Taler backend.
-@c FIXME: this should be a separate manual
-
-
@node Hello-world
@chapter Setting up a simple Web shop with GNU Taler
@@ -212,7 +208,16 @@ The function @code{post_to_backend} is shown below; we will use it
again in other examples:
@smallexample
-FIXME: "extract" post_to_backend() from helpers.php in some way.
+@include ../backend.php
+@end smallexample
+
+The function @code{build_error} is shown below, it returns JSON data
+matching a particular format for reporting errors,
+see @code{http://api.taler.net/api-common.html#errordetail}.
+
+@smallexample
+@c FIXME, build_error() doesn't respect error-reporting format yet!
+@include ../error.php
@end smallexample
After the browser has fetched the contract, the user will
