Development/Tutorials/Kross/Hello World - Revision history

Neverendingo: Text replace - "" to ""

2011-06-30T10:20:01Z

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

Neverendingo: /* CMakeLists.txt */

2011-06-29T19:49:12Z

‎CMakeLists.txt

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


2011-06-29T19:48:46Z
Text replace - "<code bash>" to "<syntaxhighlight lang="bash">"

				
				
				
				
			
			← Older revision
			Revision as of 19:48, 29 June 2011
			
Line 14:
Line 14:
  If you have already set up your environment as described in [[Getting Started/Build]], you can already use kross with the javascript language. You can choose optionally to install support for python and ruby from kdebindings. Either checkout and build kdebindings, or just the kdebindings/python and kdebindings/ruby subdirectories.   If you have already set up your environment as described in [[Getting Started/Build]], you can already use kross with the javascript language. You can choose optionally to install support for python and ruby from kdebindings. Either checkout and build kdebindings, or just the kdebindings/python and kdebindings/ruby subdirectories.
    
− <code bash> + <syntaxhighlight lang="bash">
  cd KDE   cd KDE
  svn co -N kdebindings   svn co -N kdebindings



Neverendingo: Text replace - "" to ""

2011-06-29T19:47:21Z
Text replace - "<code javascript>" to "<syntaxhighlight lang="javascript">"

				
				
				
				
			
			← Older revision
			Revision as of 19:47, 29 June 2011
			
Line 263:
Line 263:
  JavaScript sample that does the same like above but using the JavaScript language rather then Python.   JavaScript sample that does the same like above but using the JavaScript language rather then Python.
    
− <code javascript> + <syntaxhighlight lang="javascript">
  function reverseString(s){   function reverseString(s){
       return s.split("").reverse().join("");        return s.split("").reverse().join("");



Neverendingo: Text replace - "" to ""

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

				
				
				
				
			
			← Older revision
			Revision as of 19:43, 29 June 2011
			
Line 245:
Line 245:
  For example, edit krosshello.py file to include the following:   For example, edit krosshello.py file to include the following:
    
− <code python> + <syntaxhighlight lang="python">
  #!/usr/bin/env kross   #!/usr/bin/env kross
    
Line 255:
Line 255:
  It is also possible to call a function and return the result to the application.   It is also possible to call a function and return the result to the application.
    
− <code python> + <syntaxhighlight lang="python">
  def reverseString(s):   def reverseString(s):
       s = s[::-1]        s = s[::-1]



Neverendingo: Text replace - "" to ""
2011-06-29T19:42:19Z
Text replace - "</code>" to "</syntaxhighlight>"

				
				
				
				
			
			← Older revision
			Revision as of 19:42, 29 June 2011
			
Line 21:
Line 21:
  svn up ruby   svn up ruby
  cmakekde   cmakekde
− </code> + </syntaxhighlight>
    
  == Hello World ==   == Hello World ==
Line 71:
Line 71:
       return app.exec();        return app.exec();
  }   }
− </code> + </syntaxhighlight>
    
  === mainwindow.h ===   === mainwindow.h ===
Line 100:
Line 100:
    
  #endif   #endif
− </code> + </syntaxhighlight>
    
  === mainwindow.cpp ===   === mainwindow.cpp ===
Line 191:
Line 191:
     action.trigger();      action.trigger();
  }   }
− </code> + </syntaxhighlight>
    
  === CMakeLists.txt ===   === CMakeLists.txt ===
Line 207:
Line 207:
  kde4_add_executable(krosshello ${krosshello_SRCS})   kde4_add_executable(krosshello ${krosshello_SRCS})
  target_link_libraries(krosshello ${KDE4_KDEUI_LIBS} ${KDE4_KROSSUI_LIBS})   target_link_libraries(krosshello ${KDE4_KDEUI_LIBS} ${KDE4_KROSSUI_LIBS})
− </code> + </syntaxhighlight>
    
  == Using separate script files ==   == Using separate script files ==
Line 239:
Line 239:
    
     action.trigger();      action.trigger();
− </code> + </syntaxhighlight>
    
  It is no longer neccessary to set the interpreter for the action explicitly. Kross chooses the correct interpreter based on the filename given in <tt>setFile()</tt>.   It is no longer neccessary to set the interpreter for the action explicitly. Kross chooses the correct interpreter based on the filename given in <tt>setFile()</tt>.
Line 251:
Line 251:
    
  MyLabel.text = "Hello from inside a python file."   MyLabel.text = "Hello from inside a python file."
− </code> + </syntaxhighlight>
    
  It is also possible to call a function and return the result to the application.   It is also possible to call a function and return the result to the application.
Line 259:
Line 259:
       s = s[::-1]        s = s[::-1]
       return s        return s
− </code> + </syntaxhighlight>
    
  JavaScript sample that does the same like above but using the JavaScript language rather then Python.   JavaScript sample that does the same like above but using the JavaScript language rather then Python.
Line 267:
Line 267:
       return s.split("").reverse().join("");        return s.split("").reverse().join("");
  }   }
− </code> + </syntaxhighlight>
    
  Add the above to krosshello.js or krosshello.py and edit the mainwindow.cpp again to include the following after action.trigger():   Add the above to krosshello.js or krosshello.py and edit the mainwindow.cpp again to include the following after action.trigger():
Line 276:
Line 276:
  QVariant result = action.callFunction("reverseString", arguments);   QVariant result = action.callFunction("reverseString", arguments);
  lblHello->setText(result.toString());   lblHello->setText(result.toString());
− </code> + </syntaxhighlight>
    
  Usually it will not make sense to use callFunction in an application, but instead connect signals and slots directly between the application and the script.   Usually it will not make sense to use callFunction in an application, but instead connect signals and slots directly between the application and the script.
    
  This is the more practical way to use kross, and is described in more detail at [[Development/Tutorials/Kross/Connecting_Signals and slots in Kross|Connecting Signals and slots in Kross]].   This is the more practical way to use kross, and is described in more detail at [[Development/Tutorials/Kross/Connecting_Signals and slots in Kross|Connecting Signals and slots in Kross]].



Neverendingo: Text replace - "" to ""

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

				
				
				
				
			
			← Older revision
			Revision as of 19:38, 29 June 2011
			
Line 34:
Line 34:
  The main.cpp contains the entry-point for our sample application.   The main.cpp contains the entry-point for our sample application.
    
− <code cpp> + <syntaxhighlight lang="cpp">
  // First some Qt and KDE includes   // First some Qt and KDE includes
  #include <QString>   #include <QString>
Line 77:
Line 77:
  The main window class that is used to display the combobox which contains a list of available interpreters and the label which we like to change from within scripting code.   The main window class that is used to display the combobox which contains a list of available interpreters and the label which we like to change from within scripting code.
    
− <code cpp> + <syntaxhighlight lang="cpp">
  #ifndef MAINWINDOW_H   #ifndef MAINWINDOW_H
  #define MAINWINDOW_H   #define MAINWINDOW_H
Line 106:
Line 106:
  This code creates a simple dialog with a combobox showing available interpreters along with a label for displaying a message. The kross/core/manager.h and kross/core/action.h are included to provide kross functionality, which is invoked when a selection is made on the combobox. The code below makes the lblHello label available to scripts as a MyLabel object, and executes different code depending on the interpreter chosen.   This code creates a simple dialog with a combobox showing available interpreters along with a label for displaying a message. The kross/core/manager.h and kross/core/action.h are included to provide kross functionality, which is invoked when a selection is made on the combobox. The code below makes the lblHello label available to scripts as a MyLabel object, and executes different code depending on the interpreter chosen.
    
− <code cpp> + <syntaxhighlight lang="cpp">
  #include <QVBoxLayout>   #include <QVBoxLayout>
  #include <QDebug>   #include <QDebug>
Line 213:
Line 213:
  The next step is to extract the scripts into separate files. This has the obvious advantage of being editable without being recompiled. Edit the <tt>MainWindow::interpreterActivated</tt> in <tt>mainwindow.cpp</tt> to the following:   The next step is to extract the scripts into separate files. This has the obvious advantage of being editable without being recompiled. Edit the <tt>MainWindow::interpreterActivated</tt> in <tt>mainwindow.cpp</tt> to the following:
    
− <code cpp> + <syntaxhighlight lang="cpp">
  void MainWindow::interpreterActivated(const QString &strSelectedInterpreter)   void MainWindow::interpreterActivated(const QString &strSelectedInterpreter)
  {   {
Line 271:
Line 271:
  Add the above to krosshello.js or krosshello.py and edit the mainwindow.cpp again to include the following after action.trigger():   Add the above to krosshello.js or krosshello.py and edit the mainwindow.cpp again to include the following after action.trigger():
    
− <code cpp> + <syntaxhighlight lang="cpp">
  QVariantList arguments;   QVariantList arguments;
  arguments << "Hello World";   arguments << "Hello World";





Odysseus at 23:13, 19 March 2011
2011-03-19T23:13:31Z


				
				
				
				
			
			← Older revision
			Revision as of 23:13, 19 March 2011
			
Line 12:
Line 12:
  == Additional Bindings ==   == Additional Bindings ==
    
− If you have already set up your environment as described in [[Getting Started/Build]], you can already use kross with the javascript language. You can choose optionally to install support for python and ruby from kdebindings. Either checkout and build kdebindings, or just the kdebindings/python and kdebindings/ruby subdirectories ([[Getting_Started/Build/KDE4#Installing_a_subset_of_a_module|Installing_a_subset_of_a_module]]). + If you have already set up your environment as described in [[Getting Started/Build]], you can already use kross with the javascript language. You can choose optionally to install support for python and ruby from kdebindings. Either checkout and build kdebindings, or just the kdebindings/python and kdebindings/ruby subdirectories.
    
  <code bash>   <code bash>



Odysseus: /* Additional Bindings */
2011-03-19T23:07:25Z
‎Additional Bindings

				
				
				
				
			
			← Older revision
			Revision as of 23:07, 19 March 2011
			
Line 12:
Line 12:
  == Additional Bindings ==   == Additional Bindings ==
    
− If you have already set up your environment as described in [[Getting Started/Build/KDE4]], you can already use kross with the javascript language. You can choose optionally to install support for python and ruby from kdebindings. Either checkout and build kdebindings, or just the kdebindings/python and kdebindings/ruby subdirectories ([[Getting_Started/Build/KDE4#Installing_a_subset_of_a_module|Installing_a_subset_of_a_module]]). + If you have already set up your environment as described in [[Getting Started/Build]], you can already use kross with the javascript language. You can choose optionally to install support for python and ruby from kdebindings. Either checkout and build kdebindings, or just the kdebindings/python and kdebindings/ruby subdirectories ([[Getting_Started/Build/KDE4#Installing_a_subset_of_a_module|Installing_a_subset_of_a_module]]).
    
  <code bash>   <code bash>





Tampakrap: typo
2009-02-07T18:01:30Z
typo

				
				
				
				
			
			← Older revision
			Revision as of 18:01, 7 February 2009
			
Line 15:
Line 15:
    
  <code bash>   <code bash>
− cs KDE + cd KDE
  svn co -N kdebindings   svn co -N kdebindings
  cd kdebindings   cd kdebindings

@@ Line 197: / Line 197: @@
 This CMakeLists.txt file is used to build our small example using cmake.
-<syntaxhighlight lang="make">
+<syntaxhighlight lang="cmake">
 project (krosshello)

@@ Line 197: / Line 197: @@
 This CMakeLists.txt file is used to build our small example using cmake.
-<code>
+<syntaxhighlight lang="make">
 project (krosshello)