[Telepathy] Requestotron use-cases, part 2

[Simon McVittie]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 30 Apr 2008 at 14:00:18 +0100, Simon McVittie wrote:
> On Wed, 30 Apr 2008 at 12:04:01 +0200, Xavier Claessens wrote:
> > Thanks for writing all use cases! Here is a copy/past of comments I
> > wrote on IRC:
> > 
> > About the usecase "*dis3: Incoming 1-1 text message with window closed" 
> > 1) Empathy closes the channel when the window/tab is closed.
> 
> Thanks, I've updated the document.

The new text is:

_`dis3`: Incoming 1-1 text message with window closed
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

After a pause in a conversation with Romeo, Juliet closes the IM window
or tab. She then receives another message from Romeo, resuming the
conversation.

Current implementation in Empathy, _`dis3impl2`:

* The Text channel is closed (depending on protocol, this may be visible to
  the remote user, e.g. MSN's "Juliet has closed the window")

* As a result, the new message is indistinguishable from a new channel (dis1_)

Problems:

* Not associated with the previous chat session, although this could be fixed
  with "conversation thread IDs"

* Zdra doesn't think the Chat UI should Close() text channels, although
  in ``Message-ID: <1209127037.6294.41.camel at zdra-laptop>`` he doesn't
  provide any rationale or use cases. (Zdra, could you explain please?)

Alternative implementation, _`dis3impl3`:

* the same as dis3impl1_, but use the same notification icon as for a
  new channel (dis1_), and only pop up the main chat UI window if accepted

* in practice this would give basically the same UI as for dis3impl2_, but
  without actually closing the channel

Problems:

* if it is desirable to tell the remote user that the window has been closed,
  the CM can't know

* dis2problem2_ also applies here

Incorrect implementation, _`dis3impl1`:

* The Text channel is not closed

* The new message causes the chat window to pop up, possibly stealing focus

Problems:

* Focus stealing is likely
-----BEGIN PGP SIGNATURE-----

iD8DBQFIGG6wWSc8zVUw7HYRAl0YAJ0ajMg0+sWFVM/js4J8f1TqKcOm9wCgy4cP
nO+AOcUxvxW4T3qigIqCHjg=
=4IQM
-----END PGP SIGNATURE-----