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
There are two methods that still use QT in flow. These are related with the "extra" information for the creation of the blocks.
In this issue #20 , we have removed "nodes library", the purpose was to enable other developers to create new interafaces using other libraries or frameworks. This tasks will enable it completely by removing completely.
But the methods are being used now, and are very important as these allow to create richer interfaces specific to each block.
Posible solution
Create an intermediate language to explain what should be inside of that "widget" or "subwindow". For example
button {
text: "click"
callback: "name of callback in method"
},
text_entry
Then, each graphical implementation is responsible of translating that into each specific framework
The text was updated successfully, but these errors were encountered:
Intro
There are two methods that still use QT in flow. These are related with the "extra" information for the creation of the blocks.
In this issue #20 , we have removed "nodes library", the purpose was to enable other developers to create new interafaces using other libraries or frameworks. This tasks will enable it completely by removing completely.
But the methods are being used now, and are very important as these allow to create richer interfaces specific to each block.
Posible solution
Create an intermediate language to explain what should be inside of that "widget" or "subwindow". For example
Then, each graphical implementation is responsible of translating that into each specific framework
The text was updated successfully, but these errors were encountered: