summaryrefslogtreecommitdiff
path: root/examples
Commit message (Collapse)AuthorAgeFilesLines
...
* Remove obsolete CONFIG+=ordered from qmake files.Milian Wolff2013-11-131-1/+0
| | | | | Change-Id: Ide09c6f218bf7af176e03e4741f29cd022f351b8 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Make it possible to wrap QObject's on the fly.Milian Wolff2013-11-015-51/+107
| | | | | | | | This is required for factory-like methods on the C++/QML side, which we want to access from the HTML side as well. Change-Id: I2852bbc9c8effb6d6f49b5be784241a6e2320823 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Make it possible to start the examples from a different dir.Milian Wolff2013-11-012-2/+2
| | | | | Change-Id: I0a640ee38d642670211b7cae30619fc18307b688 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Greatly optimize WebChannel in various ways.Milian Wolff2013-11-013-2/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a big code drop - sorry for that. The benefits are worth it though, I'm sure. The optimizations were required to make the WebChannel useable even on a low-end embedded device with medium amount of traffic. The changes in this patch can be grouped into different parts: a) Do more in C++: Esp. by leveraging e.g. the new classInfoForObjects in QtMetaObjectPublisher (on the C++ side) one can greatly reduce the time required for initialization of the webchannel. b) Property Caching: Instead of requiring a socket roundtrip whenever a property is read on the HTML side, we now cache the property values on the HTML side. Note that for this to work properly, one needs to add proper notify signals to the property declarations, as otherwise the cache will not get updated. c) Grouping: Instead of sending separate messages to the clients for every property update, these signals are grouped by a 50ms timer, and then send aggregated to the client. This reduces the socket traffic, as more boiler plate can be shared. d) Compression: Some data was previously send repeatedly, such as property name and notify signal. This is now compressed internally where possible (i.e. for the ${propName}Changed naming scheme). e) Message Flood Prevention: Previously, one could easily flood an HTML client by sending data to it. If it could not work off the incoming stream one would freeze the HTML client. Now, we wait for an idle signal of the client prior to sending new data to it. Paired with the message grouping and property cache mentioned above, we are able to only send the newest data once the HTML client becomes active again. I.e. we discard now-obsolete property updates etc. Change-Id: I8f3ae16ed6c1f6a89b644acdce7efbf0f07fc786 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Allow IP's in base url.Milian Wolff2013-11-013-3/+3
| | | | | Change-Id: I2e20aa13a598e65eafa9b9c145931a95e5f51a0e Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Refactor QWebChannel to use a custom WebSocket server implementation.Milian Wolff2013-11-016-72/+110
| | | | | | | | | | | | | | | The code is much simpler in my opinion and much faster and far more stable. Especially the timer issues or multiple signal connects are now properly resolved. Also simplify the QML WebChannel API: - Rename slot to sendRawMessage and signal to rawMessageReceived - Add a QML helper that has a respond and sendMessage method that transforms the input to the expected JSON format. Change-Id: Ic3266329d1a2877bd46227e4ad70b88dc340d289 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Make it possible to build everything in one goMilian Wolff2013-11-013-2/+8
| | | | | | | Disable installation of examples Change-Id: I85092b0a22da871fdf02f197d0b85e7dc33243bc Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Add a callback for when the QObject integration is setup.Milian Wolff2013-11-011-7/+8
| | | | | | | | This shows an issue with consecutive signal connections due to some error in the socket communication. WebSockets should resolve this. Change-Id: I091d70e5e7498abdcc449eeca8dfe171d1ce0287 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Fix method invocation and signal submission with multiple arguments.Milian Wolff2013-11-013-17/+37
| | | | | Change-Id: I52a3fc53ba0c76489ffdc0634cfaff5b1c1e02a4 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Ensure proper signal connection and property binding.Milian Wolff2013-11-013-7/+23
| | | | | | | | | When multiple signals or properties exist we must not fall into the usual javascript closure trap - we used to only use the very last signal/property of every object... Change-Id: Ief24630cc4b4ce3935207a170711f66c3ef5d805 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Clarify connections between webview and webchannel.Milian Wolff2013-11-011-2/+2
| | | | | | | | | | | | We register objects once after the webchannel has initialized. The web view URL on the other hand gets changed via property binding after the web channel's base url is set/modified. This hopefully fixes a race condition between the client-side HTML logic and the registering of objects on the host-side QML app. Change-Id: Ie83f7a415d9005e805a544f25287e51e75fb4dec Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Simplify the code a bitMilian Wolff2013-11-011-4/+1
| | | | | Change-Id: Ic6c12fb6a51497129556b156483df59f8003c7a7 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Add a common MetaObjectPublisher::registerObjects.Milian Wolff2013-11-011-8/+1
| | | | | | | | Also move most of its implementation to C++ to reduce the context switching. Change-Id: I12d0284aa57d318eafe94d34e732796e522bcfd8 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Fix document.write call - the '+' is required...Milian Wolff2013-11-011-2/+2
| | | | | Change-Id: I6d3bdd438c02ed70281a299ae781fea49a0e4b9c Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Refactor the QObject QWebChannel and make the API reusable.Milian Wolff2013-11-019-231/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | It might becme a very common use case of the QWebChannel QML plugin. Thus it should be as simple as possible for third party consumers to setup a QWebChannel for QObject publishing. The new API basically moves the QtMetaObjectPublisher along with the JavaScript marshalling to the qwebchannl/src folder. The updated qtobject example shows how this new API can be used. Furthermore note how it is now trivially possible to register multiple objects, which was not easily possible before. Some notes on the applied refactoring: - qobject.js contains the JavaScript QObject binding and was refactored to support multiple objects. - the MetaObjectPublisher contains a new handleRequest function which handles the QML-side of the QObject binding. This is implemented in QML, while the other book keeping and esp. the classInfoForObject is still handled in C++ via the QtMetaObjectPublisher class (which is registered as MetaObjectPublisherPrivate and used by MetaObjectPublisher) Change-Id: Id45121bb654447e095bf8a8062d0c8edf9dcb018 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Port hybridshell example to newer Qt5Milian Wolff2013-11-018-254/+238
| | | | | Change-Id: Ifc6d4cbb647edacfebae83fa84be8f6021483fe7 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Make the 'go' button actually do something.Milian Wolff2013-11-011-6/+9
| | | | | | | It now sends the initial request again. Change-Id: If99b2011e52f625276e4d85079b194bd10aa6461 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Make the qmlapp example work with newer Qt5Milian Wolff2013-11-011-5/+3
| | | | | Change-Id: I759262c77c5f659e8c2d390c9fc154fac5da221d Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Port src and examples/qtobject to current Qt5Milian Wolff2013-11-019-256/+240
| | | | | | | Mostly done by using QML (i.e. QtQuick2) instead of QtDeclarative. Change-Id: I4d4f3d8c30bc10683fd7ad8c12e6198b0d848876 Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
* Fix iteration over objects - they do not have .forEach nor .length.Milian Wolff2013-11-011-8/+10
| | | | | Change-Id: Idedb73408b2ee4fb8653ba5b74bf30aa503df779 Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
* Added README fileNo'am Rosenthal2011-08-301-1/+0
|
* Change the invokeMethod syntax to allow for a return callbackNo'am Rosenthal2011-08-094-4/+14
|
* QObject exampleNo'am Rosenthal2011-08-093-80/+120
|
* Added QObject exampleNo'am Rosenthal2011-08-0914-0/+802
|
* Added license headersNo'am Rosenthal2011-08-084-0/+162
|
* Add retain slot, and shell exampleNo'am Rosenthal2011-08-0820-4/+809
|
* Switched to using http POST for exec/subscribeNo'am Rosenthal2011-08-082-2/+6
|
* Use regexp for finding the baseUrl parameterNo'am Rosenthal2011-08-042-13/+3
|
* Change message type to foobar, to make more readableNo'am Rosenthal2011-08-041-0/+1
|
* Change message type to foobar, to make more readableNo'am Rosenthal2011-08-042-2/+2
|
* Use navigator.createWebChannel instead of a global navigator.webChannelNo'am Rosenthal2011-08-041-17/+19
|
* Switch to using an IFrameNo'am Rosenthal2011-08-041-16/+7
|
* Switch to using an IFrameNo'am Rosenthal2011-08-042-7/+21
|
* move the invoking JS to the server sideNo'am Rosenthal2011-07-142-2/+12
|
* Fix some indentations, and remove more dead codeNo'am Rosenthal2011-07-132-4/+4
|
* Remove some dead codeNo'am Rosenthal2011-07-132-10/+21
|
* Remove some dead codeNo'am Rosenthal2011-07-131-2/+1
|
* Switch from WebSockets to CometNo'am Rosenthal2011-07-132-6/+22
|
* Use Uuids instead of int IDsNo'am Rosenthal2011-07-051-2/+4
|
* Allow incremental responsesNo'am Rosenthal2011-07-052-2/+2
|
* Improved on the exampleNo'am Rosenthal2011-07-013-24/+4
| | | | Removed qmlproject
* QWebChannelNo'am Rosenthal2011-06-303-0/+65
View Lorry Controller Status