You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
tdenetwork/kopete/protocols/jabber/jabberchatsession.h

102 lines
2.9 KiB

/*
jabbermessagemanager.h - Jabber Message Manager
Copyright (c) 2004 by Till Gerken <till@tantalo.net>
Kopete (c) 2004 by the Kopete developers <kopete-devel@kde.org>
*************************************************************************
* *
* This program is free software; you can redistribute it and/or modify *
* it under the terms of the GNU General Public License as published by *
* the Free Software Foundation; either version 2 of the License, or *
* (at your option) any later version. *
* *
*************************************************************************
*/
#ifndef JABBERCHATSESSION_H
#define JABBERCHATSESSION_H
#include "kopetechatsession.h"
#include "im.h"
class JabberProtocol;
class JabberAccount;
class JabberBaseContact;
namespace Kopete { class Message; }
class TQString;
/**
* @author Till Gerken
*/
class JabberChatSession : public Kopete::ChatSession
{
TQ_OBJECT
public:
JabberChatSession ( JabberProtocol *protocol, const JabberBaseContact *user,
Kopete::ContactPtrList others, const TQString &resource = "",
const char *name = 0 );
~JabberChatSession();
/**
* @brief Get the local user in the session
* @return the local user in the session, same as account()->myself()
*/
const JabberBaseContact *user () const;
/**
* @brief get the account
* @return the account
*/
JabberAccount *account() const ;
/**
* @brief Return the resource this manager is currently associated with.
* @return currently associated resource
*/
const TQString &resource () const;
public slots:
/**
* Show a message to the chatwindow, or append it to the queue.
* This is the function protocols HAVE TO call for both incoming and outgoing messages
* if the message must be showed in the chatwindow
*
* This is an overloaded version of the original implementation which
* also accepts a resource the message originates from. The message manager
* will set its own resource to the resource the message was received from.
* See @ref JabberBaseContact::manager() about how to deal with instantiating
* new message managers for messages not originating from the same resource
* a manager already exists for.
*/
void appendMessage ( Kopete::Message &msg, const TQString &fromResource );
private slots:
void slotSendTypingNotification ( bool typing );
void slotMessageSent ( Kopete::Message &message, Kopete::ChatSession *kmm );
/**
* Re-generate the display name
*/
void slotUpdateDisplayName ();
void slotSendFile();
private:
/**
* Send a notification (XMPP::MsgEvent) to the members of the chatsession.
* SlotSendTypingNotification uses it.
*/
void sendNotification( XMPP::MsgEvent event );
TQString mResource;
};
#endif