3 ms·
>You write your interface purely programmatically and it's easy to read afterwards. Personally, I disagree. For more complex UI, having XML and designer is way
by 0xFFC 9y ago
>You write your interface purely programmatically and it's easy to read afterwards.
Personally, I disagree. For more complex UI, having XML and designer is way better option than writing UI programmatically.
- pjmlp 9y agoYep, coming from Delphi, C++ Builder, Forms and quite a few good Java layout designers (Netbeans Matisse), WPF Blend, I never understood what is so cool about doing UIs by hand.
- barrkel 9y agoParticularly if you have access to things like custom components (that are themselves designed with a visual designer) and visual form inheritance; these give you back hierarchical compositional tools that you would otherwise lose in a flat composition.
- sebe 9y agoI think the sub second hot reload feature, makes it cool. Have a look at the "Unified layout" section in https://hackernoon.com/why-flutter-uses-dart-dd635a054ebf https://hackernoon.com/why-flutter-uses-dart-dd635a054ebf and or install the flutter plugin in vs code or android studio and have a play.
- pjmlp 9y agoMakes it cool, but nothing out of the ordinary for anyone used to other native GUI development tools, like the ones I referred to. Here is Interface Builder in 1986, https://paulhammant.com/2013/03/28/interface-builders-alternative-lisp-timeline/ https://paulhammant.com/2013/03/28/interface-builders-altern...
- Jyaif 9y agoComplex UI are precisely the place where purely programmatic UI is a time saver. You are going to need to do A/B testing of UI, code review, testing, accessibility/localization, and a crap ton of composability. All these are a pain when you have XML.