jadedctrl/Chat-O-Matic
jadedctrl/ Chat-O-Matic
1
0
Disbranĉigi 0
Fontkodo Issues 20 Tirpetoj Actions Packages Projects Eldonoj 2 Wiki Activity
Chat-O-Matic/application/Contact.cpp

40 lines
717 B
C++
Raw Normal View History

Usual SVN tree (branches, tags, trunk).
2010-05-07 04:47:10 -05:00
/*
Update copyright year.
2011-12-03 16:38:03 -06:00
* Copyright 2009-2011, Andrea Anzani. All rights reserved.
Setted the Person icon from haiku artwork as default contact icon.
2012-05-01 16:09:56 -05:00
* Copyright 2012, Dario Casalinuovo. All rights reserved.
Usual SVN tree (branches, tags, trunk).
2010-05-07 04:47:10 -05:00
* Distributed under the terms of the MIT License.
*
* Authors:
* Andrea Anzani, andrea.anzani@gmail.com
Setted the Person icon from haiku artwork as default contact icon.
2012-05-01 16:09:56 -05:00
* Dario Casalinuovo
Usual SVN tree (branches, tags, trunk).
2010-05-07 04:47:10 -05:00
*/
Rename ContactLinker to Contact
2021-05-23 14:39:07 -05:00
#include "Contact.h"
Usual SVN tree (branches, tags, trunk).
2010-05-07 04:47:10 -05:00
#include "RosterItem.h"
Fix crash when msn plugin is not installed. When the protocol looper is set we get its CayaProtocolAddOn and retrieve the protocol add-on's icon that is used as the default icon for the contact.
2010-05-28 12:20:02 -05:00
Rename ContactLinker to Contact
2021-05-23 14:39:07 -05:00
Contact::Contact(BString id, BMessenger msgn)
Fix some style violations.
2010-05-19 17:28:26 -05:00
:
Create Conversation class, use it instead of Contact for chats This is a commit with it's foot in a lot of places, but: The Conversation class was created as the abstraction of chats: All ImMessages that are relevant to a conversation get routed through it, meta-data on chats is stored in it (even if right now that's basically limited to the user list and ID). Server was given more methods to help accessing contacts― ContactById(BString) and AddContact(Contact*). This better allows Conversations to add and fetch Contacts as necessary. Right now, all users in chats are treated as Contacts, so in the future creating an independent userlist for Server (fUserMap?) would be useful. Server also now stores all Conversations (fChatMap) and has some convenience methods like for Contacts: Conversations(), ConversationById(BString), and AddConversation(Conversation*). CayaRenderView has been changed to not store user nicks, and will use the appropriate nick of any arbitrarily-numbered user. Users also have a map of all Conversations they are a part of (fChatMap). The Remove* methods of KeyMap now return the removed item.
2021-05-24 01:47:21 -05:00
User::User(id, msgn)
Usual SVN tree (branches, tags, trunk).
2010-05-07 04:47:10 -05:00
{
fRosterItem = new RosterItem(id.String(), this);
RegisterObserver(fRosterItem);
}
Modified ContactLinker : moved some inline methods from class declaration, added Get* methods for contact status and status message. Added code in the ChatWindow to show the current avatar of the user. Modified the Server to allow a plugin set the status message when sending a IM_CONTACT_INFO notification to the server, as before it's already possible to do it using a IM_STATUS_SET message.
2012-03-07 13:22:09 -06:00
RosterItem*
Rename ContactLinker to Contact
2021-05-23 14:39:07 -05:00
Contact::GetRosterItem() const
Modified ContactLinker : moved some inline methods from class declaration, added Get* methods for contact status and status message. Added code in the ChatWindow to show the current avatar of the user. Modified the Server to allow a plugin set the status message when sending a IM_CONTACT_INFO notification to the server, as before it's already possible to do it using a IM_STATUS_SET message.
2012-03-07 13:22:09 -06:00
{
return fRosterItem;
}
Usual SVN tree (branches, tags, trunk).
2010-05-07 04:47:10 -05:00
void
Rename ContactLinker to Contact
2021-05-23 14:39:07 -05:00
Contact::SetNotifyAvatarBitmap(BBitmap* bitmap)
Usual SVN tree (branches, tags, trunk).
2010-05-07 04:47:10 -05:00
{
Split 'Contact' class into two This dichotomy is useful and necessary in multi-user chats, so I split Contact into a parent class, User. User should be used for generic members of rooms, Contact used mainly with the roster.
2021-05-23 15:10:14 -05:00
User::SetNotifyAvatarBitmap(bitmap);
Create Conversation class, use it instead of Contact for chats This is a commit with it's foot in a lot of places, but: The Conversation class was created as the abstraction of chats: All ImMessages that are relevant to a conversation get routed through it, meta-data on chats is stored in it (even if right now that's basically limited to the user list and ID). Server was given more methods to help accessing contacts― ContactById(BString) and AddContact(Contact*). This better allows Conversations to add and fetch Contacts as necessary. Right now, all users in chats are treated as Contacts, so in the future creating an independent userlist for Server (fUserMap?) would be useful. Server also now stores all Conversations (fChatMap) and has some convenience methods like for Contacts: Conversations(), ConversationById(BString), and AddConversation(Conversation*). CayaRenderView has been changed to not store user nicks, and will use the appropriate nick of any arbitrarily-numbered user. Users also have a map of all Conversations they are a part of (fChatMap). The Remove* methods of KeyMap now return the removed item.
2021-05-24 01:47:21 -05:00
// if (fAvatarBitmap != NULL && fChatWindow != NULL)
// fChatWindow->UpdateAvatar();
Usual SVN tree (branches, tags, trunk).
2010-05-07 04:47:10 -05:00
}