4 ms·
Actually, in order to write an app that runs on both desktop and mobile platforms, you shouldn't mess with visual elements at all. You should just tell the UI l
by axilmar 13y ago
Actually, in order to write an app that runs on both desktop and mobile platforms, you shouldn't mess with visual elements at all. You should just tell the UI layer to display your data/commands/options, and let the UI layer decide how to display them.
- ygra 13y agoIronically this is easiest in things like WPF which don't have a cross-platform foothold.
- josteink 13y agoHaving worked with WPF and trying to write Android-apps it's easy to despair. They've taken the worst of WPF (XML) without offering any of the goods (data-binding, rapid application development). You feel like you're back in the stone-age of computing, only this time with XML instead of objects. This often means you have to do lots of UI-wiring in code indirectly, based on handles, and due to Java's lack of functional constructs, even wiring up a simple event-handler becomes 6 lines of tedious, annoymous class instantiation nonsense. It's horrible. Had anything like WPF been available in any stable or unstable form, I would have jumped at it in an instant.
- pjmlp 13y agoI used to complain loudly about the state of native desktop development with managed platforms, even doing some Qt prototypes instead. Then I got to do some work in WPF and was quite impressed how far the XAML stack has become. Now if Xamarin cared to support it, it would be great.