Boden cross-platform framework: Native C++11, native widgets, no JavaScript
41–50 of 98 posts
Re: Boden cross-platform framework: Native C++11, native widgets, no JavaScript
#42Re: Boden cross-platform framework: Native C++11, native widgets, no JavaScript
#43Earlier quoted context omitted.
it uses C++ and not QML for the interface, the UI components are actually native, you can use templates, etc.
So it's like React-Native, but wirh C++ instead of JS?
The only problem becomes that it is a lot of code to manually maintain or bootstrap. And possibly a decent amount of effort to add new platform widgets, but I didn't look very deeply into how exactly that would be done.
Re: Boden cross-platform framework: Native C++11, native widgets, no JavaScript
#44Rust plz.
Instead of binding view models and state you bind the entire platform with bindings for every widget and control. Its not too much work but it is a lot of boring code to write and maintain.
Re: Boden cross-platform framework: Native C++11, native widgets, no JavaScript
#45Re: Boden cross-platform framework: Native C++11, native widgets, no JavaScript
#46Rust plz.
You could make this exact same framework with rust as the backend instead of C++. I have made a proof of concept MVVM app in rust for iOS and Android. Instead of binding view models and state you bind the entire platform with bindings for every widget and control. Its not too much work but it is a lot of boring code to write and maintain.
Re: Boden cross-platform framework: Native C++11, native widgets, no JavaScript
#47If you want to go down this road, doing mobile cross-platform native, Xamarin seems much more compelling. It is supported by a very good IDE and has proper licensing for distribution on the app stores. https://visualstudio.microsoft.com/xamarin/
One question though for app developers who are experienced in this field- does anybody know the relative running time of native vs managed code on android? Does it matter at all for ux-heavy code? How does the startup time look?
Re: Boden cross-platform framework: Native C++11, native widgets, no JavaScript
#48Earlier quoted context omitted.
Native widgets don't just mean "look". They can also mean "feel". This is particularly true on macOS. On macOS, I expect certain widgets in order to accomplish certain tasks. I expect that they will respond to mouseover and button presses in a certain way. I expect to be able to use certain key combinations to cause certain widgets to do certain things, I expect keyboard combinations to be able to be redefined in Sys…
The takeaway here is that each OS trains you in its own way to look down at all those morons using one of the other ones.
For able users, that can come down to minor irritations. For users with special accessibility requirements, that's downright unacceptable.
If my listing of all the features of macOS might have come off as haughty, it's simply because I'm one of the ones who has special accessibility requirements, and the way macOS does things suits me well. Apps that don't use Cocoa, therefore, can really screw me over.
Re: Boden cross-platform framework: Native C++11, native widgets, no JavaScript
#49Earlier quoted context omitted.
Native widgets don't just mean "look". They can also mean "feel". This is particularly true on macOS. On macOS, I expect certain widgets in order to accomplish certain tasks. I expect that they will respond to mouseover and button presses in a certain way. I expect to be able to use certain key combinations to cause certain widgets to do certain things, I expect keyboard combinations to be able to be redefined in Sys…
Cocoa Touch, while being slightly simpler and less arcane than Cocoa, still has a lot of semi-hidden behaviors that are nonobvious to cross-platform UI framework implementers.
Re: Boden cross-platform framework: Native C++11, native widgets, no JavaScript
#50Is `no JavaScript` a thing now?