Development/Tutorials/Kross/Call Functions in Kross - Revision history

Neverendingo: Text replace - "" to ""

2011-06-30T10:19:57Z

Text replace - "<syntaxhighlight lang="make">" to "<syntaxhighlight lang="cmake">"

Neverendingo: /* Testscriptfile.js */

2011-06-29T19:45:53Z

‎Testscriptfile.js

Neverendingo: /* CMakeLists.txt */

2011-06-29T19:45:20Z

‎CMakeLists.txt

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


2011-06-29T19:43:26Z
Text replace - "<code python>" to "<syntaxhighlight lang="python">"

				
				
				
				
			
			← Older revision
			Revision as of 19:43, 29 June 2011
			
Line 200:
Line 200:
  The Testscriptfile.py Python file does provide us the reverseString scripting function.   The Testscriptfile.py Python file does provide us the reverseString scripting function.
    
− <code python> + <syntaxhighlight lang="python">
  def reverseString(lineedit, s):   def reverseString(lineedit, s):
       print "reverseString lineedit=%s s=%s" % (lineedit,s)        print "reverseString lineedit=%s s=%s" % (lineedit,s)

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

2011-06-29T19:42:18Z

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

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


2011-06-29T19:38:50Z
Text replace - "<code cpp>" to "<syntaxhighlight lang="cpp">"

				
				
				
				
			
			← Older revision
			Revision as of 19:38, 29 June 2011
			
Line 27:
Line 27:
  The main.cpp does create the sample application and shows the mainwindow instance.   The main.cpp does create the sample application and shows the mainwindow instance.
    
− <code cpp> + <syntaxhighlight lang="cpp">
  #include <QString>   #include <QString>
  #include <KApplication>   #include <KApplication>
Line 60:
Line 60:
  This is the main windows class which defines some displayed widgets for our small sample application.   This is the main windows class which defines some displayed widgets for our small sample application.
    
− <code cpp> + <syntaxhighlight lang="cpp">
  #ifndef MAINWINDOW_H   #ifndef MAINWINDOW_H
  #define MAINWINDOW_H   #define MAINWINDOW_H
Line 93:
Line 93:
  The implementation of the main window functionality. We are displaying a QLineEdit that will be passed as first argument to a scripting function named "reverseString". Those function returns a string that will then displayed in a QLabel. Just like at the [[Development/Tutorials/Kross/Hello World|Kross Hello World]] tutorial, we also display a QComboBox that does allow to choose an interpreter.   The implementation of the main window functionality. We are displaying a QLineEdit that will be passed as first argument to a scripting function named "reverseString". Those function returns a string that will then displayed in a QLabel. Just like at the [[Development/Tutorials/Kross/Hello World|Kross Hello World]] tutorial, we also display a QComboBox that does allow to choose an interpreter.
    
− <code cpp> + <syntaxhighlight lang="cpp">
  #include "mainwindow.h"   #include "mainwindow.h"
  #include <QVBoxLayout>   #include <QVBoxLayout>



Mvyskocil: Fix a typo in MainWindow::interpreterActivated
2008-03-13T16:13:51Z
Fix a typo in MainWindow::interpreterActivated

				
				
				
				
			
			← Older revision
			Revision as of 16:13, 13 March 2008
			
Line 133:
Line 133:
       // this time we are using external script files.        // this time we are using external script files.
       QString filename;        QString filename;
−      if(intpr == "python") // Python backend +      if(interpr == "python") // Python backend
           filename = "Testscriptfile.py";            filename = "Testscriptfile.py";
−      else if(intpr == "javascript") // JavaScript backend +      else if(interpr == "javascript") // JavaScript backend
           filename = "Testscriptfile.js";            filename = "Testscriptfile.js";
       else { // no other sample script files        else { // no other sample script files



Dipesh at 23:59, 17 January 2008
2008-01-17T23:59:03Z


				
				
				
				
			
			← Older revision
			Revision as of 23:59, 17 January 2008
			
Line 4:
Line 4:
  needed is to emit a signal and behind the scene the arguments will be     needed is to emit a signal and behind the scene the arguments will be  
  translated and a possible defined scripting function got called. A good example here is [[Development/Tutorials/SuperKaramba|SuperKaramba]] which uses the signal+slot rather then callFunction() way. All it defines is the rather huge class that inherits QObject ([http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/src/karambainterface.h?view=markup karambainterface.h]). The signals within that class are transparent mapped to scripting functions (e.g. [http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/examples/template.py?view=markup| template.py] and [http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/examples/template.js?view=markup| template.js]) while the slots are then callable from within the scripting code.   translated and a possible defined scripting function got called. A good example here is [[Development/Tutorials/SuperKaramba|SuperKaramba]] which uses the signal+slot rather then callFunction() way. All it defines is the rather huge class that inherits QObject ([http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/src/karambainterface.h?view=markup karambainterface.h]). The signals within that class are transparent mapped to scripting functions (e.g. [http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/examples/template.py?view=markup| template.py] and [http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/examples/template.js?view=markup| template.js]) while the slots are then callable from within the scripting code.
− Signals and slots are faster and more type-safe then the in this tutorial used [http://api.kde.org/4.x-api/kdelibs-apidocs/kross/html/classKross_1_1Action.html||Kross::Action::callFunction()] though callFunction() and functionNames() are more flexible. + Signals and slots are faster and more type-safe then the in this tutorial used callFunction() (see also the [http://api.kde.org/4.x-api/kdelibs-apidocs/kross/html/classKross_1_1Action.html Kross::Action] class).
    
  == The C++ Code ==   == The C++ Code ==



Dipesh at 23:54, 17 January 2008
2008-01-17T23:54:09Z


				
				
				
				
			
			← Older revision
			Revision as of 23:54, 17 January 2008
			
Line 4:
Line 4:
  needed is to emit a signal and behind the scene the arguments will be     needed is to emit a signal and behind the scene the arguments will be  
  translated and a possible defined scripting function got called. A good example here is [[Development/Tutorials/SuperKaramba|SuperKaramba]] which uses the signal+slot rather then callFunction() way. All it defines is the rather huge class that inherits QObject ([http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/src/karambainterface.h?view=markup karambainterface.h]). The signals within that class are transparent mapped to scripting functions (e.g. [http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/examples/template.py?view=markup| template.py] and [http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/examples/template.js?view=markup| template.js]) while the slots are then callable from within the scripting code.   translated and a possible defined scripting function got called. A good example here is [[Development/Tutorials/SuperKaramba|SuperKaramba]] which uses the signal+slot rather then callFunction() way. All it defines is the rather huge class that inherits QObject ([http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/src/karambainterface.h?view=markup karambainterface.h]). The signals within that class are transparent mapped to scripting functions (e.g. [http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/examples/template.py?view=markup| template.py] and [http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/examples/template.js?view=markup| template.js]) while the slots are then callable from within the scripting code.
− Signals and slots are faster and more type-safe then the in this tutorial used [http://api.kde.org/4.x-api/kdelibs-apidocs/kross/html/classKross_1_1Action.html|Kross::Action::callFunction()] though the usage of callFunction() and functionNames() are more flexible. + Signals and slots are faster and more type-safe then the in this tutorial used [http://api.kde.org/4.x-api/kdelibs-apidocs/kross/html/classKross_1_1Action.html||Kross::Action::callFunction()] though callFunction() and functionNames() are more flexible.
    
  == The C++ Code ==   == The C++ Code ==



Dipesh at 23:52, 17 January 2008
2008-01-17T23:52:38Z


				
				
				
				
			
			← Older revision
			Revision as of 23:52, 17 January 2008
			
Line 4:
Line 4:
  needed is to emit a signal and behind the scene the arguments will be     needed is to emit a signal and behind the scene the arguments will be  
  translated and a possible defined scripting function got called. A good example here is [[Development/Tutorials/SuperKaramba|SuperKaramba]] which uses the signal+slot rather then callFunction() way. All it defines is the rather huge class that inherits QObject ([http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/src/karambainterface.h?view=markup karambainterface.h]). The signals within that class are transparent mapped to scripting functions (e.g. [http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/examples/template.py?view=markup| template.py] and [http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/examples/template.js?view=markup| template.js]) while the slots are then callable from within the scripting code.   translated and a possible defined scripting function got called. A good example here is [[Development/Tutorials/SuperKaramba|SuperKaramba]] which uses the signal+slot rather then callFunction() way. All it defines is the rather huge class that inherits QObject ([http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/src/karambainterface.h?view=markup karambainterface.h]). The signals within that class are transparent mapped to scripting functions (e.g. [http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/examples/template.py?view=markup| template.py] and [http://websvn.kde.org/trunk/KDE/kdeutils/superkaramba/examples/template.js?view=markup| template.js]) while the slots are then callable from within the scripting code.
−   + Signals and slots are faster and more type-safe then the in this tutorial used [http://api.kde.org/4.x-api/kdelibs-apidocs/kross/html/classKross_1_1Action.html|Kross::Action::callFunction()] though the usage of callFunction() and functionNames() are more flexible.
− Signals and slots are faster and more type-safe then the in this tutorial used [[http://api.kde.org/4.x-api/kdelibs-apidocs/kross/html/classKross_1_1Action.html|Kross::Action::callFunction()]]. + 
    
  == The C++ Code ==   == The C++ Code ==

@@ Line 14: / Line 14: @@
 We are using cmake to build our small sample project. The CMakeLists.txt file looks like;
-<syntaxhighlight lang="make">
+<syntaxhighlight lang="cmake">
 project (krosshello)
 find_package(KDE4 REQUIRED)

@@ Line 183: / Line 183: @@
 The Testscriptfile.js JavaScript file does provide us the reverseString scripting function.
-<code javascript>
+<syntaxhighlight lang="javascript">
 function reverseString(lineedit, s)
+{

@@ Line 14: / Line 14: @@
 We are using cmake to build our small sample project. The CMakeLists.txt file looks like;
-<code>
+<syntaxhighlight lang="make">
 project (krosshello)
 find_package(KDE4 REQUIRED)

@@ Line 21: / Line 21: @@
 kde4_add_executable(krosshello ${krosshello_SRCS})
 target_link_libraries(krosshello ${KDE4_KDEUI_LIBS} ${KDE4_KROSSUI_LIBS})
-</code>
+</syntaxhighlight>
 === main.cpp ===
@@ Line 54: / Line 54: @@
      return app.exec();
+}
-</code>
+</syntaxhighlight>
 === mainwindow.h ===
@@ Line 87: / Line 87: @@
 #endif
-</code>
+</syntaxhighlight>
 === mainwindow.cpp ===
@@ Line 173: / Line 173: @@
      lblMessage->setText(result.toString());
+}
-</code>
+</syntaxhighlight>
 == The Script Files ==
@@ Line 194: / Line 194: @@
      return s.split("").reverse().join("");
+}
-</code>
+</syntaxhighlight>
 === Testscriptfile.py ===
@@ Line 206: / Line 206: @@
      lineedit.setText(s)
      return s[::-1]
-</code>
+</syntaxhighlight>