[ { "path": ".config/dotnet-tools.json", "content": "{\n \"version\": 1,\n \"isRoot\": true,\n \"tools\": {\n \"cake.tool\": {\n \"version\": \"3.0.0\",\n \"commands\": [\n \"dotnet-cake\"\n ]\n }\n }\n}" }, { "path": ".github/ISSUE_TEMPLATE/add-new-control.yml", "content": "name: Add New Control\ndescription: Suggest a new control for MAUIsland\nlabels: [\"proposal/open\", \"t/enhancement\"]\nbody:\n - type: markdown\n attributes:\n value: |\n Thank you for your interest in .NET MAUI! We welcome any and all ideas for features or improvements that you might have. All we ask is to fill in this template with some detail. A detailed description, perhaps supported with some screenshots, mockups, and a (public) API design in pseudo-code, would be very much appreciated and will help get your proposal reviewed sooner.\n \n Keep in mind that .NET MAUI is a multi-platform framework. Consider how feasible it is to implement this feature across all the supported platforms.\n \n If you're not completely sure about a request yet, feel free to [open a discussion](https://github.com/dotnet/maui/discussions/new?category=ideas) first to discuss with the team and the community first.\n - type: textarea\n id: description\n attributes:\n label: Description\n description: Please give us a detailed description of the feature that you envision. Focus on _what_ this feature does, over the _why_ you want this feature. What would be the end-result when implemented? Feel free to add any diagrams, (mocked up) screenshots, or other materials that support your story.\n placeholder: I would love to have a button that I can make shiny. This is something that is supported on all the underlaying platforms, so this would just be exposing that on the .NET MAUI layer.\n validations:\n required: true\n - type: textarea\n id: usage\n attributes:\n label: Usage\n description: Include a list of all API changes, additions, subtractions as would be required by your proposal. These APIs should be considered placeholders, so the naming is not as important as getting the concepts correct. If possible you should include some example (pseudo-)code of usage of your new API. This will not only help us understand better, but also help you think about how you want to use this feature as a developer.\n placeholder: |\n ```csharp\n var button = new Button ();\n button.MakeShiny = true; // new API\n ```\n \n The MakeShiny API works even if the button is already visible.\n validations:\n required: true\n - type: dropdown\n id: platforms\n attributes:\n label: What platforms will this control be available?\n multiple: true\n options:\n - Android \n - Windows\n - MacOS\n - IOS\n - Tizen\n - type: textarea\n id: use-case\n attributes:\n label: Properties list\n description: Provide a detailed example of where your proposal would be used and for what purpose. Focus on _why_ you want this feature instead of _what_ the feature does.\n placeholder: In my app I have a situation where I would really want a shiny button to make it stand out from the rest of the plain and boring buttons.\n validations:\n required: true\n - type: markdown\n attributes:\n value: |\n By opening the issue you agree to follow this project's [Code of Conduct](https://github.com/dotnet/maui/blob/main/.github/CODE_OF_CONDUCT.md)\n" }, { "path": ".github/ISSUE_TEMPLATE/bug-report.yml", "content": "name: Bug Report\ndescription: File a bug report\ntitle: \"[Bug]: \"\nlabels: [\"bug\", \"triage\"]\nassignees:\n - octocat\nbody:\n - type: markdown\n attributes:\n value: |\n Thanks for taking the time to fill out this bug report!\n - type: input\n id: contact\n attributes:\n label: Contact Details\n description: How can we get in touch with you if we need more info ?\n placeholder: ex. email@example.com\n validations:\n required: false\n - type: textarea\n id: what-happened\n attributes:\n label: What happened?\n description: Also tell us, what did you expect to happen?\n placeholder: Tell us what you see!\n value: \"A bug happened!\"\n validations:\n required: true\n - type: dropdown\n id: version\n attributes:\n label: Version\n description: What version of MAUI are you running?\n options:\n - 6.0 (Default)\n - 7.0\n - 8.0\n - 9.0\n validations:\n required: true\n - type: dropdown\n id: platforms\n attributes:\n label: What platforms are you seeing the problem on?\n multiple: true\n options:\n - Android \n - Windows\n - MacOS\n - IOS\n - type: textarea\n id: logs\n attributes:\n label: Relevant log output\n description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.\n render: shell\n - type: checkboxes\n id: terms\n attributes:\n label: Code of Conduct\n description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com)\n options:\n - label: I agree to respect and follow this project's rules \n required: true\n" }, { "path": ".github/ISSUE_TEMPLATE/feature.yml", "content": "name: Feature Request\ndescription: Suggest an idea for .NET MAUI\nlabels: [\"proposal/open\", \"t/enhancement\"]\nbody:\n - type: markdown\n attributes:\n value: |\n Thank you for your interest in .NET MAUI! We welcome any and all ideas for features or improvements that you might have. All we ask is to fill in this template with some detail. A detailed description, perhaps supported with some screenshots, mockups, and a (public) API design in pseudo-code, would be very much appreciated and will help get your proposal reviewed sooner.\n \n Keep in mind that .NET MAUI is a multi-platform framework. Consider how feasible it is to implement this feature across all the supported platforms.\n \n If you're not completely sure about a request yet, feel free to [open a discussion](https://github.com/dotnet/maui/discussions/new?category=ideas) first to discuss with the team and the community first.\n - type: textarea\n id: description\n attributes:\n label: Description\n description: Please give us a detailed description of the feature that you envision. Focus on _what_ this feature does, over the _why_ you want this feature. What would be the end-result when implemented? Feel free to add any diagrams, (mocked up) screenshots, or other materials that support your story.\n placeholder: I would love to have a button that I can make shiny. This is something that is supported on all the underlaying platforms, so this would just be exposing that on the .NET MAUI layer.\n validations:\n required: true\n - type: textarea\n id: api-changes\n attributes:\n label: Public API Changes \n description: Include a list of all API changes, additions, subtractions as would be required by your proposal. These APIs should be considered placeholders, so the naming is not as important as getting the concepts correct. If possible you should include some example (pseudo-)code of usage of your new API. This will not only help us understand better, but also help you think about how you want to use this feature as a developer.\n placeholder: |\n ```csharp\n var button = new Button ();\n button.MakeShiny = true; // new API\n ```\n \n The MakeShiny API works even if the button is already visible.\n validations:\n required: true\n - type: textarea\n id: use-case\n attributes:\n label: Intended Use-Case\n description: Provide a detailed example of where your proposal would be used and for what purpose. Focus on _why_ you want this feature instead of _what_ the feature does.\n placeholder: In my app I have a situation where I would really want a shiny button to make it stand out from the rest of the plain and boring buttons.\n validations:\n required: true\n - type: markdown\n attributes:\n value: |\n By opening the issue you agree to follow this project's [Code of Conduct](https://github.com/dotnet/maui/blob/main/.github/CODE_OF_CONDUCT.md)\n" }, { "path": ".github/ISSUE_TEMPLATE/showcase-submission.yml", "content": "name: Showcase Submission\ndescription: Submit your project to be showcased on MAUIsland.\ntitle: \"Showcase Submission: MAUIsland\"\nlabels:\n - showcase\n - submission\n\nbody:\n - type: markdown\n attributes:\n value: |\n Thank you for submitting your project to be showcased! Please provide the following details so we can include your project on MAUIsland.\n\n - type: input\n id: repository_url\n attributes:\n label: \"Repository URL\"\n description: \"Provide the URL of the GitHub repository for your project.\"\n placeholder: \"https://github.com/username/repository-name\"\n validations:\n required: true\n\n - type: checkboxes\n id: project_technology\n attributes:\n label: \"What technology is this project using?\"\n description: \"Select all technologies applicable to your project.\"\n options:\n - label: \".NET MAUI\"\n - label: \"Uno Platform\"\n - label: \"WinUI 3\"\n - label: \"UWP\"\n - label: \"WPF\"\n validations:\n required: true\n\n - type: checkboxes\n id: platform_support\n attributes:\n label: \"How many platforms does this project support?\"\n description: \"Select all platforms your project supports.\"\n options:\n - label: Android\n - label: iOS\n - label: Windows\n - label: MacOS\n - label: Tizen\n validations:\n required: true\n\n - type: textarea\n id: screenshots\n attributes:\n label: \"Screenshots of the application\"\n description: \"Provide links to screenshots of your application. You can upload them to your repository or a cloud storage service and share the links here.\"\n validations:\n required: true\n\n - type: dropdown\n id: device_frame\n attributes:\n label: \"Which device frame do you want to display your application on?\"\n description: \"Select one or more device frames you would like to use.\"\n multiple: true\n options:\n - Apple IPhone 15 Pro Max\n - Google Pixel 5\n - Google Pixel 6 Pro\n - Apple IPhone 13 Mini\n - Apple IPhone 15\n - Samsung Galaxy S22 Ultra\n - Samsung Galaxy S8\n validations:\n required: true\n\n - type: checkboxes\n id: terms\n attributes:\n label: Code of Conduct\n description: \"By submitting this showcase, you agree to follow our [Code of Conduct](https://example.com).\"\n options:\n - label: I agree to respect and follow this project's rules\n validations:\n required: true\n\n - type: markdown\n attributes:\n value: |\n ## Public API Changes\n\n None\n" }, { "path": ".gitignore", "content": "# globs\nMakefile.in\n*.userprefs\n*.usertasks\nappsettings.Development.json\nsrc/appsettings.Development.json\nconfig.make\nconfig.status\naclocal.m4\ninstall-sh\nautom4te.cache/\n*.tar.gz\ntarballs/\ntest-results/\n/src/Presentations/Windows/Extensions/ProductionConfig.cs\n\ntools/\n\n# Mac bundle stuff\n*.dmg\n*.app\n\n# content below from: https://github.com/github/gitignore/blob/main/Global/macOS.gitignore\n# General\n.DS_Store\n.AppleDouble\n.LSOverride\n\n# Icon must end with two \\r\nIcon\n\n\n# Thumbnails\n._*\n\n# Files that might appear in the root of a volume\n.DocumentRevisions-V100\n.fseventsd\n.Spotlight-V100\n.TemporaryItems\n.Trashes\n.VolumeIcon.icns\n.com.apple.timemachine.donotpresent\n\n# Directories potentially created on remote AFP share\n.AppleDB\n.AppleDesktop\nNetwork Trash Folder\nTemporary Items\n.apdisk\n\n# content below from: https://github.com/github/gitignore/blob/main/Global/Windows.gitignore\n# Windows thumbnail cache files\nThumbs.db\nehthumbs.db\nehthumbs_vista.db\n\n# Dump file\n*.stackdump\n\n# Folder config file\n[Dd]esktop.ini\n\n# Recycle Bin used on file shares\n$RECYCLE.BIN/\n\n# Windows Installer files\n*.cab\n*.msi\n*.msix\n*.msm\n*.msp\n\n# Windows shortcuts\n*.lnk\n\n# content below from: https://github.com/github/gitignore/blob/master/VisualStudio.gitignore\n## Ignore Visual Studio temporary files, build results, and\n## files generated by popular Visual Studio add-ons.\n##\n## Get latest from https://github.com/github/gitignore/blob/master/VisualStudio.gitignore\n\n# User-specific files\n*.suo\n*.user\n*.userosscache\n*.sln.docstates\n\n# User-specific files (MonoDevelop/Xamarin Studio)\n*.userprefs\n\n# Build results\n[Dd]ebug/\n[Dd]ebugPublic/\n[Rr]elease/\n[Rr]eleases/\nx64/\nx86/\nbld/\n[Bb]in/\n[Oo]bj/\n[Ll]og/\n\n# Visual Studio 2015/2017 cache/options directory\n.vs/\n# Uncomment if you have tasks that create the project's static files in wwwroot\n#wwwroot/\n\n# Visual Studio 2017 auto generated files\nGenerated\\ Files/\n\n# MSTest test Results\n[Tt]est[Rr]esult*/\n[Bb]uild[Ll]og.*\n\n# NUNIT\n*.VisualState.xml\nTestResult.xml\n\n# Build Results of an ATL Project\n[Dd]ebugPS/\n[Rr]eleasePS/\ndlldata.c\n\n# Benchmark Results\nBenchmarkDotNet.Artifacts/\n\n# .NET Core\nproject.lock.json\nproject.fragment.lock.json\nartifacts/\n\n# StyleCop\nStyleCopReport.xml\n\n# Files built by Visual Studio\n*_i.c\n*_p.c\n*_h.h\n*.ilk\n*.meta\n*.obj\n*.iobj\n*.pch\n*.pdb\n*.ipdb\n*.pgc\n*.pgd\n*.rsp\n*.sbr\n*.tlb\n*.tli\n*.tlh\n*.tmp\n*.tmp_proj\n*_wpftmp.csproj\n*.log\n*.vspscc\n*.vssscc\n.builds\n*.pidb\n*.svclog\n*.scc\n\n# Chutzpah Test files\n_Chutzpah*\n\n# Visual C++ cache files\nipch/\n*.aps\n*.ncb\n*.opendb\n*.opensdf\n*.sdf\n*.cachefile\n*.VC.db\n*.VC.VC.opendb\n\n# Visual Studio profiler\n*.psess\n*.vsp\n*.vspx\n*.sap\n\n# Visual Studio Trace Files\n*.e2e\n\n# TFS 2012 Local Workspace\n$tf/\n\n# Guidance Automation Toolkit\n*.gpState\n\n# ReSharper is a .NET coding add-in\n_ReSharper*/\n*.[Rr]e[Ss]harper\n*.DotSettings.user\n\n# JustCode is a .NET coding add-in\n.JustCode\n\n# TeamCity is a build add-in\n_TeamCity*\n\n# DotCover is a Code Coverage Tool\n*.dotCover\n\n# AxoCover is a Code Coverage Tool\n.axoCover/*\n!.axoCover/settings.json\n\n# Visual Studio code coverage results\n*.coverage\n*.coveragexml\n\n# NCrunch\n_NCrunch_*\n.*crunch*.local.xml\nnCrunchTemp_*\n\n# MightyMoose\n*.mm.*\nAutoTest.Net/\n\n# Web workbench (sass)\n.sass-cache/\n\n# Installshield output folder\n[Ee]xpress/\n\n# DocProject is a documentation generator add-in\nDocProject/buildhelp/\nDocProject/Help/*.HxT\nDocProject/Help/*.HxC\nDocProject/Help/*.hhc\nDocProject/Help/*.hhk\nDocProject/Help/*.hhp\nDocProject/Help/Html2\nDocProject/Help/html\n\n# Click-Once directory\npublish/\n\n# Publish Web Output\n*.[Pp]ublish.xml\n*.azurePubxml\n# Note: Comment the next line if you want to checkin your web deploy settings,\n# but database connection strings (with potential passwords) will be unencrypted\n*.pubxml\n*.publishproj\n\n# Microsoft Azure Web App publish settings. Comment the next line if you want to\n# checkin your Azure Web App publish settings, but sensitive information contained\n# in these scripts will be unencrypted\nPublishScripts/\n\n# NuGet Packages\n*.nupkg\n# The packages folder can be ignored because of Package Restore\n**/[Pp]ackages/*\n# except build/, which is used as an MSBuild target.\n!**/[Pp]ackages/build/\n# Uncomment if necessary however generally it will be regenerated when needed\n#!**/[Pp]ackages/repositories.config\n# NuGet v3's project.json files produces more ignorable files\n*.nuget.props\n*.nuget.targets\n\n# Microsoft Azure Build Output\ncsx/\n*.build.csdef\n\n# Microsoft Azure Emulator\necf/\nrcf/\n\n# Windows Store app package directories and files\nAppPackages/\nBundleArtifacts/\nPackage.StoreAssociation.xml\n_pkginfo.txt\n*.appx\n\n# Visual Studio cache files\n# files ending in .cache can be ignored\n*.[Cc]ache\n# but keep track of directories ending in .cache\n!*.[Cc]ache/\n\n# Others\nClientBin/\n~$*\n*~\n*.dbmdl\n*.dbproj.schemaview\n*.jfm\n*.pfx\n*.publishsettings\norleans.codegen.cs\n\n# Including strong name files can present a security risk\n# (https://github.com/github/gitignore/pull/2483#issue-259490424)\n#*.snk\n\n# Since there are multiple workflows, uncomment next line to ignore bower_components\n# (https://github.com/github/gitignore/pull/1529#issuecomment-104372622)\n#bower_components/\n\n# RIA/Silverlight projects\nGenerated_Code/\n\n# Backup & report files from converting an old project file\n# to a newer Visual Studio version. Backup files are not needed,\n# because we have git ;-)\n_UpgradeReport_Files/\nBackup*/\nUpgradeLog*.XML\nUpgradeLog*.htm\nServiceFabricBackup/\n*.rptproj.bak\n\n# SQL Server files\n*.mdf\n*.ldf\n*.ndf\n\n# Business Intelligence projects\n*.rdl.data\n*.bim.layout\n*.bim_*.settings\n*.rptproj.rsuser\n\n# Microsoft Fakes\nFakesAssemblies/\n\n# GhostDoc plugin setting file\n*.GhostDoc.xml\n\n# Node.js Tools for Visual Studio\n.ntvs_analysis.dat\nnode_modules/\n\n# Visual Studio 6 build log\n*.plg\n\n# Visual Studio 6 workspace options file\n*.opt\n\n# Visual Studio 6 auto-generated workspace file (contains which files were open etc.)\n*.vbw\n\n# Visual Studio LightSwitch build output\n**/*.HTMLClient/GeneratedArtifacts\n**/*.DesktopClient/GeneratedArtifacts\n**/*.DesktopClient/ModelManifest.xml\n**/*.Server/GeneratedArtifacts\n**/*.Server/ModelManifest.xml\n_Pvt_Extensions\n\n# Paket dependency manager\n.paket/paket.exe\npaket-files/\n\n# FAKE - F# Make\n.fake/\n\n# JetBrains Rider\n.idea/\n*.sln.iml\n\n# CodeRush personal settings\n.cr/personal\n\n# Python Tools for Visual Studio (PTVS)\n__pycache__/\n*.pyc\n\n# Cake - Uncomment if you are using it\n# tools/**\n# !tools/packages.config\n\n# Tabs Studio\n*.tss\n\n# Telerik's JustMock configuration file\n*.jmconfig\n\n# BizTalk build output\n*.btp.cs\n*.btm.cs\n*.odx.cs\n*.xsd.cs\n\n# OpenCover UI analysis results\nOpenCover/\n\n# Azure Stream Analytics local run output\nASALocalRun/\n\n# MSBuild Binary and Structured Log\n*.binlog\n\n# NVidia Nsight GPU debugger configuration file\n*.nvuser\n\n# MFractors (Xamarin productivity tool) working folder\n.mfractor/\n\n# Local History for Visual Studio\n.localhistory/\n\n.vs\n/src/appsettings.Development.json\n/src/Presentations/Windows/appsettings.Development.json\n/src/Presentations/Windows/Extensions/TaskHelpers.cs\n" }, { "path": ".vscode/launch.json", "content": "{\n // Use IntelliSense to learn about possible attributes.\n // Hover to view descriptions of existing attributes.\n // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387\n \"version\": \"0.2.0\",\n \"configurations\": [\n {\n \"name\": \".NET MAUI\",\n \"type\": \"maui\",\n \"request\": \"launch\",\n \"preLaunchTask\": \"maui: Build\"\n },\n {\n \"name\": \".NET Meteor Debugger\",\n \"type\": \"dotnet-meteor.debugger\",\n \"request\": \"launch\",\n \"preLaunchTask\": \"dotnet-meteor: Build\"\n }\n ]\n}" }, { "path": ".vscode/settings.json", "content": "{\n \"vscode_custom_css.imports\": [\n \"file:///C:/Users/Strypper/.vscode/extensions/webrender.synthwave-x-fluoromachine-0.0.12/synthwave-x-fluoromachine.css\"\n \"file:///C:/Users/Strypper/.vscode/extensions/thecodemonkey.synthwave-x-fluoromachine-epic-animations-1.4.13/epic-80s-transitions.css\"\n ]\n}" }, { "path": "CODE_OF_CONDUCT.md", "content": "# Contributor Covenant Code of Conduct\n\n## Our Pledge\n\nWe as members, contributors, and leaders pledge to make participation in our\ncommunity a harassment-free experience for everyone, regardless of age, body\nsize, visible or invisible disability, ethnicity, sex characteristics, gender\nidentity and expression, level of experience, education, socio-economic status,\nnationality, personal appearance, race, religion, or sexual identity\nand orientation.\n\nWe pledge to act and interact in ways that contribute to an open, welcoming,\ndiverse, inclusive, and healthy community.\n\n## Our Standards\n\nExamples of behavior that contributes to a positive environment for our\ncommunity include:\n\n* Demonstrating empathy and kindness toward other people\n* Being respectful of differing opinions, viewpoints, and experiences\n* Giving and gracefully accepting constructive feedback\n* Accepting responsibility and apologizing to those affected by our mistakes,\n and learning from the experience\n* Focusing on what is best not just for us as individuals, but for the\n overall community\n\nExamples of unacceptable behavior include:\n\n* The use of sexualized language or imagery, and sexual attention or\n advances of any kind\n* Trolling, insulting or derogatory comments, and personal or political attacks\n* Public or private harassment\n* Publishing others' private information, such as a physical or email\n address, without their explicit permission\n* Other conduct which could reasonably be considered inappropriate in a\n professional setting\n\n## Enforcement Responsibilities\n\nCommunity leaders are responsible for clarifying and enforcing our standards of\nacceptable behavior and will take appropriate and fair corrective action in\nresponse to any behavior that they deem inappropriate, threatening, offensive,\nor harmful.\n\nCommunity leaders have the right and responsibility to remove, edit, or reject\ncomments, commits, code, wiki edits, issues, and other contributions that are\nnot aligned to this Code of Conduct, and will communicate reasons for moderation\ndecisions when appropriate.\n\n## Scope\n\nThis Code of Conduct applies within all community spaces, and also applies when\nan individual is officially representing the community in public spaces.\nExamples of representing our community include using an official e-mail address,\nposting via an official social media account, or acting as an appointed\nrepresentative at an online or offline event.\n\n## Enforcement\n\nInstances of abusive, harassing, or otherwise unacceptable behavior may be\nreported to the community leaders responsible for enforcement at\nocgrb.strypperjason115@gmail.com.\nAll complaints will be reviewed and investigated promptly and fairly.\n\nAll community leaders are obligated to respect the privacy and security of the\nreporter of any incident.\n\n## Enforcement Guidelines\n\nCommunity leaders will follow these Community Impact Guidelines in determining\nthe consequences for any action they deem in violation of this Code of Conduct:\n\n### 1. Correction\n\n**Community Impact**: Use of inappropriate language or other behavior deemed\nunprofessional or unwelcome in the community.\n\n**Consequence**: A private, written warning from community leaders, providing\nclarity around the nature of the violation and an explanation of why the\nbehavior was inappropriate. A public apology may be requested.\n\n### 2. Warning\n\n**Community Impact**: A violation through a single incident or series\nof actions.\n\n**Consequence**: A warning with consequences for continued behavior. No\ninteraction with the people involved, including unsolicited interaction with\nthose enforcing the Code of Conduct, for a specified period of time. This\nincludes avoiding interactions in community spaces as well as external channels\nlike social media. Violating these terms may lead to a temporary or\npermanent ban.\n\n### 3. Temporary Ban\n\n**Community Impact**: A serious violation of community standards, including\nsustained inappropriate behavior.\n\n**Consequence**: A temporary ban from any sort of interaction or public\ncommunication with the community for a specified period of time. No public or\nprivate interaction with the people involved, including unsolicited interaction\nwith those enforcing the Code of Conduct, is allowed during this period.\nViolating these terms may lead to a permanent ban.\n\n### 4. Permanent Ban\n\n**Community Impact**: Demonstrating a pattern of violation of community\nstandards, including sustained inappropriate behavior, harassment of an\nindividual, or aggression toward or disparagement of classes of individuals.\n\n**Consequence**: A permanent ban from any sort of public interaction within\nthe community.\n\n## Attribution\n\nThis Code of Conduct is adapted from the [Contributor Covenant][homepage],\nversion 2.0, available at\nhttps://www.contributor-covenant.org/version/2/0/code_of_conduct.html.\n\nCommunity Impact Guidelines were inspired by [Mozilla's code of conduct\nenforcement ladder](https://github.com/mozilla/diversity).\n\n[homepage]: https://www.contributor-covenant.org\n\nFor answers to common questions about this code of conduct, see the FAQ at\nhttps://www.contributor-covenant.org/faq. Translations are available at\nhttps://www.contributor-covenant.org/translations.\n" }, { "path": "LICENSE", "content": "MIT License\n\nCopyright (c) 2023 Strypper Vandel Jason\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n" }, { "path": "README.md", "content": "# 🏝️ MAUIsland\n\n![](showcases/version_2.0/summary_slide.png)\n\nMAUIsland is an app that showcases all the .NET MAUI controls available for developers. It allows you to easily interact with them and see how they look and behave on different platforms. It also provides guidance, tips and tricks to help you use them effectively in your own apps. \n\n

\n \n

\n

\n MAUIsland\n

\n

\n Explore and interact. Stay up to date with the .NET MAUI Community.\n

\n

\n \n \"Store\n \n

\n\n# Version 2.0 (Dragon version)\n1. Revamped Design 🎨: The application now features a sleek, acrylic + mica material design. The interface is smoother, with enhanced contrast and reduced distractions, offering users a more engaging experience.\n\n2. Performance Enhancements 🏎️: Significant improvements have been made in page navigation, resulting in a reduced memory footprint. Additionally, internet data is cached locally in a database, enhancing performance and enabling better offline support. The lazy loading of the code view expander contributes to faster initialization of pages.\n\n3. Expanded Community Toolkit 🔨: The Community Toolkit Gallery has been enriched with the addition of four new controls, nine converters, and three layouts, empowering developers with more tools to enhance their applications.\n\n4. GitHub Community Gallery 🤝: We've integrated six widely used GitHub nuggets that are commonly utilized with .NET MAUI, including LiveChart2, ZXing.Net.Maui, and more. This gallery not only provides access to these resources but also offers UI fixes to address issues like stretched clicking and hovering targets for a smoother user interaction.\n5. Explore [Showcases](https://github.com/Strypper/mauisland/blob/main/showcases/version_2.0/Contribute.md)\n\n# ⚠️ Create appsettings.Development.json before run App\n1. Click right MAUIsland in Solution Explorer\n2. Select Add -> New Item -> only JSON File\n3. Set Name: appsettings.Development.json\n4. Click Add and copy the format below (You can leave the key value empty if you don't have the syncfusion key, but this will lead to a crash if you try to view syncfusion controls)\nAdd the json settings from the issue:\n```json\n{\n \"AppSettings\": {\n \"SyncfusionKey\": \"Your_syncfustion_key\",\n \"DiscordApplicationId\": \"Yout_discord_bot_application_id\"\n }\n}\n```\n\n# 🚀 Features\n\n1. Browse through over 50 .NET MAUI controls organized by categories\n2. See live previews of each control on iOS, Android, Windows, and Mac\n3. Learn how to use each control with code snippets and documentation links\n4. Customize each control’s properties and styles\n5. Copy code snippets to the clipboard and use them in your app\n\n# ⬇️ Installation\nTo install .NET MAUI Control Gallery on your device or emulator/simulator:\n\n1. Clone or download this repository\n2. Open the solution file (.sln) in Visual Studio 2022 or later\n3. Select your target platform and device/emulator/simulator\n4. Create the appsettings.Development.json file this file will not contain any private key\n5. Build and run the app\n\nWe will publish our application on all platforms soon enough. Stay tuned!!!\n\n# ⁉ Support\n\nIf you need help with something or have an idea, feel free to start a [Discussion](https://github.com/CommunityToolkit/WindowsCommunityToolkit/discussions) or find us on [Discord](https://discord.gg/edgzveQ9KN). If you have detailed repro steps, open an [issue here instead](https://github.com/Strypper/mauisland/issues/new/choose).\n\n# 📄 Code of Conduct\n\nThis project has adopted the code of conduct defined by the [Contributor Covenant](http://contributor-covenant.org/)\nto clarify expected behavior in our community.\nFor more information see the [.NET Foundation Code of Conduct](CODE_OF_CONDUCT.md).\n\n# Meet the contributors\n\n \n\n\nMade with [contrib.rocks](https://contrib.rocks).\n" }, { "path": "build.cake", "content": "#addin nuget:?package=Cake.FileHelpers&version=6.0.0\n\nvar target = Argument(\"target\", \"BuiltInControlPage\");\nvar group = Argument(\"group\", \"BuiltIn\");\nvar name = Argument(\"name\", \"AwesomeControl\");\nvar cardDetail = Argument(\"cardDetail\", \"CardDetail\");\nvar originalDocumentUrl = Argument(\"originalDocumentUrl\", \"DocumentLink\");\nvar configuration = Argument(\"configuration\", \"Release\");\n\n//////////////////////////////////////////////////////////////////////\n// TASKS\n//////////////////////////////////////////////////////////////////////\n\nconst string CONTROL_FODLER_PATH_TEMPLATE=\"./src/Features/Gallery/Pages/{0}/{1}\";\n\nTask(\"BuiltInControlPage\")\n .Does(() =>\n{\n var controlFolderPath = string.Format(CONTROL_FODLER_PATH_TEMPLATE, group, name);\n Information(\"Control folder path: \" + controlFolderPath);\n \n if (DirectoryExists(controlFolderPath)) {\n Warning(\"Control folder path exists\");\n return;\n }\n\n CreateDirectory(controlFolderPath);\n\n Information($\"\\n>> Generate >> {name}ControlInfo.cs\");\n FileWriteText($\"{controlFolderPath}/{name}ControlInfo.cs\", $@\"namespace MAUIsland.Gallery.{group};\nclass {name}ControlInfo : IGalleryCardInfo \n{{\n public string ControlName => nameof({name});\n public string ControlRoute => typeof({name}Page).FullName;\n public ImageSource ControlIcon => new FontImageSource()\n {{\n FontFamily = FontNames.FluentSystemIconsRegular,\n Glyph = FluentUIIcon.Ic_fluent_approvals_app_20_regular\n }};\n public string ControlDetail => \"\"{cardDetail}\"\";\n public string GitHubUrl => $\"\"https://github.com/Strypper/mauisland/tree/main/src/Features/Gallery/Pages/{group}/{{ControlName}}\"\";\n public string DocumentUrl => $\"\"{originalDocumentUrl}\"\";\n public string GroupName => ControlGroupInfo.{group}Controls;\n}}\");\n\n Information($\"\\n>> Generate >> {name}Page.xaml\");\n FileWriteText($\"{controlFolderPath}/{name}Page.xaml\", $@\"\n\n\n \n \n \n \n \n \n\n \n {name} defines the following properties:\n \n\n \n These properties are backed by BindableProperty objects, which means that they can be targets of data bindings, and styled.\n \n\n \n \n Color, of type Color , value that defines the color of the ActivityIndicator.\n ]]>\n \n \n IsRunning, of type bool,value that indicates whether the ActivityIndicator should be visible and animating, or hidden. The default value of this property is false, which indicates that the ActivityIndicator isn't visible.\n ]]>\n \n \n\n\n \n\n \n \n \n \n \n\");\n\n Information($\"\\n>> Generate >> {name}Page.xaml.cs\");\n FileWriteText($\"{controlFolderPath}/{name}Page.xaml.cs\", $@\"namespace MAUIsland;\npublic partial class {name}Page : IGalleryPage\n{{\n #region [CTor]\n public {name}Page({name}PageViewModel vm)\n {{\n InitializeComponent();\n\n BindingContext = vm;\n }}\n #endregion\n}}\");\n\n Information($\"\\n>> Generate >> {name}PageViewModel.cs\");\n FileWriteText($\"{controlFolderPath}/{name}PageViewModel.cs\", $@\"namespace MAUIsland;\npublic partial class {name}PageViewModel : NavigationAwareBaseViewModel\n{{\n #region [CTor]\n public {name}PageViewModel(\n IAppNavigator appNavigator\n ) : base(appNavigator)\n {{\n }}\n #endregion\n\n #region [Properties]\n [ObservableProperty]\n IGalleryCardInfo controlInformation;\n #endregion\n\n #region [Overrides]\n protected override void OnInit(IDictionary query)\n {{\n base.OnInit(query);\n\n ControlInformation = query.GetData();\n\n }}\n #endregion\n}}\");\n});\n\n//////////////////////////////////////////////////////////////////////\n// EXECUTION\n//////////////////////////////////////////////////////////////////////\n\nRunTarget(target);\n" }, { "path": "docs/pull_request_template.md", "content": "# COOL NEW PAGE !!!!\n### Page name: `Page`\n \n## Contributors\n\n[//]: contributor-faces\n\n\n\n[//]: contributor-faces\n \n## Describe your changes\n\n## Have we discussed about this before ? (Please link the discussion link below)\n\n## Added page requirements as following:\n- [ ] Page.xaml\n - [ ] Change the `x:Class` to project namespace standard (ex: `x:Class=\"MAUIsland.LabelPage\"`)?\n - [ ] Include `xmlns:app=\"clr-namespace:MAUIsland\"`?\n - [ ] Change `ContentPage` to `app:BasePage`?\n - [ ] Hook the `x:DataType` to the ViewModel?\n - [ ] Provide `Padding=\"10\"` to `app:BasePage`?\n - [ ] Provide `ControlInfo` to `app:BasePage.Resources`?\n - [ ] Provide `PropertiesListHeader` to `app:BasePage.Resources`?\n - [ ] Provide `PropertiesListFooter` to `app:BasePage.Resources`?\n - [ ] Provide `PropertyItemsSource` to `app:BasePage.Resources`?\n - [ ] Provide a brief `Control Info` UI ?\n ```xml\n \n