Currently we have Elements and Components in the codebase for EasyApp
Element is supposed to be an atomic unitComponent is a construct of several atomic units
In QtQuick there are Templates, Controllers and Components
Suggestion
I would suggest to use the QtQuick terminology as the Element often resembles a Template. This would make it easier for people with a background in QML to understand the purpose of the code sitting in the folders and probably also force us to write the code in a more QML-like way.
I also have the impression that we could make the EasyApp more userfriendly by only "exposing" Components and keep everything in Elements hidden from the users of EasyApp
Currently we have
ElementsandComponentsin the codebase forEasyAppElementis supposed to be an atomic unitComponentis a construct of several atomic unitsIn
QtQuickthere areTemplates,ControllersandComponentsTemplateis a non-visual implementation of aController(https://doc.qt.io/qt-6/qtquick-templates-qmlmodule.html)Controlleris an API for various ways a user can input data, suchButton,ComboBox(https://doc.qt.io/qt-6/qtquick-controls-qmlmodule.html)Componentare reusable, encapsulated QML types with well-defined interfaces.Suggestion
I would suggest to use the
QtQuickterminology as theElementoften resembles aTemplate. This would make it easier for people with a background in QML to understand the purpose of the code sitting in the folders and probably also force us to write the code in a more QML-like way.I also have the impression that we could make the
EasyAppmore userfriendly by only "exposing"Componentsand keep everything inElementshidden from the users ofEasyApp