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/views/RosterView.cpp

266 lines
6.1 KiB
C++
Raw Normal View History

Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
/*
* Copyright 2009-2011, Andrea Anzani. All rights reserved.
* Copyright 2009-2011, Pier Luigi Fiorini. All rights reserved.
* Copyright 2021, Jaidyn Levesque. All rights reserved.
* Distributed under the terms of the MIT License.
*
* Authors:
* Andrea Anzani, andrea.anzani@gmail.com
* Pier Luigi Fiorini, pierluigi.fiorini@gmail.com
* Jaidyn Levesque, jadedctrl@teknik.io
*/
#include "RosterView.h"
Localization, init catkeys
2021-07-19 09:54:27 -05:00
#include <Catalog.h>
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
#include <LayoutBuilder.h>
#include <Notification.h>
#include <ScrollView.h>
Change class names
2021-06-20 12:44:20 -05:00
#include "AppMessages.h"
#include "AppPreferences.h"
Rename Caya to Cardie
2021-06-22 01:06:00 -05:00
#include "Cardie.h"
Change class names
2021-06-20 12:44:20 -05:00
#include "ChatProtocolMessages.h"
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
#include "RosterItem.h"
#include "RosterListView.h"
Localization, init catkeys
2021-07-19 09:54:27 -05:00
#undef B_TRANSLATION_CONTEXT
#define B_TRANSLATION_CONTEXT "RosterView"
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
const uint32 kSearchContact = 'RWSC';
RosterView::RosterView(const char* title, Server* server, bigtime_t account)
:
BGroupView(title, B_VERTICAL, B_USE_DEFAULT_SPACING),
fAccount(-1),
fServer(server)
{
fSearchBox = new BTextControl("searchBox", "", "",
new BMessage(kSearchContact));
fSearchBox->SetModificationMessage(new BMessage(kSearchContact));
fListView = new RosterListView("buddyView");
BScrollView* scrollView = new BScrollView("scrollview", fListView,
B_WILL_DRAW, false, true);
BLayoutBuilder::Group<>(this, B_VERTICAL, 0.0f)
.AddGroup(B_VERTICAL)
.SetInsets(5, 5, 5, 10)
.Add(fSearchBox)
.Add(scrollView)
.End()
.End();
SetAccount(account);
}
void
RosterView::MessageReceived(BMessage* message)
{
switch (message->what) {
case kSearchContact:
{
RosterMap map = _RosterMap();
for (uint32 i = 0; i < map.CountItems(); i++) {
Contact* linker = map.ValueAt(i);
RosterItem* item = linker->GetRosterItem();
// If the search filter has been deleted show all the items,
// otherwise remove the item in order to show only items
// that matches the search criteria
if (strcmp(fSearchBox->Text(), "") == 0)
Roster list tweaks, auto-deselect
2021-07-25 17:27:04 -05:00
fListView->AddItem(item);
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
else if (linker->GetName().IFindFirst(fSearchBox->Text()) == B_ERROR)
fListView->RemoveItem(item);
else
Roster list tweaks, auto-deselect
2021-07-25 17:27:04 -05:00
fListView->AddItem(item);
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
UpdateListItem(item);
}
break;
}
case IM_MESSAGE:
ImMessage(message);
break;
default:
BGroupView::MessageReceived(message);
}
}
void
RosterView::ImMessage(BMessage* msg)
{
int32 im_what = msg->FindInt32("im_what");
switch (im_what) {
case IM_STATUS_SET:
{
int32 status;
int64 instance;
BString user_id = msg->FindString("user_id");
if (msg->FindInt32("status", &status) != B_OK
|| msg->FindInt64("instance", &instance) != B_OK
|| user_id.IsEmpty() == true)
return;
Contact* contact = fServer->ContactById(user_id, instance);
if (contact == NULL)
return;
RosterItem* rosterItem = contact->GetRosterItem();
if (rosterItem) {
UpdateListItem(rosterItem);
// Add or remove item
switch (status) {
Change class names
2021-06-20 12:44:20 -05:00
/*case STATUS_OFFLINE:
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
// By default offline contacts are hidden
Change class names
2021-06-20 12:44:20 -05:00
if (!AppPreferences::Item()->HideOffline)
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
break;
if (HasItem(rosterItem))
RemoveItem(rosterItem);
return;*/
default:
// Add item because it has a non-offline status
Roster list tweaks, auto-deselect
2021-07-25 17:27:04 -05:00
fListView->AddItem(rosterItem);
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
break;
}
UpdateListItem(rosterItem);
// Sort list view again
fListView->Sort();
// Check if the user want the notification
Change class names
2021-06-20 12:44:20 -05:00
if (!AppPreferences::Item()->NotifyContactStatus)
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
break;
switch (status) {
Change class names
2021-06-20 12:44:20 -05:00
case STATUS_ONLINE:
case STATUS_OFFLINE:
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
// Notify when contact is online or offline
Change class names
2021-06-20 12:44:20 -05:00
if (status == STATUS_ONLINE) {
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
BString message;
message << rosterItem->GetContact()->GetName();
Change class names
2021-06-20 12:44:20 -05:00
if (status == STATUS_ONLINE)
Translate more strings, update catkeys
2021-07-24 21:11:34 -05:00
message.SetTo(B_TRANSLATE("%name% is available!"));
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
else
Translate more strings, update catkeys
2021-07-24 21:11:34 -05:00
message.SetTo(B_TRANSLATE("%name% is offline!"));
Localization, init catkeys
2021-07-19 09:54:27 -05:00
message.ReplaceAll("%name%",
rosterItem->GetContact()->GetName());
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
BNotification notification(B_INFORMATION_NOTIFICATION);
Rename Caya to Cardie
2021-06-22 01:06:00 -05:00
notification.SetGroup(BString(APP_NAME));
Localization, init catkeys
2021-07-19 09:54:27 -05:00
notification.SetTitle(BString(B_TRANSLATE("Presence")));
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
notification.SetIcon(rosterItem->Bitmap());
notification.SetContent(message);
notification.Send();
}
break;
default:
break;
}
}
break;
}
Removal of roster members Now roster members can be deleted through the RosterEditWindow. IM_CONTACT_LIST_REMOVED_CONTACT was renamed to IM_CONTACT_LIST_CONTACT_REMOVED to fit style of other API messages. Fixes #1.
2021-06-19 22:37:20 -05:00
case IM_CONTACT_LIST_CONTACT_REMOVED:
{
int32 status = -1;
int64 instance;
BString user_id = msg->FindString("user_id");
if (msg->FindInt32("status", &status) != B_OK
|| msg->FindInt64("instance", &instance) != B_OK
|| user_id.IsEmpty() == true)
return;
Contact* contact = fServer->ContactById(user_id, instance);
if (contact == NULL)
return;
RosterItem* rosterItem = contact->GetRosterItem();
if (rosterItem)
fListView->RemoveItem(rosterItem);
}
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
case IM_AVATAR_SET:
case IM_CONTACT_INFO:
case IM_EXTENDED_CONTACT_INFO:
{
int32 status = -1;
int64 instance;
BString user_id = msg->FindString("user_id");
if (msg->FindInt32("status", &status) != B_OK
|| msg->FindInt64("instance", &instance) != B_OK
|| user_id.IsEmpty() == true)
return;
Contact* contact = fServer->ContactById(user_id, instance);
if (contact == NULL)
return;
RosterItem* rosterItem = contact->GetRosterItem();
if (rosterItem)
UpdateListItem(rosterItem);
break;
}
}
}
void
RosterView::AttachedToWindow()
{
fSearchBox->SetTarget(this);
fSearchBox->MakeFocus(true);
}
void
RosterView::SetInvocationMessage(BMessage* msg)
{
fListView->SetInvocationMessage(msg);
}
void
RosterView::SetAccount(bigtime_t instance_id)
{
fAccount = instance_id;
RosterMap contacts = _RosterMap();
fListView->MakeEmpty();
for (int i = 0; i < contacts.CountItems(); i++)
Roster list tweaks, auto-deselect
2021-07-25 17:27:04 -05:00
fListView->AddItem(contacts.ValueAt(i)->GetRosterItem());
Split RosterWindow into per-account RosterView Most of RosterWindow's special functions have been split into a special BGroupView (including both the roster search-box and roster list), RosterView. This will give some more flexibility in other uses of the roster list. In addition, RosterViews can be tied to a specific account by its looper's instance ID, allowing it to either show all contacts (globally; if the ID is set to -1) or only those of the specified account. This can be useful, for example, when inviting contacts to a room― you can only invite contacts that use the same protocol, and are associated with your account, so showing all contacts doesn't make sense. The SearchBarTextControl class was removed, as it isn't particularly necessary.
2021-06-18 16:41:09 -05:00
}
void
RosterView::UpdateListItem(RosterItem* item)
{
if (fListView->HasItem(item))
fListView->InvalidateItem(fListView->IndexOf(item));
}
RosterListView*
RosterView::ListView()
{
return fListView;
}
RosterMap
RosterView::_RosterMap()
{
RosterMap contacts;
if (fAccount < 0)
contacts = fServer->Contacts();
else {
ProtocolLooper* looper = fServer->GetProtocolLooper(fAccount);
contacts = looper->Contacts();
}
return contacts;
}