This year the Qt World Summit is back in Europe. It will be held October 11th and 12th in Berlin. basysKom is proud to sponsor and to participate in a number of ways.
At the exhibition we will showcase a distributed industrial automation scenario based on Qt Quick and QOpcUa. QOpcUa is an upcoming Qt module basysKom initiated, aiming for simple integration between industrial controllers and HMIs. The showcase also features integration of telemetry data into a Microsoft Azure-based Cloud-Application via MQTT. To highlight the cross platform capabilities of Qt, the HMI is deployed to a number of different devices.
At the conference we will present our Qt Lite experience. “Practical Qt Lite” will be held Wednesday at 15:00, Room A03. Come visit us if you are interested in having smaller Qt builds for your embedded project.
This year, the Qt Contributor Summit is co-located with the World Summit. Contributors to Qt discuss the development and directions of the Qt project. The Contributor summit happens Monday and Tuesday, right before the World Summit. basysKom will offer a session on QOpcUa on Tuesday at 15:00 in Room2. If your are interested in OPC-UA and its integration into Qt please join the session!
Qt Lite is an initiative driven by The Qt Company striving for smaller and leaner Qt builds. It utilizes the new configuration system introduced with Qt 5.8 to create custom builds stripped of features or classes that aren’t needed for a given application. Focus is mostly on Embedded Linux with the goal of making Qt a feasible option on smaller systems. In this post we will have a look at the current state of affairs and we will provide guidance on how to experiment with Qt Lite on your own. Continue reading Qt Lite
basysKom will sponsor the biggest Qt event in Europe, QtCon 2016 in Berlin.
Our Development Lead is looking forward to visiting this event in order to have exciting technical discussions with you. If you want to schedule a meeting upfront, please send an email to firstname.lastname@example.org.
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!
At this years Embedded World trade show basyskom presents its services for the Digital Industry in an UI context. We demonstrate OPC UA used in a hybrid user interface and cloud scenario. Also you can meet our UI design partner HMI Project at our booth.
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.