Hi, I think most of the work is mechanical but since this API is huge I'm sure there is a lot of nuance especially in the callbacks from the API.
One of the problems with Cordova porting is that Cordova by its essence is limited to JavaScripts asynchronous functionality. The proponents of JS claim this as an advantage but it's a huge disadvantage as operating systems & hardware are by their nature synchronous (e.g. bluetooth) so it makes the most sense to just have a thread reading from/to said device. This would actually be simpler and reduce the implementation size considerably. But this is non-trivial to do especially for a feature that is so huge. I'm sure we can cut out some API's from this mix but it would still be a lot of code to deal with. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/codenameone-discussions. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/86ef711f-fa99-429a-bf69-38467b9459e3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
