The field of web technology is evolving at a rapid pace. Unlike Qt, which offers a complete, prepackaged solution, there is a multitude of tools and libraries which need to be combined into a functional stack. This article presents a stack proven in cross-platform projects and our experience gathered with it.
Modern web technology provides a powerful foundation for cross-platform application development. By using responsive design techniques a browser based application can already cover desktop and mobile platforms. Using the right set of tools, such an application can be developed further into a real mobile app and/or an embedded touch interface.
The building blocks of a modern “cross-platform web application” are the web runtime environment, the single-page application and the back-end system. Let’s have a look at the definition of these three terms and their relation to each other.
Also this year you can meet the basyskom staff at the Embedded World trade show, stand 400 in hall 4.
We present a connected HMI scenario in an industrial setup, having interesting discussions. Topics are QtOpcUA, QtWebChannel and more. It is those applications of our customers out there in the field which make our business so fascinating!
How much does a property you define in QML code cost in terms of memory? This simple question led me down a merry chase into the source of the QML engine. The result is this article and in the end a contribution to Qt5.6.
Before we get started, let’s do a quick recap of what we know about Qt properties on the C++ side. Qt has compile time properties which can be added to QObject derived classes. The various methods associated with such a property (read/write/reset/notify/…) are specified using the Q_PROPERTY macro. The properties themselves are typically stored as C++ member variables. They integrate with the meta object system and are therefore also accessible from the QML-side.
basysKom has been working on the new Qt module QtOpcUa which brings support for the industrial communication standard OPC UA into the Qt world. We recently have offered this module as a contribution to the Qt-project. It is currently under review, we aim to make it a tech preview in Qt 5.7.
basysKom will show QtOpcUa based demos at the Qt World Summit 06./07.10.2015 in Berlin. We are happy to discuss use cases, improvements and OPC UA in general. Looking forward to see you in Berlin.
What is OPC UA?
OPC UA is a communication suite for industrial applications like process or factory automation. Its specification is developed and maintained by the OPC Foundation. The first version has been released in 2008. OPC UA is the successor of the popular original OPC standard (which is now OPC Classic). Unlike its predecessor which was based on Microsoft DCOM, OPC UA is designed with the focus on platform independence and scalability. Beside others, it includes features such as data modeling and much improved security mechanisms. This lines the vision of OPC UA to provide a standard communication protocol to be used on all levels of an industrial plant, ranging from field devices to the ERP system. The involvement of companies like Bosch, Siemens and Honeywell within the OPC Foundation as well as the development of the OPC UA specification itself shows that OPC UA will play an important role in future projects and products.
In Qt 5.4 NFC support is restricted to Blackberry 10. After working on basic desktop support for Qt 5.5 through neard, basysKom decided to kick off NFC support for Android as well.
After two months of work, basysKom has committed Android NFC support to a Qt development branch, based on previous work by Juhana Jauhiainen and colleagues. The patches have passed the review process and we are proud to announce that Qt NFC support for Android will be part of Qt 5.6.
Just so you do not have to take our word for it (or build the dev branches yourself), have a look at the video.
Here you see the NFC corkboard demo from the Qt examples on Nexus 7 running Android 5.0.2 and Qt 5.5 Alpha with our NFC patches. The provided NFC tag has 3 NDEF records – one URI record and two text records. These show up as post-its on the corkboard.
Visit us at the Qt Dev Days 2014 in Berlin.
basysKom will present a QtWebChannel based application supporting both – Qt and web based clients.
Thanks to the Qt Dev Days Organizers we will have Sponsors’ Showcases: Visit us to get an overview on LG’s webOS smart TV.