diff options
author | ng0 <ng0@infotropique.org> | 2017-09-07 08:09:02 +0000 |
---|---|---|
committer | ng0 <ng0@infotropique.org> | 2017-09-07 08:09:02 +0000 |
commit | 618f08aa628c0d99b91ab0cf5fd3eac59871ae4c (patch) | |
tree | d09884682128f2c28d61ed8a61996191c1420f19 /doc/chapters | |
parent | 4257203c2bf0708cd29a3a8e1809e5e08d795737 (diff) | |
download | gnunet-618f08aa628c0d99b91ab0cf5fd3eac59871ae4c.tar.gz gnunet-618f08aa628c0d99b91ab0cf5fd3eac59871ae4c.zip |
doc: chapters/user.texi: Some comment placeholders for images, some @uref{} fixes.
Diffstat (limited to 'doc/chapters')
-rw-r--r-- | doc/chapters/user.texi | 29 |
1 files changed, 22 insertions, 7 deletions
diff --git a/doc/chapters/user.texi b/doc/chapters/user.texi index 6b2d515a7..8028f5345 100644 --- a/doc/chapters/user.texi +++ b/doc/chapters/user.texi | |||
@@ -45,8 +45,12 @@ please study the installation and configuration handbooks. | |||
45 | 45 | ||
46 | First, you should launch @code{gnunet-gtk}, the graphical user interface for | 46 | First, you should launch @code{gnunet-gtk}, the graphical user interface for |
47 | GNUnet which will be used for most of the tutorial. You can do this from the | 47 | GNUnet which will be used for most of the tutorial. You can do this from the |
48 | command-line by typing@ | 48 | command-line by typing |
49 | @code{@ $ gnunet-gtk}@ | 49 | |
50 | @example | ||
51 | $ gnunet-gtk | ||
52 | @end example | ||
53 | |||
50 | (note that @code{$} represents the prompt of the shell for a normal user). | 54 | (note that @code{$} represents the prompt of the shell for a normal user). |
51 | Depending on your distribution, you may also find @code{gnunet-gtk} in your | 55 | Depending on your distribution, you may also find @code{gnunet-gtk} in your |
52 | menus. After starting @code{gnunet-gtk}, you should see the following window: | 56 | menus. After starting @code{gnunet-gtk}, you should see the following window: |
@@ -55,6 +59,7 @@ menus. After starting @code{gnunet-gtk}, you should see the following window: | |||
55 | 59 | ||
56 | The five images on top represent the five different graphical applications that | 60 | The five images on top represent the five different graphical applications that |
57 | you can use within @code{gnunet-gtk}. They are (from left to right): | 61 | you can use within @code{gnunet-gtk}. They are (from left to right): |
62 | |||
58 | @itemize @bullet | 63 | @itemize @bullet |
59 | @item Statistics | 64 | @item Statistics |
60 | @item Peer Information | 65 | @item Peer Information |
@@ -119,9 +124,13 @@ To publish a file, select "File Sharing" in the menu bar just below the | |||
119 | 124 | ||
120 | Afterwards, the following publishing dialog will appear: | 125 | Afterwards, the following publishing dialog will appear: |
121 | 126 | ||
127 | @c Add image here | ||
128 | |||
122 | In this dialog, select the "Add File" button. This will open a file selection | 129 | In this dialog, select the "Add File" button. This will open a file selection |
123 | dialog: | 130 | dialog: |
124 | 131 | ||
132 | @c Add image here | ||
133 | |||
125 | Now, you should select a file from your computer to be published on GNUnet. To | 134 | Now, you should select a file from your computer to be published on GNUnet. To |
126 | see more of GNUnet's features later, you should pick a PNG or JPEG file this | 135 | see more of GNUnet's features later, you should pick a PNG or JPEG file this |
127 | time. You can leave all of the other options in the dialog unchanged. Confirm | 136 | time. You can leave all of the other options in the dialog unchanged. Confirm |
@@ -134,9 +143,13 @@ might be interested in the progress dialog and potential errors that might be | |||
134 | encountered during processing. After the progress dialog automatically | 143 | encountered during processing. After the progress dialog automatically |
135 | disappears, your file should now appear in the publishing dialog: | 144 | disappears, your file should now appear in the publishing dialog: |
136 | 145 | ||
146 | @c Add image here | ||
147 | |||
137 | Now, select the file (by clicking on the file name) and then click the "Edit" | 148 | Now, select the file (by clicking on the file name) and then click the "Edit" |
138 | button. This will open the editing dialog: | 149 | button. This will open the editing dialog: |
139 | 150 | ||
151 | @c Add image here | ||
152 | |||
140 | In this dialog, you can see many details about your file. In the top left area, | 153 | In this dialog, you can see many details about your file. In the top left area, |
141 | you can see meta data extracted about the file, such as the original filename, | 154 | you can see meta data extracted about the file, such as the original filename, |
142 | the mimetype and the size of the image. In the top right, you should see a | 155 | the mimetype and the size of the image. In the top right, you should see a |
@@ -159,6 +172,8 @@ GNUnet! Afterwards, you should see the main dialog with a new area showing the | |||
159 | list of published files (or ongoing publishing operations with progress | 172 | list of published files (or ongoing publishing operations with progress |
160 | indicators): | 173 | indicators): |
161 | 174 | ||
175 | @c Add image here | ||
176 | |||
162 | @node Searching | 177 | @node Searching |
163 | @subsection Searching | 178 | @subsection Searching |
164 | @c %**end of header | 179 | @c %**end of header |
@@ -312,7 +327,7 @@ create a new (empty) record group under the label "test". Now click on | |||
312 | and push ENTER to confirm. Afterwards, a new dialog will pop up, asking to enter | 327 | and push ENTER to confirm. Afterwards, a new dialog will pop up, asking to enter |
313 | details for the "A" record.@ | 328 | details for the "A" record.@ |
314 | 329 | ||
315 | "A" records are used in the Domain Name System (DNS) to specify IPv4 addresses. | 330 | "A" records are used in the @dfn{Domain Name System} (DNS) to specify IPv4 addresses. |
316 | An IPv4 address is a number that is used to identify and address a computer on | 331 | An IPv4 address is a number that is used to identify and address a computer on |
317 | the Internet (version 4). Please enter "217.92.15.146" in the dialog below | 332 | the Internet (version 4). Please enter "217.92.15.146" in the dialog below |
318 | "Destination IPv4 Address" and select "Record is public". Do not change any of | 333 | "Destination IPv4 Address" and select "Record is public". Do not change any of |
@@ -398,7 +413,7 @@ Here, select "Settings..." to open the proxy settings dialog. Select "Manual | |||
398 | proxy configuration" and enter "localhost" with port 7777 under SOCKS Host. | 413 | proxy configuration" and enter "localhost" with port 7777 under SOCKS Host. |
399 | Select SOCKS v5 and then push "OK". | 414 | Select SOCKS v5 and then push "OK". |
400 | 415 | ||
401 | You must also go to About:config and change the | 416 | You must also go to about:config and change the |
402 | @code{browser.fixup.alternate.enabled} option to @code{false}, otherwise the | 417 | @code{browser.fixup.alternate.enabled} option to @code{false}, otherwise the |
403 | browser will autoblunder an address like @code{@uref{http://www.gnu/, www.gnu}} | 418 | browser will autoblunder an address like @code{@uref{http://www.gnu/, www.gnu}} |
404 | to @code{@uref{http://www.gnu.com/, www.gnu.com}}. | 419 | to @code{@uref{http://www.gnu.com/, www.gnu.com}}. |
@@ -407,10 +422,10 @@ After configuring your browser, you might want to first confirm that it | |||
407 | continues to work as before. (The proxy is still experimental and if you | 422 | continues to work as before. (The proxy is still experimental and if you |
408 | experience "odd" failures with some webpages, you might want to disable it again | 423 | experience "odd" failures with some webpages, you might want to disable it again |
409 | temporarily.) Next, test if things work by typing | 424 | temporarily.) Next, test if things work by typing |
410 | "@uref{http://test.gnu/, http://test.gnu/}" into the URL bar of your browser. | 425 | "@uref{http://test.gnu/}" into the URL bar of your browser. |
411 | This currently fails with (my version of) Firefox as Firefox is super-smart and | 426 | This currently fails with (my version of) Firefox as Firefox is super-smart and |
412 | tries to resolve "@uref{http://www.test.gnu/, www.test.gnu}" instead of | 427 | tries to resolve "@uref{http://www.test.gnu/}" instead of |
413 | "test.gnu". Chromium can be convinced to comply if you explicitly include the | 428 | "@uref{test.gnu}". Chromium can be convinced to comply if you explicitly include the |
414 | "http://" prefix --- otherwise a Google search might be attempted, which is not | 429 | "http://" prefix --- otherwise a Google search might be attempted, which is not |
415 | what you want. If successful, you should see a simple website. | 430 | what you want. If successful, you should see a simple website. |
416 | 431 | ||