On 23 Oct 2020, at 14:21, Mo_Al_ wrote:
> I don’t know of Apple’s cureent stance. Currently, however, as far as non-native gui toolkits targetting iOS the only 2 out there that I’m aware of are flutter and Qt QML. The other frameworks targetting iOS either target UIKit’s native widgets such as Xamarin and React Native, or target iOS’s webview and are basically hybrid web apps, ionic, cordova and the likes, which also don’t have a native look and feel by Apple’s standards.
> Fltk can be styled in a way, like the other solutions, to have an iOS style (white window, cupertino colors, flat buttons, the works).
> From my previous experience publishing an iOS app using Cordova, the app store review process checks for the bytecode and asks for a presentable screenshot for the app store. A qml app was refused because they require static linking.
I don't have a clue what Apple would do...
As I recall (and this is just from memory, so likely to be flawed!) our concern at the time was that Apple would always reject fltk-based apps, even if they were tailored to look exactly like native, because of the way we use the underlying API’s, which ISTR was liable to violate their terms...
Whether the rules have changed in the intervening time, I do not know.
The upshot was that no one wanted to put a lot of effort into a port that was likely to been unusable in practice!
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/5F8CF25D-B3FE-4DBA-AB30-D47D0EF96549%40gmail.com.
[ Direct Link to Message ]