/***************************************************************************
                            KCModule.h -  description
                             -------------------
    begin                : Fri Mar  8 13:55:08 2002
    copyright            : (C) 2000-2002 Lost Highway Ltd. All rights reserved.
    email                : Lost_Highway@tipitina.demon.co.uk
    generated by         : duke@tipitina on Fri Mar  8 13:55:08 2002, using kalyptus 0.9.
 ***************************************************************************/

/***************************************************************************
 *                                                                         *
 *   This library is free software; you can redistribute it and/or modify  *
 *   it under the terms of the GNU Library General Public License as       *
 *   published by the Free Software Foundation; either version 2 of the    *
 *   License, or (at your option) any later version.                       *
 *                                                                         *
 ***************************************************************************/

#ifndef KCMODULE_H
#define KCMODULE_H

#include <Foundation/NSObject.h>
#include <Foundation/NSString.h>
#include <qtobjc/QWidget.h>

/**

 The base class for control center modules.

 Starting from KDE 2.0, control center modules are realized as shared
 libraries that are loaded into the control center at runtime.

 The module in principle is a simple widget displaying the
 item to be changed. The module has a very small interface.

 All the necessary glue logic and the GUI bells and whistles
 are provided by the control center and must not concern
 the module author.

 To write a config module, you have to create a library
 that contains at one factory function like this:

 <pre>
  #-include <kgenericfactory.h>

 typedef KGenericFactory<YourKCModule, QWidget> YourKCModuleFactory;
 K_EXPORT_COMPONENT_FACTORY( yourLibName, YourKCModuleFactory );
 </pre>

 See kdebase/kcontrol/HOWTO for more detailed documentation.

 @author Matthias Hoelzer-Kluepfel <hoelzer@kde.org>
 
 @short 
 The base class for control center modules.
*/
@class KAboutData; 

@class KInstance; 

@interface KCModule : QWidget 
- initWithWidget: (QWidget *)parent name: (NSString *)name args: (NSArray *)args;
- init;
- initWithInstance: (KInstance*)instance parent: (QWidget *)parent args: (NSArray *)args;
- initWithInstance: (KInstance*)instance ;
- (void) dealloc;

/** 
 Load the configuration data into the module.

 The load method sets the user interface elements of the
 module to reflect the current settings stored in the
 configuration files.

 This method is invoked whenever the module should read its configuration
 (most of the times from a config file) and update the user interface.
 This happens when the user clicks the "Reset" button in the control
 center, to undo all of his changes and restore the currently valid
 settings. NOTE that this is not called after the modules is loaded,
 so you probably want to call this method in the constructor.
   
*/
- load;

/** 
 Save the configuration data.

 The save method stores the config information as shown
 in the user interface in the config files.

 If necessary, this method also updates the running system,
 e.g. by restarting applications.

 save is called when the user clicks "Apply" or "Ok".
   
*/
- save;

/** 
 Sets the configuration to sensible default values.

 This method is called when the user clicks the "Default"
 button. It should set the display to useful values.
   
*/
- defaults;

/** 
 Set the configuration to system default values.

 This method is called when the user clicks the "System-Default"
 button. It should set the display to the system default values.

 NOTE: The default behaviour is to call -defaults.
   
*/
- sysdefaults;

/** 
 Return a quick-help text.

 This method is called when the module is docked.
 The quick-help text should contain a short description of the module and
 links to the module's help files. You can use QML formating tags in the text.

 NOTE: Please make sure the quick help text gets translated (use -i18n).
   
*/
- (NSString *) quickHelp;

/** 
 Returns a the KAboutData for this module
 This is generally only called for the KBugReport.
 Override and have it return a pointer to a constant
   
*/
- (KAboutData*) aboutData;

/** 
 Indicate which buttons will be used.

 The return value is a value or'ed together from
 the Button enumeration type.

*/
- (int) buttons;

/** 
 Get the RootOnly message for this module.

 When the module must be run as root, or acts differently
 for root and a normal user, it is sometimes useful to
 customize the message that appears at the top of the module
 when used as a normal user. This function returns this
 customized message. If none has been set, a default message
 will be used.

*/
- (NSString *) rootOnlyMsg;

/** 
 Tell if KControl should show a RootOnly message when run as
 a normal user.

 In some cases, the module don't want a RootOnly message to
 appear (for example if it has already one). This function
 tells KControl if a RootOnly message should be shown

*/
- (BOOL) useRootOnlyMsg;
- (KInstance*) instance;

/** 
 Sets the buttons to display.

 Help: shows a "Help" button.
 Default: shows a "Use Defaults" button
 Apply: in kcontrol this will show an "Apply" and "Reset" button
        in kcmshell this will show an "Ok", "Apply" and "Cancel" button

 If Apply is not specified, kcmshell will show a "Close" button.

*/
- setButtons: (int)btn;

/** 
 Sets the RootOnly message.

 This message will be shown at the top of the module of the
 corresponding desktop file contains the line X-KDE-RootOnly=true.
 If no message is set, a default one will be used.

*/
- setRootOnlyMsg: (NSString *)msg;

/** 
 Change wether or not the RootOnly message should be shown.

 Following the value of @p on, the RootOnly message will be
 shown or not.

*/
- setUseRootOnlyMsg: (BOOL)on;
+ (int) Help;
+ (int) Default;
+ (int) Apply;
+ (int) Reset;
+ (int) Cancel;
+ (int) Ok;
+ (int) SysDefault;
@end

/** Override these methods in subclasses of KCModule to customise event handling behaviour */
@protocol KCModuleEventHandling
- keyPressEvent:(QKeyEvent*) arg1;
- keyReleaseEvent:(QKeyEvent*) arg1;
- focusOutEvent:(QFocusEvent*) arg1;
- childEvent:(QChildEvent*) arg1;
- dragMoveEvent:(QDragMoveEvent*) arg1;
- leaveEvent:(QEvent*) arg1;
- tabletEvent:(QTabletEvent*) arg1;
- showEvent:(QShowEvent*) arg1;
- contextMenuEvent:(QContextMenuEvent*) arg1;
- mousePressEvent:(QMouseEvent*) arg1;
- imComposeEvent:(QIMEvent*) arg1;
- customEvent:(QCustomEvent*) arg1;
- mouseReleaseEvent:(QMouseEvent*) arg1;
- mouseDoubleClickEvent:(QMouseEvent*) arg1;
- dragLeaveEvent:(QDragLeaveEvent*) arg1;
- enterEvent:(QEvent*) arg1;
- focusInEvent:(QFocusEvent*) arg1;
- imEndEvent:(QIMEvent*) arg1;
- dropEvent:(QDropEvent*) arg1;
- dragEnterEvent:(QDragEnterEvent*) arg1;
- mouseMoveEvent:(QMouseEvent*) arg1;
- moveEvent:(QMoveEvent*) arg1;
- wheelEvent:(QWheelEvent*) arg1;
- hideEvent:(QHideEvent*) arg1;
- imStartEvent:(QIMEvent*) arg1;
- closeEvent:(QCloseEvent*) arg1;
- paintEvent:(QPaintEvent*) arg1;
- timerEvent:(QTimerEvent*) arg1;
- resizeEvent:(QResizeEvent*) arg1;
@end


#endif
