wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

More syntax fixes

Browse source
This commit is contained in:
Kegan Dougal 2015-02-06 13:05:28 +00:00
parent 3b696878f5
commit 047355b5c9
2 changed files with 11 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

2
drafts/typing_notifications.rst
View file

@ -7,7 +7,7 @@ Client APIs
To set "I am typing for the next N msec":: To set "I am typing for the next N msec"::
PUT .../rooms/:room_id/typing/:user_id PUT .../rooms/:room_id/typing/:user_id
Content: { "typing": true, "timeout": N } Content: { "typing": true, "timeout": N }
# timeout is in msec; I suggest no more than 20 or 30 seconds # timeout is in msec; I suggest no more than 20 or 30 seconds
This should be re-sent by the client to continue informing the server the user This should be re-sent by the client to continue informing the server the user
is still typing; I suggest a safety margin of 5 seconds before the expected is still typing; I suggest a safety margin of 5 seconds before the expected

17
drafts/use_cases.rst
View file

@ -268,6 +268,7 @@ Chat Screen
What's visible: What's visible:
- Enough scrollback to fill a "screen full" of content. - Enough scrollback to fill a "screen full" of content.
- Threads: - Threads:
- Initially will only display the timestamp and user ID of the *first* - Initially will only display the timestamp and user ID of the *first*
message. But can expand to show the entire tree. message. But can expand to show the entire tree.
- Tree of messages indicating which message is a reply to which. - Tree of messages indicating which message is a reply to which.
@ -280,6 +281,7 @@ Chat Screen
- Desktop/Push Notifications for messages - Desktop/Push Notifications for messages
What you can do: What you can do:
- Send a message in reply to another message: - Send a message in reply to another message:
- Immediate local echo, may cause messages to re-order - Immediate local echo, may cause messages to re-order
- Messages that haven't reached the server are queued. - Messages that haven't reached the server are queued.
- Thread is displayed where it should be in the thread order once the - Thread is displayed where it should be in the thread order once the
@ -296,13 +298,14 @@ Chat Screen
The columns start and end as threads split and rejoin the main conversation The columns start and end as threads split and rejoin the main conversation
The messages for each thread are ordered by how recent they are:: The messages for each thread are ordered by how recent they are::
Room #1 Room # 2 Room # 2 Room #1 Room # 2 Room # 2
+------------+ +----------------+ Side thread. +------------+ +----------------+ Side thread.
| * Message1 | | * Root | +--------------+ | * Message1 | | * Root | +--------------+
| * Message2 | | * A1 -> Root | | * B1 -> Root | | * Message2 | | * A1 -> Root | | * B1 -> Root |
+------------+ | * A2 -> A1 | | * B2 -> B1 | +------------+ | * A2 -> A1 | | * B2 -> B1 |
| * M -> A2, B2 | +--------------+ | * M -> A2, B2 | +--------------+
+----------------+ +----------------+
- Typing notifications. Displayed within the correct thread/column. - Typing notifications. Displayed within the correct thread/column.
What you can do: What you can do: