On Tuesday 05 July 2011, Artur de Souza wrote: > Quoting Marco Martin <notm...@gmail.com>: > > so, what else remains to do?? > > Besides not working right now I think that the "module API" that today > uses QScriptValue will still be present (I just asked for it anyway in > qt-qml mailing list). Even if it doesn't use QScriptValue but some > other stuff in the future.
this could be good, is it something already existent or planned? (I don't know a lot of that stuff) how would be possible to register a non qobject without a qscriptvalue? > With this module API we would be able to export the non-QObject stuff. > But I think that a good solution would be to "git reset --hard origin" i think that would still force us to rewrite the bindings, forgetting everything about the old js bindings (interesting trivia, that was my first version, there is still a version of bindings that has a plasmoid.* and doesn't use the engine at all, then unfortunately discovered the access to the engine, kinda wish i never did now :/) > our relationship with QML guys: these days they look like more > responsive on mailing lists and we could try to talk with them about > real solutions for our problems... that's nice ;) > I know this didn't work in the past, but I would like to give another > try but without coming to the qt-qml mailing list saying "this is > *@#&$(@" hehe :). > > Marco, can you help me on qt-qml mailing list and post these problems > and "ask for advice"? I will help you there ;) ok, (re)subscribed now ;) Cheers, Marco Martin _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
