us to use QScriptEngines from other sources (such as QML) we need
to change the code so that we don't have a custom QScriptEngine
subclass - only one codebase can do that at a time. The scriptenv
is now a normal QObject and contains a QScriptEngine instead of
inheriting from it.
svn path=/trunk/KDE/kdebase/runtime/; revision=1094259
* discovered QByteArrays were completely opaque to the runtime, obviously not good seeing how many things use them. fortunately, Qt has bindings for them ... in the examples! so just pulled those over (license compatible, thankfully) and now that works
* implement the remaining security hooks so it knows the difference between different kinds of urls
* export KIO::Job into the runtime; i really wish we could have had more time to do something more elegant than just pushing the object wholesale into the runtime as it exposes a LOT of API, but this works, should be safe (security wise) and as we are in feature freeze there's really nothing better that can be done to replace it at this point in time
* move some of the utility bindings (i18n, DataEngine) into simplebindings/ for consistency
* break out the qvariant stuff that is used outside of the DataEngine bindings for clarity
* brea out a bunch of the bookkeeping setup stuff from simplejavascriptapplet.cpp (it was getting messy) and put it into a separate .cpp file
svn path=/trunk/KDE/kdebase/runtime/; revision=1063070
* don't set the widget to aimate on an animation if the parent is automatically set to the applet; this has odd side-effects like Fade animations causing the plasmoid to disappear ;)
svn path=/trunk/KDE/kdebase/runtime/; revision=1062483
We should definetely have a common header for the layout bindings
so we avoid duplicating the "layoutItem" function with different
names all around.
I created some macros to help creating the binding for GridLayout
that may be helpful in other scenarious. Maybe put this macros on
this shared header too ?
Anyway, the bindings for this class are ready if I didn't forget
any important functions and the code for layout item was a little
bit simplified trying to qscriptvalue_cast to QGraphicsLayout* instead
of each implementation of it.
svn path=/trunk/KDE/kdebase/runtime/; revision=1055930
* error nicely in in it( )so there is more visible feedback with meaning to the user
* sketch in the beginnings of extension loading
svn path=/trunk/KDE/kdebase/runtime/; revision=1047344
Now we have support for anchor layout on javascript
plasmoids. This is at 90%. It's not working properly yet
as we need either a patch in Qt (being discussed) or another
not so beautiful approach. After this it will work 98%, and
I'll just need to do the QGraphicsAnchor bindings to support
spacing and size policies of anchors.
svn path=/trunk/KDE/kdebase/runtime/; revision=1044107
l = new Label;
l.text = 'check this out'
fadeAnim = animation("fade")
fadeAnim.widgetToAnimate = l
rotateAnim = animation("rotate")
animGroup = new AnimationGroup
animGroup.parallel = true
animGroup.add(fadeAnim)
animGroup.add(rotateAnim)
animGroup.start()
and watch the label flip fade out while the whole plasmoid rotates. sweet.
svn path=/trunk/KDE/kdebase/runtime/; revision=1038372
