Hi P5,
I feel from your tone that you are coping with frustration. The CEF bit
seems to not be a 100% finished product but I know the reasons for adopting
it were very compelling. I don't think it's fair to judge CN1 too harshly
on this. Testing a browser can be very time consuming. Having us users do
the actual testing probably is the right way in this case. I've seen a lot
of activity from CN1's side in solving CEF issues so I don't think they're
really ignoring them either. As a developer, I know that every new released
feature goes through many rounds of "testing" with real users. There simply
are too many use cases (and then you also have to multiply them by the
number of different devices, user settings, etc). In short, making a
platform (CN1) that relies on other platforms (Android/iOS/CEF) is a huge
task. Let's encourage CN1 to keep going :)
Are you developing a desktop app? If not, I'd focus on testing and
debugging directly on your device (android/iOS). You can capture any js
error by adding the following to your html and passing it back via a
callback
window.onerror = function (message, file, line, col, error) {
//pass back to app via callback
};
On Tuesday, 9 March 2021 at 07:48:34 UTC P5music wrote:
> Already done debugging on Android in regard to this:
> BrowserComponent: mouse events handled differently in Android device than
> simulator (google.com)
> <https://groups.google.com/g/codenameone-discussions/c/121OlNeKXh0>
>
> Mouse events for long press are not working. I filed an issue.
> It seems that you released the CEF without even bothering to check some
> HTML-Javascript content inside.
>
> Now I cannot publish my app because the very first functioning of a
> BrowserComponent is not available. And I already wasted a month of Apple
> developer program, not mentioning being on this project from June 2020.
>
> I have a free account but one could look at it from a different
> perspective: you released a new feature without any testing and luckily you
> have an early tester for free.
> But you are not listening to it.
>
> When I subscribed as CN developer I received an e-mail saying like "please
> help us to spread the use of the CodenameOne" or something similar.
> But how are we supposed to help if you do not fix issues of such
> importance, that are already deployed in fact.
>
> Believe me, many times I returned to my Swift project, not difficult to
> update it because a few lines of development were possible for me to do in
> months with this very painful day-to-day before-going-bed "free" assistance
> you think is doing good for CN here and on StackOverflow,
>
> but Swift/SwiftUI is so awful that I had to continue with the CN project,
>
> that I like, do not misunderstand me, it has many avantages I want in a
> project,
>
> and I believe in having an easy way to develop for iOS without
> surrendering to Apple.
> This it the "plus" of CodenameOne, not the cross-platform stuff for
> Android or Blackberry or desktop.
>
> How do you see it?
> Regards
>
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/codenameone-discussions/25c3c777-77ba-40db-a1bd-abba5e5a6bfcn%40googlegroups.com.
