diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md deleted file mode 100644 index ac82dc8..0000000 --- a/.github/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,15 +0,0 @@ -Thank you for contributing to XAML Standard! We are at the **_very early stages_** of a long term collaboration towards a unified XAML vocabulary that all XAML developers can comfortably rely on to target all your desired end points. - -## All submissions -- [ ] Have you read the [principles](https://github.com/Microsoft/xaml-standard/blob/staging/docs/reviewboard.md#principles)? -- [ ] Have you checked that your post fits the [nature of proposals](https://github.com/Microsoft/xaml-standard/blob/staging/docs/proposalsfaq.md#nature-of-a-proposal)? -- [ ] Have you checked to ensure that there aren't other open [issues](https://github.com/Microsoft/xaml-standard/issues) for the same topic? -- [ ] Have you followed the [contributor code of conduct](https://dotnetfoundation.org/code-of-conduct)? - -## If you are posting an API for XAML standard consideration: -- Add a brief overview of what you are proposing and why it belongs in XAML Standard (in keeping with the principles of the effort). -- Provide a clear usecase/scenario that describes how this API benefits in sharing cross-platform UI code, preferably a scenario from your experience or application that clearly illustrates why a control/API would benefit from being standardized. -- Add a brief example in XAML syntax for your proposal. -- Provide links to issues/discussions where this proposal has been talked about as well as any other pointer to where this originated or got discussed that could describe the motivation. - -For discussions that are not concrete proposals, please prefix title with "Discussion" so we can categorize accordingly. diff --git a/.gitignore b/.gitignore deleted file mode 100644 index f1e3d20..0000000 --- a/.gitignore +++ /dev/null @@ -1,252 +0,0 @@ -## Ignore Visual Studio temporary files, build results, and -## files generated by popular Visual Studio add-ons. - -# User-specific files -*.suo -*.user -*.userosscache -*.sln.docstates - -# User-specific files (MonoDevelop/Xamarin Studio) -*.userprefs - -# Build results -[Dd]ebug/ -[Dd]ebugPublic/ -[Rr]elease/ -[Rr]eleases/ -x64/ -x86/ -bld/ -[Bb]in/ -[Oo]bj/ -[Ll]og/ - -# Visual Studio 2015 cache/options directory -.vs/ -# Uncomment if you have tasks that create the project's static files in wwwroot -#wwwroot/ - -# MSTest test Results -[Tt]est[Rr]esult*/ -[Bb]uild[Ll]og.* - -# NUNIT -*.VisualState.xml -TestResult.xml - -# Build Results of an ATL Project -[Dd]ebugPS/ -[Rr]eleasePS/ -dlldata.c - -# DNX -project.lock.json -artifacts/ - -*_i.c -*_p.c -*_i.h -*.ilk -*.meta -*.obj -*.pch -*.pdb -*.pgc -*.pgd -*.rsp -*.sbr -*.tlb -*.tli -*.tlh -*.tmp -*.tmp_proj -*.log -*.vspscc -*.vssscc -.builds -*.pidb -*.svclog -*.scc - -# Chutzpah Test files -_Chutzpah* - -# Visual C++ cache files -ipch/ -*.aps -*.ncb -*.opendb -*.opensdf -*.sdf -*.cachefile -*.VC.db -*.VC.VC.opendb - -# Visual Studio profiler -*.psess -*.vsp -*.vspx -*.sap - -# TFS 2012 Local Workspace -$tf/ - -# Guidance Automation Toolkit -*.gpState - -# ReSharper is a .NET coding add-in -_ReSharper*/ -*.[Rr]e[Ss]harper -*.DotSettings.user - -# JustCode is a .NET coding add-in -.JustCode - -# TeamCity is a build add-in -_TeamCity* - -# DotCover is a Code Coverage Tool -*.dotCover - -# NCrunch -_NCrunch_* -.*crunch*.local.xml -nCrunchTemp_* - -# MightyMoose -*.mm.* -AutoTest.Net/ - -# Web workbench (sass) -.sass-cache/ - -# Installshield output folder -[Ee]xpress/ - -# DocProject is a documentation generator add-in -DocProject/buildhelp/ -DocProject/Help/*.HxT -DocProject/Help/*.HxC -DocProject/Help/*.hhc -DocProject/Help/*.hhk -DocProject/Help/*.hhp -DocProject/Help/Html2 -DocProject/Help/html - -# Click-Once directory -publish/ - -# Publish Web Output -*.[Pp]ublish.xml -*.azurePubxml -# TODO: Comment the next line if you want to checkin your web deploy settings -# but database connection strings (with potential passwords) will be unencrypted -*.pubxml -*.publishproj - -# Microsoft Azure Web App publish settings. Comment the next line if you want to -# checkin your Azure Web App publish settings, but sensitive information contained -# in these scripts will be unencrypted -PublishScripts/ - -# NuGet Packages -*.nupkg -# The packages folder can be ignored because of Package Restore -**/packages/* -# except build/, which is used as an MSBuild target. -!**/packages/build/ -# Uncomment if necessary however generally it will be regenerated when needed -#!**/packages/repositories.config -# NuGet v3's project.json files produces more ignoreable files -*.nuget.props -*.nuget.targets - -# Microsoft Azure Build Output -csx/ -*.build.csdef - -# Microsoft Azure Emulator -ecf/ -rcf/ - -# Windows Store app package directories and files -AppPackages/ -BundleArtifacts/ -Package.StoreAssociation.xml -_pkginfo.txt - -# Visual Studio cache files -# files ending in .cache can be ignored -*.[Cc]ache -# but keep track of directories ending in .cache -!*.[Cc]ache/ - -# Others -ClientBin/ -~$* -*~ -*.dbmdl -*.dbproj.schemaview -*.pfx -*.publishsettings -node_modules/ -orleans.codegen.cs - -# Since there are multiple workflows, uncomment next line to ignore bower_components -# (https://github.com/github/gitignore/pull/1529#issuecomment-104372622) -#bower_components/ - -# RIA/Silverlight projects -Generated_Code/ - -# Backup & report files from converting an old project file -# to a newer Visual Studio version. Backup files are not needed, -# because we have git ;-) -_UpgradeReport_Files/ -Backup*/ -UpgradeLog*.XML -UpgradeLog*.htm - -# SQL Server files -*.mdf -*.ldf - -# Business Intelligence projects -*.rdl.data -*.bim.layout -*.bim_*.settings - -# Microsoft Fakes -FakesAssemblies/ - -# GhostDoc plugin setting file -*.GhostDoc.xml - -# Node.js Tools for Visual Studio -.ntvs_analysis.dat - -# Visual Studio 6 build log -*.plg - -# Visual Studio 6 workspace options file -*.opt - -# Visual Studio LightSwitch build output -**/*.HTMLClient/GeneratedArtifacts -**/*.DesktopClient/GeneratedArtifacts -**/*.DesktopClient/ModelManifest.xml -**/*.Server/GeneratedArtifacts -**/*.Server/ModelManifest.xml -_Pvt_Extensions - -# Paket dependency manager -.paket/paket.exe -paket-files/ - -# FAKE - F# Make -.fake/ - -# JetBrains Rider -.idea/ -*.sln.iml diff --git a/LICENSE b/LICENSE deleted file mode 100644 index 2b16ea5..0000000 --- a/LICENSE +++ /dev/null @@ -1,13 +0,0 @@ -License Notice  -  -Specification License. -Microsoft grants you a worldwide, nonexclusive, perpetual, license to make, reference, modify and otherwise use, and allow third party contractors and consultants to make, reference, modify and use, a reasonable number of copies of the specifications to develop implementations of the technologies described in the specification documentation.   -  -Contributions to the Specification. -If you make modifications to the specification, you grant to Microsoft and to others a worldwide, nonexclusive, perpetual, irrevocable, royalty-free, fully paid up license to make, reference, modify and otherwise use, and allow third party contractors and consultants to make, reference, modify and use such modifications.      -  -Reservation of Rights. -Except as expressly licensed as described above, all other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise. -  -Specification Offered “As-Is.” -The specification is provided “as-is” and there are no express warranties, guarantees or conditions.  To the extent permitted under local law, Microsoft excludes the implied warranties of merchantability, fitness for a particular purpose, title and non-infringement.  diff --git a/README.md b/README.md index 1b2d0d2..e89eb37 100644 --- a/README.md +++ b/README.md @@ -1,27 +1,3 @@ -# XAML Standard : a set of principles that drive XAML dialect alignment +# XAML Standard: sorry -## Updates: -**03-JAN-2023: -This repo is being archived.** The focus of aligning the XAML dialect across a number of our XAML-based languages was our initial goal. We were unable to find a direct alignment with our product areas as we’d hoped. To that end, we are choosing to archive this repo. Our frameworks such as [Windows Presentation Foundation (WPF)](https://learn.microsoft.com/dotnet/desktop/wpf/overview/?view=netdesktop-6.0), [WinAppSDK](https://learn.microsoft.com/windows/apps/windows-app-sdk/), and [.NET MAUI](https://learn.microsoft.com/dotnet/maui/what-is-maui?view=net-maui-7.0) are rich with features powerful for each use case and can leverage XAML declarative markup unique to their own scenarios and underlying platforms they serve. We will continue to evolve those frameworks as appropriate, enabling developers choosing those platforms for their apps to be most successful in their developer scenarios and targets. - -## Principles: - -* Different platforms have different personalities and capabilities. For the best end-user experience, developers build native apps that embrace the native personalities and capabilities of the platforms and device form factors. -* **Xamarin** and **Xamarin.Forms** are optimized for developers building native mobile scenarios and focuses on exposing the common and abstracted subset of controls and capabilities most needed by mobile developers. -* **Windows 10 XAML** and **WPF** are optimized for native Windows experiences and focuses on exposing the full and unique capabilities of the Windows platform. Developers empowered with **Windows 10 XAML** and **WPF**, can harness the full and unique capabilities of the Windows platform, including the most rich and demanding experiences optimized for use with mouse, keyboard and touch. -* We will continue to optimize **Xamarin.Forms** as an abstraction layer for native mobile development and optimize **Windows 10 XAML** and **WPF** for Windows native experiences. XAML Standard is an alignment effort targeted at finding the right middle ground of concepts and tags that can be shared between Microsoft’s XAML UI systems to make it easier to work with XAML regardless of target platforms. - -## Revised definition and scope: - -* XAML Standard is set of principles that drive XAML dialect alignment and not a product or product feature. - -## Timeframe: -As a first phase of alignment, we are making a set of additive updates to Windows 10 XAML and Xamarin.Forms. For example: -* TextBlock, StackPanel (and several other tags as requested here) are being added to Xamarin.Forms - see [aka.ms/xf-xamlstandard]() for details on how you can try these out. -* Similarly ease of use APIs like StackPanel.Spacing etc., are being added to Windows 10 XAML. - -For the full list of aligned tags at this time, see [here](docs/v1draft.md). - -If you have further feedback on XAML alignment, please provide that on either the [UWP XAML uservoice](https://wpdev.uservoice.com/forums/110705-universal-windows-platform) or the [Xamarin.Forms community forums](https://developercommunity.visualstudio.com/spaces/8/index.html) - -This project has adopted the code of conduct defined by the [Contributor Covenant](http://contributor-covenant.org/) to clarify expected behavior in our community. For more information, see the [.NET Foundation Code of Conduct](http://www.dotnetfoundation.org/code-of-conduct). +At the time of announcement (2017), we did intend on making XAML Standard happen. But that clearly didn't work out. Sorry. diff --git a/SECURITY.md b/SECURITY.md deleted file mode 100644 index 869fdfe..0000000 --- a/SECURITY.md +++ /dev/null @@ -1,41 +0,0 @@ - - -## Security - -Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/). - -If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below. - -## Reporting Security Issues - -**Please do not report security vulnerabilities through public GitHub issues.** - -Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report). - -If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey). - -You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). - -Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue: - - * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.) - * Full paths of source file(s) related to the manifestation of the issue - * The location of the affected source code (tag/branch/commit or direct URL) - * Any special configuration required to reproduce the issue - * Step-by-step instructions to reproduce the issue - * Proof-of-concept or exploit code (if possible) - * Impact of the issue, including how an attacker might exploit the issue - -This information will help us triage your report more quickly. - -If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs. - -## Preferred Languages - -We prefer all communications to be in English. - -## Policy - -Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd). - - diff --git a/docs/faq.md b/docs/faq.md deleted file mode 100644 index 3499d45..0000000 --- a/docs/faq.md +++ /dev/null @@ -1,32 +0,0 @@ -# FAQs - -## Additional resources -* **NEW!!** [Xamarin.Forms - XAML Standard preview](https://developer.xamarin.com/guides/xamarin-forms/xaml/standard/) -* [Introducing XAML Standard and .NET Standard 2.0 blog](https://blogs.windows.com/buildingapps/2017/05/19/introducing-xaml-standard-net-standard-2-0) -* [.NET Standard 2.0, UWP support and UI futures, Ch9 Interview with Tim Heuer, Scott Hunter and Miguel de Icaza](https://channel9.msdn.com/Events/Build/2017/C9L13) - -## What is XAML Standard? -XAML Standard is an alignment effort to improve productivity for developers creating UI with Windows10 XAML and Xamarin.Forms. It is targeted at finding the right middle ground of concepts and tags that can be shared between Microsoft’s XAML UI systems - Windows10 XAML, WPF and Xamarin.Forms to make it easier to work with XAML regardless of target platforms. - -## What is the relationship between XAML Standard, Windows10 XAML, WPF and Xamarin.Forms? -* XAML Standard is set of principles that drive XAML dialect alignment and not a product or product feature. -* Windows10 XAML, WPF and Xamarin Forms are concrete frameworks that implement the XAML Standard. -* We will continue to optimize Xamarin.Forms as an abstraction layer for native mobile development and optimize Windows 10 XAML and WPF for Windows native experiences - -## What can I do after XAML Standard that I couldn’t do before? -We are at the beginning of a journey that makes it easy for you to align concepts between Xamarin.Forms, Windows10 XAML and even WPF to a large extent. For example - once Phase1 of XAML Standard is supported by Xamarin.Forms, you can use `` in your markup and have it supported in a Xamarin.Forms app targeting iOS and Android instead of needing to know and use `