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 auf dem Entwicklerforum HMI in München
basysKom wird auch in diesem Jahr auf dem Entwicklerforum HMI am 18.05.2017 in München als Aussteller HMI-Entwicklung mit Qt und QML präsentieren.
Wir freuen uns auf Ihren Besuch!
Continue reading basysKom auf dem Entwicklerforum HMI in München
QtCon 2016 – Berlin
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 info@basyskom.com.
See you in Berlin!
Cross-platform application development for desktop, mobile and embedded with modern web technology
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.
Introduction
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.
basysKom auf dem Entwicklerforum HMI in München
basysKom wird auf dem Entwicklerforum HMI am 16.06.2016 in München als Aussteller HMI-Entwicklung mit Qt und QML präsentieren. Wir freuen uns auf Ihren Besuch!
Unser Development Lead Frank Meerkötter wird des Weiteren in einem Vortrag die Nutzung von Qt/QML aus der Perspektive von industriellen Anwendungen präsentieren. Continue reading basysKom auf dem Entwicklerforum HMI in München
Greetings from Nuremberg!
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!
basyskom at Embedded World 2016
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.
Welcome to our stand 400 in hall 4!
QtWS15: A deep dive into QML memory management internals
If you missed our session “A deep dive into QML memory management internals” during the QtWS15 you can now watch a recording here or have a look at the slides. Enjoy!
Storage of QML defined properties explained (Part 1)
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.
Back to the initial question: how much memory is needed for a QML defined property? To answer this, one first needs to figure out how and where they are Continue reading Storage of QML defined properties explained (Part 1)
Introducing QtOpcUa
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.