* 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
Now I figured it out: the c++ class has no properties because
the setters need to get the row or the column and this is not
a property. So now this commit fixes the problem of exporting
it as properties in the binding.
svn path=/trunk/KDE/kdebase/runtime/; revision=1055931
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