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/windows/RosterWindow.h

43 lines
1.0 KiB
C
Raw Permalink Normal View History

Move roster into its own generic window The roster list is now split from MainWindow into RosterWindow, which can be used arbitrarily for selecting something from contacts. The im_what, title, and target can be specified. Right now it's in use under the Chat menu, "New chat…". Chats can only have two members (DM/PM), so "New chat…" directly leads to the roster list. In the future, roster list might be extended to allow specification of non-contact users based on their identifiers, or filtering based on protocol/account― this could help it with "invites" to future rooms, etc. IM_CREATE_CHAT and IM_CHAT_CREATED were also added to the protocol API, allowing a new chat to be explicitly created from Caya or the protocol.
2021-05-26 07:48:25 -05:00
/*
* Copyright 2009-2011, Andrea Anzani. All rights reserved.
* Copyright 2009-2011, Pier Luigi Fiorini. All rights reserved.
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 2021, Jaidyn Levesque. All rights reserved.
Move roster into its own generic window The roster list is now split from MainWindow into RosterWindow, which can be used arbitrarily for selecting something from contacts. The im_what, title, and target can be specified. Right now it's in use under the Chat menu, "New chat…". Chats can only have two members (DM/PM), so "New chat…" directly leads to the roster list. In the future, roster list might be extended to allow specification of non-contact users based on their identifiers, or filtering based on protocol/account― this could help it with "invites" to future rooms, etc. IM_CREATE_CHAT and IM_CHAT_CREATED were also added to the protocol API, allowing a new chat to be explicitly created from Caya or the protocol.
2021-05-26 07:48:25 -05:00
* Distributed under the terms of the MIT License.
*
* Authors:
* Andrea Anzani, andrea.anzani@gmail.com
* Pier Luigi Fiorini, pierluigi.fiorini@gmail.com
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
* Jaidyn Levesque, jadedctrl@teknik.io
Move roster into its own generic window The roster list is now split from MainWindow into RosterWindow, which can be used arbitrarily for selecting something from contacts. The im_what, title, and target can be specified. Right now it's in use under the Chat menu, "New chat…". Chats can only have two members (DM/PM), so "New chat…" directly leads to the roster list. In the future, roster list might be extended to allow specification of non-contact users based on their identifiers, or filtering based on protocol/account― this could help it with "invites" to future rooms, etc. IM_CREATE_CHAT and IM_CHAT_CREATED were also added to the protocol API, allowing a new chat to be explicitly created from Caya or the protocol.
2021-05-26 07:48:25 -05:00
*/
#ifndef ROSTERWINDOW_H
#define ROSTERWINDOW_H
#include <Window.h>
Sorting of RosterWindow by accounts
2021-06-18 18:42:10 -05:00
class BMenuField;
Move roster into its own generic window The roster list is now split from MainWindow into RosterWindow, which can be used arbitrarily for selecting something from contacts. The im_what, title, and target can be specified. Right now it's in use under the Chat menu, "New chat…". Chats can only have two members (DM/PM), so "New chat…" directly leads to the roster list. In the future, roster list might be extended to allow specification of non-contact users based on their identifiers, or filtering based on protocol/account― this could help it with "invites" to future rooms, etc. IM_CREATE_CHAT and IM_CHAT_CREATED were also added to the protocol API, allowing a new chat to be explicitly created from Caya or the protocol.
2021-05-26 07:48:25 -05:00
class 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
class RosterView;
Move roster into its own generic window The roster list is now split from MainWindow into RosterWindow, which can be used arbitrarily for selecting something from contacts. The im_what, title, and target can be specified. Right now it's in use under the Chat menu, "New chat…". Chats can only have two members (DM/PM), so "New chat…" directly leads to the roster list. In the future, roster list might be extended to allow specification of non-contact users based on their identifiers, or filtering based on protocol/account― this could help it with "invites" to future rooms, etc. IM_CREATE_CHAT and IM_CHAT_CREATED were also added to the protocol API, allowing a new chat to be explicitly created from Caya or the protocol.
2021-05-26 07:48:25 -05:00
/* A window with the a list of the user's contacts, will send a message to
the server with contact info, once a contact is selected. */
class RosterWindow : public BWindow {
public:
Support sending invitations Fixes #5
2021-06-08 21:43:30 -05:00
RosterWindow(const char* title, BMessage* selectMsg, BMessenger* messenger,
Use Server::Get(), clean up header usage Instead of passing around pointers to the Server, Server::Get() returns the server's pointer (simplifying some things a good bit). As a result, headers have been cleaned up, and some redundant KeyMaps have been placed in Maps.h.
2022-02-23 15:42:46 -06:00
bigtime_t instance = -1);
Move roster into its own generic window The roster list is now split from MainWindow into RosterWindow, which can be used arbitrarily for selecting something from contacts. The im_what, title, and target can be specified. Right now it's in use under the Chat menu, "New chat…". Chats can only have two members (DM/PM), so "New chat…" directly leads to the roster list. In the future, roster list might be extended to allow specification of non-contact users based on their identifiers, or filtering based on protocol/account― this could help it with "invites" to future rooms, etc. IM_CREATE_CHAT and IM_CHAT_CREATED were also added to the protocol API, allowing a new chat to be explicitly created from Caya or the protocol.
2021-05-26 07:48:25 -05:00
void MessageReceived(BMessage* message);
void UpdateListItem(RosterItem* item);
private:
Sorting of RosterWindow by accounts
2021-06-18 18:42:10 -05:00
BButton* fOkButton;
BMenuField* fAccountField;
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
RosterView* fRosterView;
Move roster into its own generic window The roster list is now split from MainWindow into RosterWindow, which can be used arbitrarily for selecting something from contacts. The im_what, title, and target can be specified. Right now it's in use under the Chat menu, "New chat…". Chats can only have two members (DM/PM), so "New chat…" directly leads to the roster list. In the future, roster list might be extended to allow specification of non-contact users based on their identifiers, or filtering based on protocol/account― this could help it with "invites" to future rooms, etc. IM_CREATE_CHAT and IM_CHAT_CREATED were also added to the protocol API, allowing a new chat to be explicitly created from Caya or the protocol.
2021-05-26 07:48:25 -05:00
BMessenger* fTarget;
BMessage* fMessage;
};
#endif // ROSTERWINDOW_H