31–40 of 92 posts
Earlier quoted context omitted.
> https://www.codenameone.com/gallery.html The Codename One app gallery says otherwise.
It's a partial gallery and keep in mind it's installed apps. There aren't 180M apps in existence so interpreting that number in that way wouldn't make sense...
Earlier quoted context omitted.
[disclaimer: I work on the Flutter project] We're adding more Cupertino (iOS-flavor) widgets. A few that we already have: spinner, toggle slider, button, alert. Check out the library ( https://docs.flutter.io/flutter/cupertino/cupertino-library.... ) and let us know which ones you'd like to see next! https://flutter.io/issues Thanks!
Will your custom widgets work with all iOS accessibility features? Accessibility is often forgotten when something gets reimplemented.
Codename One ( https://www.codenameone.com/ ) runs circles around fluttr.
Hot-reloading and good performance are very attractive parts of Flutter, but they really should have reconsidered the decision to make their own UI widgets. When you use the native UI elements, you get that native look-and-feel for free, and you don't have to dump man hours into replicating that behavior. They could have a "UI backend" which calls out to the native UI elements for each platform. The great thing is that since they use these UI widgets natively on Fuchsia, they can use their existing code as just another backend on that platform without having to throw the work away.
Earlier quoted context omitted.
> https://www.codenameone.com/gallery.html The Codename One app gallery says otherwise.
It's a partial gallery and keep in mind it's installed apps. There aren't 180M apps in existence so interpreting that number in that way wouldn't make sense...
And if the look of the Codebase One apps weren't enough to make you turn and run the ridiculous pricing strategy of Codebase One would. Why would I pay a fee for unrestricted cross platform development when better alternatives that are free already exist.
I had high hopes for flutter but gave up after a while. It feels like their design meetings were spent arguing about grammar and splitting hairs, rather than thinking about ergonomics and how people would use it. In Flutter, everything is a nested pile of objects with too many APIs to keep track of. Take this example: https://github.com/flutter/flutter/blob/master/examples/stoc... Why do I need to care if something t…
Count me a skeptic. This is the same approach taken by Java's Swing (now JavaFX) toolkit and apparently it has exactly the same issues. Swing never felt quite right even after decades of tweaking.
I had high hopes for flutter but gave up after a while. It feels like their design meetings were spent arguing about grammar and splitting hairs, rather than thinking about ergonomics and how people would use it. In Flutter, everything is a nested pile of objects with too many APIs to keep track of. Take this example: https://github.com/flutter/flutter/blob/master/examples/stoc... Why do I need to care if something t…
I mean, if you're using IntelliJ or Visual Studio Code it automatically completes which argument something takes, it's hardly like you need to go around digging for that stuff. Personally, I think it makes sense to differentiate between something which takes one child and something which takes an array of children.
Could you please explain this - it doesn't make sense to me.
To me it seems clearly and unambiguously true that a single child is not a special case vs multiple children, but rather just a list of children that is 1 long. I can't think of any cases where handling both as an array would possibly have you write worse code.
Earlier quoted context omitted.
I mean, if you're using IntelliJ or Visual Studio Code it automatically completes which argument something takes, it's hardly like you need to go around digging for that stuff. Personally, I think it makes sense to differentiate between something which takes one child and something which takes an array of children.
> Personally, I think it makes sense to differentiate between something which takes one child and something which takes an array of children. Could you please explain this - it doesn't make sense to me. To me it seems clearly and unambiguously true that a single child is not a special case vs multiple children, but rather just a list of children that is 1 long. I can't think of any cases where handling both as an arr…