[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] [gnunet] branch master updated: add missing images, fixes #

From: gnunet
Subject: [GNUnet-SVN] [gnunet] branch master updated: add missing images, fixes #5516
Date: Fri, 21 Jun 2019 22:18:32 +0200

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository gnunet.

The following commit(s) were added to refs/heads/master by this push:
     new 56436c888 add missing images, fixes #5516
56436c888 is described below

commit 56436c888427d7963e9ce3304cc33bc17fb89573
Author: Christian Grothoff <address@hidden>
AuthorDate: Fri Jun 21 22:17:38 2019 +0200

    add missing images, fixes #5516
 doc/handbook/chapters/developer.texi |  8 ++++++--
 doc/handbook/chapters/user.texi      | 16 +++++++---------
 2 files changed, 13 insertions(+), 11 deletions(-)

diff --git a/doc/handbook/chapters/developer.texi 
index 3225a6359..b725f4111 100644
--- a/doc/handbook/chapters/developer.texi
+++ b/doc/handbook/chapters/developer.texi
@@ -556,7 +556,7 @@ stacked together to construct complex buildings and it is 
generally easy
 to swap one block for a different one that has the same shape. GNUnet's
 architecture is based on LEGOs:
-@c @image{images/service_lego_block,5in,,picture of a LEGO block stack - 3 
APIs as connectors upon Network Protocol on top of a Service}
+@image{images/service_lego_block,5in,,picture of a LEGO block stack - 3 APIs 
upon IPC/network protocol provided by a service}
 This chapter documents the GNUnet LEGO system, also known as GNUnet's
 system architecture.
@@ -573,10 +573,14 @@ Like services, they have holes to be filled by APIs of 
other services.
 Unlike services, daemons do not implement their own network protocol and
 they have no API:
+@image{images/daemon_lego_block,5in,,A daemon in GNUnet is a component that 
does not offer an API for others to build upon}
 The GNUnet system provides a range of services, daemons and user
 interfaces, which are then combined into a layered GNUnet instance (also
 known as a peer).
+@image{images/service_stack,5in,,A GNUnet peer consists of many layers of 
 Note that while it is generally possible to swap one service for another
 compatible service, there is often only one implementation. However,
 during development we often have a "new" version of a service in parallel
@@ -587,7 +591,7 @@ easily investigated by swapping out individual components. 
This is
 typically achieved by simply changing the name of the "BINARY" in the
 respective configuration section.
-Key properties of GNUnet services are that they must be separate
+Key properties of GNUnet services are that they must be separate        
 processes and that they must protect themselves by applying tight error
 checking against the network protocol they implement (thereby achieving a
 certain degree of robustness).
diff --git a/doc/handbook/chapters/user.texi b/doc/handbook/chapters/user.texi
index 55518bc34..1c78e8f48 100644
--- a/doc/handbook/chapters/user.texi
+++ b/doc/handbook/chapters/user.texi
@@ -526,7 +526,7 @@ shell) and create an entry home-phone in your master zone.
 For the record type, select PHONE. You should then see the
 PHONE dialog:
-@c image here
+@image{images/gnunet-namestore-gtk-phone,5in,,Dialog to publish a PHONE record}
 Note: Do not choose the expiry time to be 'Never'. If you
 do that, you assert that this record will never change and
@@ -645,7 +645,7 @@ Now, using your normal user (not the @code{gnunet} system 
user), run
 master zone. For the record type, select @code{VPN}. You should then
 see the VPN dialog:
-@c insert image
+@image{images/gnunet-namestore-gtk-vpn,5in,,Dialog to publish a VPN record}
 Under peer, you need to supply the peer identity of your own peer. You can
 obtain the respective string by running @command{gnunet-peerinfo -sq}
@@ -1314,12 +1314,12 @@ To publish a file, select "File Sharing" in the menu 
bar just below the
 Afterwards, the following publishing dialog will appear:
-@c Add image here
+@image{images/gnunet-gtk-0-10-fs-publish,5in,,The gnunet-fs-gtk publishing 
 In this dialog, select the "Add File" button. This will open a
 file selection dialog:
-@c Add image here
+@image{images/gnunet-gtk-0-10-fs-publish-select,5in,,Dialog to select the file 
to publish (looks may differ for other Gtk+ versions)}
 Now, you should select a file from your computer to be published on
 GNUnet. To see more of GNUnet's features later, you should pick a
@@ -1335,12 +1335,12 @@ and potential errors that might be encountered during 
 After the progress dialog automatically disappears, your file
 should now appear in the publishing dialog:
-@c Add image here
+@image{images/gnunet-gtk-0-10-fs-publish-with-file,5in,,Publishing dialog with 
file added}
 Now, select the file (by clicking on the file name) and then click
 the "Edit" button. This will open the editing dialog:
-@c Add image here
+@image{images/gnunet-gtk-0-10-fs-publish-editing,5in,,Editing meta data of a 
file to be published}
 In this dialog, you can see many details about your file. In the
 top left area, you can see meta data extracted about the file,
@@ -1364,9 +1364,7 @@ You should now be back at the "Publish content on GNUnet" 
dialog. Select
 "Execute" in the bottom right to close the dialog and publish your file
 on GNUnet! Afterwards, you should see the main dialog with a new area
 showing the list of published files (or ongoing publishing operations
-with progress indicators):
-@c Add image here
+with progress indicators).
 @node gtk-Searching
 @subsubsection Searching

To stop receiving notification emails like this one, please contact

reply via email to

[Prev in Thread] Current Thread [Next in Thread]