Development/Tutorials/Kross/Scripts-as-Plugins - Revision history

Neverendingo: Text replace - "" to ""

2011-06-29T20:52:44Z

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

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


2011-06-29T20:42:32Z
Text replace - "<code ruby>" to "<syntaxhighlight lang="ruby">"

				
				
				
				
			
			← Older revision
			Revision as of 20:42, 29 June 2011
			
Line 184:
Line 184:
  The following Ruby script does the same as the Python scripting code above except by using the Ruby scripting language. This shows, that the same rich API functionality is accessible independend of the used scripting language.   The following Ruby script does the same as the Python scripting code above except by using the Ruby scripting language. This shows, that the same rich API functionality is accessible independend of the used scripting language.
    
− <code ruby> + <syntaxhighlight lang="ruby">
  # import the published MyObject instance.   # import the published MyObject instance.
  require 'myobject'   require 'myobject'



Neverendingo: Text replace - "" to ""

2011-06-29T20:35:33Z
Text replace - "<code javascript>" to "<syntaxhighlight lang="javascript">"

				
				
				
				
			
			← Older revision
			Revision as of 20:35, 29 June 2011
			
Line 226:
Line 226:
  The following JavaScript script does the same as the Python and the Ruby scripting code above but uses Kjs+KjsEmbed (both included in kdelibs). So, the same rich API functionality is also accessible from within the JavaScript language.   The following JavaScript script does the same as the Python and the Ruby scripting code above but uses Kjs+KjsEmbed (both included in kdelibs). So, the same rich API functionality is also accessible from within the JavaScript language.
    
− <code javascript> + <syntaxhighlight lang="javascript">
  // this function got called if the init(QTimer*,int)   // this function got called if the init(QTimer*,int)
  // signal got emitted.   // signal got emitted.



Neverendingo: Text replace - "" to ""

2011-06-29T20:34:30Z
Text replace - "<code python>" to "<syntaxhighlight lang="python">"

				
				
				
				
			
			← Older revision
			Revision as of 20:34, 29 June 2011
			
Line 144:
Line 144:
  First we import the myobject module. This module provides us access to the MyObject {{qt|QObject}} instance and it's slots, signals and properties. Within the init() Python function we set the interval to 2000 milliseconds = 2 seconds. Then we start the {{qt|QTimer}} of our MyObject instance by calling it's start() slot. Then each 2 seconds the update() signal will be emitted what in turn calls our update() Python function.   First we import the myobject module. This module provides us access to the MyObject {{qt|QObject}} instance and it's slots, signals and properties. Within the init() Python function we set the interval to 2000 milliseconds = 2 seconds. Then we start the {{qt|QTimer}} of our MyObject instance by calling it's start() slot. Then each 2 seconds the update() signal will be emitted what in turn calls our update() Python function.
    
− <code python> + <syntaxhighlight lang="python">
  # import the published MyObject instance.   # import the published MyObject instance.
  import myobject   import myobject



Neverendingo: Text replace - "" to ""

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

				
				
				
				
			
			← Older revision
			Revision as of 20:29, 29 June 2011
			
Line 22:
Line 22:
  So, it depends on the use-cases of your application what QObject instances may needed for the scripting code and how they look like. You may also like to look at the tutorials for [[Development/Tutorials/KWord_Scripting|KWord]], [[Development/Tutorials/KSpread_Scripting|KSpread]], [[Development/Tutorials/Krita_Scripting|Krita]] and [[Development/Tutorials/SuperKaramba|SuperKaramba]] to get an idea how scripting was done there.   So, it depends on the use-cases of your application what QObject instances may needed for the scripting code and how they look like. You may also like to look at the tutorials for [[Development/Tutorials/KWord_Scripting|KWord]], [[Development/Tutorials/KSpread_Scripting|KSpread]], [[Development/Tutorials/Krita_Scripting|Krita]] and [[Development/Tutorials/SuperKaramba|SuperKaramba]] to get an idea how scripting was done there.
    
− <code cppqt> + <syntaxhighlight lang="cpp-qt">
  #include <QObject>   #include <QObject>
  #include <QTimer>   #include <QTimer>
Line 81:
Line 81:
  Now we demonstrate how the MyObject class we defined above could be made scriptable using Kross.   Now we demonstrate how the MyObject class we defined above could be made scriptable using Kross.
    
− <code cppqt> + <syntaxhighlight lang="cpp-qt">
  #include <kross/core/action.h>   #include <kross/core/action.h>
    
Line 122:
Line 122:
    
  Once executed you are also able to use [http://websvn.kde.org/trunk/KDE/kdelibs/kross/core/errorinterface.h?view=markup Kross::ErrorInterface] to check if the action was executed successfully like demonstrate below.   Once executed you are also able to use [http://websvn.kde.org/trunk/KDE/kdelibs/kross/core/errorinterface.h?view=markup Kross::ErrorInterface] to check if the action was executed successfully like demonstrate below.
− <code cppqt> + <syntaxhighlight lang="cpp-qt">
     if( action->hadError() )      if( action->hadError() )
       kDebug() << action->errorMessage();        kDebug() << action->errorMessage();
  </code>   </code>
  The [http://websvn.kde.org/trunk/KDE/kdelibs/kross/core/manager.h?view=markup Kross::Manager] provides also the option to connect with the started and finished signals that got emitted if a script got executed.   The [http://websvn.kde.org/trunk/KDE/kdelibs/kross/core/manager.h?view=markup Kross::Manager] provides also the option to connect with the started and finished signals that got emitted if a script got executed.
− <code cppqt> + <syntaxhighlight lang="cpp-qt">
  connect(&Kross::Manager::self(), SIGNAL( started(Kross::Action*) ),   connect(&Kross::Manager::self(), SIGNAL( started(Kross::Action*) ),
           this, SLOT( started(Kross::Action*) ));            this, SLOT( started(Kross::Action*) ));



Tampakrap at 13:12, 25 July 2008
2008-07-25T13:12:58Z


				
				
				
				
			
			← Older revision
			Revision as of 13:12, 25 July 2008
			
Line 49:
Line 49:
       // We pass our used QTimer instance and an interval        // We pass our used QTimer instance and an interval
       // integer value as arguments.        // integer value as arguments.
−      void callInit() { emit init(m_timer, 2000); } +      void callInit() { emit init(timer(), 2000); }
    
     public Q_SLOTS:      public Q_SLOTS:
Line 66:
Line 66:
       // If emitted calls the init(timer,interval) scripting        // If emitted calls the init(timer,interval) scripting
       // function if available.        // function if available.
−      void init(QTimer*, int); +      void init(QObject*, int);
    
       // If emitted calls the update() scripting function        // If emitted calls the update() scripting function



Dipesh: typo--
2007-10-11T00:17:28Z
typo--

				
				
				
				
			
			← Older revision
			Revision as of 00:17, 11 October 2007
			
Line 142:
Line 142:
  The following Python script demonstrates how a Python plugin looks like. The init() and the update() functions will be called if the matching signals at the myobject instance are emitted.   The following Python script demonstrates how a Python plugin looks like. The init() and the update() functions will be called if the matching signals at the myobject instance are emitted.
    
− First we import myobject module. This module provides us access to the MyObject {{qt|QObject}} instance and it's slots, signals and properties. Within the init() Python function we set the interval to 2000 milliseconds = 2 seconds. Then we start the {{qt|QTimer}} of our MyObject instance by calling it's start() slot. Then each 2 seconds the update() signal will be emitted what in turn calls our update() Python function. + First we import the myobject module. This module provides us access to the MyObject {{qt|QObject}} instance and it's slots, signals and properties. Within the init() Python function we set the interval to 2000 milliseconds = 2 seconds. Then we start the {{qt|QTimer}} of our MyObject instance by calling it's start() slot. Then each 2 seconds the update() signal will be emitted what in turn calls our update() Python function.
    
  <code python>   <code python>



Dipesh: /* The QObject code */
2007-10-11T00:10:55Z
‎The QObject code

				
				
				
				
			
			← Older revision
			Revision as of 00:10, 11 October 2007
			
Line 51:
Line 51:
       void callInit() { emit init(m_timer, 2000); }        void callInit() { emit init(m_timer, 2000); }
    
−    Q_SLOTS: +    public Q_SLOTS:
    
       // Return the QTimer instance.        // Return the QTimer instance.



Dhaumann: adept to new kdebug
2007-09-22T09:15:47Z
adept to new kdebug

				
				
				
				
			
			← Older revision
			Revision as of 09:15, 22 September 2007
			
Line 124:
Line 124:
  <code cppqt>   <code cppqt>
     if( action->hadError() )      if( action->hadError() )
−      kDebug() << action->errorMessage() << endl; +      kDebug() << action->errorMessage();
  </code>   </code>
  The [http://websvn.kde.org/trunk/KDE/kdelibs/kross/core/manager.h?view=markup Kross::Manager] provides also the option to connect with the started and finished signals that got emitted if a script got executed.   The [http://websvn.kde.org/trunk/KDE/kdelibs/kross/core/manager.h?view=markup Kross::Manager] provides also the option to connect with the started and finished signals that got emitted if a script got executed.



Dipesh at 14:23, 17 August 2007
2007-08-17T14:23:31Z


				
				
				
				
			
			← Older revision
			Revision as of 14:23, 17 August 2007
			
Line 4:
Line 4:
    
  See also...   See also...
− * [Development/Tutorials/Kross/Introduction Introduction to Kross] + * [[Development/Tutorials/Kross/Introduction|Introduction to Kross]]
− * [Development/Tutorials/KWord_Scripting KWord Scripting Tutorial] + * [[Development/Tutorials/KWord_Scripting|KWord Scripting Tutorial]]
− * [Development/Tutorials/KSpread_Scripting KSpread Scripting Tutorial] + * [[Development/Tutorials/KSpread_Scripting|KSpread Scripting Tutorial]]
− * [Development/Tutorials/Krita_Scripting Krita Scripting Tutorial] + * [[Development/Tutorials/Krita_Scripting|Krita Scripting Tutorial]]
− * [Development/Tutorials/SuperKaramba SuperKaramba Tutorial] + * [[Development/Tutorials/SuperKaramba|SuperKaramba Tutorial]]
    
  ==The C++ code==   ==The C++ code==

@@ Line 75: / Line 75: @@
      QTimer* m_timer;
 };
-</code>
+</syntaxhighlight>
 ===The Kross code===
@@ Line 109: / Line 109: @@
    myobject->callInit();
+}
-</code>
+</syntaxhighlight>
 The execScriptFile function does create an instance of [http://websvn.kde.org/trunk/KDE/kdelibs/kross/core/action.h?view=markup Kross::Action] that is used as abstract container to deal with scripts / script files.
@@ Line 125: / Line 125: @@
    if( action->hadError() )
      kDebug() << action->errorMessage();
-</code>
+</syntaxhighlight>
 The [http://websvn.kde.org/trunk/KDE/kdelibs/kross/core/manager.h?view=markup Kross::Manager] provides also the option to connect with the started and finished signals that got emitted if a script got executed.
 <syntaxhighlight lang="cpp-qt">
@@ Line 132: / Line 132: @@
 connect(&Kross::Manager::self(), SIGNAL( finished(Kross::Action*) ),
          this, SLOT( finished(Kross::Action*) ));
-</code>
+</syntaxhighlight>
 The [http://websvn.kde.org/trunk/KDE/kdelibs/kross/core/actioncollection.h?view=markup Kross::ActionCollection] class manages collections of [http://websvn.kde.org/trunk/KDE/kdelibs/kross/core/action.h?view=markup Kross::Action] instances, enables hierachies and implements serializing from/to XML.
@@ Line 178: / Line 178: @@
    # instance and then use the interval Q_PROPERTY.
    print "interval=%i" % myobject.timer().interval
-</code>
+</syntaxhighlight>
 ===Ruby===
@@ Line 220: / Line 220: @@
    puts "interval=%i" % Myobject.timer().interval
 end
-</code>
+</syntaxhighlight>
 ===JavaScript===
@@ Line 261: / Line 261: @@
    println( "interval=" + myobject.timer().interval );
+}
-</code>
+</syntaxhighlight>