search

microsoft / xaml-standard

XAML Standard : a set of principles that drive XAML dialect alignment
Other
805 stars 50 forks source link

Cover use cases of Windows Desktop Controls #184

Open birbilis opened 7 years ago

birbilis commented 7 years ago

https://msdn.microsoft.com/en-us/library/windows/desktop/dn688964(v=vs.85).aspx https://msdn.microsoft.com/library/windows/desktop/dn742399.aspx

guess the same applies to other platforms, should check what controls desktop (and not just mobile) platforms have and try to cover them with related specs (even if those specs are included as optional or platform-specific profiles in the standard).

This can help third parties implementing them either with platform specific (say native control wrappers) or cross-platform renderers (say pure XAML with child controls or drawn with paths etc.). Speaking of implementation (and a dev using that impl) obviously an implementation could opt to use native control rendering and fallback to portable renderer (if available) on other platforms

birbilis commented 7 years ago

since I was speaking of implementations potentially using native controls where available and falling back to portable versions of controls, actually FMX (FireMonkey) of Delphi seems to have a property where the developer of an app can choose the behavior they want (e.g. set it to always use the non-native version so that the app looks indentical on all platforms [useful when creating documentation or want a specific branding/styling on an app UI, when making a game etc.])