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
Whats there in DOtherrSide is great, but there are pretty large gaps compared to the full QML API.
I have forked DOtherSide for now, and will attempt to fill in some gaps as I go, to add full support in Zig .. but its going to be a long process.
Basically, anything that isnt currently supported in DOtherSide, will put off trying to fix until we get 99% of the existing parts ported.
In terms of wrapping DOtherSide with a Zig API - its an interesting problem.
I really like the final API with the go-qml port, as you simply add Go objects to the QML and it just works. The implementation code is just horrible though, and not easy to port to Zig. Its mostly work to get around the fact that Go is not ABI compatible with C code.
The Rust binding is good to follow to get hints on what to do. However the user API that you end up with seems a bit convoluted.
Surprisingly, the D API looks great, and the implementation of DOtherSide is really clean and easy to follow. Wasnt expecting that !
The text was updated successfully, but these errors were encountered:
Dothersider has its limitations. This week, I was looking at this project in order to find a solution or alternative. slint-ui/slint#142 (reply in thread)
I have updated the correcting build.zig changes made by zig v.0.10-master (w/ stage2 backend default). And recently the new version of DOtherSide (v0.9.0) will support Qt5/Qt6.
It will probably be necessary to revise the translated API. Although currently, haven't seen any problems using stage1 & stage2 with Qt5.
The most recent commit the newest version of dotherside library with Qt6 support. After testing locally, some examples (*.qml) will need to be refactored.
Also, new potential enhancements using the experimental c2z transpiler are under testing.
Whats there in DOtherrSide is great, but there are pretty large gaps compared to the full QML API.
I have forked DOtherSide for now, and will attempt to fill in some gaps as I go, to add full support in Zig .. but its going to be a long process.
Basically, anything that isnt currently supported in DOtherSide, will put off trying to fix until we get 99% of the existing parts ported.
In terms of wrapping DOtherSide with a Zig API - its an interesting problem.
I really like the final API with the go-qml port, as you simply add Go objects to the QML and it just works. The implementation code is just horrible though, and not easy to port to Zig. Its mostly work to get around the fact that Go is not ABI compatible with C code.
The Rust binding is good to follow to get hints on what to do. However the user API that you end up with seems a bit convoluted.
Surprisingly, the D API looks great, and the implementation of DOtherSide is really clean and easy to follow. Wasnt expecting that !
The text was updated successfully, but these errors were encountered: