Ticket #1525 (assigned task)

Opened 4 years ago

Last modified 16 months ago

Integrate Single Message windows with the Chat & MUC tabbed window.

Reported by: spike411@… Owned by: nicfit
Priority: low Milestone:
Component: usability Version:
Severity: minor Keywords:
Cc: Blocked By:
OS: All Blocking:

Description

I think the Single Message window (both sending & receiving) could be (optionally) integrated with the Chat & MUC window (I don't like many windows floating around).

Attachments

Change History

  Changed 4 years ago by nk

  • owner changed from asterix to nicfit
  • milestone set to 0.11

  Changed 4 years ago by nicfit

  • status changed from new to assigned

  Changed 4 years ago by nicfit

Some discussion in #938 which is now closed as a dupe of this ticket.

  Changed 4 years ago by jim++

See also #1228, need to switch to next single message easily.

  Changed 4 years ago by bb

I myself rarely send a single message and am very happy with the way it's

accessed right now... I don't like many buttons hanging around

  Changed 4 years ago by bb

additionally, Id like to say that the "send" button has in my case never

been used. I always click 'send & close'. in my opinion, you could just leave out the current send button and rename 'send & close' to 'send'.

  Changed 4 years ago by asterix

maybe you are not subscribed to a RSS feed :) have them in a single window

is usefull in that case.

also see #1823

  Changed 4 years ago by anonymous

Replying to asterix:

> maybe you are not subscribed to a RSS feed :)

correct!

  Changed 4 years ago by jim++

See also #2271, disable reply button for headlines.

  Changed 4 years ago by patrys@…

As some clients and services tend to send single messages as default I'd

ask for either:

  • Replacing Send by Send&Close (keeping "Send" as the name) and adding "Switch to Chat"
  • Merging single message window with the Chat window and adding a subject line above the body (and also switch to chat and switch to single respectively) - this way you can receive say 50 event in a nice scrollable window instead of 50 windows with no way to see the "next pending message from this contact"

  Changed 4 years ago by asterix

  • milestone changed from 0.11 to 0.12

  Changed 4 years ago by jim++

We also need support for urls in single messages :

 http://www.xmpp.org/extensions/xep-0066.html

And find a good way to save it in DB...

  Changed 4 years ago by asterix

  • type changed from defect to task

  Changed 4 years ago by junglecow

Closed #2897, which suggested adding a Next button to Single Message Window, as duplicate of this ticket.

  Changed 3 years ago by anonymous

  • component changed from dialogs to usability

  Changed 3 years ago by roidelapluie

  • os set to All

I would prefer keep a single window...

  Changed 3 years ago by lukas.polivka@…

Clients like Exodus or Coccinella treat Single Messages more like e-mail clients: they arrive in "Inbox" from which you can delete them or keep them there for later.

follow-up: ↓ 19   Changed 2 years ago by steve-e

Nicfit, Asterix do you plan to finish your work for 0.12?

in reply to: ↑ 18   Changed 2 years ago by nicfit

Replying to steve-e:

Nicfit, Asterix do you plan to finish your work for 0.12?

Not I, for this release at least.

  Changed 2 years ago by asterix

  • milestone 0.12 deleted

that's not a real need for 0.12, and we want to release ASAP

  Changed 16 months ago by wojtek

An option (like in PSI) "treat all incomming messages as chat" would be fantastic

  Changed 16 months ago by asterix

look in ACE "treat_incoming_messages"

  Changed 16 months ago by wojtek

sorry, been there but must have missed it. thanks for reply

Add/Change #1525 (Integrate Single Message windows with the Chat & MUC tabbed window.)

Author


E-mail address and user name can be saved in the Preferences.


Change Properties
<Author field>
Action
as assigned
as The resolution will be set. Next status will be 'closed'
to The owner will change from nicfit. Next status will be 'new'
Next status will be 'needinfo'
 
Note: See TracTickets for help on using tickets.