Fossil SCM
Chat docs: added notes about client-side message deletion and clarified hyperlink parsing a bit.
Commit
a6177fd43dbef3cef8194ff0eab827f0087bf807aba01f3d05d9ee4ab884faf8
Parent
e85b679d99619a0…
1 file changed
+25
-2
+25
-2
| --- www/chat.md | ||
| +++ www/chat.md | ||
| @@ -70,15 +70,38 @@ | ||
| 70 | 70 | * Any word that begins with "http://" or "https://" is assumed |
| 71 | 71 | to be a hyperlink and is tagged. |
| 72 | 72 | |
| 73 | 73 | * Text within `[...]` is parsed and it if is a valid hyperlink |
| 74 | 74 | target (according to the way that [Fossil Wiki](/wiki_rules) or |
| 75 | - [Markdown](/md_rules) understand hyperlinks) then that text | |
| 76 | - is tagged. | |
| 75 | + [Markdown](/md_rules) understand hyperlinks) then that text is | |
| 76 | + tagged. Note that only URLs and fossil-internal constructs such | |
| 77 | + as checkin hashes and wiki pages names are recognized here, not | |
| 78 | + constructs such as `[URL | label]` or `[label](URL)`. | |
| 77 | 79 | |
| 78 | 80 | Apart from adding hyperlink anchor tags to bits of text that look |
| 79 | 81 | like hyperlinks, no changes are made to the input text. |
| 82 | + | |
| 83 | +Files may be sent via chat using the file selection element at the | |
| 84 | +bottom of the page. If the desktop environment system supports it, | |
| 85 | +files may be dragged and dropped onto that element. Files are not | |
| 86 | +automatically sent - selection of a file can be cancelled using the | |
| 87 | +Cancel button which appears only when a file is selected. When the | |
| 88 | +Send button is pressed, any pending text is submitted along with the | |
| 89 | +selected file. Image files sent this way will, by default, appear | |
| 90 | +inline in messages but each user may toggle that via the settings | |
| 91 | +popup menu, such that images instead appear as downloadable links. | |
| 92 | +Non-image files always appear in messages as download links. | |
| 93 | + | |
| 94 | +### Deletion of Messages | |
| 95 | + | |
| 96 | +Any user may *locally* delete a given message by clicking on the "tab" | |
| 97 | +at the top of the message and clicking the button which appears. Such | |
| 98 | +deletions are local-only and the messages will reappear if the page | |
| 99 | +page is reloaded. Admin users may additionally choose to globally | |
| 100 | +delete a message from the chat record, which deletes it not only from | |
| 101 | +their own browser but also propagates the removal to all connected | |
| 102 | +clients the next time they poll for new messages. | |
| 80 | 103 | |
| 81 | 104 | ## Implementation Details |
| 82 | 105 | |
| 83 | 106 | *You do not need to understand how Fossil chat works in order to use it. |
| 84 | 107 | But many developers prefer to know how their tools work. |
| 85 | 108 |
| --- www/chat.md | |
| +++ www/chat.md | |
| @@ -70,15 +70,38 @@ | |
| 70 | * Any word that begins with "http://" or "https://" is assumed |
| 71 | to be a hyperlink and is tagged. |
| 72 | |
| 73 | * Text within `[...]` is parsed and it if is a valid hyperlink |
| 74 | target (according to the way that [Fossil Wiki](/wiki_rules) or |
| 75 | [Markdown](/md_rules) understand hyperlinks) then that text |
| 76 | is tagged. |
| 77 | |
| 78 | Apart from adding hyperlink anchor tags to bits of text that look |
| 79 | like hyperlinks, no changes are made to the input text. |
| 80 | |
| 81 | ## Implementation Details |
| 82 | |
| 83 | *You do not need to understand how Fossil chat works in order to use it. |
| 84 | But many developers prefer to know how their tools work. |
| 85 |
| --- www/chat.md | |
| +++ www/chat.md | |
| @@ -70,15 +70,38 @@ | |
| 70 | * Any word that begins with "http://" or "https://" is assumed |
| 71 | to be a hyperlink and is tagged. |
| 72 | |
| 73 | * Text within `[...]` is parsed and it if is a valid hyperlink |
| 74 | target (according to the way that [Fossil Wiki](/wiki_rules) or |
| 75 | [Markdown](/md_rules) understand hyperlinks) then that text is |
| 76 | tagged. Note that only URLs and fossil-internal constructs such |
| 77 | as checkin hashes and wiki pages names are recognized here, not |
| 78 | constructs such as `[URL | label]` or `[label](URL)`. |
| 79 | |
| 80 | Apart from adding hyperlink anchor tags to bits of text that look |
| 81 | like hyperlinks, no changes are made to the input text. |
| 82 | |
| 83 | Files may be sent via chat using the file selection element at the |
| 84 | bottom of the page. If the desktop environment system supports it, |
| 85 | files may be dragged and dropped onto that element. Files are not |
| 86 | automatically sent - selection of a file can be cancelled using the |
| 87 | Cancel button which appears only when a file is selected. When the |
| 88 | Send button is pressed, any pending text is submitted along with the |
| 89 | selected file. Image files sent this way will, by default, appear |
| 90 | inline in messages but each user may toggle that via the settings |
| 91 | popup menu, such that images instead appear as downloadable links. |
| 92 | Non-image files always appear in messages as download links. |
| 93 | |
| 94 | ### Deletion of Messages |
| 95 | |
| 96 | Any user may *locally* delete a given message by clicking on the "tab" |
| 97 | at the top of the message and clicking the button which appears. Such |
| 98 | deletions are local-only and the messages will reappear if the page |
| 99 | page is reloaded. Admin users may additionally choose to globally |
| 100 | delete a message from the chat record, which deletes it not only from |
| 101 | their own browser but also propagates the removal to all connected |
| 102 | clients the next time they poll for new messages. |
| 103 | |
| 104 | ## Implementation Details |
| 105 | |
| 106 | *You do not need to understand how Fossil chat works in order to use it. |
| 107 | But many developers prefer to know how their tools work. |
| 108 |