From dfe289850f068f19ba4a83ab4e7e22a7e09c13c9 Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Sat, 26 Jan 2013 13:17:21 -0600 Subject: Rename a number of libraries and executables to avoid conflicts with KDE4 --- tdeparts/browserinterface.h | 54 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) create mode 100644 tdeparts/browserinterface.h (limited to 'tdeparts/browserinterface.h') diff --git a/tdeparts/browserinterface.h b/tdeparts/browserinterface.h new file mode 100644 index 000000000..82521376f --- /dev/null +++ b/tdeparts/browserinterface.h @@ -0,0 +1,54 @@ +#ifndef __browserinterface_h__ +#define __browserinterface_h__ + +#include +#include + +#include + +namespace KParts +{ + +/** + * The purpose of this interface is to allow a direct communication between + * a KPart and the hosting browser shell (for example Konqueror) . A + * shell implementing this interface can propagate it to embedded kpart + * components by using the setBrowserInterface call of the part's + * KParts::BrowserExtension object. + * + * This interface looks not very rich, but the main functionality is + * implemented using the callMethod method for part->shell + * communication and using Qt properties for allowing a part to + * to explicitly query information from the shell. + * + * Konqueror in particular, as 'reference' implementation, provides + * the following functionality through this interface: + * + * Qt properties: + * + * TQ_PROPERTY( uint historyLength READ historyLength ); + * + * + * Callable methods: + * + * void goHistory( int ); + * + * + */ +class KPARTS_EXPORT BrowserInterface : public TQObject +{ + Q_OBJECT +public: + BrowserInterface( TQObject *parent, const char *name = 0 ); + virtual ~BrowserInterface(); + + /** + * Perform a dynamic invocation of a method in the BrowserInterface + * implementation. Methods are to be implemented as simple Qt slots. + */ + void callMethod( const char *name, const TQVariant &argument ); +}; + +} + +#endif -- cgit v1.2.1