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
It is relatively easy to implement getters and setters to make using the library less repetitive/painful.
They can shorten set<value>() calls to just an assigment and get<value>() calls to a single property access.
I'd also consider using default objects for the obvous parts such as the Central widget of mainWindow, but I dont know yet, how much of that is already implemented in Qt.
However this modification will impact the memory, so I could either do this as a fork, or a separate plugin library, so we dont frighten the old fashioned programmers.
I am fully willing to make the typescript wrapper modifications to this but it'll take a while since I can only work on this in my free time, and my current prioritiy is to find and sqash the cause of #1012.
The idea would be that on the cpp level nothing would change and the new wrapper just would use the old functions, leaving their full functionality. But the result should be a lot more like DOM in browser JS.
The text was updated successfully, but these errors were encountered:
It is relatively easy to implement getters and setters to make using the library less repetitive/painful.
They can shorten
set<value>()
calls to just an assigment andget<value>()
calls to a single property access.I'd also consider using default objects for the obvous parts such as the Central widget of mainWindow, but I dont know yet, how much of that is already implemented in Qt.
However this modification will impact the memory, so I could either do this as a fork, or a separate plugin library, so we dont frighten the old fashioned programmers.
I am fully willing to make the typescript wrapper modifications to this but it'll take a while since I can only work on this in my free time, and my current prioritiy is to find and sqash the cause of #1012.
The idea would be that on the cpp level nothing would change and the new wrapper just would use the old functions, leaving their full functionality. But the result should be a lot more like DOM in browser JS.
The text was updated successfully, but these errors were encountered: