[Psi-devel] Message-Container

[Mircea Bardac]

Note: this is a follow-up of the "Smart-reply 0.5" e-mail announcement.

I believe that Psi needs a MessageContainer window.

Current situation:
* we know that all messages are shown in the message dialog.
* unfortunately, some message types are hard to interpret (such as the invite 
to groupchat/authorize messages).

To elaborate:
What do they all have in common?
* the header of the dialog
* the next button

I suggest putting all the common widgets in a dialog (a message-container) 
together with a dropdown button called "Actions" to group unnatural actions 
such as Quote/Forward etc for an auth event, for example. This 
message-container dialog could be extended afterwards by adding a different 
content widget, depending on the content type.

The content widget could also be used to display all types of messages in the 
Message Manager.

Am example of content widget usage:
I would like a different content widget for authorization messages which would 
NOT change the default next/close buttons with:
* radio button: Accept/Deny (accept by default)
* checkbox with: "Add contact to roster" (checked by default).
* checkbox with: "Request authorization" (checked by default)
(if this is checked, the "Add contact to roster" checkbox must be disabled and 
checked automatically)

Why those checkboxes?
Because:
(1) I might NOT want to add the user but accept the request
(2) I might want to add it but NOT WANT to request authorization.
Why so? Why not?
I have wondered many times why does XMPP have subscription types 
"to/from/both" if I can't actually make them happen. Another question: Why do 
I need to press "Add/Auth"? Shouldn't it be "Add && Auth"? That button is 
very confusing.

The XMPP RFC seems to allow adding roster items without requesting 
authorization (including subscription='none').

Examples:
(2) I want psa in my roster, because I want to let him know something from 
time to time (the roster is like an address book for me). He doesn't need me 
in his 600+ user roster because he will most likely not need to talk to me 
that often. I could just add it, without bothering him with an auth request.

(1) Using Psi right now, if somebody(me) would ask psa for auth, to auth that 
somebody (me), he will also need to add that person to his roster (which is 
already big). On the other side, I could use knowing when psa is online, 
because *I* need to talk to him. An option for him to allow my request but 
NOT add me would be better.

Mircea
/IceRAM

P.S. well, this was another "check-this-idea,free-memory-occupied-by-the-idea" 
e-mail.
P.S.2. this kind of turned out to a "change the auth/add method" feature 
request - I think I will FlySpray this.

-- 
Psi Forums Moderator/Bug Tracker Manager
Psi Windows Installer Maintainer/ArchLinux Package Maintainerer
http://mircea.bardac.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://listserver.dreamhost.com/pipermail/psi-devel-affinix.com/attachments/20050520/df95fe2c/attachment.bin