Development/Tutorials/Kross/Connecting Signals and slots in Kross - Revision history

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 172:
Line 172:
  Now follows a javascript function that converts the string to [http://en.wikipedia.org/wiki/Pig_Latin pig latin]:   Now follows a javascript function that converts the string to [http://en.wikipedia.org/wiki/Pig_Latin pig latin]:
    
− <code javascript> + <syntaxhighlight lang="javascript">
  function textChanged(text)   function textChanged(text)
  {   {



Neverendingo: /* krossSigsSlots.js */
2011-06-29T19:46:20Z
‎krossSigsSlots.js

				
				
				
				
			
			← Older revision
			Revision as of 19:46, 29 June 2011
			
Line 136:
Line 136:
  This script does the same as the script above but using the JavaScript scripting language.   This script does the same as the script above but using the JavaScript scripting language.
    
− <code javascript> + <syntaxhighlight lang="javascript">
  function reverseString(s){   function reverseString(s){
       MyLabel.text = s.split("").reverse().join("");        MyLabel.text = 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 119:
Line 119:
  This script catches the textChanged SIGNAL of the QLineEdit, and connects it to a simple python function to reverse the string in the QLineEdit and display it in the QLabel.   This script catches the textChanged SIGNAL of the QLineEdit, and connects it to a simple python function to reverse the string in the QLineEdit and display it in the QLabel.
    
− <code python> + <syntaxhighlight lang="python">
  #!/usr/bin/env kross   #!/usr/bin/env kross
    
Line 162:
Line 162:
  === Simplified scripts ===   === Simplified scripts ===
  The following python code provides a function that reverses the string:   The following python code provides a function that reverses the string:
− <code python> + <syntaxhighlight lang="python">
  import MyLabel   import MyLabel
    
Line 194:
Line 194:
  in c++ code. To illustrate this, change the python script to emit the setEnabled(bool) signal of the QCombobox:   in c++ code. To illustrate this, change the python script to emit the setEnabled(bool) signal of the QCombobox:
    
− <code python> + <syntaxhighlight lang="python">
  #!/usr/bin/env kross   #!/usr/bin/env kross
    



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 46:
Line 46:
    
  #endif   #endif
− </code> + </syntaxhighlight>
    
  === mainwindow.cpp ===   === mainwindow.cpp ===
Line 112:
Line 112:
     action->trigger();      action->trigger();
  }   }
− </code> + </syntaxhighlight>
    
  The changes are addition of a text entry field and the reorganisation of logic handling the Kross::Action. Note also that there is no code in mainwindow.cpp to set the label, as there was in the previous tutorial. Instead, Objects are simply made available to the scripting interface through the <tt>action->addObject</tt> calls, without any knowledge of what the script will use them for. This removes the need to know at the time of writing the application what function the scripts will perform, and is therefore suited to a plugin interface.   The changes are addition of a text entry field and the reorganisation of logic handling the Kross::Action. Note also that there is no code in mainwindow.cpp to set the label, as there was in the previous tutorial. Instead, Objects are simply made available to the scripting interface through the <tt>action->addObject</tt> calls, without any knowledge of what the script will use them for. This removes the need to know at the time of writing the application what function the scripts will perform, and is therefore suited to a plugin interface.
Line 131:
Line 131:
    
  MyInputString.connect("textChanged(const QString &)", reverseString)   MyInputString.connect("textChanged(const QString &)", reverseString)
− </code> + </syntaxhighlight>
    
  === krossSigsSlots.js ===   === krossSigsSlots.js ===
Line 143:
Line 143:
  connect(MyInputString, "textChanged(const QString &)", this, "reverseString(const QString &)");   connect(MyInputString, "textChanged(const QString &)", this, "reverseString(const QString &)");
    
− </code> + </syntaxhighlight>
    
  {{TODO|Write similar for other interpreters}}   {{TODO|Write similar for other interpreters}}
Line 157:
Line 157:
  action->addObject(cmbInterpreters, "MyInterpreter");   action->addObject(cmbInterpreters, "MyInterpreter");
  action->addObject(lblMessage, "MyLabel");   action->addObject(lblMessage, "MyLabel");
− </code> + </syntaxhighlight>
  The <tt>Kross::ChildrenInterface::AutoConnectSignals</tt> argument causes signals of the object to be automatically connected with scripting functions of the same name. Therefore, the scripts can again be simplified:   The <tt>Kross::ChildrenInterface::AutoConnectSignals</tt> argument causes signals of the object to be automatically connected with scripting functions of the same name. Therefore, the scripts can again be simplified:
    
Line 168:
Line 168:
     s = s[::-1]      s = s[::-1]
     MyLabel.text = s      MyLabel.text = s
− </code> + </syntaxhighlight>
    
  Now follows a javascript function that converts the string to [http://en.wikipedia.org/wiki/Pig_Latin pig latin]:   Now follows a javascript function that converts the string to [http://en.wikipedia.org/wiki/Pig_Latin pig latin]:
Line 179:
Line 179:
     MyLabel.text = pigLatin;      MyLabel.text = pigLatin;
  }   }
− </code> + </syntaxhighlight>
    
  {{TODO|Write similar for other interpreters}}   {{TODO|Write similar for other interpreters}}
Line 191:
Line 191:
  <syntaxhighlight lang="cpp">   <syntaxhighlight lang="cpp">
     emit signalName();      emit signalName();
− </code> + </syntaxhighlight>
  in c++ code. To illustrate this, change the python script to emit the setEnabled(bool) signal of the QCombobox:   in c++ code. To illustrate this, change the python script to emit the setEnabled(bool) signal of the QCombobox:
    
Line 207:
Line 207:
     s = MyInputString.text[::-1]      s = MyInputString.text[::-1]
     MyLabel.text = s      MyLabel.text = s
− </code> + </syntaxhighlight>
    
  If 'off' is written in the text field, the setEnabled signal is emitted and the combobox is greyed out. It is not re-enabled again until 'on' is written in the text field.   If 'off' is written in the text field, the setEnabled signal is emitted and the combobox is greyed out. It is not re-enabled again until 'on' is written in the text field.
    
  This is a simple demonstration of signal-slot relationships using kross. More complex interfaces may be written to complete a plugin architecture.   This is a simple demonstration of signal-slot relationships using kross. More complex interfaces may be written to complete a plugin architecture.



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 17:
Line 17:
  First edit the mainwindow.h to handle the changes to mainwindow.cpp. Note that the change is the addition of a private <tt>Kross::Action</tt> .   First edit the mainwindow.h to handle the changes to mainwindow.cpp. Note that the change is the addition of a private <tt>Kross::Action</tt> .
    
− <code cpp> + <syntaxhighlight lang="cpp">
  #ifndef MAINWINDOW_H   #ifndef MAINWINDOW_H
  #define MAINWINDOW_H   #define MAINWINDOW_H
Line 51:
Line 51:
  Using the same CmakeLists.txt and main.cpp from the previous [[Development/Tutorials/Kross/Hello_World|Hello World]] tutorial, edit the mainwindow.cpp as follows:   Using the same CmakeLists.txt and main.cpp from the previous [[Development/Tutorials/Kross/Hello_World|Hello World]] tutorial, edit the mainwindow.cpp as follows:
    
− <code cpp> + <syntaxhighlight lang="cpp">
  #include "mainwindow.h"   #include "mainwindow.h"
    
Line 151:
Line 151:
  It is possible to connect signals from your Object to slots in your script file automatically. Edit the mainwindow.cpp file to add another argument to the addObject function:   It is possible to connect signals from your Object to slots in your script file automatically. Edit the mainwindow.cpp file to add another argument to the addObject function:
    
− <code cpp> + <syntaxhighlight lang="cpp">
  action->addObject(txtInputString, "MyInputString",   action->addObject(txtInputString, "MyInputString",
                     Kross::ChildrenInterface::AutoConnectSignals);                      Kross::ChildrenInterface::AutoConnectSignals);
Line 189:
Line 189:
  So far this tutorial has described connecting signals in c++ objects with slots in scripts. The objects published to kross scripts also make their signals available to the scripts. The signals can then be emitted by calling them. This is equivalent to calling:   So far this tutorial has described connecting signals in c++ objects with slots in scripts. The objects published to kross scripts also make their signals available to the scripts. The signals can then be emitted by calling them. This is equivalent to calling:
    
− <code cpp> + <syntaxhighlight lang="cpp">
     emit signalName();      emit signalName();
  </code>   </code>



Dipesh: /* Simplified scripts */
2007-11-07T14:51:05Z
‎Simplified scripts

				
				
				
				
			
			← Older revision
			Revision as of 14:51, 7 November 2007
			
Line 170:
Line 170:
  </code>   </code>
    
− Now follows a javascript function that converts the string to [http://en.wikipedia.org/wiki/Pig_Latin|pig latin]: + Now follows a javascript function that converts the string to [http://en.wikipedia.org/wiki/Pig_Latin pig latin]:
    
  <code javascript>   <code javascript>



Dipesh: /* Simplified scripts */
2007-11-07T14:49:32Z
‎Simplified scripts

				
				
				
				
			
			← Older revision
			Revision as of 14:49, 7 November 2007
			
Line 170:
Line 170:
  </code>   </code>
    
− Now follows a javascript function that converts the string to [[http://en.wikipedia.org/wiki/Pig_Latin|pig latin]]: + Now follows a javascript function that converts the string to [http://en.wikipedia.org/wiki/Pig_Latin|pig latin]:
    
  <code javascript>   <code javascript>



Dipesh: /* Simplified scripts */
2007-11-07T14:48:44Z
‎Simplified scripts

				
				
				
				
			
			← Older revision
			Revision as of 14:48, 7 November 2007
			
Line 161:
Line 161:
    
  === Simplified scripts ===   === Simplified scripts ===
− The python function reverses the string: + The following python code provides a function that reverses the string:
  <code python>   <code python>
− #!/usr/bin/env kross  
−  
  import MyLabel   import MyLabel
    
Line 170:
Line 168:
     s = s[::-1]      s = s[::-1]
     MyLabel.text = s      MyLabel.text = s
−  
  </code>   </code>
    
− The javascript function converts the string to [[pig latin]]: + Now follows a javascript function that converts the string to [[http://en.wikipedia.org/wiki/Pig_Latin|pig latin]]:
    
  <code javascript>   <code javascript>
Line 180:
Line 177:
     text = text.replace(/\b([aeiou][a-z]*)\b/gi, "$1way"); // Rule 2      text = text.replace(/\b([aeiou][a-z]*)\b/gi, "$1way"); // Rule 2
     pigLatin = text.replace(/\b([bcdfghjklmnpqrstvwxyz]+)([a-z]*)\b/gi, "$2$1ay"); // Rule 1      pigLatin = text.replace(/\b([bcdfghjklmnpqrstvwxyz]+)([a-z]*)\b/gi, "$2$1ay"); // Rule 1
−  
     MyLabel.text = pigLatin;      MyLabel.text = pigLatin;
−  
  }   }
  </code>   </code>



Dipesh: /* Update source files */
2007-11-07T14:41:42Z
‎Update source files

				
				
				
				
			
			← Older revision
			Revision as of 14:41, 7 November 2007
			
Line 11:
Line 11:
    
  == Update source files ==   == Update source files ==
  + 
  + This tutorial is based on the [[Development/Tutorials/Kross/Hello_World|Hello World]] tutorial and extends the codebase we wrote there with new functionality.
    
  === mainwindow.h ===   === mainwindow.h ===
− Edit mainwindow.h to handle the changes to mainwindow.cpp. Note that the change is the addition of a private <tt>Kross::Action</tt> . + First edit the mainwindow.h to handle the changes to mainwindow.cpp. Note that the change is the addition of a private <tt>Kross::Action</tt> .
    
  <code cpp>   <code cpp>
Line 25:
Line 27:
  #include <kross/core/action.h>   #include <kross/core/action.h>
           
  + // The main window to display our combobox and the label.
  class MainWindow : public QWidget   class MainWindow : public QWidget
  {   {
       Q_OBJECT        Q_OBJECT
     public:      public:
  +     // The constructor.
       MainWindow(QWidget *parent=0);        MainWindow(QWidget *parent=0);
     private Q_SLOTS:      private Q_SLOTS:
  +     // This slot is called when the item in the combobox is changed.
       void interpreterActivated(const QString &);        void interpreterActivated(const QString &);
     private:      private:
Line 36:
Line 41:
       QLabel* lblMessage;        QLabel* lblMessage;
       QComboBox* cmbInterpreters;        QComboBox* cmbInterpreters;
  +     // We now have the action as class-member.
       Kross::Action* action;        Kross::Action* action;
  };   };
Line 43:
Line 49:
    
  === mainwindow.cpp ===   === mainwindow.cpp ===
− Using the same CmakeLists.txt and main.cpp from the previous tutorial, edit the mainwindow.cpp as follows: + Using the same CmakeLists.txt and main.cpp from the previous [[Development/Tutorials/Kross/Hello_World|Hello World]] tutorial, edit the mainwindow.cpp as follows:
    
  <code cpp>   <code cpp>
Line 54:
Line 60:
  #include <kross/core/action.h>   #include <kross/core/action.h>
    
  + // the constructor.
  MainWindow::MainWindow(QWidget *parent) : QWidget(parent)   MainWindow::MainWindow(QWidget *parent) : QWidget(parent)
  {   {
Line 73:
Line 80:
     setLayout(vLayout);      setLayout(vLayout);
    
  +   // This time we create the Kross::Action already within the
  +   // constructor and add the objects that should be accessible
  +   // from within scripting code.
     action = new Kross::Action(this, "MyScript");      action = new Kross::Action(this, "MyScript");
    
Line 80:
Line 90:
  }   }
    
  + // this slot is called when the active item of the combobox changes.
  void MainWindow::interpreterActivated(const QString &strSelectedInterpreter)   void MainWindow::interpreterActivated(const QString &strSelectedInterpreter)
  {   {
Line 87:
Line 98:
     }      }
    
  +   // this time we are using external script files.
     QString filename;      QString filename;
−  
     if(strSelectedInterpreter == "python")      if(strSelectedInterpreter == "python")
       filename = "krossSigsSlots.py";        filename = "krossSigsSlots.py";
Line 96:
Line 107:
       return;        return;
    
  +   // set the script file that should be executed.
     action->setFile(filename);      action->setFile(filename);
  +   // finally execute the scripting code.
     action->trigger();      action->trigger();
  }   }



Steveire: Some cleanup and a note about emitting object signals from scripts.
2007-11-07T00:49:13Z
Some cleanup and a note about emitting object signals from scripts.

				
				
				
				
			
			← Older revision
			Revision as of 00:49, 7 November 2007
			
Line 78:
Line 78:
     action->addObject(cmbInterpreters, "MyInterpreter");      action->addObject(cmbInterpreters, "MyInterpreter");
     action->addObject(lblMessage, "MyLabel");      action->addObject(lblMessage, "MyLabel");
−  
−   action->trigger();  
  }   }
    
Line 123:
Line 121:
    
  === krossSigsSlots.js ===   === krossSigsSlots.js ===
− This script does the same like the script above but using the JavaScript scripting language. + This script does the same as the script above but using the JavaScript scripting language.
    
  <code javascript>   <code javascript>
Line 133:
Line 131:
    
  </code>   </code>
  + 
  + {{TODO|Write similar for other interpreters}}
    
  == Autoconnecting Signals and Slots ==   == Autoconnecting Signals and Slots ==
Line 166:
Line 166:
  {   {
     text = text.replace(/\b([aeiou][a-z]*)\b/gi, "$1way"); // Rule 2      text = text.replace(/\b([aeiou][a-z]*)\b/gi, "$1way"); // Rule 2
−    pigLatin = text.replace(/\b([bcdfghjklmnpqrstvwxy]+)([a-z]*)\b/gi, "$2$1ay"); // Rule 1 +    pigLatin = text.replace(/\b([bcdfghjklmnpqrstvwxyz]+)([a-z]*)\b/gi, "$2$1ay"); // Rule 1
    
     MyLabel.text = pigLatin;      MyLabel.text = pigLatin;
Line 172:
Line 172:
  }   }
  </code>   </code>
  + 
  + {{TODO|Write similar for other interpreters}}
  + 
  + [[Image:Krosssigsandslots1.png]]
  + 
  + == Emitting signals from within scripts ==
  + 
  + So far this tutorial has described connecting signals in c++ objects with slots in scripts. The objects published to kross scripts also make their signals available to the scripts. The signals can then be emitted by calling them. This is equivalent to calling:
  + 
  + <code cpp>
  +   emit signalName();
  + </code>
  + in c++ code. To illustrate this, change the python script to emit the setEnabled(bool) signal of the QCombobox:
  + 
  + <code python>
  + #!/usr/bin/env kross
  + 
  + import MyLabel
  + import MyInterpreter
  + 
  + def textChanged(s):
  +   if s == "off":
  +     MyInterpreter.setEnabled(False)
  +   elif s == "on":
  +     MyInterpreter.setEnabled(True)
  +   s = MyInputString.text[::-1]
  +   MyLabel.text = s
  + </code>
  + 
  + If 'off' is written in the text field, the setEnabled signal is emitted and the combobox is greyed out. It is not re-enabled again until 'on' is written in the text field.
  + 
  + This is a simple demonstration of signal-slot relationships using kross. More complex interfaces may be written to complete a plugin architecture.