[Bugs] #525 UNSP: Should Chat really resume by default?
SugarLabs Bugs
bugtracker-noreply at sugarlabs.org
Thu Mar 12 11:54:17 EDT 2009
#525: Should Chat really resume by default?
------------------------------------------+---------------------------------
Reporter: CarolineM | Owner: morgs
Type: defect | Status: new
Priority: Unspecified by Maintainer | Milestone: Unspecified by Release Team
Component: Chat | Version: Unspecified
Severity: Unspecified | Resolution:
Keywords: | Distribution: Unspecified
Status_field: Unconfimed |
------------------------------------------+---------------------------------
Comment(by eben):
But it's not really "someone else's" chat. It was a chat between you and
them, regardless of who started it. If they are offline, then perhaps the
alert should indicate that bit of info instead of suggesting to share it.
That would be much more useful in context.
Resuming simply means to go back into the last open instance of that
activity. I strongly disagree that we should allow the behavior to vary
based on who started the activity, or on the activity itself. I think
this adds a number of variables to the equation which won't be obvious.
The current model is nice and simple, so we just need to figure out in
what cases the current model isn't effective, and find a solution that
takes those cases into account.
It seems that it's a user preference whether they want to create something
new or resume a previous activity instance, and perhaps the ability to do
one or the other is too hidden in the current design.
--
Ticket URL: <http://dev.sugarlabs.org/ticket/525#comment:4>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list