b1920dad47
Registration of custom chat commands and menu-items for protocols was done by the IM_REGISTER_* messages, and is now done through direct calls to the CayaProtocol object. The new model for call/message for protocols is this: Temporary information (chat messages, roster members, etc.) should be accessed through messages. Relatively static data (protocol name, commands) should be accessed through direct calls to the protocol object.
23 lines
579 B
C++
23 lines
579 B
C++
/*
|
|
* Copyright 2021, Jaidyn Levesque <jadedctrl@teknik.io>
|
|
* All rights reserved. Distributed under the terms of the MIT license.
|
|
*/
|
|
#ifndef DEFAULTITEMS_H
|
|
#define DEFAULTITEMS_H
|
|
|
|
#include <ObjectList.h>
|
|
|
|
class BMessage;
|
|
|
|
|
|
BObjectList<BMessage> DefaultCommands();
|
|
BObjectList<BMessage> DefaultChatPopUpItems();
|
|
BObjectList<BMessage> DefaultUserPopUpItems();
|
|
BMessage* _UserMenuItem(const char* label, BMessage* msg,
|
|
int32 user_perms, int32 target_perms,
|
|
int32 target_lacks, bool ignorePriority,
|
|
bool toProtocol);
|
|
|
|
|
|
#endif // DEFAULTITEMS_H
|