Skip to content
This repository has been archived by the owner on Mar 8, 2024. It is now read-only.

XAML Standard API Specificity #227

Open
jkoritzinsky opened this issue Nov 19, 2017 · 3 comments
Open

XAML Standard API Specificity #227

jkoritzinsky opened this issue Nov 19, 2017 · 3 comments

Comments

@jkoritzinsky
Copy link
Member

As XAML Standard is developed, can the standard spec file include the specific list of members that each control must support to implement the XAML Standard?

As a developer of another XAML-based UI that's planning on trying to support XAML Standard, it's really difficult to make sure we're implementing our XAML Standard controls with the correct behavior without knowing exactly which properties/events are required by the standard.

@insinfo
Copy link

insinfo commented Nov 19, 2017

@jkoritzinsky I agree and support +1

@touseefbsb
Copy link

yes set of events, properties and methods should be standardized for sure

@4creators
Copy link
Contributor

4creators commented Nov 20, 2017

That's an obvious requirement for any reasonable interoperability via standard specification which even indirectly involves an API. It is possible to define XAML standard with restricting it only to xaml declarations, nevertheless, to achive anything close to interoperability an API standard is a must.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants