Development/Tutorials/KIO Slaves/Using KIO Slaves in your Program - Revision history

Jan: /* Kompile, link and run it */ Kompile->Compile and use bash syntax highlighting

2011-07-08T12:57:17Z

‎Kompile, link and run it: Kompile->Compile and use bash syntax highlighting

Jan: /* CMakeLists.txt */ use cmake syntax highlighting

2011-07-08T12:56:16Z

‎CMakeLists.txt: use cmake syntax highlighting

Neverendingo: Text replace - "" to ""

2011-06-29T20:52:24Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T20:44:55Z
Text replace - "<code>" to "<syntaxhighlight lang="text">"

				
				
				
				
			
			← Older revision
			Revision as of 20:44, 29 June 2011
			
Line 85:
Line 85:
    
  == CMakeLists.txt ==   == CMakeLists.txt ==
− <code> + <syntaxhighlight lang="text">
  PROJECT( browser )   PROJECT( browser )
  FIND_PACKAGE(KDE4 REQUIRED)   FIND_PACKAGE(KDE4 REQUIRED)



Neverendingo: Text replace - "" to ""

2011-06-29T20:29:17Z
Text replace - "<code cppqt>" to "<syntaxhighlight lang="cpp-qt">"

				
				
				
				
			
			← Older revision
			Revision as of 20:29, 29 June 2011
			
Line 5:
Line 5:
    
  == main.cpp ==   == main.cpp ==
− <code cppqt> + <syntaxhighlight lang="cpp-qt">
  #include <QString>   #include <QString>
  #include <kapplication.h>   #include <kapplication.h>
Line 32:
Line 32:
    
  == browser.h ==     == browser.h ==  
− <code cppqt> + <syntaxhighlight lang="cpp-qt">
  #ifndef KDE4START_H__   #ifndef KDE4START_H__
  #define KDE4START_H__   #define KDE4START_H__
Line 54:
Line 54:
    
  == browser.cpp ==   == browser.cpp ==
− <code cppqt> + <syntaxhighlight lang="cpp-qt">
  #include <kio/scheduler.h>   #include <kio/scheduler.h>
  #include <kurl.h>   #include <kurl.h>



Rakuco: /* The files */ Change method capitalization - dataishere -> dataIsHere
2009-08-18T02:20:12Z
‎The files:  Change method capitalization - dataishere -> dataIsHere

				
				
				
				
			
			← Older revision
			Revision as of 02:20, 18 August 2009
			
Line 48:
Line 48:
     public slots:      public slots:
       void slotButtonClicked();        void slotButtonClicked();
−      void dataishere(KIO::Job *,const QByteArray &); +      void dataIsHere(KIO::Job *,const QByteArray &);
  };   };
  #endif   #endif
Line 73:
Line 73:
     // creating a kioslave      // creating a kioslave
     KIO::TransferJob *job = KIO::get(KUrl("http://www.kde.org"));      KIO::TransferJob *job = KIO::get(KUrl("http://www.kde.org"));
−    connect (job, SIGNAL(  data(KIO::Job *, const QByteArray & )), this, SLOT(dataishere(KIO::Job *,const QByteArray &))); +    connect (job, SIGNAL(  data(KIO::Job *, const QByteArray & )), this, SLOT(dataIsHere(KIO::Job *,const QByteArray &)));
  }   }
    
− void Browser::dataishere(KIO::Job *,const QByteArray & data ) + void Browser::dataIsHere(KIO::Job *,const QByteArray & data )
  {   {
     kDebug() << "data is here";      kDebug() << "data is here";
Line 82:
Line 82:
  }   }
  </code>   </code>
− As discussed, the Browser class does not do a busy wait for the data to arrive from the web. Instead, it uses the http kioslave's signal data by connecting it to the slot dataishere. Dataishere gets the http transmission via its parameter data and just outputs it. That's it - no blocking, no busy wait! + As discussed, the Browser class does not do a busy wait for the data to arrive from the web. Instead, it uses the http kioslave's signal data by connecting it to the slot dataishere. <tt>dataIsHere</tt> gets the http transmission via its parameter data and just outputs it. That's it - no blocking, no busy wait!
    
  == CMakeLists.txt ==   == CMakeLists.txt ==



Rakuco: Add syntax highlighting to the code blocks
2009-05-09T22:36:55Z
Add syntax highlighting to the code blocks

				
				
				
				
			
			← Older revision
			Revision as of 22:36, 9 May 2009
			
Line 5:
Line 5:
    
  == main.cpp ==   == main.cpp ==
− <pre> + <code cppqt>
  #include <QString>   #include <QString>
  #include <kapplication.h>   #include <kapplication.h>
Line 28:
Line 28:
     khello.exec();      khello.exec();
  }   }
− </pre> + </code>
  The purpose of main is to create a Browser instance and hold it open while the KDE event loop is running (i.e. the KDE program is ready).   The purpose of main is to create a Browser instance and hold it open while the KDE event loop is running (i.e. the KDE program is ready).
    
  == browser.h ==     == browser.h ==  
− <pre> + <code cppqt>
  #ifndef KDE4START_H__   #ifndef KDE4START_H__
  #define KDE4START_H__   #define KDE4START_H__
Line 51:
Line 51:
  };   };
  #endif   #endif
− </pre> + </code>
    
  == browser.cpp ==   == browser.cpp ==
− <pre> + <code cppqt>
  #include <kio/scheduler.h>   #include <kio/scheduler.h>
  #include <kurl.h>   #include <kurl.h>
Line 81:
Line 81:
     kDebug() << data;      kDebug() << data;
  }   }
− </pre> + </code>
  As discussed, the Browser class does not do a busy wait for the data to arrive from the web. Instead, it uses the http kioslave's signal data by connecting it to the slot dataishere. Dataishere gets the http transmission via its parameter data and just outputs it. That's it - no blocking, no busy wait!   As discussed, the Browser class does not do a busy wait for the data to arrive from the web. Instead, it uses the http kioslave's signal data by connecting it to the slot dataishere. Dataishere gets the http transmission via its parameter data and just outputs it. That's it - no blocking, no busy wait!
    
  == CMakeLists.txt ==   == CMakeLists.txt ==
− <pre> + <code>
  PROJECT( browser )   PROJECT( browser )
  FIND_PACKAGE(KDE4 REQUIRED)   FIND_PACKAGE(KDE4 REQUIRED)
Line 99:
Line 99:
    
  install(TARGETS browser  DESTINATION ${BIN_INSTALL_DIR} )   install(TARGETS browser  DESTINATION ${BIN_INSTALL_DIR} )
− </pre> + </code>
    
  = Kompile, link and run it =   = Kompile, link and run it =
    cmake . && make && ./browser     cmake . && make && ./browser



Dhaumann: Use kioslaves in your program moved to Development/Tutorials/KIO Slaves/Using KIO Slaves in your Program: subpage
2008-09-23T22:04:49Z
Use kioslaves in your program moved to Development/Tutorials/KIO Slaves/Using KIO Slaves in your Program: subpage

			
			← Older revision
			Revision as of 22:04, 23 September 2008
			


Tstaerk: New page: In this chapter we write a simple browser to show how easy it is to use kioslaves in KDE 4. The browser will download the page www.kde.org and show the html sourcecode. It will not render ...
2008-09-23T19:21:59Z
New page: In this chapter we write a simple browser to show how easy it is to use kioslaves in KDE 4. The browser will download the page www.kde.org and show the html sourcecode. It will not render ...
New page
In this chapter we write a simple browser to show how easy it is to use kioslaves in KDE 4. The browser will download the page www.kde.org and show the html sourcecode. It will not render html - remember this is a programming demo.

The purpose of kioslaves is to have access to a given storage or data representation without the need for blocking calls. This is solved via QT's signal/slot mechanism: Once the data has arrived, e.g. from a web page, it triggers a signal. The signal is connected to the respective slot and can start processing the data.



= The files =



== main.cpp ==

<pre>

#include <QString>

#include <kapplication.h>

#include <kaboutdata.h>

#include <klocalizedstring.h>

#include <kmessagebox.h>

#include <kcmdlineargs.h>

#include <KMainWindow>

#include <browser.h>



int main (int argc, char *argv[])

{

  // KAboutData (const QByteArray &appName, const QByteArray &catalogName, const KLocalizedString &programName, const QByteArray &version,

  const QByteArray& ba=QByteArray("test");

  const KLocalizedString name=ki18n("myName");

  KAboutData aboutData( ba, ba, name, ba, name);

  KCmdLineArgs::init( argc, argv, &aboutData );

  KApplication khello;



  Browser *mw = new Browser();

  mw->show();

  khello.exec();

}

</pre>

The purpose of main is to create a Browser instance and hold it open while the KDE event loop is running (i.e. the KDE program is ready).



== browser.h == 

<pre>

#ifndef KDE4START_H__

#define KDE4START_H__



#include <kmainwindow.h>

#include <kio/scheduler.h>

#include <kurl.h>

#include <kio/jobclasses.h>



class Browser : public QWidget

{

  Q_OBJECT

  public:

    Browser();

  public slots:

    void slotButtonClicked();

    void dataishere(KIO::Job *,const QByteArray &);

};

#endif

</pre>



== browser.cpp ==

<pre>

#include <kio/scheduler.h>

#include <kurl.h>

#include <kio/jobclasses.h>

#include <kdebug.h>

#include <browser.h>



class TransferJob;



Browser::Browser() : QWidget(NULL)

{

  slotButtonClicked();

}



void Browser::slotButtonClicked()

{

  kDebug() << "entering function";

  // creating a kioslave

  KIO::TransferJob *job = KIO::get(KUrl("http://www.kde.org"));

  connect (job, SIGNAL(  data(KIO::Job *, const QByteArray & )), this, SLOT(dataishere(KIO::Job *,const QByteArray &)));

}



void Browser::dataishere(KIO::Job *,const QByteArray & data )

{

  kDebug() << "data is here";

  kDebug() << data;

}

</pre>

As discussed, the Browser class does not do a busy wait for the data to arrive from the web. Instead, it uses the http kioslave's signal data by connecting it to the slot dataishere. Dataishere gets the http transmission via its parameter data and just outputs it. That's it - no blocking, no busy wait!



== CMakeLists.txt ==

<pre>

PROJECT( browser )

FIND_PACKAGE(KDE4 REQUIRED)

INCLUDE_DIRECTORIES( ${KDE4_INCLUDES} . )





SET(kde4startSources main.cpp browser.cpp )





KDE4_ADD_EXECUTABLE(browser ${kde4startSources} )



TARGET_LINK_LIBRARIES(browser ${KDE4_KDEUI_LIBS} ${KDE4_KPARTS_LIBS} )



install(TARGETS browser  DESTINATION ${BIN_INSTALL_DIR} )

</pre>



= Kompile, link and run it =

 cmake . && make && ./browser

@@ Line 101: / Line 101: @@
 </syntaxhighlight>
-= Kompile, link and run it =
+= Compile, link and run it =
- cmake . && make && ./browser
+<syntaxhighlight lang="bash">