3 ms·
The "lack" of styling is because you are supposed to declare the theming programmatically and be done with it (UIApperance) For your claim of Microsoft's super
by bunnycorn 8y ago
The "lack" of styling is because you are supposed to declare the theming programmatically and be done with it (UIApperance)
For your claim of Microsoft's superiority, I find it very unfounded, it's superior in which way?
With Apple's tools, I can write my on controls, and change my own values and see them updated live in the designer.
- pjmlp 8y agoJust like you can when using Blend.
- bunnycorn 8y agoNo, Blend only works one way. What IB allows you to do is to subclass UIView, design your own controls in code and preview the results of changing instance variables directly in IB.
- pjmlp 8y agoYou can do that by implementing designer aware controls since .NET 1.0, so I don't see the difference, other than having a bit extra code maybe.
- jchb 8y agoI suppose you are referring to this WPF functionality https://docs.microsoft.com/en-us/dotnet/framework/wpf/controls/creating-a-control-that-has-a-customizable-appearance https://docs.microsoft.com/en-us/dotnet/framework/wpf/contro..., and similarly in UWP: https://docs.microsoft.com/en-us/windows/uwp/design/controls-and-patterns/control-templates#specify-the-visual-behavior-of-a-control https://docs.microsoft.com/en-us/windows/uwp/design/controls...? While it looks powerful, I have to say that the Xcode interface builder and code annotation approach has a lot less friction.
- pjmlp 8y agoYes, exactly that, but you don't need to go the full way. It depends on what kind of rendering one wants to present to the user/developer, even with DesignerAttribute one can provide a custom rendering for the control. Here with a forms example, but similar way can be done for the XAML variants. https://msdn.microsoft.com/en-us/library/ms171824.aspx https://msdn.microsoft.com/en-us/library/ms171824.aspx