Viadeo Twitter Google Bookmarks ! Facebook Digg MySpace Yahoo MyWeb Blinklist Netvouz Reddit Simpy StumbleUpon Bookmarks Windows Live Favorites 
Logo Documentation Qt ·  Page d'accueil  ·  Toutes les classes  ·  Toutes les fonctions  ·  Vues d'ensemble  · 

QScriptClass Class Reference
[QtScript module]

The QScriptClass class provides an interface for defining custom behavior of (a class of) Qt Script objects. More...

 #include <QScriptClass>

This class is not part of the Qt GUI Framework Edition.

This class was introduced in Qt 4.4.

Public Types

enum Extension { Callable, HasInstance }
enum QueryFlag { HandlesReadAccess, HandlesWriteAccess }
flags QueryFlags

Public Functions

QScriptClass ( QScriptEngine * engine )
virtual ~QScriptClass ()
QScriptEngine * engine () const
virtual QVariant extension ( Extension extension, const QVariant & argument = QVariant() )
virtual QString name () const
virtual QScriptClassPropertyIterator * newIterator ( const QScriptValue & object )
virtual QScriptValue property ( const QScriptValue & object, const QScriptString & name, uint id )
virtual QScriptValue::PropertyFlags propertyFlags ( const QScriptValue & object, const QScriptString & name, uint id )
virtual QScriptValue prototype () const
virtual QueryFlags queryProperty ( const QScriptValue & object, const QScriptString & name, QueryFlags flags, uint * id )
virtual void setProperty ( QScriptValue & object, const QScriptString & name, uint id, const QScriptValue & value )
virtual bool supportsExtension ( Extension extension ) const

Detailed Description

The QScriptClass class provides an interface for defining custom behavior of (a class of) Qt Script objects.

The QScriptClass class defines an interface for handling various aspects of interaction with the Qt Script objects associated with the class. Such objects are created by calling QScriptEngine::newObject(), passing a pointer to the QScriptClass as argument.

By subclassing QScriptClass, you can define precisely how access to properties of the objects that use your class is handled. This enables a fully dynamic handling of properties, e.g. it's more powerful than QScriptEngine::newQObject(). For example, you can use QScriptClass to implement array-type objects (i.e. objects that handle the length property, and properties whose names are valid array indexes, in a special way), or to implement a "live" (runtime-defined) proxy to an underlying object.

If you just need to handle access to a set of properties that are known at the time an object is created (i.e. "semi-statically"), you might consider using QScriptValue::setProperty() to define getter/setter functions for the relevant properties, rather than subclassing QScriptClass.

Reimplement queryProperty() to specify which properties are handled in a custom way by your script class (i.e. should be delegated to the QScriptClass), and which properties should be handled just like normal Qt Script object properties.

Reimplement property() and setProperty() to perform the actual access (read or write) to the properties that your class handles. Additionally, you can reimplement propertyFlags() to specify custom flags for your properties.

Reimplement newIterator() to provide an iterator for objects of your custom class. This is only necessary if objects of your class can have custom properties that you want to be reported when an object is used together with the QScriptValueIterator class, or when an object is used in a for-in enumeration statement in a script.

When implementing custom classes of objects, you typically use QScriptValue::setData() to store instance-specific data as part of object initialization; the data won't be accessible from scripts directly, but you can access it in e.g. your reimplementations of property() and setProperty() (by calling QScriptValue::data()) to perform custom processing.

Reimplement prototype() to provide a custom prototype object for your script class.

Reimplement supportsExtension() and extension() if your custom script class supports one or more of the extensions specified by the Extension enum.

See also QScriptClassPropertyIterator, QScriptEngine::newObject(), and Custom Script Class Example.

Member Type Documentation

enum QScriptClass::Extension

This enum specifies the possible extensions to a QScriptClass.

QScriptClass::Callable0Instances of this class can be called as functions.
QScriptClass::HasInstance1Instances of this class implement [[HasInstance]].

See also extension().

enum QScriptClass::QueryFlag
flags QScriptClass::QueryFlags

This enum describes flags that are used to query a QScriptClass regarding how access to a property should be handled.

QScriptClass::HandlesReadAccess0x01The QScriptClass handles read access to this property.
QScriptClass::HandlesWriteAccess0x02The QScriptClass handles write access to this property.

The QueryFlags type is a typedef for QFlags<QueryFlag>. It stores an OR combination of QueryFlag values.

See also queryProperty().

Member Function Documentation

QScriptClass::QScriptClass ( QScriptEngine * engine )

Constructs a QScriptClass object to be used in the given engine.

The engine does not take ownership of the QScriptClass object.

QScriptClass::~QScriptClass ()   [virtual]

Destroys the QScriptClass object.

If a QScriptClass object is deleted before the associated engine(), any Qt Script objects using the QScriptClass will be "demoted" to normal Qt Script objects.

QScriptEngine * QScriptClass::engine () const

Returns the engine that this QScriptClass is associated with.

QVariant QScriptClass::extension ( Extension extension, const QVariant & argument = QVariant() )   [virtual]

This virtual function can be reimplemented in a QScriptClass subclass to provide support for extensions. The optional argument can be provided as input to the extension; the result must be returned in the form of a QVariant. You can call supportsExtension() to check if an extension is supported by the QScriptClass. By default, no extensions are supported, and this function returns an invalid QVariant.

If you implement the Callable extension, Qt Script will call this function when an instance of your class is called as a function (e.g. from a script or using QScriptValue::call()). The argument will contain a pointer to the QScriptContext that represents the function call, and you should return a QVariant that holds the result of the function call. In the following example the sum of the arguments to the script function are added up and returned:

 if (extension == Callable) {
     QScriptContext *context = qvariant_cast<QScriptContext*>(argument);
     QScriptEngine *engine = context->engine();
     double sum = 0;
     for (int i = 0; i < context->argumentCount(); ++i)
         sum += context->argument(i).toNumber();
     return sum;

If you implement the HasInstance extension, Qt Script will call this function as part of evaluating the instanceof operator, as described in ECMA-262 Section 11.8.6. The argument is a QScriptValueList containing two items: The first item is the object that HasInstance is being applied to (an instance of your class), and the second item can be any value. extension() should return true if the value delegates behavior to the object, false otherwise.

See also supportsExtension().

QString QScriptClass::name () const   [virtual]

Returns the name of the script class.

Qt Script uses this name to generate a default string representation of objects in case you do not provide a toString function.

The default implementation returns a null string.

QScriptClassPropertyIterator * QScriptClass::newIterator ( const QScriptValue & object )   [virtual]

Returns an iterator for traversing custom properties of the given object.

The default implementation returns 0, meaning that there are no custom properties to traverse.

Reimplement this function if objects of your script class can have one or more custom properties (e.g. those reported to be handled by queryProperty()) that you want to appear when an object's properties are enumerated (e.g. by a for-in statement in a script).

Qt Script takes ownership of the new iterator object.

See also QScriptValueIterator.

QScriptValue QScriptClass::property ( const QScriptValue & object, const QScriptString & name, uint id )   [virtual]

Returns the value of the property with the given name of the given object.

The id argument is only useful if you assigned a value to it in queryProperty().

The default implementation does nothing and returns an invalid QScriptValue.

See also setProperty() and propertyFlags().

QScriptValue::PropertyFlags QScriptClass::propertyFlags ( const QScriptValue & object, const QScriptString & name, uint id )   [virtual]

Returns the flags of the property with the given name of the given object.

The id argument is only useful if you assigned a value to it in queryProperty().

The default implementation returns 0.

See also property().

QScriptValue QScriptClass::prototype () const   [virtual]

Returns the object to be used as the prototype of new instances of this class (created with QScriptEngine::newObject()).

The default implementation returns an invalid QScriptValue, meaning that the standard Object prototype will be used. Reimplement this function to provide your own custom prototype.

Typically you initialize your prototype object in the constructor of your class, then return it in this function.

See the "Making Use of Prototype-Based Inheritance" section in the QtScript documentation for more information on how prototypes are used.

QueryFlags QScriptClass::queryProperty ( const QScriptValue & object, const QScriptString & name, QueryFlags flags, uint * id )   [virtual]

Queries this script class for how access to the property with the given name of the given object should be handled. The given flags specify the aspects of interest. This function should return a subset of flags to indicate which aspects of property access should be further handled by the script class.

For example, if the flags contain HandlesReadAccess, and you would like your class to handle the reading of the property (through the property() function), the returned flags should include HandlesReadAccess. If the returned flags do not contain HandlesReadAccess, the property will be handled as a normal script object property.

You can optionally use the id argument to store a value that will subsequently be passed on to functions such as property() and setProperty().

The default implementation of this function returns 0.

Note: This function is only called if the given property isn't already a normal property of the object. For example, say you advertise that you want to handle read access to property foo, but not write access; if foo is then assigned a value, it will become a normal script object property, and subsequently you will no longer be queried regarding read access to foo.

See also property().

void QScriptClass::setProperty ( QScriptValue & object, const QScriptString & name, uint id, const QScriptValue & value )   [virtual]

Sets the property with the given name of the given object to the given value.

The id argument is only useful if you assigned a value to it in queryProperty().

The default implementation does nothing.

An invalid value represents a request to remove the property.

See also property().

bool QScriptClass::supportsExtension ( Extension extension ) const   [virtual]

Returns true if the QScriptClass supports the given extension; otherwise, false is returned. By default, no extensions are supported.

Reimplement this function to indicate which extensions your custom class supports.

See also extension().


Best Of

Actualités les plus lues

  1. « Quelque chose ne va vraiment pas avec les développeurs "modernes" », un développeur à "l'ancienne" critique la multiplication des bibliothèques 78
  2. Apercevoir la troisième dimension ou l'utilisation multithreadée d'OpenGL dans Qt, un article des Qt Quarterly traduit par Guillaume Belz 0
  3. Les développeurs ignorent-ils trop les failles découvertes dans leur code ? Prenez-vous en compte les remarques des autres ? 17
  4. BlackBerry 10 : premières images du prochain OS de RIM qui devrait intégrer des widgets et des tuiles inspirées de Windows Phone 0
  5. Quelles nouveautés de C++11 Visual C++ doit-il rapidement intégrer ? Donnez-nous votre avis 10
  6. Adieu qmake, bienvenue qbs : Qt Building Suite, un outil déclaratif et extensible pour la compilation de projets Qt 17
  7. 2017 : un quinquennat pour une nouvelle version du C++ ? Possible, selon Herb Sutter 6
Page suivante

Le Qt Quarterly au hasard


Les aventures de QLALR - utiliser QLALR pour générer un parseur pour une aventure textuelle

Qt Quarterly est la revue trimestrielle proposée par Nokia et à destination des développeurs Qt. Ces articles d'une grande qualité technique sont rédigés par des experts Qt. Lire l'article.



Liens utiles


  • Vous souhaitez rejoindre la rédaction ou proposer un tutoriel, une traduction, une question... ? Postez dans le forum Contribuez ou contactez-nous par MP ou par email (voir en bas de page).

Qt dans le magazine

Cette page est une traduction d'une page de la documentation de Qt, écrite par Nokia Corporation and/or its subsidiary(-ies). Les éventuels problèmes résultant d'une mauvaise traduction ne sont pas imputables à Nokia. Qt 4.6
Copyright © 2012 Developpez LLC. Tous droits réservés Developpez LLC. Aucune reproduction, même partielle, ne peut être faite de ce site et de l'ensemble de son contenu : textes, documents et images sans l'autorisation expresse de Developpez LLC. Sinon, vous encourez selon la loi jusqu'à 3 ans de prison et jusqu'à 300 000 E de dommages et intérêts. Cette page est déposée à la SACD.
Vous avez déniché une erreur ? Un bug ? Une redirection cassée ? Ou tout autre problème, quel qu'il soit ? Ou bien vous désirez participer à ce projet de traduction ? N'hésitez pas à nous contacter ou par MP !

Hébergement Web