You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Component are reusable, encapsulated QML types with well-defined interfaces.
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
The text was updated successfully, but these errors were encountered:
Currently we have
Elements
andComponents
in the codebase forEasyApp
Element
is supposed to be an atomic unitComponent
is a construct of several atomic unitsIn
QtQuick
there areTemplates
,Controllers
andComponents
Template
is a non-visual implementation of aController
(https://doc.qt.io/qt-6/qtquick-templates-qmlmodule.html)Controller
is an API for various ways a user can input data, suchButton
,ComboBox
(https://doc.qt.io/qt-6/qtquick-controls-qmlmodule.html)Component
are reusable, encapsulated QML types with well-defined interfaces.Suggestion
I would suggest to use the
QtQuick
terminology as theElement
often 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
EasyApp
more userfriendly by only "exposing"Components
and keep everything inElements
hidden from the users ofEasyApp
The text was updated successfully, but these errors were encountered: