View Details

Yesterday marked a bitter sweet moment in the world of mobile development: Xamarin, a tool that has been instrumental in the evolution of cross-platform mobile applications, was officially archived. This news brings a mix of emotions for me. As a... Continue Reading →

View Details

I am writing this at 2 AM so there will certainly be some emotions involved, but this blog post needs to be written.

Yesterday it was the 1st of May, 2024, and the Xamarin reached the end of its life (support), with a short message:

Xamarin support ended on May 1, 2024 for all Xamarin SDKs including Xamarin.Forms.

... and the public repository has been archived forever.

To be honest, this was announced way back, enough months ago, but this happening triggered some emotions in me.

I am writing this because the Xamarin project and the whole community around it greatly impacted my professional and private life.

Through the last 8 years, I delivered more than 30 Xamarin-related sessions and workshops and answered a lot of questions about it, I can proudly say that I spread a huge amount of word regarding Xamarin... and back in 2018, I made also a couple of code contributions to Xamarin.Forms.

And now, the code written by me will always stay there, sealed and archived, resting and living inside thousands of mobile apps.

I will always remember the first time my PR was approved, and how I felt when my code was merged into the Xamarin.Forms project. Those moments are for life! ❤️

I got the recognition from MicrosoftFor the first time, I started playing with Xamarin back in 2016, and after a few lines of code, I fell in love, which led to the fact that this platform will always be in my heart ❤️

  View this post on Instagram      A post shared by Almir Vuk (@almir.vuk)

Through this journey I had a chance to meet and hang out with some of the greatest people I know, I contributed to the Xamarin.Forms project, I have written a lot of Xamarin content on my blog, I spoke at Xamarin Expert Day events a couple of times.

And one of my favourite photos ever was taken at Xamarin Expert Day in Cologne.

Back in 2019, Cologne, Germany, Xamarin Expert Day ❤️... more speaking engagements here:

Speaking about Xamarin in Zagreb, Croatia, in December of 2017Speaking about Xamarin.Forms in Neum, Bosnia and Herzegovina, April 2017Portoroz, Slovenia, Xamarin session, 2019... and there a lot of more and a huge bucket of great memories and events related to Xamarin!

Now what comes next?
Microsoft now has .NET MAUI and a new project and I want to see them succeed with it. If you did not check it out, you should definitely!

In short words, .NET MAUI is:

*Multi-platform*
.NET MAUI uses the latest technologies for building native apps on Windows, macOS, iOS, and Android, abstracting them into one common framework built on .NET.

*One codebase*
Use a single C# codebase and project system for all device targets to build apps that look and feel like the native platforms.

*Productive*
Build beautiful apps faster and easier by integrating the power of Visual Studio with .NET MAUI.

... and regarding me, I will continue to play with .NET MAUI, and mobile apps as a side project for now.

Currently, I am working as a Lead Architect at run.events GmbH, where my daily work is not much related to the mobile side.

But you can expect here to read content about .NET MAUI or mobile development from time to time.

Regarding the mobile dev, in my free time, I am working on my own workshop regarding mobile development and it will be based on different mobile frameworks including the .NET MAUI.

Thank you, Xamarin! 💙
I am sad to see Xamarin going away, but I am confident that the .NET MAUI team will do their best to keep this .NET mobile story going with the MAUI project.

I am sad to see Xamarin reaching the end since it had a huge impact on my career, my private life, my connections, the stories which are written, the friends which are made, and the best community in the world this framework had!

I will always remember the "old days" and the old version of Xamarin, all the interactions we had on Twitter, and at the events... I will always remember Xamarin University, Planet Xamarin... and the best team working on it...

... in other words, this special framework will always be in my heart!

So Long, and Thanks for All the Fish, Xamarin! 💙

... Requiescat in pace, my friend Xamarin 💌

View Details

TL;DR: Learn to design a directional compass using Syncfusion .NET MAUI Radial Gauge control. Dynamically update the directional compass values using the Compass sensor and customize the Radial Guage’s appearance for better visualization.

Syncfusion .NET MAUI Radial Gauge is a multi-purpose data visualization control that displays numerical values on a circular scale. Its rich set of features includes axes, ranges, pointers, and annotations that are fully customizable and extendable. We can use this control to design speedometers, temperature monitors, multi-axis clocks, circular progress indicators, watches, and more.

In this blog, we’ll see how to design a directional compass using the Syncfusion .NET MAUI Radial Gauge control and update the direction using the Compass sensor.

Let’s dive in!

Understanding the compass sensorThe Compass sensor monitors the device’s orientation relative to the Earth’s magnetic North. By providing real-time information on device heading direction, it enables us to create dynamic compass apps.

For more details, refer to the Compass Platform-specific information.

Monitoring the compass sensorUsing the Compass sensor, you can monitor the device’s magnetic North heading. Using the ICompass interface, you can determine whether the compass is actively monitored or not. The IsMonitoring property returns true if monitoring is ongoing. You can start monitoring using the ICompass.Start and stop it with ICompass.Stop methods.

Refer to the following code example.

RadialGuageViewModel.cs

private void ToggleCompass(){ if (Compass.Default.IsSupported) { if (!Compass.Default.IsMonitoring) { Compass.Default.ReadingChanged += OnCompassReadingChanged; Compass.Default.Start(SensorSpeed.UI); } else { Compass.Default.Stop(); Compass.Default.ReadingChanged -= OnCompassReadingChanged; } }} Updating the compass heading changesTo obtain the changes in the compass heading, we will utilize the ICompass.ReadingChanged event. By using this event and handling it in our OnCompassReadingChanged method, we can dynamically update the compass direction.

Refer to the following code example.

RadialGuageViewModel.cs

private double reading, rotationAngle; public double Reading { get { return reading; } set { reading = value; this.RaisePropertyChanged(nameof(Reading)); } } public double RotationAngle { get { return rotationAngle; } set { rotationAngle = value; this.RaisePropertyChanged(nameof(RotationAngle)); } } private void OnCompassReadingChanged(object sender, CompassChangedEventArgs e) { this.Reading = e.Reading.HeadingMagneticNorth; this.RotationAngle = 360 - e.Reading.HeadingMagneticNorth; } In the above code example, we’ve updated the Reading property with the current heading and calculated the rotation angle to reflect the direction accurately.

The RadialGuageViewModel class subscribes to the Compass.ReadingChanged event to receive updates on compass heading changes. Within the event handler Compass_ReadingChanged, you can handle the compass heading changes as required.

Refer to the following code example, which illustrates how to update the direction text based on the compass heading changes dynamically.

RadialGuageViewModel.cs

private string readingText;public string ReadingText{ get { return readingText; } set { readingText = value; this.RaisePropertyChanged(nameof(ReadingText)); }} private void OnCompassReadingChanged(object sender, CompassChangedEventArgs e){ this.Reading = e.Reading.HeadingMagneticNorth; this.RotationAngle = 360 - e.Reading.HeadingMagneticNorth; var degree = (int)this.Reading; string direction = string.Empty; if (degree < 30) { direction = "N"; } else if (degree >= 30 && degree < 90) { direction = "NE"; } else if (degree >= 90 && degree <= 120) { direction = "E"; } else if (degree >= 120 && degree < 180) { direction = "SE"; } else if (degree >= 180 && degree <= 210) { direction = "S"; } else if (degree >= 210 && degree < 270) { direction = "SW"; } else if (degree >= 270 && degree <= 300) { direction = "W"; } else if (degree >= 300 && degree < 360) { direction = "NW"; } ReadingText = $"{degree}\u00B0 {direction}";} The RadialGuageViewModel class efficiently handles updating direction text when there are changes in the compass heading.

Designing a directional compass using .NET MAUI Radial GaugeWe can create a visually appealing and functional compass by customizing the .NET MAUI Radial Gauge’s properties and binding the Compass sensor values.

To do so, please follow these steps:

Step1: Register the Syncfusion core handlerFirst, we should set up the Syncfusion core handler in the MauiProgram.cs file to utilize the Syncfusion NET MAUI controls (In this case, Radial Gauge).

MauiProgram.cs

builder .UseMauiApp<App>() .ConfigureSyncfusionCore() Step 2: Initialize the Radial GaugeInitialize the Syncfusion .NET MAUI Radial Gauge control in the MainPage.xaml file using this documentation.

Refer to the following code example.

xmlns:gauge="clr-namespace:Syncfusion.Maui.Gauges;assembly=Syncfusion.Maui.Gauges"<gauge:SfRadialGauge/> Step 3: Customize the Radial Gauge axis angleLet’s customize the Radial Gauge axis by setting its StartAngle and EndAngle to 270 degrees to place the North (N) direction label at the top. Usually, the Radial Gauge axis’s start angle is zero and will be updated clockwise by default.

Refer to the following code example.

MainPage.xaml

<gauge:SfRadialGauge> <gauge:SfRadialGauge.Axes> <gauge:RadialAxis StartAngle="270" EndAngle="270" RadiusFactor="0.6"> </gauge:RadialAxis> </gauge:SfRadialGauge.Axes></gauge:SfRadialGauge> Step 4: Customize the Radial Gauge axis labelYou can customize the Radial Gauge axis labels by adjusting the properties such as LabelPosition, CanRotateLabels, Minimum, Maximum, and ShowLastLabel properties.

Refer to the following code example.

MainPage.xaml

<gauge:SfRadialGauge> <gauge:SfRadialGauge.Axes> <gauge:RadialAxis LabelPosition="Outside" CanRotateLabels="True" Minimum="0" Maximum="360" ShowLastLabel="False"> </gauge:SfRadialGauge.Axes> Step 5: Customize Radial Gauge axis ticksThen, customize the Radial Gauge axis ticks by utilizing the TickPosition, ShowAxisLine, and MinorTicksPerInterval properties.

Refer to the following code example.

MainPage.xaml

<gauge:SfRadialGauge> <gauge:SfRadialGauge.Axes> <gauge:RadialAxis ShowAxisLine="False" TickPosition="Outside" MinorTicksPerInterval="5" Interval="30"> <gauge:RadialAxis.MajorTickStyle> <gauge:RadialTickStyle LengthUnit="Pixel" StrokeThickness="2" Length="15" /> </gauge:RadialAxis.MajorTickStyle> <gauge:RadialAxis.MinorTickStyle> <gauge:RadialTickStyle LengthUnit="Pixel" Length="10" /> </gauge:RadialAxis.MinorTickStyle> </gauge:SfRadialGauge.Axes> Step 6: Customize the Radial Gauge axis shape pointerUsing the ShapePointer class, let’s add an inverted triangle to indicate the current value on the Radial Gauge axis.

MainPage.xaml

<gauge:RadialAxis.Pointers> <gauge:ShapePointer Offset="-45" OffsetUnit="Pixel" ShapeType="InvertedTriangle" /></gauge:RadialAxis.Pointers> Step 7: Customize the Radial Gauge axis needle pointerNow, add a NeedlePointer to indicate the directions as shown in the following code example.

MainPage.xaml

<gauge:RadialAxis.Pointers> <gauge:NeedlePointer Value="0" NeedleLengthUnit="Factor" NeedleLength="0.3" NeedleStartWidth="1" NeedleEndWidth="1" NeedleFill="#FFC4C4C4" KnobRadius="0" TailLengthUnit="Factor" TailLength="0.3" TailWidth="1" TailFill="#FFC4C4C4"> </gauge:NeedlePointer> <gauge:NeedlePointer Value="270" NeedleLengthUnit="Factor" NeedleLength="0.3" NeedleStartWidth="1" NeedleEndWidth="1" NeedleFill="#FFC4C4C4" KnobRadius="0" TailLengthUnit="Factor" TailLength="0.3" TailWidth="1" TailFill="#FFC4C4C4"> </gauge:NeedlePointer></gauge:RadialAxis.Pointers> Step 8: Customize Radial Gauge axis annotationTo enhance the visual representation of the Radial Gauge, add the direction label onto the gauge axis using the Annotations.

MainPage.xaml

<gauge:RadialAxis.Annotations> <gauge:GaugeAnnotation DirectionUnit="AxisValue" DirectionValue="270" PositionFactor="0.6"> <gauge:GaugeAnnotation.Content> <Label Text="W" FontAttributes="Bold" FontSize="20" TextColor="Black" /> </gauge:GaugeAnnotation.Content> </gauge:GaugeAnnotation> <gauge:GaugeAnnotation DirectionUnit="AxisValue" DirectionValue="0" PositionFactor="0.6"> <gauge:GaugeAnnotation.Content> <Label Text="N" FontAttributes="Bold" FontSize="20" TextColor="Black" /> </gauge:GaugeAnnotation.Content> </gauge:GaugeAnnotation> <gauge:GaugeAnnotation DirectionUnit="AxisValue" DirectionValue="90" PositionFactor="0.6"> <gauge:GaugeAnnotation.Content> <Label Text="E" FontAttributes="Bold" FontSize="20" TextColor="Black" /> </gauge:GaugeAnnotation.Content> </gauge:GaugeAnnotation> <gauge:GaugeAnnotation DirectionUnit="AxisValue" DirectionValue="180" PositionFactor="0.6"> <gauge:GaugeAnnotation.Content> <Label Text="S" FontAttributes="Bold" FontSize="20" TextColor="Black" /> </gauge:GaugeAnnotation.Content> </gauge:GaugeAnnotation></gauge:RadialAxis.Annotations> Designing a directional compass using .NET MAUI Radial GaugeBind compass value in the .NET MAUI Radial GaugeFinally, bind the Compass’ Reading property value from the RadialGuageViewModel class in the .NET MAUI Radial Gauge axis Shape pointer, which indicates the current direction.

Also, bind the RotationAngle property value from the RadialGuageViewModel class to the Radial Gauge’s Rotation property to rotate the Radial Gauge based on the Compass value.

Refer to the following code example.

MainPage.xaml

xmlns:system="clr-namespace:System;assembly=netstandard" <VerticalStackLayout.BindingContext> <local:RadialGuageViewModel/></VerticalStackLayout.BindingContext><!--Display direction text--> <Label x:Name="CompassLabel" HorizontalTextAlignment="Center" FontAttributes="Italic,Bold" VerticalOptions="Center" HorizontalOptions="Center"> <Label.FormattedText> <FormattedString> <Span Text="Current location" /> <Span Text="{x:Static system:Environment.NewLine}" /> <Span Text="{Binding ReadingText}" FontAutoScalingEnabled="True" FontAttributes="Italic,Bold" FontSize="20" /> </FormattedString> </Label.FormattedText> </Label> <!-- Bind Compass value in the .NET MAUI Radial Gauge --> <gauge:SfRadialGauge Rotation="{Binding RotationAngle}" > <gauge:SfRadialGauge.Axes> … <gauge:RadialAxis.Pointers> <gauge:ShapePointer Value="{Binding Reading}" Offset="-100" OffsetUnit="Pixel" ShapeType="InvertedTriangle" /> </gauge:RadialAxis.Pointers> </gauge:SfRadialGauge.Axes> </gauge:SfRadialGauge> Refer to the following output image

Dynamically updating the directional compass valuesGitHub referenceFor more details, refer to Creating a directional compass using .NET MAUI Radial Gauge GitHub demo.

ConclusionThanks for reading! In this blog, we’ve seen how to design a directional compass using Syncfusion’s .NET MAUI Radial Gauge control and how to update its direction using the Compass sensor.

We’d appreciate your feedback! If you have any suggestions, specific requirements, or ideas for controls you’d like to see in our .NET MAUI suite, please share them in the comments section below.

Syncfusion’s .NET MAUI controls are meticulously crafted with .NET MAUI, ensuring seamless integration with native framework controls. Optimized to handle extensive data, these controls are ideal for developing high-quality, cross-platform mobile and desktop apps.

If you need further assistance, don’t hesitate to contact us through our support forum, support portal, or feedback portal. We’re always ready to help!

Related blogs* Developing a Temperature Monitor UI in .NET MAUI * Everything You Need to Know About .NET MAUI Radial Gauge Control * Design Different Styles of Radial Sliders Using the .NET MAUI Radial Gauge * Create a Modern Conversational UI with the .NET MAUI Chat Control

View Details

View Details

This blog explains how to create a patient appointment manager app using Syncfusion .NET MAUI controls.

View Details

In October 2022, Microsoft announced that Xamarin and Xamarin.Forms apps will no longer be supported after May 1, 2024, which is just eight months from the writing of this post. The reason for this deadline is that Xamarin is being replaced by its successor technology, .NET MAUI.

What Happens if You Do Nothing?

Most likely, your Xamarin apps will continue working for a few months after that date. However, starting on May 1, Apple will require that updates to any apps be built with their latest SDKs, versions that will not be supported by older versions of Xamarin (but are supported by .NET MAUI). And Google will likely do the same at a later date. This is why you’ll have to upgrade to .NET MAUI before you can make even the smallest update or fix to your app and release it to the store.

Several months later, the app stores will likely start to remove apps that haven’t been updated to their latest SDKs, meaning your Xamarin app that hasn’t been updated to .NET MAUI will be delisted.

Upgrade Path: Xamarin Native Apps

For businesses with Xamarin Native apps, the migration to .NET for iOS and .NET for Android can be a shorter effort than that required from Xamarin.Forms apps. To assist with this, Trailhead Technology Partners offers a structured approach, starting with a thorough analysis of your existing Xamarin Native app.

Our experienced mobile developers can then refactor and adapt your codebase to the latest versions of .NET, optimizing performance, and leveraging any new .NET MAUI features. Throughout the migration process, we prioritize maintaining app functionality and a first-class user experience, ensuring a seamless transition for your users.

Upgrade Path: Xamarin.Forms Apps

Xamarin.Forms apps can be migrated to .NET MAUI. While this can require a bit of manual work, it has the benefit of getting your app onto the very latest .NET mobile technologies.

Trailhead Technology Partners guides this migration by first assessing your Xamarin.Forms app to identify any necessary adjustments before migrating it to a .NET MAUI app. Our skilled team then undertakes any necessary code modifications and UI changes, all while leveraging .NET MAUI’s advanced features to deliver a consistent and polished user experience across multiple platforms.

With a focus on code reusability and responsive design, Trailhead will ensure that your app shines in .NET MAUI.

Similarities to Y2K

You also may have noticed that this May ’24 deadline for migrating Xamarin apps to .NET MAUI bears some resemblances to the Y2K crisis. Just as the year 2000 threatened to disrupt software due to the way dates were encoded, the shift to .NET MAUI is driven by the need to modernize and adapt to the changing mobile technological landscape. And as with Y2K, ignoring this transition could lead to serious consequences, including app delisting and loss of business.

However, with the right strategy and partners in place, this situation can be turned into an opportunity for growth and modernization of your mobile app.

Four Options: Which One Is Right for You?

Hopefully, by now you’re convinced to make the upgrade. If so, you may be wondering what process is the best fit for your specific mobile app. At Trailhead, we can help evaluate your app’s specific needs, but we see all Xamarin apps falling under one of these four approaches:

1. Migrate to .NET MAUI or Xamarin Native to .NET

The first and most proactive option is to migrate your Xamarin.Forms apps to .NET MAUI and Xamarin Native to .NET for iOS and Android. Beginning this migration process early is imperative to ensure enough time for a smooth transition before the May ’24 deadline.

At Trailhead, we specialize in these migrations, with a deep understanding of both Xamarin and .NET MAUI ecosystems. Our experienced team will work closely with you to ensure your apps not only meet the new technological standards but also leverage the enhanced capabilities of .NET MAUI.

2. Embrace Web-Based Mobile Technologies

Another viable path forward is migrating your Xamarin or Xamarin.Forms apps to web-based technologies like React Native or Ionic. By leveraging web technologies, some teams can streamline their development processes and potentially reach a broader audience. However, this option requires careful consideration of your app’s complexity, your team’s capabilities, and your specific user experience requirements.

Trailhead’s expertise in both native and web-based app development equips us to guide you through this transition and recommend the best approach for your business.

3. Graceful App Shutdown

If your app’s lifecycle has reached its natural end, gracefully shutting it down before the May ’24 deadline could be a prudent decision. This approach ensures a smooth exit for your users and prevents any negative impact on your brand’s reputation.

Our team at Trailhead can help you devise an exit strategy that minimizes disruption and communicates the transition effectively to your user base.

4. Do Nothing

Our least recommended approach is to do nothing and risk crashing out of the app stores. Inaction could lead to app delisting and a loss of customer trust. At Trailhead, we strongly advise against this approach. Before allowing this to happen, please contact us so we can leverage our expertise to help you navigate your options.

Trailhead: Your Migration Partner

At Trailhead Technology Partners, we are experts in cross-platform mobile development and understand the importance of planning carefully for your Xamarin to .NET MAUI transition. With our extensive experience in building Xamarin and Xamarin.Forms apps, we’re poised to guide you through this process seamlessly.

Our team of experts will collaborate closely with your business to determine the best path forward, ensuring your apps remain relevant, reliable, and competitive beyond May 2024. Don’t let this transition be a daunting challenge—let it be a steppingstone towards innovation and growth.

Contact Trailhead today to embark on this exciting journey together!

The post Are You Prepared for the End of Xamarin Support? appeared first on Trailhead Technology Partners.

View Details

View Details

//I will be updating this post soon
Inside azure portal Create a Resouce “+” sign >Select Mobile> SelectMobileApp>
I have written :
AppName : MyForm
Subscription:Payasyougo
Select a new resource group or create a new one
Now you have to select free plan for dev/testers for Appservice Plans and Create it
Step2:
After your service is activated then go to all resouces and select myform(appservice)
Inside which you have to select EasyTable option:
Create a database for now i am creating a free database use any credential as you like and select the free category for testing database API.
Step3:
After Free DataBase API is created then we have to

View Details

Embedding  free icons :
Step 1 :  Download the .ttf file from here :   https://materialdesignicons.com/

Step 2 : Add the .ttf file inside  shared project [In my case materialdesignicons-webfont.ttf is my .ttf  file]

Step 3 : Inside your Shared Project you will have assemblyinfo.cs file.
Put this assembly info  :
[assembly: ExportFont(“materialdesignicons-webfont.ttf”, Alias = “PermanentMarker”)]
You can Rename Alias Name as  “materialdesignicons” too.

Step 4 : Inside your MainPage.Xaml

<Image BackgroundColor=”Red” VerticalOptions=”CenterAndExpand” HorizontalOptions=”CenterAndExpand”>
<Image.Source>
<FontImageSource Glyph=”&#xf029;” FontFamily=”materialdesignicons-webfont” Size=”44″/>
</Image.Source> </Image>

Embedding Text Font inside Xamarin forms :

Step 1  : Download ttf file from here  https://fonts.google.com/
Step 2 : Add  .ttf file inside shared Project

Step 3 : Inside your Shared Project you will have assemblyinfo.cs file.
Put this assembly info  :
[assembly: ExportFont(“Pacifico-Regular.ttf”, Alias = “Pacifico”)]/

Step 4 : Inside your MainPage.Xaml

<Label Text=”Welcome to Xamarin.Forms!” FontFamily=”Pacifico” HorizontalOptions=”Center”
VerticalOptions=”CenterAndExpand” >
</Label>

View Details

Different regions and cultures follow distinct calendar systems, reflecting their unique traditions and historical context. These calendar systems often vary in month lengths, year starts, and year ends. In today’s globalized world, developing applications that cater to users from diverse cultures and regions is essential.

The Syncfusion .NET MAUI Calendar control provides different calendar types, enabling developers to cater to a broader user base and users to interact with dates according to their cultural or regional preferences.

In this blog, we’ll explore the different calendar types and their basic functionalities in the .NET MAUI Calendar control.

Note: If you are new to this control, refer to the .NET MAUI Calendar getting started documentation for background knowledge.

Different calendar types

The .NET MAUI Calendar supports different calendar types and displays dates, months, and years based on the one specified. Gregorian is the default calendar type.

You can easily change the calendar type using the Identifier property in the SfCalendar. Refer to the following code example.

<calendar:SfCalendar x:Name="Calendar" Identifier="Hijri"> </Calendar:SfCalendar>

Different calendar views

The .NET MAUI Calendar control enriches the experience of using different calendar types by incorporating various calendar views, including month, year, decade, and century views. These distinct views offer versatile options for interacting with dates, months, and years based on the specified calendar type.

Different calendar views in .NET MAUI Calendar control

You can change the calendar view using the View property in the SfCalendar. Refer to the following code example.

<calendar:SfCalendar x:Name="Calendar" Identifier="Hijri" View="Month"> </Calendar:SfCalendar>

Specifying the date value

When working with different calendar types in the .NET MAUI Calendar, you can assign a date value to its properties in two ways.

Generating a date

You can create a date value by declaring the calendar type while creating the date instance.

Refer to the following code example. Here, we’ve declared the date by specifying the calendar type as Hijri.

SfCalendar calendar = new SfCalendar();Calendar hijriCalendar = new HijriCalendar();DateTime date = new DateTime(1444, 12, 6, hijriCalendar);calendar.SelectedDate = date;

Generating a date without calendar type

You can also create a date value without explicitly specifying the calendar type. In this case, the .NET MAUI Calendar will automatically convert and interpret the date value based on the specified local system’s calendar type.

Refer to the following code example. Here, we’ve used the Gregorian date, but the .NET MAUI Calendar control converts it to the corresponding Hijri calendar date.

SfCalendar calendar = new SfCalendar();DateTime date = new DateTime(2023, 6, 24);calendar.SelectedDate = date;

Specifying the flow direction

The .NET MAUI Calendar control automatically adjusts the flow direction based on the specified calendar type. This means that when you choose a calendar type with a right-to-left flow direction, such as in the Arabic calendar, the .NET MAUI Calendar control will automatically display the calendar elements in a right-to-left orientation.

The right-to-left supported calendar types in the .NET MAUI Calendar are:

• Hijri
• Persian
• UmAlQura

Conclusion

Thanks for reading! In this blog, we have explored the various calendar types available in the Syncfusion .NET MAUI Calendar control and their versatile features. With this, you can enhance the experience of your global users.

Explore other features in the Calendar control in its documentation. Try out the .NET MAUI demos available on GitHub and share your feedback or ask questions in the comments section.

If you are not a Syncfusion customer, try our 30-day free trial to see how our components can enhance your productivity.

You can also contact us through our support forum, support portal, or feedback portal. We are always happy to assist you!

Related Blogs

• Chart of the Week: Creating a .NET MAUI Horizontal Bar Chart to Compare Grocery Prices Between Two Countries
• Replicating a Storage UI in a .NET MAUI App
• Easily Build ChatGPT-like App in .NET MAUI using OpenAI APIs
• Load Custom Badge UI in Your .NET MAUI App: An Overview

View Details

As you may already know, there’s no App Center support for .NET MAUI yet (and possibly won’t be). Trailhead is using Azure Pipelines for many of our projects, including for generating our mobile builds and distributing them to the app stores (Apple and Android). One of the challenges when you do this is bringing in […]

The post Using Private NuGet Feeds with .NET MAUI and Azure Pipelines appeared first on Trailhead Technology Partners.

View Details

Hi there 👋

As you know or maybe don't know. I write for *InfoQ*, and approximately I wrote 3-4 news coverage articles per month.

I am part of the *.NET Content editors team* and each month, we write and cover new stuff in the #dotnet world.

Last month, August 2023, I

View Details

Syncfusion is preparing for its third major release of the year, Essential Studio 2023 Volume 3. It will bring exciting new features to enhance the user experience. Anticipated for release by the end of September, we’re confident that this update will surpass our users’ expectations.

In this blog, we’ll see some new features we expect to roll out in the Syncfusion Xamarin platform as part of 2023 Volume 3.

PDF Viewer

You can expect the following new features in the Xamarin.Forms PDF Viewer.

Text search for rotated text and documents

This feature will allow you to search for specific words that are rotated in normal and rotated PDF documents. This will help us save time when compared with manual scrolling through pages to find the needed content.

Render the document link annotation’s border

From 2023 Volume 3 on, you can render borders for the document link annotations.

GoTo action button for the form field

You can navigate to a specific page in a PDF when pressing the GoTo button in the form field.

Conclusion

Thanks for reading! Along with these highlights, you can enjoy other exciting new features and bug fixes in our Syncfusion Xamarin platform for the 2023 Volume 3 release. Check them out once the release is launched. It won’t be long!

Stay tuned to our official YouTube, Twitter, Facebook, and LinkedIn channels for announcements about the release. Please let us know in the comments section below if you have any feedback.

You can also reach us through our support forums, support portal, or feedback portal. We are always happy to assist you!

Related blogs

• Step-by-Step Guide: Downloading PDFs from SharePoint and Displaying Them in a Xamarin App
• Easily Lock and Unlock Annotations Using Xamarin.Forms PDF Viewer
• Lazy Load JSON Data in Xamarin.Forms ListView: An Overview
• View PDF Annotations as a List and Navigate Using Xamarin.Forms PDF Viewer

View Details

Welcome to our Chart of the Week blog series!

Today, we’ll create a horizontal bar chart to visualize the price comparison of groceries using the Syncfusion .NET MAUI Cartesian Charts control. This control is supported on both desktop (Windows and Mac) and mobile platforms (Android and iOS).

In this blog post, we’ll compare the prices of groceries in the United States and the United Kingdom using a horizontal bar chart that resembles a pyramid graph. It will allow us to identify and compare the prices of various grocery items easily.

Let’s get started!

Step 1: Collecting grocery price data

Before creating the chart, let’s gather data on grocery prices in the United States and the United Kingdom.

Step 2: Preparing data for the chart

Create a Model class that includes properties for storing information about grocery items and their prices in the United States and the United Kingdom.

Refer to the following code example.

public class Model{ public string GroceryItem { get; set; } public double USPrice { get; set; } public double UKPrice { get; set; } }

Then, configure the ViewModel class to create a collection of grocery item price details and store it in an observable collection using the GroceryPriceDetails property.

Refer to the following code example.

public class ViewModel{ public ObservableCollection<Model> GroceryPriceDetails { get; set; } public ViewModel() { GroceryPriceDetails = new ObservableCollection<Model>(); GroceryPriceDetails.Add(new Model() { GroceryItems = "Milk (1 L)", USPrice = 1.03, UKPrice = 1.05 }); GroceryPriceDetails.Add(new Model() { GroceryItems = "White Bread (500 g)", USPrice = 3.54, UKPrice = 1.08 }); GroceryPriceDetails.Add(new Model() { GroceryItems = "White Rice (1 kg)", USPrice = 4.56, UKPrice = 1.42 }); GroceryPriceDetails.Add(new Model() { GroceryItems = "Eggs (12)", USPrice = 4.40, UKPrice = 2.27 }); GroceryPriceDetails.Add(new Model() { GroceryItems = "Chicken Fillets(1 kg)", USPrice = 12.00, UKPrice = 5.89 }); ; GroceryPriceDetails.Add(new Model() { GroceryItems = "Cheese (1 kg)", USPrice = 12.87, UKPrice = 6.13 }); GroceryPriceDetails.Add(new Model() { GroceryItems = "Beef Round (1 kg)", USPrice = 15.21, UKPrice = 9.15 }); } }

Step 3: Layout definition

Define the layout using a Border element. Inside the border, we utilize a Grid to place our content.

Refer to the following code example.

<Border StrokeShape="RoundRectangle 20" StrokeThickness="4" Stroke="Gray" Margin="20"> <Grid ColumnSpacing="0"> <Grid.ColumnDefinitions> <ColumnDefinition Width="*"/> <ColumnDefinition Width="*"/> </Grid.ColumnDefinitions> <Grid.RowDefinitions> <RowDefinition Height="*"/> </Grid.RowDefinitions> </Grid></Border>

Step 4: Configuring the Syncfusion .NET MAUI Cartesian Charts

Let’s configure the Syncfusion .NET MAUI Cartesian Charts control using this documentation.

Refer to the following code example.

<Grid > <!--US Chart --> <chart:SfCartesianChart Grid.Row="1" Grid.Column="0" <chart:SfCartesianChart.XAxes> <Chart:CategoryAxis /> </chart:SfCartesianChart.XAxes> <chart:SfCartesianChart.YAxes> <Chart:NumericalAxis /> </chart:SfCartesianChart.YAxes> </chart:SfCartesianChart> <!--UK Chart --> <chart:SfCartesianChart Grid.Column="1" Grid.Row="1" <chart:SfCartesianChart.XAxes> <Chart:CategoryAxis /> </chart:SfCartesianChart.XAxes> <chart:SfCartesianChart.YAxes> <Chart:NumericalAxis /> </chart:SfCartesianChart.YAxes> </chart:SfCartesianChart></Grid>

Now that we’ve configured the Syncfusion .NET MAUI Cartesian Charts control, let’s see how to create a horizontal bar chart that resembles a pyramid with it!

Step 5: Initialize the horizontal bar chart

To compare the grocery item prices, we’ll use the ColumnSeries instance and set the IsTransposed property to true to initialize the horizontal bar chart.

<!--US Grocery Items Price Chart --><chart:SfCartesianChart IsTransposed="True" > .. <Chart:ColumnSeries /></chart:SfCartesianChart><!--UK Grocery Items Price Chart --><chart:SfCartesianChart IsTransposed="True" > … <Chart:ColumnSeries /></chart:SfCartesianChart>

Step 6: Binding data to the bar chart

This step involves using the ColumnSeries instance to bind the grocery items’ price data.

Refer to the following code example.

<!--US Grocery Items Price Chart --><chart:SfCartesianChart IsTransposed="True" > … <chart:ColumnSeries ItemsSource="{Binding GroceryPriceDetails}" XBindingPath="GroceryItem" YBindingPath="USPrice" /></chart:SfCartesianChart><!--UK Grocery Items Price Chart --><chart:SfCartesianChart IsTransposed="True" > … <chart:ColumnSeries ItemsSource="{Binding GroceryPriceDetails}" XBindingPath="GroceryItems" YBindingPath="UKPrice"/></chart:SfCartesianChart>

In the previous code, we’ve bound the ItemSource property with the GroceryPriceDetails property. The XBindingPath is bound with the grocery items count, and the YBindingPath is bound with the price details.

Step 7: Initializing the legend

A legend displays information corresponding to the chart series. Let’s implement a legend in our bar chart, as shown in the following code example.

<chart:SfCartesianChart.Legend> <Chart:ChartLegend/></chart:SfCartesianChart.Legend>

Step 8: Customizing the chart appearance

We can customize the appearance of the horizontal bar chart using various properties and styles.

Customizing the title

Refer to the following code example, which customizes the chart title using the Label property. In it, we’ve defined the title’s Text, FontSize, FontAttributes, and other properties.

<Label Grid.Row="0" Grid.ColumnSpan="2" Text="Creating a Horizontal Bar Chart to Compare Grocery Item Prices of Two Countries" TextColor="Black" FontSize="16" FontFamily="TimeSpan" FontAttributes="Bold" HorizontalOptions="Start" Padding="350,5,0,0"/>

Customizing the axes

Let’s customize the x- and y-axes using properties such as LabelStyle, AxisLineStyle, and MajorTickStyle.

<!--US Chart Axis Customization --> <chart:SfCartesianChart.XAxes> <chart:CategoryAxis IsInversed="True" ShowMajorGridLines="False" LabelCreated="CategoryAxis\_LabelCreated"> <Chart:CategoryAxis.LabelStyle> <chart:ChartAxisLabelStyle TextColor="#49454F" FontSize="12" LabelAlignment="Center"/> </Chart:CategoryAxis.LabelStyle> <Chart:CategoryAxis.AxisLineStyle> <chart:ChartLineStyle StrokeWidth ="0"/> </Chart:CategoryAxis.AxisLineStyle> <Chart:CategoryAxis.MajorTickStyle> <chart:ChartAxisTickStyle Stroke="#C5C8CE"/> </Chart:CategoryAxis.MajorTickStyle> </Chart:CategoryAxis> </chart:SfCartesianChart.XAxes> <chart:SfCartesianChart.YAxes> <chart:NumericalAxis IsInversed="True" ShowMajorGridLines="False" Maximum="18" IsVisible="False"> </Chart:NumericalAxis> </chart:SfCartesianChart.YAxes><!--UK Chart Axis Customization --> <chart:SfCartesianChart.XAxes> <chart:CategoryAxis ShowMajorGridLines="False" IsInversed="True"> <Chart:CategoryAxis.LabelStyle> <chart:ChartAxisLabelStyle TextColor="Transparent" FontSize="1" Margin="-5"/> </Chart:CategoryAxis.LabelStyle> <Chart:CategoryAxis.AxisLineStyle> <chart:ChartLineStyle StrokeWidth ="0"/> </Chart:CategoryAxis.AxisLineStyle> <Chart:CategoryAxis.MajorTickStyle> <chart:ChartAxisTickStyle Stroke="#C5C8CE"/> </Chart:CategoryAxis.MajorTickStyle> </Chart:CategoryAxis> </chart:SfCartesianChart.XAxes> <chart:SfCartesianChart.YAxes> <chart:NumericalAxis IsVisible="False" ShowMajorGridLines="False" Maximum="10"> </Chart:NumericalAxis> </chart:SfCartesianChart.YAxes>

Customizing the series data labels

Add the chart’s data label and customize the label formats as shown in the following code example.  

<!--US Chart Axis Customization --><chart:ColumnSeries ShowDataLabels="True" Label="United States (US)"> <Chart:ColumnSeries.DataLabelSettings> <chart:CartesianDataLabelSettings LabelPlacement="Outer"> <chart:CartesianDataLabelSettings.LabelStyle> <chart:ChartDataLabelStyle LabelFormat="0.00'$" Background="White"/> </chart:CartesianDataLabelSettings.LabelStyle> </chart:CartesianDataLabelSettings> </Chart:ColumnSeries.DataLabelSettings></Chart:ColumnSeries><!--UK Chart Axis Customization --><chart:ColumnSeries ShowDataLabels="True" Label="United Kingdom (UK)"> <Chart:ColumnSeries.DataLabelSettings> <chart:CartesianDataLabelSettings LabelPlacement="Outer"> <chart:CartesianDataLabelSettings.LabelStyle> <chart:ChartDataLabelStyle LabelForm”t="0.00’£" Background="White"/> </chart:CartesianDataLabelSettings.LabelStyle> </chart:CartesianDataLabelSettings> </Chart:ColumnSeries.DataLabelSettings></Chart:ColumnSeries>

Customizing the series appearance

We also apply the color for each series using the Fill property. Refer to the following example.

<!--US Series--><chart:ColumnSeries Fill="#CD6688"></Chart:ColumnSeries><!--UK Series--><chart:ColumnSeries Fill="#AED8CC"></Chart:ColumnSeries>

After executing the previous code examples, our output will look like the following image.

GitHub reference

For more information, refer to the project on GitHub.

Conclusion

Thanks for reading! This blog showed how to create a horizontal bar chart using the Syncfusion .NET MAUI Cartesian Charts control to visualize a price comparison of grocery items in the United States and the United Kingdom. We encourage you to follow the steps provided and share your thoughts on the experience in the comment section below.

You can contact us through our support forum, support portal, or feedback portal. We are always happy to assist you!

Related blogs

• Load Custom Badge UI in Your .NET MAUI App: An Overview
• Creating a .NET MAUI Hospital Appointment Booking App
• Navigating Location on OSM Layer Using the TileLayer of .NET MAUI Maps
• Chart of the Week: Creating a .NET MAUI Box and Whisker Chart for Machine Impact Test Analysis

View Details

This blog explains the steps to replicate a storage UI using Syncfusion .NET MAUI controls with code examples.

View Details

This blog explains how to create a simple .NET MAUI app that provides a ChatGPT-like user interface and service using OpenAI APIs.

View Details

View Details

In the ever-evolving landscape of software development, staying abreast of new technologies is a crucial undertaking. The introduction of .NET MAUI, the successor to Xamarin.Forms, has ignited discussions among project managers, team leads, and software engineers about the potential benefits and implications of migrating from the familiar Xamarin.Forms framework. This article delves into the considerations […]

View Details

View Details

View Details

This blog explains the process of incorporating custom symbol badges into your app using the Syncfusion .NET MAUI Badge View control.

View Details

This blog explains the steps to create a hospital appointment booking application using Syncfusion .NET MAUI controls with code examples.

View Details

View Details

While .NET MAUI layouts are extremely useful for developing graphical interfaces, it’s always nice to have additional options for arranging elements on the screen. In this article, you will learn about the DockLayout, a layout provided by the .NET MAUI Community Toolkit! To facilitate the understanding of this explanation, I will divide it into the following subtopics: 🔹 .NET MAUI…Continue Reading→

View Details

View Details

This blog explains the use of the TileLayer of .NET MAUI Maps to navigate locations on OSM (OpenStreetMap).

View Details

This blog explains how to visualize machine impact test results using the Syncfusion .NET MAUI Box and Whisker Chart.

View Details

In this post, I want to show you how to publish a .NET MAUI app via TestFlight from an Azure Pipeline. These tools allow you to create cross-platform Android and iOS apps, then use pipelines to build the app any time its code changes, and deploy an unofficial version of the app to a group […]

The post .Net MAUI + Azure Pipelines + iOS TestFlight! appeared first on Trailhead Technology Partners.

View Details

We are using : https://github.com/icsharpcode/SharpZipLib Library for Zipping and Unzipping the Files inside our dotnet maui project. MainPage.xaml MainPage.xaml.cs MainPageViewModel.cs Make sure you have setup Media integration inside your Dotnet maui project for taking camera photo. https://learn.microsoft.com/en-us/dotnet/maui/platform-integration/device-media/picker?tabs=android

View Details

View Details

View Details

View Details

This blog provides the show notes for our July 20, 2023, webinar, “Develop a Loan Interest Calculator App in .NET MAUI.”

View Details

In this post, I'll focus on basic and intermediate animations that can be incorporated into .NET MAUI projects. INFO: The authenticity of my publications is my most sincere commitment. I always start by putting my ideas into my own words and occasionally use GPT-3.5 to improve the content. In this way, I seek to ensure maximum clarity in my writings. If I use GPT-3.5 or another similar too...

View Details

Step 1 : Plugins to add https://github.com/takuya-takeuchi/UltraFaceDotNet Step 2 : Files to be downloaded .bin and .param https://github.com/Linzaer/Ultra-Light-Fast-Generic-Face-Detector-1MB/tree/master/ncnn/data/version-RFB Step 3 : Add this downloaded files to newly created data folder of your project and don’t forget make it as Embedded Resource Step 4 : MainPage.xaml Step 5 : MainPage.xaml.cs Step 6: DetectService.cs Step 7: IDetectService.cs Read More

View Details

View Details

This blog explains how to visualize the global wealth distribution in 2021 using the Syncfusion .NET MAUI Pyramid Chart.

View Details

When performing an operation that takes time, it’s crucial to inform users that a process is ongoing and that they need to wait before taking further action. Progress indicators are a good option to achieve this, as they visually show the percentage of progress that a process takes. In this article, we will learn how to use them in .NET…Continue Reading→

View Details

In this blog post, I'll show you how to use the Android emulator on macOS to debug a .NET MAUI or Xamarin.Forms application from a virtual machine with Windows and Visual Studio 2022.

The post How to use the Android emulator on a macOS host for debugging in a virtual machine with Windows appeared first on MSicc's Blog.

View Details

View Details

View Details

James does some experiments with building .NET MAUI UI without any XAML at all and completely in C#! We discuss the pros, cons, and if James will continue his journey to C# only! Follow Us Frank: Twitter, Blog, GitHub James: Twitter, Blog, GitHub Merge Conflict: Twitter, Facebook, Website, Chat on Discord Music : Amethyst Seer - Citrine by Adventureface ⭐⭐ Review Us (https://itunes.apple.com/us/podcast/merge-conflict/id1133064277?mt=2&ls=1) ⭐⭐ Machine transcription available on http://mergeconflict.fm

View Details

View Details

This blog explains how to visualize the top coffee-producing countries worldwide in 2020 using the Syncfusion .NET MAUI doughnut chart control.

View Details

In this blog post we will play and see what layout features CollectionView is providing to .NET MAUI developers. CollectionView is a layout/control which we can be useed in order to show some collection of data.

MAUIUIJuly is back! This post is my entry for .NET MAUI UI July

View Details

This blog explains the features of the new .NET MAUI Accordion control rolled out in the 2023 Volume 2 release and the steps to get started with it.

View Details

This blog explains how to develop a hotel booking UI using Syncfusion .NET MAUI controls with code examples.

View Details

This blog explains the numeric up-down button feature available in the Syncfusion .NET MAUI Numeric Entry control and the steps to get started with it.

View Details

Howdy! 💁‍♀️ I am thrilled to share my article for the .NET MAUI UI July 2023 calendar created by Matt Goldman, during the month of July, this calendar will publish various educational contributions created by industry experts about .NET MAUI. In this article, I will guide you step-by-step in building the Uber Delivery screen in a simple way. Let’s get started!…Continue Reading→

View Details

View Details

View Details

.NET 8 is on the way and we have some great updates on C# 12, NativeAOT for .NET iOS apps, and oh.... .NET MAUI gets a VS Code extension!!! Tune in! Follow Us Frank: Twitter, Blog, GitHub James: Twitter, Blog, GitHub Merge Conflict: Twitter, Facebook, Website, Chat on Discord Music : Amethyst Seer - Citrine by Adventureface ⭐⭐ Review Us (https://itunes.apple.com/us/podcast/merge-conflict/id1133064277?mt=2&ls=1) ⭐⭐ Machine transcription available on http://mergeconflict.fm

View Details

This blog explains the features of the new .NET MAUI Expander control introduced in the 2023 Volume 2 release and the steps to get started with it.

View Details

This blog explains the features of the new .NET MAUI Chips control introduced in the 2023 Volume 2 release and the steps to get started with it.

View Details

In this blog, we’ll see how US tech companies tend to utilize the dual-class voting structure more frequently than non-tech companies using the Syncfusion .NET MAUI Area Chart.

View Details

.NET 8 is the next LTS release and is currently in preview. .NET, .NET MAUI, and Visual Studio 2022 release a public preview every month for quite some time. On Tue, Jul 11, another preview version of .NET 8 got released along with VS2022 17.7.0 Preview 3.0. After installing the latest preview bits. the Android […]

View Details

View Details

View Details

For my last year’s contribution to the .NET MAUI UI July event, I replicated the F1 TV app. This year…

The post MAUI UI July 2023 – Replicating Wolt app appeared first on Andreas Nesheim.

View Details

View Details

View Details

This blog explains the features of the new Syncfusion .NET MAUI Numeric Entry control and the steps to get started with it.

View Details

This blog explains the features of the new .NET MAUI Image Editor control released in the 2022 Volume 2 and the steps to get started with it.

View Details

View Details

MainPage.xaml.cs MainPage.xaml

View Details

Discover what you missed at Microsoft Build 2023 regarding the migration to .NET MAUI.

View Details

View Details

Knowing how to save files in our applications is very important, however, the perception has been that implementation can be tedious. Thanks to the .NET MAUI Community Toolkit using FileSaver, you can now save files much faster. In this article I will show you all the necessary elements to achieve it. 🔧 First of all… What do I need to know?…Continue Reading→

View Details

In this blog, we will visualize the U.S. methane gas emission data for the year 2021 using the Syncfusion .NET MAUI pie chart control.

View Details

This blog explains the new features planned for inclusion in the Syncfusion Essential Studio 2023 Volume 2 release for the Xamarin.Forms platform.

View Details

View Details

This article shares the experience of the team Syncfusion at the Microsoft Build conference for the year. 2023.

View Details

In this blog, we will use the Syncfusion .NET MAUI waterfall chart to track monthly sales details for a year and look at accompanying code examples.

View Details

Youtube Link : https://youtu.be/swYvmdlgWS0 Everything is based on server setup. Less code lies for dotnet maui :

View Details

Pour valider les nouvelles fonctionnalités d’une application, il vaut mieux les tester dans un environnement isolé. En effet, tu ne voudrais pas risquer les données de tes utilisateurs ! Découvre alors comment configurer différents environnements pour ton application mobile.

View Details

Image caching is a technique that stores images in cache memory to improve an app’s performance. If we search for an image, the app first looks for the image in the cache. If the image is found in the cache, the application will not try to load the image from the source.

The image cache is significant because it helps reduce the app’s loading time and data usage. By caching images, the app can retrieve them more efficiently, which leads to a better user experience.

In this blog, we’ll see how to implement the image caching feature in Syncfusion’s .NET MAUI Avatar View control.

Image caching in .NET MAUI

In .NET MAUI, ImageSource is a default feature that caches downloaded images for a day. The UriImageSource class provides properties to customize the image caching behavior. The Uri property specifies the image’s URI, and the CacheValidity property sets the image’s local storage duration.

The default value for CacheValidity is one day. CachingEnabled is another property that toggles image caching on or off, with the default value being true.

Refer to the following code example.

<Image> <Image.Source> <UriImageSource Uri="https://www.syncfusion.com/blogs/wp-content/uploads/2022/06/Introducing-.NET-MAUI-Avatar-View-Control-thegem-blog-justified.png" CacheValidity="10" /> </Image.Source></Image>

Implement image caching in .NET MAUI Avatar View

The .NET MAUI Avatar View is a graphical representation of a user’s image. It allows you to customize the view by adding images, background color, icons, text, and more. You can also display useful information such as initials and status.

Developers can easily create an Avatar View by customizing the prebuilt vector images to meet their specific requirements. This control can be utilized in various apps such as social media, messaging, and email clients, where user profiles play a vital role.

Let’s see the steps to add the Syncfusion Avatar View control to your .NET MAUI app and implement the image caching feature in it.

Step 1: Create a .NET MAUI app

First, create a .NET MAUI application.

Step 2: Add .NET MAUI Avatar View reference

The Syncfusion .NET MAUI controls are available on NuGet.org. To add the .NET MAUI Avatar View to your project, open the NuGet Package Manager in Visual Studio, and search for Syncfusion.Maui.Core, and then install it.

Step 3: Register the handler

Syncfusion.Maui.Core NuGet is a dependent package for all Syncfusion .NET MAUI controls. In the MauiProgram.cs file, register the handler for Syncfusion core.

Public static class MauiProgram{ public static MauiApp CreateMauiApp() { var builder = MauiApp.CreateBuilder(); builder .UseMauiApp>App>() .ConfigureFonts(fonts => { fonts.AddFont(“OpenSans-Regular.ttf”, “OpenSansRegular”); fonts.AddFont(“OpenSans-Semibold.ttf”, “OpenSansSemibold”); }); builder.ConfigureSyncfusionCore(); return builder.Build(); }}

Step 4: Add the namespace

Add the Syncfusion.Maui.Core namespace on your XAML page.

xmlns: syncfusion ="clr-namespace:Syncfusion.Maui.Core;assembly=Syncfusion.Maui.Core"

Step 5: Initialize the .NET MAUI Avatar View control

Then, initialize the .NET MAUI Avatar View control using the following code.

<syncfusion:SfAvatarView />

Step 6: Load custom image in .NET MAUI Avatar View

You can add a custom image in the Avatar View using the ImageSource property and by setting Custom as the value in the ContentType property. Refer to the following code example.

<syncfusion:SfAvatarView ImageSource="avatarviewimage.png" ContentType="Custom" VerticalOptions="Center" HorizontalOptions="Center" HeightRequest="200" WidthRequest="400" />

Step 7: Implement image caching in .NET MAUI Avatar View

Finally, implement the image caching feature in the .NET MAUI Avatar View using the ImageSource property for optimal image handling.

<syncfusion:SfAvatarView ContentType="Custom" VerticalOptions="Center" HorizontalOptions="Center" HeightRequest="200" WidthRequest="400" > < syncfusion:SfAvatarView.ImageSource> <UriImageSource CachingEnabled="True" Uri="https://www.syncfusion.com/blogs/wp-content/uploads/2022/06/Introducing-.NET-MAUI-Avatar-View-Control-thegem-blog-justified.png" CacheValidity="10" /> </ syncfusion:SfAvatarView.ImageSource></ syncfusion:SfAvatarView>

Now, you can quickly search for images and retrieve them without reloading them from the remote source in the .NET MAUI Avatar View control.

Reference

For more details, refer to the project on GitHub.

Conclusion

Thanks for reading! In this blog, we’ve seen how to implement the image caching feature in the .NET MAUI Avatar View control for optimal image handling. To try out the Avatar View control, download our Essential Studio for .NET MAUI.

If you are not a Syncfusion customer, you can use our 30-day free trial to see how our components can benefit your projects.

We encourage you to check out our .NET MAUI controls’ demos on GitHub and share your feedback or questions in the comments below.

You can also contact us through our support forum, support portal, or feedback portal. Our team is always ready to assist you!

Related blogs

• Time Regions in .NET MAUI Scheduler—An Overview
• Easily Replicate a Sign-Up UI in .NET MAUI
• Create a Place Explorer App Using .NET MAUI and ChatGPT
• Chart of the Week: Creating a .NET MAUI Inversed Column Chart to Visualize Meta Reality Labs’s Yearly Operating Loss

View Details

View Details

WeatherForecastController.cs Don’t forget to add plugin : https://github.com/tomasmcguinness/dotnet-passbook

View Details

Implementing single sign-on (SSO) in Xamarin.Forms involve integrating with an identity provider that supports SSO protocols like OAuth or OpenID Connect. Here’s a general outline of the steps involved:

• Choose an Identity Provider: Select an identity provider that supports the SSO protocol you want to use, such as OAuth or OpenID Connect. Popular choices include Google, Facebook, Microsoft Azure Active Directory, and Okta.
• Set up Identity Provider: Follow the documentation provided by the identity provider to create an application or client, obtain the necessary client credentials (client ID and client secret), and configure the allowed redirect URLs.
• Add NuGet Packages: In your Xamarin.Forms project, add the necessary NuGet packages to handle the SSO integration. The specific packages required will depend on the identity provider and protocol you’re using. Common packages include Xamarin.Auth and Microsoft.Identity.Client.
• Implement Login Page: Create a login page in your Xamarin.Forms application where users can initiate the SSO process. The page should have a button or link that triggers the authentication flow.
• Handle Authentication Flow: When the user clicks the SSO button, initiate the authentication flow by invoking the respective APIs provided by the selected identity provider. This typically involves redirecting the user to the identity provider’s login page.
• Receive Callback: Configure a callback URL in your application, which will be used by the identity provider to redirect the user back to your app after authentication. Handle this callback in your app’s code to retrieve the authentication token or code.
• Exchange Token/Code: Once you receive the authentication token or code from the identity provider, exchange it for an access token or id token by making a request to the identity provider’s token endpoint. This step may require using the client credentials (client ID and client secret) obtained during the setup phase.
• Store and Use Tokens: Store the received tokens securely (e.g., in the device’s secure storage or encrypted) and use them for subsequent authenticated requests to the identity provider’s APIs or any other protected resources.
• Implement Logout: Provide a logout mechanism in your app that allows users to end their SSO session. This usually involves invoking the identity provider’s logout endpoint and clearing the stored tokens from your app.
• Error Handling: Implement appropriate error handling throughout the SSO process, including cases like token expiration, token revocation, network errors, etc.

View Details

Time regions are specific units of time used to define periods or durations. The .NET MAUI Scheduler supports customizing time regions. This customization includes adjusting the duration of time regions, setting specific start and end times, handling interactions in time regions, and defining recurring time regions.

By having their time regions customized, schedulers become more efficient and tailored to individual needs. For instance, in a doctor’s scheduling application, time regions can be customized to account for lunch and break times, which can prevent appointment scheduling during those times. This customization is essential to ensure there are no conflicts between appointments and that sufficient time is allocated for rest and meals.

Note: If you are new to this control, refer to the .NET MAUI Scheduler getting started documentation before proceeding.

This blog will show you how to create and customize time regions in the .NET MAUI Scheduler control.

Defining the time region

Defining the time region requires the essential details in the following table.

Interaction restriction on a time region

In the .NET MAUI Scheduler, the SchedulerTimeRegion class supports controlling, enabling, or disabling touch interaction for a time region using the EnablePointerInteraction property. It prevents touch interaction on disabled time slots.

Time region globalization

The time region feature provides globalization support, enabling users to customize time regions to align with different time zones or regional conventions using the TimeZone property. This can reduce errors when working across different time zones.

Recurring time region

The time region feature provides recurrence support to repeat the same time region on a regular or periodic interval using RecurrenceRule. For example, you can schedule a daily lunch break for a doctor’s appointment scheduling system.

For more details about the recurrence rule, refer to the recurrence rule documentation.

The recurring exception is an advanced feature of time region recurrence that allows the exclusion of specific occurrences of a recurring time region by using the RecurrenceExceptionDates property in the SchedulerTimeRegion class. This feature is useful when a regular schedule needs to be altered on a particular day or for a particular period, such as holidays or planned maintenance.

Resource-based time region

The time region feature provides resource support to create customized time slots based on specific resources or assets using the ResourceIds property. A resource-based time region defines the availability of those resources for scheduling.

Applying the time regions to .NET MAUI Scheduler

The .NET MAUI Scheduler uses the TimeRegions property in the SchedulerTimeSlotView class to customize the timeslots based on specified time regions and their properties such as StartTime, EndTime, Text, Background, and TimeZone.

SfScheduler scheduler = new SfScheduler();scheduler.View = SchedulerView.Week;ObservableCollection<SchedulerTimeRegion> timeRegions = new ObservableCollection<SchedulerTimeRegion>();//// Adding time region in the scheduler time region collection.timeRegions.Add(new SchedulerTimeRegion(){ StartTime = DateTime.Today.Date.AddHours(13), EndTime = DateTime.Today.Date.AddHours(14), Text = "Lunch", EnablePointerInteraction = false, RecurrenceRule = "FREQ=DAILY;INTERVAL=1",});//// Assigning the scheduler time region collection to the TimeRegions in DayView of .NET MAUI Scheduler.scheduler.DaysView.TimeRegions = timeRegions;this.Content = scheduler;

Conclusion

Thank you for your time! This blog post showed you how to create and set a time region in the .NET MAUI Scheduler. You can explore other features in the Scheduler control in its documentation.

If you are not a Syncfusion customer, try our 30-day free trial to see how our components can enhance your projects.

Please try the samples available in our .NET MAUI sample location and share your feedback or ask questions in the comments section. Or contact us through our support forum, support portal, or feedback portal. We are happy to assist you!

Related blogs

• Elevate Your App’s User Experience with the New .NET MAUI Shimmer Control
• Introducing the New .NET MAUI Popup Control
• Introducing the New .NET MAUI Masked Entry Control
• Streamline MAUI Projects with the Syncfusion .NET MAUI Template Studio

View Details

View Details

This article will broaden your understanding of XAML by demonstrating how to replicate a sign-up user interface in .NET MAUI.

View Details

ChatGPT and Copilot were the primary focus of this year’s MSBuild 2023, Microsoft’s annual developer conference. From the .NET MAUI perspective, with just around 1 year of official support left for Xamarin, which will end on May 1, 2024, the main focus was on the upgrade from Xamarin to .NET MAUI. Two options are available […]

View Details

In this blog post, we will explore the process of developing a .NET MAUI application that leverages OpenAI’s ChatGPT APIs to deliver place recommendations based on the user’s location. The application will feature a user-friendly interface where users can input their geographical location, and in return, they will receive information about popular landmarks and attractions nearby.

To get started with developing the application, there are a few prerequisites that need to be fulfilled:

• OpenAI account: You will need to have an account with OpenAI to access their APIs and obtain an API key.
• OpenAI API key: Once you have an account, generate an API key from OpenAI. This key will be used to authenticate your requests to their APIs.
• .NET MAUI installation: Ensure you have the necessary dependencies and tools installed for .NET MAUI application development. This includes having the .NET SDK, MAUI workload, and related libraries set up on your development machine.

Next, I’ll detail how to meet these prerequisites.

Note: To access OpenAI’s APIs in your .NET MAUI application, you need the API key, which is not free. If you are considering a paid account, this blog will give you an idea of how you might utilize it, even if you can’t follow along. Check the pricing page for more details.

How to create an Open AI account

To create an OpenAI account, follow these steps:

1. Go to the official OpenAI website. 
2. Look for the Sign Up button on the website’s homepage and click on it. This will direct you to the account creation page.
3. Fill out the required information in the sign-up form.
4. Verify your email address by clicking on a verification link sent to your registered email.
5. Once your registration is successful, you should be able to log in to your OpenAI account using the credentials you provided during the sign-up process.

By following these steps, you can create an OpenAI account and gain access to their services.

How to get an OpenAI API key

To obtain an OpenAI API key:

1. Visit the OpenAI website and sign in using your account credentials.
2. Navigate to the API section of the OpenAI platform. This can be found in the Account Settings.
3. Create a new secret API key. This is where you are required to purchase it.

Create a place explorer app with .NET MAUI

Please create a .NET MAUI application and follow the instructions within the project.

Configuring ChatGPT APIs

To integrate the ChatGPT library and call its APIs in your .NET MAUI project, follow these steps:

1. Reference and bootstrap the ChatGptNet library. Open the Package Manager Console from the Tools menu in Visual Studio, and run the following command to install the ChatGptNet library.

   Install-Package ChatGptNet

2. In the MauiProgram.cs file, locate the CreateMauiApp Add the following code.

   builder.Services.AddChatGpt(options =>{ options.ApiKey = ""; // Your API Key Here; options.Organization = null; // Optional options.DefaultModel = ChatGptModels.Gpt35Turbo; // Default: ChatGptModels.Gpt35Turbo options.MessageLimit = 10; // Default: 10 options.MessageExpiration = TimeSpan.FromMinutes(5); // Default: 1 hour});

Add necessary NuGet packages

In this application, I will utilize the Syncfusion .NET MAUI controls, specifically the Maps, Busy Indicator, and Popup controls. These controls will play crucial roles in enhancing the functionality and user experience of the app.

The Maps control will be the centerpiece of the application, allowing users to select a specific location by picking the latitude and longitude. With the Maps control, users will have an interactive and visually appealing interface to navigate and explore different areas.

To provide a seamless user experience, I will incorporate the Busy Indicator control. This control will be activated when the application communicates with the ChatGPT API to retrieve recommendations based on the selected location. The Busy Indicator will display an animated loading indicator, assuring users that the app is working in the background to fetch the desired information.

I will utilize the Popup control to present the output corresponding to the selected location. This control will enable me to display relevant information and recommendations in an organized and visually appealing manner.

Syncfusion .NET MAUI components are available on NuGet.org. To add SfMaps to your project, open the NuGet package manager in Visual Studio, search for Syncfusion.Maui.Maps, and then install it. Similarly, SfBusyIndicator is available in the Syncfusion.Maui.Core NuGet package and SfPopup is available in the Syncfusion.Maui.Popup NuGet package.

Handler registration

Syncfusion.Maui.Core NuGet is a dependent package for all Syncfusion .NET MAUI controls. In the MauiProgram.cs file, register the handler for Syncfusion core.

using ChatGptNet;using ChatGptNet.Models;using Microsoft.Extensions.Logging;using Syncfusion.Maui.Core.Hosting;namespace ChatGPTinMAUI;public static class MauiProgram{ public static MauiApp CreateMauiApp() {var builder = MauiApp.CreateBuilder();builder.UseMauiApp<App>() builder.ConfigureSyncfusionCore(); builder.Services.AddChatGpt(options => { options.ApiKey = ""; // Your API key here; options.Organization = null; // Optional options.DefaultModel = ChatGptModels.Gpt35Turbo; // Default: ChatGptModels.Gpt35Turbo options.MessageLimit = 10; // Default: 10 options.MessageExpiration = TimeSpan.FromMinutes(5); // Default: 1 hour }); #if DEBUG builder.Logging.AddDebug(); #endif return builder.Build(); }}

Designing the UI

Create the required UI:

1. Declare the required namespaces in the ContentPage, which represents a page in the application’s user interface.

   The XAML code begins with declaring the necessary namespaces using the xmlns attribute. The required namespaces are:

   • “clr-namespace:Syncfusion.Maui.Maps;assembly=Syncfusion.Maui.Maps” for the Syncfusion Maps control.
   • “clr-namespace:Syncfusion.Maui.Core;assembly=Syncfusion.Maui.Core” for the Syncfusion BusyIndicator control.
   • “clr-namespace:Syncfusion.Maui.Popup;assembly=Syncfusion.Maui.Popup” for the Syncfusion Popup control.

     <ContentPage xmlns="http://schemas.microsoft.com/dotnet/2021/maui" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" xmlns:maps="clr-namespace:Syncfusion.Maui.Maps;assembly=Syncfusion.Maui.Maps" xmlns:busy="clr-namespace:Syncfusion.Maui.Core;assembly=Syncfusion.Maui.Core" xmlns:syncfusion="clr-namespace:Syncfusion.Maui.Popup;assembly=Syncfusion.Maui.Popup" x:Class="ChatGPTinMAUI.MainPage"></ContentPage>

2. Inside the ContentPage, add an instance of the busy:SfBusyIndicator control. Here, I am naming it busyIndicator.

   <ContentPage xmlns="http://schemas.microsoft.com/dotnet/2021/maui" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" xmlns:maps="clr-namespace:Syncfusion.Maui.Maps;assembly=Syncfusion.Maui.Maps" xmlns:busy="clr-namespace:Syncfusion.Maui.Core;assembly=Syncfusion.Maui.Core" xmlns:syncfusion="clr-namespace:Syncfusion.Maui.Popup;assembly=Syncfusion.Maui.Popup" x:Class="ChatGPTinMAUI.MainPage"> <busy:SfBusyIndicator x:Name="busyIndicator"> </busy:SfBusyIndicator></ContentPage>

3. Add a ScrollView element to provide vertical scrolling functionality for the content within the page. Within the ScrollView, add a Grid element. The Grid is a container for other controls and allows flexible layout arrangements.

   <ContentPage xmlns="http://schemas.microsoft.com/dotnet/2021/maui" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" xmlns:maps="clr-namespace:Syncfusion.Maui.Maps;assembly=Syncfusion.Maui.Maps" xmlns:busy="clr-namespace:Syncfusion.Maui.Core;assembly=Syncfusion.Maui.Core" xmlns:syncfusion="clr-namespace:Syncfusion.Maui.Popup;assembly=Syncfusion.Maui.Popup" x:Class="ChatGPTinMAUI.MainPage"> <busy:SfBusyIndicator x:Name="busyIndicator"> <ScrollView> <Grid> </Grid> </ScrollView> </busy:SfBusyIndicator></ContentPage>

4. Inside the grid, add a maps:SfMaps control. This control displays a map using OpenStreetMap tiles. The MapTileLayer element defines the URL template for the map tiles, and the MapZoomPanBehavior specifies the zooming and panning behavior.

   <ContentPage xmlns="http://schemas.microsoft.com/dotnet/2021/maui" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" xmlns:maps="clr-namespace:Syncfusion.Maui.Maps;assembly=Syncfusion.Maui.Maps" xmlns:busy="clr-namespace:Syncfusion.Maui.Core;assembly=Syncfusion.Maui.Core" xmlns:syncfusion="clr-namespace:Syncfusion.Maui.Popup;assembly=Syncfusion.Maui.Popup" x:Class="ChatGPTinMAUI.MainPage"> <busy:SfBusyIndicator x:Name="busyIndicator"> <ScrollView> <Grid > <maps:SfMaps x:Name="maps"> <maps:SfMaps.Layer> <maps:MapTileLayer UrlTemplate="https://tile.openstreetmap.org/{z}/{x}/{y}.png"> <maps:MapTileLayer.ZoomPanBehavior> <maps:MapZoomPanBehavior MinZoomLevel="3" MaxZoomLevel="10" EnableDoubleTapZooming="True" ZoomLevel="3"> </maps:MapZoomPanBehavior> </maps:MapTileLayer.ZoomPanBehavior> </maps:MapTileLayer> </maps:SfMaps.Layer> </maps:SfMaps> </Grid> </ScrollView> </busy:SfBusyIndicator></ContentPage>

5. Inside the Grid, add a syncfusion:SfPopup control. I am naming popupDisplay. It displays a pop-up window when triggered. The SfPopup.ContentTemplate defines the content that will be displayed in the pop-up. It contains a grid with a label displaying the places to visit in the selected location and a scroll view with a label bound to a ContentText property for displaying the content.

   <ContentPage xmlns="http://schemas.microsoft.com/dotnet/2021/maui" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" xmlns:maps="clr-namespace:Syncfusion.Maui.Maps;assembly=Syncfusion.Maui.Maps" xmlns:busy="clr-namespace:Syncfusion.Maui.Core;assembly=Syncfusion.Maui.Core" xmlns:syncfusion="clr-namespace:Syncfusion.Maui.Popup;assembly=Syncfusion.Maui.Popup" x:Class="ChatGPTinMAUI.MainPage"> <busy:SfBusyIndicator x:Name="busyIndicator"> <ScrollView> <Grid > <maps:SfMaps x:Name="maps"> <maps:SfMaps.Layer> <maps:MapTileLayer UrlTemplate="https://tile.openstreetmap.org/{z}/{x}/{y}.png"> <maps:MapTileLayer.ZoomPanBehavior> <maps:MapZoomPanBehavior MinZoomLevel="3" MaxZoomLevel="10" EnableDoubleTapZooming="True" ZoomLevel="3"> </maps:MapZoomPanBehavior> </maps:MapTileLayer.ZoomPanBehavior> </maps:MapTileLayer> </maps:SfMaps.Layer> </maps:SfMaps> <syncfusion:SfPopup x:Name="popupDisplay" IsOpen="false" ShowHeader="False" WidthRequest="500" HeightRequest="300"> <syncfusion:SfPopup.ContentTemplate> <DataTemplate> <Grid RowDefinitions="20,*"> <Label Text="5 places to visit in this location :" FontSize="14" FontAttributes="Bold" /> <ScrollView Grid.Row="1" > <Label Text="{Binding ContentText}" Margin="0,10,0,10" /> </ScrollView> </Grid> </DataTemplate> </syncfusion:SfPopup.ContentTemplate> </syncfusion:SfPopup> </Grid> </ScrollView> </busy:SfBusyIndicator></ContentPage>

Overall, the XAML code creates a content page with a Busy Indicator control, a scroll view, a Maps control, and a Popup control.

Implementing the code-behind

1. Declare the following namespaces in the code-behind file:
   • ChatGptNet and ChatGptNet.Models: Namespaces for the ChatGptNet library, which provides functionality for making calls to OpenAI’s ChatGPT API.
   • Syncfusion.Maui.Maps: The Syncfusion Maps control’s namespace for displaying maps.

     using ChatGptNet;using ChatGptNet.Models;using Syncfusion.Maui.Maps;

     The code is within the ChatGPTinMAUI namespace, and the MainPage class is defined as a partial class extending the ContentPage class.

     using ChatGptNet;using ChatGptNet.Models;using Syncfusion.Maui.Maps;namespace ChatGPTinMAUI;
     public partial class MainPage : ContentPage{}

2. Define the Title and ContentText properties. The Title is a bindable property defined using the BindableProperty.Create method. It represents the title of the page and enables binding, animation, and styling. The ContentText property is also a bindable property, representing the content text displayed on the page.

   using ChatGptNet;using ChatGptNet.Models;using Syncfusion.Maui.Maps;namespace ChatGPTinMAUI;public partial class MainPage : ContentPage{ public String Title { get { return (String)GetValue(TitleProperty); } set { SetValue(TitleProperty, value); } } public static readonly BindableProperty TitleProperty = BindableProperty.Create("Title", typeof(String), typeof(MainPage), String.Empty); public String ContentText { get { return (String)GetValue(ContentTextProperty); } set { SetValue(ContentTextProperty, value); } } public static readonly BindableProperty ContentTextProperty = BindableProperty.Create("ContentText", typeof(String), typeof(MainPage), String.Empty);}

3. In the MainPage constructor, initialize the page by calling InitializeComponent and subscribe to the Loaded event.

   using ChatGptNet;using ChatGptNet.Models;using Syncfusion.Maui.Maps;namespace ChatGPTinMAUI;public partial class MainPage : ContentPage{ public String Title { get { return (String)GetValue(TitleProperty); } set { SetValue(TitleProperty, value); } } public static readonly BindableProperty TitleProperty = BindableProperty.Create("Title", typeof(String), typeof(MainPage), String.Empty); public String ContentText { get { return (String)GetValue(ContentTextProperty); } set { SetValue(ContentTextProperty, value); } } public static readonly BindableProperty ContentTextProperty = BindableProperty.Create("ContentText", typeof(String), typeof(MainPage), String.Empty); private IChatGptClient \_chatGptClient; private Guid \_sessionGuid = Guid.Empty; MapMarkerCollection mapMarkers = new MapMarkerCollection(); MapMarker mapMarker = new MapMarker(); public MainPage() { InitializeComponent(); this.Loaded += MainPage\_Loaded; mapMarkers.Add(mapMarker); this.BindingContext = this; }}

4. The MainPage\_Loaded event handler is invoked when the page is loaded. Retrieve an instance of the IChatGptClient service using dependency injection in this event.

   using ChatGptNet;using ChatGptNet.Models;using Syncfusion.Maui.Maps;namespace ChatGPTinMAUI;public partial class MainPage : ContentPage{ public String Title { get { return (String)GetValue(TitleProperty); } set { SetValue(TitleProperty, value); } } public static readonly BindableProperty TitleProperty = BindableProperty.Create("Title", typeof(String), typeof(MainPage), String.Empty); public String ContentText { get { return (String)GetValue(ContentTextProperty); } set { SetValue(ContentTextProperty, value); } } public static readonly BindableProperty ContentTextProperty = BindableProperty.Create("ContentText", typeof(String), typeof(MainPage), String.Empty); private IChatGptClient \_chatGptClient; private Guid \_sessionGuid = Guid.Empty; MapMarkerCollection mapMarkers = new MapMarkerCollection(); MapMarker mapMarker = new MapMarker(); public MainPage() { InitializeComponent(); this.Loaded += MainPage\_Loaded; mapMarkers.Add(mapMarker); this.BindingContext = this; } private void MainPage\_Loaded(object sender, EventArgs e) { \_chatGptClient = Handler.MauiContext.Services.GetService<IChatGptClient>(); }}

5. Add the MainPage\_Tapped event handler. The MainPage\_Tapped event handler is called when the user taps on the map. It retrieves the latitude and longitude of the tapped location and calls the GetNearByTouristAttraction method.

   using ChatGptNet;using ChatGptNet.Models;using Syncfusion.Maui.Maps;namespace ChatGPTinMAUI;public partial class MainPage : ContentPage{ public String Title { get { return (String)GetValue(TitleProperty); } set { SetValue(TitleProperty, value); } } public static readonly BindableProperty TitleProperty = BindableProperty.Create("Title", typeof(String), typeof(MainPage), String.Empty); public String ContentText { get { return (String)GetValue(ContentTextProperty); } set { SetValue(ContentTextProperty, value); } } public static readonly BindableProperty ContentTextProperty = BindableProperty.Create("ContentText", typeof(String), typeof(MainPage), String.Empty); private IChatGptClient \_chatGptClient; private Guid \_sessionGuid = Guid.Empty; MapMarkerCollection mapMarkers = new MapMarkerCollection(); MapMarker mapMarker = new MapMarker(); public MainPage() { InitializeComponent(); this.Loaded += MainPage\_Loaded; mapMarkers.Add(mapMarker); this.BindingContext = this; } private void MainPage\_Loaded(object sender, EventArgs e) { \_chatGptClient = Handler.MauiContext.Services.GetService<IChatGptClient>(); } private async void MainPage\_Tapped(object sender, Syncfusion.Maui.Maps.TappedEventArgs e) { var latlong = (this.maps.Layer as MapTileLayer).GetLatLngFromPoint(e.Position); var geoLocation = "Latitude:"+ latlong.Latitude.ToString() + ",Longitude:" + latlong.Longitude.ToString(); await GetNearByTouristAttraction(geoLocation); this.popupDisplay.Show(e.Position.X, e.Position.Y); this.popupDisplay.Show(e.Position.X, e.Position.Y); }}

   The GetNearByTouristAttraction method is an asynchronous method that fetches nearby tourist attractions based on the provided geolocation. It displays a loading indicator while the request is being processed. It makes a request to the ChatGPT Client to get recommendations for tourist attractions and then updates the ContentText property with the response.

   using ChatGptNet;using ChatGptNet.Models;using Syncfusion.Maui.Maps;namespace ChatGPTinMAUI;public partial class MainPage : ContentPage{ public String Title { get { return (String)GetValue(TitleProperty); } set { SetValue(TitleProperty, value); } } public static readonly BindableProperty TitleProperty = BindableProperty.Create("Title", typeof(String), typeof(MainPage), String.Empty); public String ContentText { get { return (String)GetValue(ContentTextProperty); } set { SetValue(ContentTextProperty, value); } } public static readonly BindableProperty ContentTextProperty = BindableProperty.Create("ContentText", typeof(String), typeof(MainPage), String.Empty); private IChatGptClient \_chatGptClient; private Guid \_sessionGuid = Guid.Empty; MapMarkerCollection mapMarkers = new MapMarkerCollection(); MapMarker mapMarker = new MapMarker(); public MainPage() { InitializeComponent(); this.Loaded += MainPage\_Loaded; mapMarkers.Add(mapMarker); this.BindingContext = this; } private void MainPage\_Loaded(object sender, EventArgs e) { \_chatGptClient = Handler.MauiContext.Services.GetService<IChatGptClient>(); } private async void MainPage\_Tapped(object sender, Syncfusion.Maui.Maps.TappedEventArgs e) { var latlong = (this.maps.Layer as MapTileLayer).GetLatLngFromPoint(e.Position); var geoLocation = "Latitude:"+ latlong.Latitude.ToString() + ",Longitude:" + latlong.Longitude.ToString(); await GetNearByTouristAttraction(geoLocation); this.popupDisplay.Show(e.Position.X, e.Position.Y); this.popupDisplay.Show(e.Position.X, e.Position.Y); } private async Task GetNearByTouristAttraction(string geoLocation) { this.busyIndicator.IsRunning = true; if (string.IsNullOrWhiteSpace(geoLocation)) { await DisplayAlert("Empty location", "No Suggestions", "OK"); return; } if (\_sessionGuid == Guid.Empty) { \_sessionGuid = Guid.NewGuid(); } var query = "Tell me 5 places near the following location (Each with 20 words) " + geoLocation; ChatGptResponse response = await \_chatGptClient.AskAsync(\_sessionGuid, query); this.ContentText = response.GetMessage(); this.busyIndicator.IsRunning = false; }}

That’s it; we have successfully created a .NET MAUI application with a map control that displays popular tourist attractions near a selected location.

Reference

For more details, refer to the project on GitHub.

Conclusion

This blog guided you in creating a .NET MAUI application that leverages the power of the OpenAI ChatGPT API to deliver tourist recommendations based on the user’s location.

Feel free to experiment by modifying the prompts to enhance the quality of the suggestions. Additionally, you can explore the option of changing the ChatGptModels enum value within the AddChatGpt method in MauiProgram.cs to observe if different models yield improved outcomes.

Syncfusion’s collection of .NET MAUI controls offers a comprehensive suite of tools that enable developers to create robust and feature-rich applications. With their extensive customization options and intuitive APIs, Syncfusion controls provide seamless integration into the .NET MAUI framework, making building cross-platform applications with enhanced functionality easier.

Please try out the steps in this blog and share your feedback in the comment section below. You can also reach us through our support forum, support portal, or feedback portal. We are always happy to assist you!

Related blogs

• Data Visualization with a Heat Map Using .NET MAUI Scheduler
• Creating a .NET MAUI Column Chart to Visualize Yearly Box Office Data
• Google-Powered Autocomplete: Leveraging Search Suggestions in .NET MAUI
• Creating a .NET MAUI Inversed Column Chart to Visualize Meta Reality Labs’s Yearly Operating Loss

View Details

Welcome to our Chart of the Week blog series. Today, we’ll create an inverted column chart using the Syncfusion .NET MAUI Cartesian Charts control. The inverted column chart is commonly used for plotting comparative data values in reverse order. In this example, we will compare Meta Reality Labs’s yearly operating losses from 2019 to 2022.

Step 1: Gather yearly revenue loss data

Refer to the Meta’s Money Pit: Metaverse Bet Bleeds Billions article by Statista and extract data from it. We will utilize the .NET MAUI column chart to create the same user interface.

Step 2: Populate the data for the inversed column chart

Create the MetaLabLossModel class to hold the year and loss data for Meta’s Reality Labs division with the Year and Loss properties.

Refer to the following code example.

public class MetaLabLossModel
{ public double Year { get; set; } public double Loss { get; set; }}

Then, generate a collection of Reality Labs division’s operating details with the help of the MetaLabLossDetails class.

public class MetaLabLossDetails
{ public MetaLabLossDetails() { LossDetails = new List<MetaLabLossModel>() { new MetaLabLossModel {Year = 2019, Loss = -4.5}, new MetaLabLossModel {Year = 2020, Loss = -6.6}, new MetaLabLossModel {Year = 2021, Loss = -10.2}, new MetaLabLossModel {Year = 2022, Loss = -13.7} }; } public List< MetaLabLossModel > LossDetails { get; set; }}

Step 3: Configure the Syncfusion .NET MAUI Cartesian Charts control

Now, configure the Syncfusion .NET MAUI Cartesian Charts control by following this documentation.

Refer to the following code example.

<Chart:SfCartesianChart x:Name="chart"> <Chart:SfCartesianChart.XAxes> <Chart:NumericalAxis> </Chart:NumericalAxis> </Chart:SfCartesianChart.XAxes> <Chart:SfCartesianChart.YAxes> <Chart:NumericalAxis> </Chart:NumericalAxis> </Chart:SfCartesianChart.YAxes></Chart:SfCartesianChart>

Step 4: Bind data to the chart

Use Syncfusion’s ColumnSeries instance to bind the Meta Reality Labs’s operating loss data into the chart.

Refer to the following code example.

<Chart:ColumnSeries XBindingPath="Year" YBindingPath="Loss" ItemsSource="{Binding LossDetails}"></Chart:ColumnSeries>

In this example, we’ve bound the LossDetails with the ItemSource property. We’ve also specified the XBindingPath and YBindingPath with the Year and Loss properties, respectively.

Step 5: Position the chart axis

To design the inversed column chart, position the chart axis using the CrossesAt and Name properties of the chart axis.

<Chart:SfCartesianChart.XAxes> <Chart:NumericalAxis CrossesAt="-1" Name="primary"> </Chart:NumericalAxis></Chart:SfCartesianChart.XAxes>

To assign the crossing axis to the chart series, use the XAxisName property.

<Chart:ColumnSeries XAxisName="primary"></Chart:ColumnSeries>

Step 6: Customize the chart appearance

Let’s enhance the appearance of the column chart by customizing the axis elements, data labels, column colors, and titles.

Refer to the following code example to add a title to the chart.

<Chart:SfCartesianChart.Title> <Label Text="Operating Loss of Meta's Reality Labs Division" HorizontalTextAlignment="Center" FontSize="Title" TextColor="#FF5E768E"/></Chart:SfCartesianChart.Title>

Then, configure the axis and modify the axis elements as shown in the following code example.

<Chart:SfCartesianChart.XAxes> <Chart:NumericalAxis Interval="1" ShowMajorGridLines="False" > <Chart:NumericalAxis.LabelStyle> <Chart:ChartAxisLabelStyle FontSize="20" Margin="-40" TextColor="Black"/> </Chart:NumericalAxis.LabelStyle> <Chart:NumericalAxis.MajorTickStyle> <Chart:ChartAxisTickStyle StrokeWidth="0"/> </Chart:NumericalAxis.MajorTickStyle> <Chart:NumericalAxis.AxisLineStyle> <Chart:ChartLineStyle Stroke="Black"/> </Chart:NumericalAxis.AxisLineStyle> </Chart:NumericalAxis></Chart:SfCartesianChart.XAxes><Chart:SfCartesianChart.YAxes> <Chart:NumericalAxis Maximum="0" IsVisible="False" ShowMajorGridLines="False"/></Chart:SfCartesianChart.YAxes>

Then, customize the column colors and enable data labels with the desired label formats.

<Chart:ColumnSeries XBindingPath="Year" Fill="#FF0A3B7E" YBindingPath="Loss" ItemsSource="{Binding LossDetails}" ShowDataLabels="True"> <Chart:ColumnSeries.DataLabelSettings> <Chart:CartesianDataLabelSettings> <Chart:CartesianDataLabelSettings.LabelStyle> <Chart:ChartDataLabelStyle FontSize="20" LabelFormat="$0.0B"/> </Chart:CartesianDataLabelSettings.LabelStyle> </Chart:CartesianDataLabelSettings> </Chart:ColumnSeries.DataLabelSettings></Chart:ColumnSeries>

After executing these code examples, we will get output like in the following image.

GitHub reference

For more information, refer to the project on GitHub.

Conclusion

Thanks for reading! In this blog, we’ve created an inversed column chart to visualize the net revenue loss of Meta’s Reality Labs over time using the Syncfusion .NET MAUI Cartesian Chart. We encourage you to try these steps to visualize your desired data and share your feedback in the comments section below.

You can also reach us through our support forum, support portal, or feedback portal. We are always happy to assist you!

See you in our next blog!

Related blogs

• Data Visualization with a Heat Map Using .NET MAUI Scheduler
• Creating a .NET MAUI Column Chart to Visualize Yearly Box Office Data
• Create and Validate a Login Form in .NET MAUI
• Create a Line Chart to Visualize the Surge in U.S. Egg Prices

View Details

In this walkthrough, we will explore the custom filtering support provided by Syncfusion’s Autocomplete control. The Autocomplete control was designed to give users possible matches as they type, and it comes with a range of features such as different suggestion modes and custom search.

Using the custom filter support, we can create a Google search experience where suggestions are filtered based on user input.

This blog will guide you through the steps to achieve this behavior. By implementing this custom filtering feature, you can provide your users with more accurate and relevant search suggestions that enhance their overall experience. So, let’s learn how to utilize this feature of Autocomplete control in a .NET MAUI app.

How to add the Syncfusion control

First, we’ll incorporate the Autocomplete control and associate data with it.

Step 1: Add the .NET MAUI Autocomplete reference

Syncfusion’s .NET MAUI controls are available on NuGet.org. To add the .NET MAUI Autocomplete to your project, open the NuGet package manager in Visual Studio, search for Syncfusion.Maui.Inputs , and then install it.

Step 2: Handler registration

In the MauiProgram.cs file, register the handler for the Syncfusion core.

using Microsoft.Extensions.Logging;
using Syncfusion.Maui.Core.Hosting;namespace GoogleSearchDemo;public static class MauiProgram{ public static MauiApp CreateMauiApp() {var builder = MauiApp.CreateBuilder();builder .ConfigureSyncfusionCore() .UseMauiApp<App>() .ConfigureFonts(fonts => { fonts.AddFont("OpenSans-Regular.ttf", "OpenSansRegular"); fonts.AddFont("OpenSans-Semibold.ttf", "OpenSansSemibold"); }); #if DEBUG builder.Logging.AddDebug(); #endif return builder.Build(); }}

Step 3: Include the namespace

After adding the NuGet package to the project, as discussed in the previous reference section, add the XML namespace to the MainPage.xaml file, as shown in the following code example.

xmlns:editors="clr-namespace:Syncfusion.Maui.Inputs;assembly=Syncfusion.Maui.Inputs"

Step 4: Add the Autocomplete control

Add the Autocomplete control inside a grid. Also, customize the Autocomplete control with these properties:

• Placeholder: Displays a text hint inside the control before the user inputs any value.
• MaxDropDownHeight: Maximum height of the dropdown list that appears when it gets opened.
• TextSearchMode: Sets the search mode for matching items in the Autocomplete control’s data source. This property is set to Contains, meaning the control will show all items containing the typed text.
• WidthRequest and HeightRequest: These properties set the preferred width and height of the control.

<Grid Margin="0,20,0,0"> <editors:SfAutocomplete HeightRequest="50" Placeholder="Search something" MaxDropDownHeight="250" TextSearchMode="Contains" WidthRequest="300"> </editors:SfAutocomplete></Grid>

Step 5: Set custom filtering class

The Autocomplete control supports applying custom filter logic to suggest items based on your filter criteria using the FilterBehavior and SearchBehavior properties. The default value of FilterBehavior and SearchBehavior is null. Here, the FilterBehavior is set to CustomFiltering. Creation of the CustomFiltering class is explained in the upcoming section.

<Grid Margin="0,20,0,0"> <editors:SfAutocomplete HeightRequest="50" Placeholder="Search something" MaxDropDownHeight="250" TextSearchMode="Contains" WidthRequest="300"> <editors:SfAutocomplete.FilterBehavior> <local:CustomFiltering/> </editors:SfAutocomplete.FilterBehavior> </editors:SfAutocomplete></Grid>

With this, the UI part is completely implemented. Let’s focus on the backend where the CustomFiltering class is implemented.

Creating the CustomFiltering class

Next, let’s create a Google-like suggestion filter using the custom filter property of the .NET MAUI Autocomplete control.

Step 1: Create a custom class

Create a class named CustomFiltering and import the Syncfusion.Maui.Inputs namespace, which provides classes and interfaces for the Autocomplete control.

using Syncfusion.Maui.Inputs;using System.Xml.Linq;namespace GoogleSearchDemo{ public class CustomFiltering { }}

Step 2: Implement the interface

Implement the interface IAutocompleteFilterBehavior in the CustomFiltering class. This interface defines the filtering behavior for the control. The first step is to import the necessary namespaces required for the code to execute.

using Syncfusion.Maui.Inputs;using System.Xml.Linq;namespace GoogleSearchDemo : IAutocompleteFilterBehavior{ public class CustomFiltering { }}

Step 3: Customize the constructor method

Define a constructor method, which is called when an instance of the CustomFiltering class is created. In the constructor, call the GetGoogleSuggestions method with the initial search term test.

using Syncfusion.Maui.Inputs;using System.Xml.Linq;namespace GoogleSearchDemo{ public class CustomFiltering : IAutocompleteFilterBehavior { public CustomFiltering() { GetGoogleSuggestions("test"); } }}

Step 4: Define the filtering method from IAutocompleteFilterBehavior

Define the GetMatchingItemsAsync method, which is responsible for filtering the data for the Autocomplete control. It takes two arguments: the SfAutocomplete class’s source object and an instance of the AutocompleteFilterInfo class. The AutocompleteFilterInfo class contains the current filter text entered by the user.

using Syncfusion.Maui.Inputs;using System.Xml.Linq;namespace GoogleSearchDemo{ public class CustomFiltering : IAutocompleteFilterBehavior { public CustomFiltering() { GetGoogleSuggestions("test"); } public Task<object> GetMatchingItemsAsync(SfAutocomplete source, AutocompleteFilterInfo filterInfo) { return GetGoogleSuggestions(filterInfo.Text); } }}

Step 5: Define a method to get Google suggestions

Define a private, asynchronous method named GetGoogleSuggestions, which makes a web request to the Google search suggestions API to fetch suggestions for the given query.

It takes a string parameter query as input and returns a list of suggestions as an object. It uses the HttpClient class to make the web request and parses the XML response to extract the suggestions.

using Syncfusion.Maui.Inputs;using System.Xml.Linq;namespace GoogleSearchDemo{ public class CustomFiltering : IAutocompleteFilterBehavior { public CustomFiltering() { GetGoogleSuggestions("test"); } public Task<object> GetMatchingItemsAsync(SfAutocomplete source, AutocompleteFilterInfo filterInfo) { return GetGoogleSuggestions(filterInfo.Text); } private async Task<object> GetGoogleSuggestions(string query) { if (string.IsNullOrEmpty(query) || string.IsNullOrWhiteSpace(query)) { return new List<string>(); } string xmlSuggestions; using (HttpClient client = new HttpClient()) { try { var searchQuery = String.Format("https://www.google.com/complete/search?output=toolbar&q={0}", query); xmlSuggestions = await client.GetStringAsync(searchQuery); } catch { return null; } } XDocument doc = XDocument.Parse(xmlSuggestions); var suggestions = doc.Descendants("CompleteSuggestion") .Select( item => item.Element("suggestion").Attribute("data").Value); return suggestions.ToList(); } }}

GitHub reference

For more information, refer to the demo on GitHub.

Conclusion

Thank you for taking the time to read this blog post. In this article, we have discussed the necessary steps to display Google search suggestions in our .NET MAUI Autocomplete control with custom filtering support. We recommend exploring the Getting Started documentation. We hope you found this information helpful.

If you are an existing Syncfusion customer, the new version of Essential Studio is available for download from the License and Downloads page. For those who are not yet Syncfusion customers, we offer a 30-day free trial to explore our available features.

Please let us know in the comments section below if you have any specific feature requests for our .NET MAUI controls. Additionally, you can contact us for assistance through our support forums, support portal, or feedback portal. We are always happy to help you!

Related blogs

• Data Visualization with a Heat Map Using .NET MAUI Scheduler
• Chart of the Week: Creating a .NET MAUI Column Chart to Visualize Yearly Box Office Data
• Create and Validate a Login Form in .NET MAUI
• Elevate Your App’s User Experience with the New .NET MAUI Shimmer Control

View Details

View Details

James is on a mission to get his app on as many platforms as possible. This time he dives through his journey of getting his Android apps into the Amazon App Store which also means onto Windows 11! What did he have to do and what was the experience like for his end users?

Follow Us* Frank: Twitter, Blog, GitHub * James: Twitter, Blog, GitHub * Merge Conflict: Twitter, Facebook, Website, Chat on Discord * Music : Amethyst Seer - Citrine by Adventureface

⭐⭐ Review Us ⭐⭐

Machine transcription available on http://mergeconflict.fm

Sponsored By:

• Laird Superfood: Are you ready to feel more energized, focused, and supported? Go to https://zen.ai/mergeconflict2 and add nourishing, plant-based foods to fuel you from sunrise to sunset. Use our promo code mergeconflict at checkout to save 15% off your purchase today! Promo Code: mergeconflict

Support Merge Conflict

View Details

If you’re looking to improve your app’s user-friendliness and interactivity, consider adding animations. Lottie makes it possible to incorporate animations in JSON format without slowing down your app. Learn more about Lottie and how to integrate it into .NET MAUI by reading our article!

The explanation will be divided into the following points:

What is a Lottie animation?

Initial setup

Choosing your animation

Adding the animation to your project

First of all… What do I need to know?

What is a Lottie animation?

Lottie is an open-source file format for animations based on JSON. It’s part of SkiaSharp and allows you to send animations to any platform as easily as sending static assets. Lottie is an alternative to GIFs and other types of animated files, and offers the following benefits:

Reduced file size: Lottie files are much smaller than other formats like GIF or MP4 while maintaining the same quality.

Vector-based adaptability: Lottie’s animations are vector-based, allowing you to scale them without affecting resolution.

Limitless customization: Since Lottie’s animations are vector-based, you can customize them without worrying about resolution.

Interactivity: You can manipulate animation elements to make them interactive and respond to user interactions such as scrolling, clicking, and mouse-over.

Let’s start! 

We will learn to implement it by applying the following instructions:

Initial setup

Add from NuGet Package – SkiaSharp.Extended.UI.Maui – At the time of writing this article, this Nuget Package is in a preview version. To add it, you must activate the “Include prereleases” option.

Go to your MauiProgram.cs file

In the CreateMauiApp method, go to the line .UseMauiApp<App>() and add the following line of code just below it:

Don’t forget to add the using SkiaSharp.Views.Maui.Controls.Hosting; at the top of the class.

Go to your .xaml file and add the following namespace. (In this example we will add it in the MainPage.xaml)

Choosing your animation

Now you need to select the animation you want to use in your app. You have two options for doing so:

Create an animation in Adobe After Effects: You can create your animation and export it to a JSON file with the help of the Bodymovin extension.

  Or select an animation already created in Lottiefiles. – In this article, we will implement this option. Therefore, apply the steps explained below:

Step 1: To find an animation on Lottiefiles, start by creating an account. Next, use the search bar to enter a topic. For the purpose of this example, I will search for “Girl”. Once you have located the desired animation, click on it.

Step 2: Once you have clicked on the animation, go to Download button Upload to My Workspace option.

Step 3: Once you have completed the previous step, a button will appear to save the animation. This will be available in your workspace, ready to download. To do this, go to the right side menu and select Lottie JSON Download.

Adding the animation to your project

We have already downloaded the animation to use in our app! Now all that remains is to add it to the project.

Add the animation to the Raw folder: Go to Resources Raw Right click add Existing files  yourAnimation.json.

Displaying the animation: 

To add the animation, we will use the SKLottieView from the SkiaSharp namespace, which we added at the beginning of this article with the alias “skia”.

SKLottieView provides different properties that allow you to have more direct control over the animations. The most important of these properties are the following:

Source:  It’s the animation that will be played in your application, remember that it’s in .JSON format– [Of type SKLottieImageSource]

Progress:  It’s the animation’s current playback progress. – [Of type TimeSpan]

RepeatCount: You can specify how many times the animation should be repeated. It’s default value is 0, but you can set it to -1 to repeat the animation infinitely. – [Of type int]

RepeatMode: It’s the way in which the animation will be repeated. This can be Restart or Reverse. the default is Reset. – [Of type SKLottieRepeatMode]

How to do it code?

To visualize your animation, it is important to add the HeightRequest and WidthRequest properties.

And done! From now on, you are ready to implement Lottie animations in your .NET MAUI applications!

<Label Text=”Thanks for reading!  ” />

Spanish post:

• https://es.askxammy.com/animaciones-con-lottie-en-net-maui/

View Details

Welcome to the second blog of our blog series, Chart of the Week!

Today, we are going to create a line chart to visualize the rising average egg prices in the U.S. using the Syncfusion .NET MAUI line chart control. This control is supported on both desktop (Windows and MacCatalyst) and mobile platforms (Android and iOS).

Due to avian influenza, the national average egg price in the United States has increased by 120% since the beginning of 2022. The national average cost for a dozen large, grade A eggs more than doubled, from $1.93 in January to $4.25 in December 2022.

Let’s see the steps to create a line chart visualizing the surge in U.S. egg prices in 2022 using the Syncfusion .NET MAUI line chart control.

Step 1: Gathering surge in egg price data

Before creating a chart, we should gather the egg price data from the United States consumer price index.

For this blog, we are obtaining data on the rise in egg prices from January to December 2022. You can also download it as a CSV file.

Step 2: Preparing the data for the chart

To create a line chart in .NET MAUI, we should provide the egg price data in a specific format. Therefore, create the EggPriceModel class to hold monthly data using the Month and AveragePrice properties.

Refer to the following code example.

public class EggPriceModel{ public DateTime Month { get; set; } public double AveragePrice { get; set; } public EggPriceModel(DateTime month, double averagePrice) { Month = month; AveragePrice = averagePrice; }}

Next, generate the collection of egg prices with the help of the AverageEggPrices class and its AveragePrices property. Convert the CSV data to a collection of egg prices using the ReadCSV method and store it in the AveragePrices property.

public class AverageEggPrices { private List<EggPriceModel> averagePrices; public List<EggPriceModel> AveragePrices { get{ return averagePrices; } set { averagePrices = value; } } public AverageEggPrices() { AveragePrices = new List<EggPriceModel>(ReadCSV()); } public IEnumerable<EggPriceModel> ReadCSV() { Assembly executingAssembly = typeof(App).GetTypeInfo().Assembly; Stream inputStream = executingAssembly.GetManifestResourceStream("EggPriceChart.Resources.Raw.eggpricechart.csv"); string? line; List<string> lines = new List<string>(); using StreamReader reader = new StreamReader(inputStream); while ((line = reader.ReadLine()) != null) { lines.Add(line); } return lines.Select(line => { string[] data = line.Split(','); DateTime date = DateTime.ParseExact(data[0], "MMMM", CultureInfo.InvariantCulture); return new EggPriceModel((date), Convert.ToDouble(data[1])); }); }}

Step 3: Configuring the Syncfusion .NET MAUI Cartesian Charts

Let’s configure the Syncfusion .NET MAUI Cartesian Charts control using this documentation.

Refer to the following the code example.

<chart:SfCartesianChart > <chart:SfCartesianChart.XAxes> <chart:DateTimeAxis > </chart:DateTimeAxis> </chart:SfCartesianChart.XAxes> <chart:SfCartesianChart.YAxes> <chart:NumericalAxis> </chart:NumericalAxis> </chart:SfCartesianChart.YAxes></chart:SfCartesianChart>

Step 4: Binding egg price data

Now, let’s bind the egg price data in the chart using the LineSeries. Refer to the following code example.

<chart:LineSeries XBindingPath="Month" YBindingPath="AveragePrice" ItemsSource="{Binding AveragePrices}"></chart:LineSeries>

In this example, we bound our chart to the AveragePrices property containing the monthly egg price data. We have also specified the x and y critical paths with the Month and AveragePrice properties, respectively, which inform the chart about the data points to be utilized for the x- and y-axes.

Step 5: Customizing the chart appearance.

We can customize the line chart’s appearance by changing the axis elements’ appearance, like showing data labels at the line points, changing the line style, adding data markers, and adding titles to the charts.

Refer to the following code example to customize the line chart title using the Title property.

<chart:SfCartesianChart.Title> <Grid HeightRequest="100"> <Grid.RowDefinitions> <RowDefinition Height="0.7*"/> <RowDefinition Height="0.3*"/> </Grid.RowDefinitions> <Label Grid.Row="0" Margin="3" Text="Average Egg Price Surges" HorizontalOptions="StartAndExpand" VerticalOptions="CenterAndExpand" FontAttributes="Bold" TextColor="Black" FontSize="Header" /> <Label Grid.Row="1" HorizontalOptions="StartAndExpand" VerticalOptions="CenterAndExpand" Text="The average price for a dozen grade A eggs in the U.S. rose in 2022" TextColor="Black" FontAttributes="Bold" FontSize="20"/> </Grid></chart:SfCartesianChart.Title>

Let’s customize the axis title and set the interval type, text color, font size, and other properties.

<chart:SfCartesianChart.XAxes> <chart:DateTimeAxis ShowMajorGridLines="False" IntervalType="Months" Interval="1" EdgeLabelsDrawingMode="Fit"> <chart:DateTimeAxis.Title> <chart:ChartAxisTitle TextColor="Black" FontSize="14" Text="Month"> </chart:ChartAxisTitle> </chart:DateTimeAxis.Title> </chart:DateTimeAxis></chart:SfCartesianChart.XAxes><chart:SfCartesianChart.YAxes> <chart:NumericalAxis> <chart:NumericalAxis.Title> <chart:ChartAxisTitle TextColor="Black" FontSize="14" Text="Price USD"> </chart:ChartAxisTitle> </chart:NumericalAxis.Title> </chart:NumericalAxis></chart:SfCartesianChart.YAxes>

Refer to the following code example to customize the line chart’s axis lines and tick lines.

<chart:SfCartesianChart.XAxes> <chart:DateTimeAxis > <chart:DateTimeAxis.AxisLineStyle> <chart:ChartLineStyle Stroke="GhostWhite" /> </chart:DateTimeAxis.AxisLineStyle> <chart:DateTimeAxis.MajorTickStyle> <chart:ChartAxisTickStyle Stroke="GhostWhite" /> </chart:DateTimeAxis.MajorTickStyle> </chart:DateTimeAxis></chart:SfCartesianChart.XAxes><chart:SfCartesianChart.YAxes> <chart:NumericalAxis > <chart:NumericalAxis.AxisLineStyle> <chart:ChartLineStyle Stroke="GhostWhite" /> </chart:NumericalAxis.AxisLineStyle> <chart:NumericalAxis.MajorTickStyle> <chart:ChartAxisTickStyle Stroke="GhostWhite" /> </chart:NumericalAxis.MajorTickStyle> </chart:NumericalAxis></chart:SfCartesianChart.YAxes>

Refer to the following code example to customize the axis labels using the LabelFormat property and set the Minimum and Maximum properties for the NumericalAxis.

<chart:SfCartesianChart.XAxes> <chart:DateTimeAxis.LabelStyle> <chart:ChartAxisLabelStyle LabelFormat="MMM" FontSize="13" TextColor="Black" /> </chart:DateTimeAxis.LabelStyle> </chart:DateTimeAxis></chart:SfCartesianChart.XAxes><chart:SfCartesianChart.YAxes> <chart:NumericalAxis Minimum="1.5" Maximum="5"> <chart:NumericalAxis.LabelStyle> <chart:ChartAxisLabelStyle LabelFormat="$###.##" FontSize="13" TextColor="Black" /> </chart:NumericalAxis.LabelStyle> </chart:NumericalAxis></chart:SfCartesianChart.YAxes>

Then, customize the line stroke style, color, and width using the StrokeDashArray, Fill, and StrokeWidth properties, respectively.

<chart:LineSeries x:Name="series" Fill="#e19620" StrokeWidth="5" StrokeDashArray="2,3,3" XBindingPath="Month" YBindingPath="AveragePrice" ShowMarkers="True" ShowDataLabels="True" ItemsSource="{Binding AveragePrices}"></chart:LineSeries>

Customize the chart data labels using the CartesianDataLabelSettings property and the label style with the appropriate format. To show the data labels, we need to enable the ShowDataLabels property in the LineSeries.

<chart:LineSeries.DataLabelSettings> <chart:CartesianDataLabelSettings LabelPlacement="Outer" UseSeriesPalette="False"> <chart:CartesianDataLabelSettings.LabelStyle> <chart:ChartDataLabelStyle LabelFormat="$###.##" Margin="0,25,0,0" LabelPadding="10" FontAttributes="Bold" /> </chart:CartesianDataLabelSettings.LabelStyle> </chart:CartesianDataLabelSettings></chart:LineSeries.DataLabelSettings>

Then, customize the chart’s data points using the MarkerSetting property and enable the markers using the ShowMarkers property in the LineSeries.

<chart:LineSeries.MarkerSettings> <chart:ChartMarkerSettings Height="55" Width="20" Fill="white" Type="Circle" Stroke="Black" StrokeWidth="2" > </chart:ChartMarkerSettings></chart:LineSeries.MarkerSettings>

Finally, let’s customize the chart’s plot area like in the following code example.

<chart:SfCartesianChart.PlotAreaBackgroundView> <AbsoluteLayout BackgroundColor="#c8e1f7"> <Label LineBreakMode="WordWrap" Margin="10" TextColor="Gray" WidthRequest="{OnPlatform Android='300',WinUI='500',iOS='300',MacCatalyst='500'}" Text="A few years ago, Avian flu caused egg prices to rise by 40% within nine months. By September 2015, the price of a dozen eggs had increased to $2.97." FontSize="{OnPlatform WinUI='13',Android='10',MacCatalyst='13',iOS='10'}" AbsoluteLayout.LayoutBounds="0,0.04,-1,-1" AbsoluteLayout.LayoutFlags="PositionProportional"/> </AbsoluteLayout></chart:SfCartesianChart.PlotAreaBackgroundView>

After executing these code examples, we will get the output like in the following image.

GitHub reference

For more details, refer to the demo on GitHub.

Conclusion

Thanks for reading! In this blog, we have seen how to use the Syncfusion .NET MAUI line chart to visualize the rise in U.S. egg prices in 2022. Like this, you can also visualize other trends and changes in prices over time. We encourage you to try the steps discussed and share your thoughts in the comments below.

If you require assistance, please don’t hesitate to contact us via our support forum, support portal, or feedback portal. We are always eager to help you!

Related blogs

• Simplify Data Visualization with Multi-Axis Charts in .NET MAUI
• Streamline MAUI Projects with the Syncfusion .NET MAUI Template Studio
• Elevate Your App’s User Experience with the New .NET MAUI Shimmer Control
• Chart of the Week: Creating a .NET MAUI Column Chart to Visualize Yearly Box Office Data

View Details

A login form allows users to enter their credentials, such as an email address and password, to authenticate and gain access to a website or application.

The .NET MAUI DataForm can be used to create various data forms. In this blog, I will explain how to develop and validate a login data form using the .NET MAUI DataForm.

Initialize the data from the control

1. Create a new .NET MAUI application in Visual Studio.
2. Syncfusion .NET MAUI components are available at nuget.org. To add the SfDataForm to your project, open the NuGet package manager in Visual Studio, search for Syncfusion.Maui.DataForm, and then install it.
3. To initialize the control, import the control namespace Syncfusion.Maui.DataForm in XAML or C# code and initialize the DataForm.

Refer to the following code to initialize the .NET MAUI DataForm.

MainPage.xaml

xmlns:dataForm="clr-namespace:Syncfusion.Maui.DataForm;assembly=Syncfusion.Maui.DataForm"<dataForm:SfDataForm x:Name="loginForm"/>

Register the ConfigureSyncfusionCore handler for Syncfusion core in the MauiProgram.cs file.

MauiProgram.cs

using Syncfusion.Maui.Core.Hosting;public static class MauiProgram{ public static MauiApp CreateMauiApp() { var builder = MauiApp.CreateBuilder(); builder.ConfigureSyncfusionCore(); builder.ConfigureSyncfusionCore(); }}

Create login data from the model

Create a login form with the following fields to get email addresses and passwords.

LoginFormModel.cs

public class LoginFormModel{ [Display(Prompt = "example@mail.com", Name = "Email")] public string Email{ get; set; } [Display(Name = "Password")] [DataType(DataType.Password)] public string Password { get; set; }}

Create login form editors

By default, the data form auto-generates the data editors based on primitive data types such as string, enumeration, DateTime, and TimeSpan in the DataObject property.

You can change the editor layout default (label and editor) and floating label layout using the LayoutType property.

Refer to the following code example. In it, we set the data form model (LoginFormModel) to the DataObject property from the view model class to create the data editors for the login form with a floating label layout.

Please refer to the code to bind the LoginFormModel property from the DataFormViewModel class.

MainPage.xaml

...<ContentPage.BindingContext> <local:DataFormViewModel/></ContentPage.BindingContext><dataForm:SfDataForm x:Name="loginForm" DataObject="{Binding LoginFormModel}" LayoutType="TextInputLayout" />

Refer to the code to initialize the LoginFormModel property.

DataFormViewModel.cs

public class DataFormViewModel{ /// <summary> /// Initializes a new instance of the <see cref="DataFormViewModel" /> class. /// </summary> public DataFormViewModel() { this.LoginFormModel = new LoginFormModel(); } /// <summary> /// Gets or sets the login form model. /// </summary> public LoginFormModel LoginFormModel { get; set; }}

Design the login form page

Let’s design the login page with images, buttons, checkboxes, and labels. 

Refer to the following code to add an image to the login form.

MainPage.xaml

<Border Grid.ColumnSpan="{OnIdiom Default=2, Desktop=1}" Stroke="Transparent" Background="{OnIdiom Phone=#83E9EE,Desktop=Transparent}" Grid.RowSpan="{OnIdiom Default=1, Desktop=2}"> <Border.StrokeShape> <RoundRectangle CornerRadius="0,0,100,100"/> </Border.StrokeShape> <Image Source="login.png" Grid.Row="0" Grid.Column="0" HorizontalOptions="Center" Aspect="AspectFit"/></Border>

Next, add the Remember Me checkbox and Forgot password label in the login form.

MainPage.xaml

<Grid ColumnDefinitions="0.5*,0.5*" Grid.Row="2" Padding="12,0,0,0" VerticalOptions="Start"> <HorizontalStackLayout VerticalOptions="Center" Padding="10,0,0,0" > <CheckBox Color="{StaticResource Primary}"/> <Label Text="Remember me" FontSize="12" VerticalOptions="Center" /> </HorizontalStackLayout> <Label Text="Forgot password?" Grid.Column="1" TextColor="{StaticResource Primary}" HorizontalTextAlignment="Center" Padding="10,0,0,0" FontSize="12" VerticalOptions="Center" /></Grid>

Then, add the LOGIN button in the login form.

MainPage.xaml

<Button Text="LOGIN" x:Name="loginButton" HeightRequest="40" VerticalOptions="End" HorizontalOptions="Fill" Margin="20,0,20,0" CornerRadius="10" Padding="0" FontAttributes="Bold" Grid.Row="3" Background="{StaticResource Primary}"/>

Next, refer to the following code to add the Don’t have an account? Sign Up label in the login form. You can refer to this blog for how to create a signup form.

MainPage.xaml

<Label Grid.Row="4" Padding="0,12,0,0" HorizontalOptions="Center" HorizontalTextAlignment="Center" FontSize="14"> <Label.FormattedText> <FormattedString> <Span Text="Don't have an account? " /> <Span Text="Sign Up" TextDecorations="Underline" TextColor="{StaticResource Primary}"/> </FormattedString> </Label.FormattedText></Label>

Change the keyboard for the email editor

Use the email field keyboard by updating the keyboard property in the GenerateDataFormItem event.

Refer to the following code to change the keyboard for the email editor.

MainPage.xaml

<ContentPage.Behaviors> <local:LoginFormBehavior/></ContentPage.Behaviors>

LoginFormBehavior.cs

this.dataForm = bindable.FindByName<SfDataForm>("loginForm"); this.dataForm.GenerateDataFormItem += this.OnGenerateDataFormItem;private void OnGenerateDataFormItem(object sender, GenerateDataFormItemEventArgs e){ if (e.DataFormItem != null && e.DataFormItem.FieldName == nameof(LoginFormModel.Email) && e.DataFormItem is DataFormTextEditorItem textItem) { textItem.Keyboard = Keyboard.Email; }}

Validate the login form

The email address and password fields must not be empty. If either field is left blank or has invalid data, an error message will be displayed, and the user cannot submit the form.

Please refer to the code to add EmailAddress and Required validation attributes.

LoginFormModel.cs

public class LoginFormModel{ [Display(Prompt = "example@mail.com", Name = "Email")] [EmailAddress(ErrorMessage = "Enter your email - example@mail.com")] public string Email { get; set; } [Display(Name = "Password")] [DataType(DataType.Password)] [Required(ErrorMessage = "Enter the password")] public string Password { get; set; }}

The data form supports validating the data by using the ValidationMode property.

Refer to the following code to set the validation mode to PropertyChanged; the value will be validated immediately when changed.

MainPage.xaml

<dataForm:SfDataForm x:Name="loginForm" LayoutType="TextInputLayout" Grid.Row="1" DataObject="{Binding LoginFormModel}" ValidationMode="PropertyChanged" > <ContentPage.Behaviors> <local:LoginFormBehavior/> </ContentPage.Behaviors>

Login form validation can be handled while submitting the login button using the Validate method.

LoginFormBehavior.cs

private async void OnLoginButtonCliked(object sender, EventArgs e){ if(this.dataForm != null && App.Current?.MainPage != null) { if(this.dataForm.Validate()) { await App.Current.MainPage.DisplayAlert("", "Signed in successfully", "OK"); } else { await App.Current.MainPage.DisplayAlert("", "Please enter the required details", "OK"); } }}

GitHub reference

Refer to the GitHub demo on this topic.

Conclusion

Thanks for reading. This blog demonstrated how to create and validate a login form using the .NET MAUI DataForm control. Try out the steps in this blog and leave your feedback in the comments section below.

For current Syncfusion customers, the newest version of Essential Studio is available from the license and downloads page. If you are not a customer, try our 30-day free trial to check out these new features. If you have questions, contact us through our support forums, feedback portal, or support portal. We are always happy to assist you!

Related Blogs

• Simplify Data Visualization with Multi-Axis Charts in .NET MAUI
• Building a Hijri Calendar with .NET MAUI Scheduler: A Beginner’s Guide
• Elevate Your App’s User Experience with the New .NET MAUI Shimmer Control
• Streamline MAUI Projects with the Syncfusion .NET MAUI Template Studio

View Details

That is right! Everyone's favorite MP3 player is back! This time due to a collaboration with Guardians of the Galaxy, but it doesn't matter because Hanselman and others have found ways to revive it in 2023. We discuss the Zune software, UI stack, why we loved it, and why it may have been the best XAML to XAML.

Follow Us* Frank: Twitter, Blog, GitHub * James: Twitter, Blog, GitHub * Merge Conflict: Twitter, Facebook, Website, Chat on Discord * Music : Amethyst Seer - Citrine by Adventureface

⭐⭐ Review Us ⭐⭐

Machine transcription available on http://mergeconflict.fm

Support Merge Conflict

Links:

• Zune.net: Empowering the Galaxy
• ZuneDev

View Details

Event name:                                  Update Days: .NET MAUI

Talk name:                                     .NET MAUI Layouts, navigation, shell &  MAUI Community Toolkit

Official Site:                                  https://maui.updatedays.cz/schedule/en

Location:                                        Prague, Czech Republic

Language:                                       English

Date:                                                March 23th & 24th, 2023

I was invited to speak at the Update Days .NET MAUI event held in Czech Republic. This prestigious conference brings together some of the most renowned experts in the industry to discuss the latest developments in .NET MAUI, the new technology developed by #Microsoft.

I’m incredibly grateful for the opportunity to have contributed my knowledge to all the participants at this event. I also had the privilege of meeting and connecting with other brilliant professionals in the industry, including Gerald Versluis , Roman Jasek!

Special thanks to Tomáš Herceg for the invitation!

Thank for ready!

View Details

View Details

View Details

I’ve posted my .NET MAUI For Xamarin.Forms Programmers and Advanced .NET MAUI videos on YouTube.

View Details

We are well into .NET6 and .NET7 release lifecycle and .NET8 coming up soon. Additionally end of life of Xamarin is coming increasingly closer, so I bet a lot of people are looking towards migrating to the newer bits.

View Details

The old way

Before iOS 16, it was pretty easy to lock a Page into a certain orientation. It was basically just one line of code (if you don’t count the DependencyService boilerplate code in):

UIDevice.CurrentDevice.SetValueForKey(new NSNumber((int)UIInterfaceOrientation.Portrait), new NSString("orientation"));

By calling this method whenever the size of a page was allocated, we were able to lock the orientation at runtime with Xamarin.Forms. With iOS 16, this does no longer work – even on native iOS applications.

The new way

To understand the why of the new way, you have to understand the SceneDelegate architecture Apple introduced with iOS 13. Before continuing, you should read this blog post by Donny Wals, which explains it very detailed: Understanding the iOS 13 Scene Delegate – Donny Wals.

Now that we know that the SceneDelegate is, we can move on with our implementation.

Page implementation

Both Xamarin.Forms and .NET MAUI implement the SceneDelegate architecture. That’s why we can update our code similarly to what native iOS implementations look like:

var rootWindowScene = (UIApplication.SharedApplication.ConnectedScenes.ToArray()?.FirstOrDefault()) as UIWindowScene;if (rootWindowScene == null) return;rootWindowScene.RequestGeometryUpdate(new UIWindowSceneGeometryPreferencesIOS(UIInterfaceOrientationMask.Portrait),error =>{ Debug.WriteLine("Error while attempting to lock orientation: {Error}", error.LocalizedDescription);});

On top, we have to tell the underlying ViewControllers to update their orientation as well:

var rootViewController = UIApplication.SharedApplication.KeyWindow?.RootViewController;if (rootViewController == null) return;rootViewController.SetNeedsUpdateOfSupportedInterfaceOrientations();rootViewController.NavigationController?.SetNeedsUpdateOfSupportedInterfaceOrientations();

The ViewController can be informed via the SetNeedsUpdateOfSupportedInterfaceOrientations method that it needs to redraw its view. If we put this all together, we can have a reusable implementation for our DeviceOrientationService implementation:

private void SetOrientation(UIInterfaceOrientationMask uiInterfaceOrientationMask){ var rootWindowScene = (UIApplication.SharedApplication.ConnectedScenes.ToArray()?.FirstOrDefault()) as UIWindowScene; if (rootWindowScene == null) return; var rootViewController = UIApplication.SharedApplication.KeyWindow?.RootViewController; if (rootViewController == null) return; rootWindowScene.RequestGeometryUpdate(new UIWindowSceneGeometryPreferencesIOS(uiInterfaceOrientationMask), error => { Debug.WriteLine("Error while attempting to lock orientation: {Error}", error.LocalizedDescription); }); rootViewController.SetNeedsUpdateOfSupportedInterfaceOrientations(); rootViewController.NavigationController?.SetNeedsUpdateOfSupportedInterfaceOrientations();}

To keep our existing code for older iOS versions working as well. We now just check if we are on iOS 16 and call our new method, below we still can use our traditional way:

public void LockPortrait(){ if (UIDevice.CurrentDevice.CheckSystemVersion(16, 0)) { \_applicationDelegate.CurrentLockedOrientation = UIInterfaceOrientationMask.Portrait; SetOrientation(UIInterfaceOrientationMask.Portrait); } else { UIDevice.CurrentDevice.SetValueForKey(new NSNumber((int)UIInterfaceOrientation.Portrait), new NSString("orientation")); }}

This will, however, do nothing without the last, very important step. You may have noticed the CurrentLockedOrientation property on the application delegate member above.

Every time the application has to decide whether to rotate or not, the application:supportedInterfaceOrientationsForWindow: gets called to ask for the supported orientations. Only if the application and the ViewController agree on the supported orientations, the action will be executed.

Extending our AppDelegate

Just as on native iOS, we need to implement the method above in our AppDelegate. Xamarin and .NET MAUI do this via the Export attribute, which tells the compiler to override the eventually existing native implementation.

For my solution, I created a derived version of the FormsApplicationDelegate / MauiUIApplicationDelegate classes, passing the current desired UIInterfaceOrientationMask value to the CurrentLockedOrientation property. Finally, I implement the GetSupportedInterfaceOrientationsForWindow method and just return the value of the CurrentLockedOrientation property:

public abstract class AppDelegateEx : MauiUIApplicationDelegate{ public virtual UIInterfaceOrientationMask CurrentLockedOrientation { get; set; } //according to the Apple docs, Application and ViewController have to agree on the supported orientation, this forces it //https://developer.apple.com/documentation/uikit/uiapplicationdelegate/1623107-application?language=objc [Foundation.Export("application:supportedInterfaceOrientationsForWindow:")] public virtual UIInterfaceOrientationMask GetSupportedInterfaceOrientationsForWindow(UIApplication application, UIWindow forWindow) => this.CurrentLockedOrientation;}

Now we just make the AppDelegate derive from AppDelegateEx (or whatever you call it) to finish the implementation for the orientation lock. Finally, locking the orientation works also on iOS 16.

Samples

I created two samples – one for Xamarin.Forms and one for .NET MAUI. The sample work similar on both platforms, and I wrote the code in a reusable way. You can find the samples in the corresponding GitHub repo.

Conclusion

It took me some time to figure out why the traditional way of locking the orientation doesn’t work any longer. After some research and some trial-and-error coding, I was able to come up with a clean and easy-to use solution, which is also reusable. I also learned some new things, like how MAUI implements Scenes and ViewControllers and got a better understanding of the iOS application structure and lifecycle on newer OS versions.

As always, I hope this post will be helpful for some of you as well.

Until the next post, happy coding!

Helpful links:

• Understanding the iOS 13 Scene Delegate – Donny Wals
• swift – How to resolve: ‘keyWindow’ was deprecated in iOS 13.0 – Stack Overflow
• requestGeometryUpdateWithPreferences:errorHandler: | Apple Developer Documentation
• application:supportedInterfaceOrientationsForWindow: | Apple Developer Documentation
• (UIInterfaceOrientationMask)applic… | Apple Developer Forums
• Forcing specific MAUI view to Landscape Orientation using MultiTargeting Feature working for Android but not iOS – Stack Overflow

Title Image created via Bing Create with AI

The post How to lock orientation at runtime on iOS 16 with .NET MAUI and Xamarin.Forms appeared first on MSicc's Blog.

View Details

View Details

Show NotesIt's been a little bit... but James, David, and Matt are back with the latest .NET MAUI and Azure news!

Latest Releases* The latest on .NET MAUI * .NET Upgrade Assistant * .NET Upgrade Assistant NuGet * .NET 8 Preview 3 * Visual Studio 17.6 preview 2 * Visual Studio 17.5 updates

Latest News* Drawing elements on maps in .NET MAUI * Azure Developers - .NET Day * Let's Learn .NET - All Around the World * Build, Build, and more Build * File and folder dialogs in with the .NET MAUI Community Toolkit

Azure News* Getting started with OpenAI in .NET * Data API Builder - Public Preview * .NET SQL Passwordless connections

Azure Service of the Month* Microsoft Dev Box

Pick of the Pod* Apple command line tooling

Follow Us:

• James: Twitter, Blog, GitHub, Merge Conflict Podcast
• Matt: Twitter, Blog, GitHub
• David: Twitter, Github

View Details

I have gone all in on Arm devices! My main MAC machine is a Mac Book Air M1 and now my main driver at work is a Windows Dev Kit 2023 (aka Project Volterra). One tricky thing for developers is getting all the software we use to work properly on Arm. Things have come a long way since the original release of Arm devices for Mac and Windows. I have a full setup guide for my M1 for Xamarin and now .NET MAUI development, but what about Windows?

Visual Studio 2022 recently released a full native Arm version and they have been adding more workloads for developers to use. .NET MAUI was recently introduced, which got me excited but I right away ran into an issue, which was that there are no compatible Android emulators for Windows Arm and apparently no plans from Google :(. So, what are our options? Two come to mind.

Deploy to a device

Well, it may be obvious, but you can just plug in a device and use something like Vysor to mirror your device. I am always a fan of deploying and testing on devices as you have full access to everything including Google Play services. As a bonus you don't drag down any resources on your main machine. If you don't have a device, you are still in luck!

Windows Subsystem for Android

That's right! I have blogged and talked about it a bunch, but the Windows Subsystem for Android(WSA) is a great way to deploy and debug applications on any Windows 11 machine. It has expanded into more regions since its first release, which is awesome. If you haven't heard about WSA, it is a mode that you can enable that allows you to run Android applications directly on your Windows machine. There are limitations of course, the largest being no access to Google Play services, but for a lot of developers this will get you off the ground running. Checkout my full video:

If you are using Visual Studio 2022 there is a great extension that will help you get up and running and automatically connect.

Once you have it all set up, it is ready and available!

So, there you go! Two ways to get deploying Android apps if you are developing on a Windows Arm device.

View Details

This post will be focused on some hints that can help you to make the migration from Xamarin.Forms to .NET MAUI a smoother process.

View Details

In recent years, the development of mobile applications has gained great importance in the world of technology. The demand for mobile apps has increased significantly, which has led to increased competition in the market. For this reason, developers are looking for tools and technologies that allow them to create mobile applications faster and more efficiently. One of these tools is .NET MAUI.

.NET MAUI is an open-source mobile development platform that allows developers to create mobile apps for Android, iOS, and Windows in a single codebase. This means that developers only have to write the code once and can compile it for different mobile platforms. .NET MAUI is a Xamarin.Forms-based technology that has been enhanced for a smoother and easier development experience.

In this article, we’ll teach you how to create a mobile app with .NET MAUI in 10 easy steps. These steps guide you from initial setup to creating a user interface, connecting to a database, and publishing your app to app stores.

.NET MAUI in 10 easy steps

Step 1: Set up your development environment

The first thing you need to do is set up your development environment. To work with .NET MAUI you will need to have Visual Studio 2022 installed. You also need to install the .NET 6.0 SDK. In addition, you’ll need to install the .NET MAUI plug-in for Visual Studio.

Guide: Installing Visual Studio 2022

Step 2: Create a .NET MAUI Project

The next step is to create a new .NET MAUI project in Visual Studio. To do this, select “File” from the menu bar, then “New” and “Project”. Select “.NET MAUI Mobile App” and set the project name and location.

Tutorial: Tutorial: Creating a MAUI Application

Step 3: Build your project

Build or run your first cross-platform .NET MAUI app in Visual Studio 2022 on Windows or Visual Studio 2022 for Mac. This will help ensure that the development environment is configured correctly.

Walkthrough: Building Your First MAUI App

Step 4: Create a user interface

Once you’ve set up the project, it’s time to create the user interface. To do this, you can use a wide variety of controls. These controls allow you to design the user interface easily and quickly.

Documentation: Controls – .NET MAUI

Step 5: Add functionality to your app

After you create the UI, it’s time to add functionality to your app. You can add functionality such as camera, GPS, and Internet connectivity using the .NET MAUI Community Toolkit libraries.

Documentation: .NET MAUI Community Toolkit documentation

You can also integrate third-party services such as social networks or online payment services.

Documentation: Consuming a REST-based Web Service

Step 6: Connect to a database

Most mobile apps require a database to store and manage the data. With .NET MAUI, you can use the SQLite library to connect to a database. SQLite is a relational database that is very easy to use and is compatible with most mobile platforms.

Documentation: Local .NET MAUI Databases

Step 7: Test and debug your app

Before you publish your app to the app stores, it’s important to test and debug it to make sure it’s working properly. Use the Visual Studio debugger to find and fix errors.

Documentation: Debugging on the Android Emulator

Step 8: Publish the app

Once you’ve tested and debugged your app, it’s time to publish it to the app stores. To do this, you’ll need to create a developer account on the Google Play Store and Apple’s App Store. Then, you’ll need to follow the steps to publish the app to each of the stores.

Documentation: Deployment – .NET MAUI

Step 9: Maintain and update the application

Once your app is published, it’s important to keep it up to date and fix any errors that arise. It is also important to update the application to add new functionalities and improve the user experience.

Step 10: Track and analyze performance

Finally, it’s important that you track and analyze your app’s performance. Use tools like Google Analytics or App Annie to monitor the number of downloads, retention rate, and other key performance indicators.

Conclusion

Creating a mobile app with .NET MAUI is easier than it sounds. In just 10 steps, you can create a mobile app for Android, iOS, and Windows using a single codebase. In addition, .NET MAUI lets you build an app with an attractive user interface, advanced features, and a robust database.

If you’re a developer looking for an easy-to-use and efficient mobile development platform, .NET MAUI is a great choice. Follow these 10 steps, and you’ll be well on your way to creating a successful mobile app.

The post How to create a mobile app with .NET MAUI in 10 easy steps appeared first on Luis Matos.

View Details

When it comes to custom renderers in your Xamarin.Forms app, how do those migrate to .NET MAUI? One option is handlers.

View Details

Use Ansight to record, replay and analyse testing sessions of your Android apps. No SDKs, code changes or developer tools needed. Fully plug and play. Framework agnostic.

More

View Details

Roll up your sleeves! It’s time to get to work migrating a real app from Xamarin to .NET MAUI!

View Details

What steps should you take when preparing to migrate your app from Xamarin.Forms to .NET MAUI? This list will help you think it through.

View Details

Examine the benefits of migrating to .NET MAUI from Xamarin.Forms for the dev experience, the app and our end users, plus any downsides, so you can decide if and when migration is right for your app.

View Details

A new property in .NET 8 helps to make the app context-aware thus improving the overall user experience.

View Details

Xamarin Forms developers need to take note of these small yet significant changes from the layout rules you knew in Xamarin to how layouts will work in .NET MAUI.

View Details

When it comes to developing mobile apps, there are many tools available in the market. However, not all tools are created equal. Some tools are better suited for specific projects, while others may be more flexible and versatile. In this article, we’ll talk about the advantages of .NET MAUI compared to other mobile development tools and why you should consider using it for your next project.

.NET MAUI and its advantages

.NET MAUI is a cross-platform mobile development tool that allows developers to create iOS, Android, and Windows apps in a single project. Here are some advantages of .NET MAUI compared to other mobile development tools:

1. Familiar programming language: .NET MAUI is based on C# and .NET, popular languages widely used in the developer community. This means that developers won’t have to learn a new programming language to use .NET MAUI, allowing them to speed up the development process and be more efficient.
2. Visual Studio integration: .NET MAUI integrates seamlessly with Visual Studio, Microsoft’s integrated development environment (IDE). This means that developers can use Visual Studio to develop .NET MAUI applications, allowing them to take advantage of the advanced debugging features and productivity tools offered by Visual Studio.
3. Support for the latest version of .NET: .NET MAUI supports the latest version of .NET. This means developers can take advantage of the new features and performance improvements offered by .NET to build faster, more efficient applications.
4. Community and Support: The .NET MAUI community is active and growing, which means there are many resources available for developers who need help or have questions. In addition, Microsoft, the creator of .NET MAUI, offers support and continuous updates for the tool, ensuring it keeps up with the latest technologies and trends.
5. Responsive design: .NET MAUI uses XAML, a markup language, and C# for UI design. These tools allow developers to create responsive layouts that automatically adjust to the screen size of the device the app is running on. This means developers can create user interfaces that look good on devices of different sizes and resolutions.
6. Control and Component Library: .NET MAUI provides an extensive library of controls and components to help developers create sophisticated, customized user interfaces. These controls and components can be used in iOS, Android, and Windows apps, enabling developers to create consistent, high-quality apps across platforms.
7. Integrated debugging and testing: .NET MAUI provides advanced debugging and testing tools built into Visual Studio. Developers can debug their code in real time and perform automated testing to make sure their app works correctly on all platforms.

Recommendations

If you’re looking for a cross-platform mobile development tool, you should consider .NET MAUI. Some recommendations for getting the most out of .NET MAUI include:

1. Learn C# and .NET: If you’re not familiar with C# and .NET, you should take the time to learn these programming languages. This will allow you to get the most out of .NET MAUI and be more efficient in the development process.
2. Use Visual Studio: If you’re not already using Visual Studio, you should start using it to develop .NET MAUI applications. Visual Studio offers advanced debugging and productivity tools that help you be more efficient in the development process.
3. Join the .NET MAUI Community: If you have questions or need help with .NET MAUI, you should join the .NET MAUI community. There are many resources available, including forums, discussion groups, and online tutorials.
4. Use the MVVM pattern: .NET MAUI integrates seamlessly with the MVVM (Model-View-ViewModel) pattern, which is a design pattern commonly used in Xamarin apps. Using the MVVM pattern can help developers create more structured and maintainable applications.
5. Use web services: .NET MAUI integrates well with web services, which means developers can use web services to store and retrieve data in their applications. Using web services can help developers build more scalable and efficient applications.
6. Test on real devices: Although .NET MAUI offers advanced debugging and testing tools, it is important to test your application on real devices before releasing it to the market. Developers should ensure that their app looks and works properly on all supported devices and operating systems.

Resources

Here is a list of helpful resources to learn more about .NET MAUI:

1. Official .NET MAUI documentation: The official .NET MAUI documentation provides detailed guidance on how to get started developing cross-platform mobile apps using .NET MAUI. You can access the documentation on Microsoft’s official website.
2. Microsoft Developer YouTube channel: The Microsoft Developer YouTube channel offers instructional videos on .NET MAUI, including tutorials on how to build cross-platform mobile apps with .NET MAUI.
3. .NET MAUI Community: The .NET MAUI community is a valuable resource for any developer interested in this tool. The community website offers forums, blogs, and discussion groups where developers can interact and share information about .NET MAUI.
4. Microsoft Learn Course: Microsoft Learn offers a comprehensive course on .NET MAUI that covers everything from the basics to building sophisticated cross-platform mobile apps.
5. .NET MAUI sample code: Microsoft has published a lot of sample .NET MAUI code on its website, which can help developers understand how the tool works in practice.
6. Visual Studio Community: Visual Studio Community is a free version of Visual Studio that includes all the tools needed to develop cross-platform mobile apps with .NET MAUI.
7. Xamarin.Forms Documentation: Xamarin.Forms is the mobile development tool that predates .NET MAUI, but is still supported. The Xamarin.Forms documentation is useful for understanding the concepts and patterns that apply in .NET MAUI.

Conclusion

In conclusion, .NET MAUI is a cross-platform mobile development tool that offers many advantages compared to other tools. By using familiar programming languages, integrating with Visual Studio, supporting .NET 6, and having an active community and ongoing support, .NET MAUI presents itself as a versatile and efficient tool for cross-platform mobile application development.

If you’re looking for a mobile development tool that allows you to build iOS, Android, and Windows apps in a single project, you should consider .NET MAUI as a viable option.

I hope these advantages and recommendations will help you consider .NET MAUI as an effective tool for cross-platform mobile application development. Good luck in your mobile app development project!

The post Why is .NET MAUI the best tool for cross-platform mobile development? appeared first on Luis Matos.

View Details

Cuando se trata de desarrollar aplicaciones móviles, hay muchas herramientas disponibles en el mercado. Sin embargo, no todas las herramientas son iguales. Algunas herramientas son más adecuadas para proyectos específicos, mientras que otras pueden ser más flexibles y versátiles. En este artículo, hablaremos sobre las ventajas de .NET MAUI en comparación con otras herramientas de desarrollo móvil y por qué deberías considerar utilizarla para tu próximo proyecto.

.NET MAUI y sus ventajas

.NET MAUI es una herramienta de desarrollo móvil multiplataforma que permite a los desarrolladores crear aplicaciones para iOS, Android y Windows en un solo proyecto. A continuación, se presentan algunas ventajas de .NET MAUI en comparación con otras herramientas de desarrollo móvil:

1. Lenguaje de programación familiar: .NET MAUI se basa en C# y .NET, lenguajes populares y ampliamente utilizados en la comunidad de desarrolladores. Esto significa que los desarrolladores no tendrán que aprender un nuevo lenguaje de programación para utilizar .NET MAUI, lo que les permitirá acelerar el proceso de desarrollo y ser más eficientes.
2. Integración con Visual Studio: .NET MAUI se integra perfectamente con Visual Studio, el entorno de desarrollo integrado (IDE) de Microsoft. Esto significa que los desarrolladores pueden utilizar Visual Studio para desarrollar aplicaciones de .NET MAUI, lo que les permitirá aprovechar las características avanzadas de depuración y herramientas de productividad que ofrece Visual Studio.
3. Compatibilidad con la última versión de .NET: .NET MAUI es compatible con la última versión de .NET. Esto significa que los desarrolladores pueden aprovechar las nuevas características y mejoras de rendimiento que ofrece .NET para crear aplicaciones más rápidas y eficientes.
4. Comunidad y soporte: La comunidad de .NET MAUI es activa y en crecimiento, lo que significa que hay muchos recursos disponibles para los desarrolladores que necesitan ayuda o tienen preguntas. Además, Microsoft, el creador de .NET MAUI, ofrece soporte y actualizaciones continuas para la herramienta, lo que garantiza que se mantenga al día con las últimas tecnologías y tendencias.
5. Diseño adaptable: .NET MAUI utiliza XAML, un lenguaje de marcado, y C# para el diseño de interfaces de usuario. Estas herramientas permiten a los desarrolladores crear diseños adaptables que se ajustan automáticamente al tamaño de la pantalla del dispositivo en el que se está ejecutando la aplicación. Esto significa que los desarrolladores pueden crear interfaces de usuario que se vean bien en dispositivos de diferentes tamaños y resoluciones.
6. Biblioteca de controles y componentes: .NET MAUI ofrece una amplia biblioteca de controles y componentes para ayudar a los desarrolladores a crear interfaces de usuario sofisticadas y personalizadas. Estos controles y componentes se pueden utilizar en aplicaciones de iOS, Android y Windows, lo que permite a los desarrolladores crear aplicaciones coherentes y de alta calidad en todas las plataformas.
7. Depuración y pruebas integradas: .NET MAUI ofrece herramientas avanzadas de depuración y pruebas integradas en Visual Studio. Los desarrolladores pueden depurar su código en tiempo real y realizar pruebas automatizadas para asegurarse de que su aplicación funciona correctamente en todas las plataformas.

Recomendaciones

Si estás buscando una herramienta de desarrollo móvil multiplataforma, deberías considerar .NET MAUI. Algunas recomendaciones para aprovechar al máximo .NET MAUI incluyen:

1. Aprender C# y .NET: Si no estás familiarizado con C# y .NET, deberías tomar el tiempo para aprender estos lenguajes de programación. Esto te permitirá aprovechar al máximo .NET MAUI y ser más eficiente en el proceso de desarrollo.
2. Utilizar Visual Studio: Si aún no estás utilizando Visual Studio, deberías empezar a utilizarlo para desarrollar aplicaciones de .NET MAUI. Visual Studio ofrece herramientas avanzadas de depuración y productividad que te ayudarán a ser más eficiente en el proceso de desarrollo.
3. Unirse a la comunidad de .NET MAUI: Si tienes preguntas o necesitas ayuda con .NET MAUI, deberías unirte a la comunidad de .NET MAUI. Hay muchos recursos disponibles, incluyendo foros, grupos de discusión y tutoriales en línea.
4. Utilizar el patrón MVVM: .NET MAUI se integra perfectamente con el patrón MVVM (Model-View-ViewModel), que es un patrón de diseño comúnmente utilizado en aplicaciones de Xamarin. Utilizar el patrón MVVM puede ayudar a los desarrolladores a crear aplicaciones más estructuradas y fáciles de mantener.
5. Utilizar servicios web: .NET MAUI se integra bien con servicios web, lo que significa que los desarrolladores pueden utilizar servicios web para almacenar y recuperar datos en sus aplicaciones. Utilizar servicios web puede ayudar a los desarrolladores a crear aplicaciones más escalables y eficientes.
6. Probar en dispositivos reales: Aunque .NET MAUI ofrece herramientas avanzadas de depuración y pruebas, es importante probar la aplicación en dispositivos reales antes de lanzarla al mercado. Los desarrolladores deben asegurarse de que su aplicación se vea y funcione correctamente en todos los dispositivos y sistemas operativos compatibles.

Recursos

Aquí hay una lista de recursos útiles para obtener más información sobre .NET MAUI:

1. Documentación oficial de .NET MAUI: La documentación oficial de .NET MAUI ofrece una guía detallada sobre cómo comenzar a desarrollar aplicaciones móviles multiplataformas utilizando .NET MAUI. Puedes acceder a la documentación en el sitio web oficial de Microsoft.
2. Canal de YouTube de Microsoft Developer: El canal de YouTube de Microsoft Developer ofrece videos instructivos sobre .NET MAUI, incluyendo tutoriales sobre cómo crear aplicaciones móviles multiplataformas con .NET MAUI.
3. Comunidad de .NET MAUI: La comunidad de .NET MAUI es un recurso valioso para cualquier desarrollador interesado en esta herramienta. El sitio web de la comunidad ofrece foros, blogs y grupos de discusión donde los desarrolladores pueden interactuar y compartir información sobre .NET MAUI.
4. Curso de Microsoft Learn: Microsoft Learn ofrece un curso completo sobre .NET MAUI que cubre todo, desde los conceptos básicos hasta la creación de aplicaciones móviles multiplataforma sofisticadas.
5. Código de ejemplo de .NET MAUI: Microsoft ha publicado una gran cantidad de código de ejemplo de .NET MAUI en su sitio web, lo que puede ayudar a los desarrolladores a comprender cómo funciona la herramienta en la práctica.
6. Visual Studio Community: Visual Studio Community es una versión gratuita de Visual Studio que incluye todas las herramientas necesarias para desarrollar aplicaciones móviles multiplataformas con .NET MAUI.
7. Xamarin.Forms Documentation: Xamarin.Forms es la herramienta de desarrollo móvil anterior a .NET MAUI, pero que aún es compatible. La documentación de Xamarin.Forms es útil para comprender los conceptos y patrones que se aplican en .NET MAUI.

Conclusión

En conclusión, .NET MAUI es una herramienta de desarrollo móvil multiplataforma que ofrece muchas ventajas en comparación con otras herramientas. Al utilizar lenguajes de programación familiares, integrarse con Visual Studio, ser compatible con .NET 6 y contar con una comunidad activa y un soporte continuo, .NET MAUI se presenta como una herramienta versátil y eficiente para el desarrollo de aplicaciones móviles multiplataforma.

Si estás buscando una herramienta de desarrollo móvil que te permita crear aplicaciones para iOS, Android y Windows en un solo proyecto, deberías considerar .NET MAUI como una opción viable.

Espero que estas ventajas y recomendaciones te ayuden a considerar .NET MAUI como una herramienta eficaz para el desarrollo de aplicaciones móviles multiplataforma. ¡Buena suerte en tu proyecto de desarrollo de aplicaciones móviles!

The post ¿Por qué .NET MAUI es la mejor herramienta para el desarrollo móvil multiplataforma? appeared first on Luis Matos.

View Details

The Syncfusion .NET MAUI Rating control is the first choice for developers who need to get or display a rating in their .NET MAUI application. It enables users to assign a rating value from a group of visual symbols, typically in the form of stars.

With this control, developers can create intuitive and user-friendly interfaces that allow users to provide quick feedback in the form of ratings, helping to improve the overall user experience. For instance, it can be utilized to rate the quality of movies, software apps, or services a business provides.

This control also offers a customizable shape feature that allows you to use custom shapes that align with your brand or your needs. In this blog, we’ll see how to apply a custom shape to the Rating control. The control offers 100 custom shapes that can be readily applied.

Predefined shapes of .NET MAUI Rating control

There are four predefined shapes available in the .NET MAUI Rating control:

• Star (default)
• Heart
• Circle
• Diamond

The star is the default shape, but the other shapes can be chosen to provide a more unique rating UI control.

Custom shapes of .NET MAUI Rating control

The custom shapes feature allows developers to apply their desired shape as the rating UI. To use this feature, set the RatingShape property to Custom and assign the custom path to the Path property of the .NET MAUI Rating control.

Refer to the following code example for the custom shape Bell.

<rating:SfRating x:Name="rating" RatingShape="Custom" Path="M17.5 35.5C19.9063 35.5 21.875 33.8846 21.875 31.9103H13.125C13.125 33.8846 15.0719 35.5 17.5 35.5ZM30.625 24.7308V15.7564C30.625 10.2462 27.0375 5.63334 20.7812 4.41282V3.19231C20.7812 1.70256 19.3156 0.5 17.5 0.5C15.6844 0.5 14.2188 1.70256 14.2188 3.19231V4.41282C7.94063 5.63334 4.375 10.2282 4.375 15.7564V24.7308L0 28.3205V30.1154H35V28.3205L30.625 24.7308Z"/>

Refer to the following output image.

100 custom shape paths for .NET MAUI Rating control

Refer to the following code for the 100 custom shape paths. Use them to integrate more interesting shapes into the .NET MAUI Rating control.

1. Bell

<rating:SfRating Path="M17.5 35.5C19.9063 35.5 21.875 33.8846 21.875 31.9103H13.125C13.125 33.8846 15.0719 35.5 17.5 35.5ZM30.625 24.7308V15.7564C30.625 10.2462 27.0375 5.63334 20.7812 4.41282V3.19231C20.7812 1.70256 19.3156 0.5 17.5 0.5C15.6844 0.5 14.2188 1.70256 14.2188 3.19231V4.41282C7.94063 5.63334 4.375 10.2282 4.375 15.7564V24.7308L0 28.3205V30.1154H35V28.3205L30.625 24.7308Z"/>

2. Flag

<rating:SfRating Path="M13.600255,0C13.900248,1.2000122 16.30025,4.6000366 19.20032,6.7000122 22.300347,9 27.20045,10.600037 27.100473,16.200012 27.000434,25.600037 18.100328,27.600037 14.300218,21L14.20024,20.900024 14.300218,21.300049C15.90028,30.200012,23.600417,32,23.600417,32L3.6000639,32C11.200193,30,12.800224,24.200012,13.000209,20.800049L13.000209,20.600037C9.1001521,27.900024 0.10000761,25.600037 0,16 -1.0474832E-07,10.5 4.7000877,8.8000488 7.9001514,6.5 11.100185,4.5 13.300202,1.2000122 13.600255,0z"/>

3. Spade

<rating:SfRating Path="M13.600255,0C13.900248,1.2000122 16.30025,4.6000366 19.20032,6.7000122 22.300347,9 27.20045,10.600037 27.100473,16.200012 27.000434,25.600037 18.100328,27.600037 14.300218,21L14.20024,20.900024 14.300218,21.300049C15.90028,30.200012,23.600417,32,23.600417,32L3.6000639,32C11.200193,30,12.800224,24.200012,13.000209,20.800049L13.000209,20.600037C9.1001521,27.900024 0.10000761,25.600037 0,16 -1.0474832E-07,10.5 4.7000877,8.8000488 7.9001514,6.5 11.100185,4.5 13.300202,1.2000122 13.600255,0z"/>

4. Clover

 <rating:SfRating Path="M16.499985,0C19.999982,0 22.799979,2.7999992 22.799979,6.1999998 22.799979,9.0999994 20.799981,11.5 18.099983,12.2L18.099983,15.6 20.199982,15.6C21.29998,13.7 23.299978,12.4 25.699976,12.4 29.199973,12.4 31.99997,15.2 31.99997,18.6 31.99997,22 29.199973,24.8 25.699976,24.8 23.099979,24.8 20.899981,23.3 19.899982,21.1L18.099983,21.1 18.099983,27 21.299981,30.3C21.39998,30.400001 21.49998,30.6 21.39998,30.8 21.19998,31.000001 21.099981,31.1 20.999981,31.1L11.39999,31.1C11.19999,31.1 11.09999,31.000001 10.99999,30.8 10.89999,30.6 10.99999,30.500001 11.09999,30.3L14.299987,27 14.299987,21.1 12.099989,21.1C11.09999,23.3 8.899992,24.8 6.2999954,24.8 2.7999973,24.8 0,22 0,18.6 0,15.2 2.7999973,12.4 6.2999954,12.4 8.6999922,12.4 10.69999,13.7 11.79999,15.6L14.299987,15.6 14.299987,12C11.899989,11.099999 10.099991,8.8999996 10.099991,6.1999998 10.099991,2.7999992 12.999989,0 16.499985,0z"/>

5. Box

<rating:SfRating Path="M32,7.199995L32,22.6 17.699982,28.900001 17.699982,13.499996z M0,6.9000072L14.299988,13.199993 14.299988,28.599998 0,22.299997z M15.799988,0L28.600006,5.4000077 16.100006,10.8 2.7999878,5.1000046z"/>

6. Cloud

<rating:SfRating Path="M16.057999,0C19.938004,1.2542023E-07 23.380997,2.294006 24.832001,5.7030019 25.012009,6.126006 25.421005,6.4270009 25.900009,6.5299977 29.384003,7.2799977 32,10.303007 32,13.912992 32,18.084988 28.512009,21.479 24.220001,21.479L5.697998,21.479C2.5550003,21.479 0,18.989986 0,15.936002 0,12.877989 2.5550003,10.39401 5.697998,10.39401 5.7389984,10.39401 5.7789993,10.39401 5.8199997,10.394987 6.2430038,10.406004 6.598999,10.093992 6.5740051,9.7049845 6.5650024,9.5490092 6.5600052,9.3930043 6.5600052,9.2369984 6.5600052,4.1430048 10.820999,1.2542023E-07 16.057999,0z"/>

7. Shield

<rating:SfRating Path="M12.678023,5.8000488C12.678023,5.8000488 17.477961,8.7000122 20.577904,8.2000122 20.577904,8.2000122 22.67792,22.600037 12.678023,26.600037 2.6781254,22.600037 4.7780793,8.2000122 4.7780793,8.2000122 7.878023,8.8000488 12.678023,5.8000488 12.678023,5.8000488z M12.678023,2.1000366C12.678023,2.1000366 6.1780894,6 2.0780948,5.3000488 2.0780948,5.3000488 -0.82183857,24.600037 12.678023,30 26.177883,24.700012 23.277888,5.4000244 23.277888,5.4000244 19.177956,6.1000366 12.678023,2.1000366 12.678023,2.1000366z M12.678023,0L13.577977,0.60003662C14.977987,1.4000244 19.27793,3.6000366 22.177923,3.6000366 22.477909,3.6000366 22.67792,3.6000366 22.977904,3.5L24.777872,3.2000122 25.077858,5C25.177893,5.8000488,27.977852,25.800049,13.377966,31.600037L12.678023,32 11.978017,31.700012C-2.6218688,25.900024,0.17815109,5.9000244,0.27812545,5.1000366L0.57811038,3.3000488 2.3780797,3.6000366C2.5780898,3.6000366 2.8780745,3.7000122 3.1781204,3.7000122 6.0780538,3.7000122 10.377997,1.5 11.778007,0.70001221z"/>

8. Check mark

<rating:SfRating Path="M28.805753,0L31.974733,0C32.167724,0.27001924 31.208732,0.60900805 30.678737,0.9630113 22.839801,6.2050091 16.330854,13.03398 10.513902,19.745 6.9349381,16.519997 3.7629682,13.021987 0,9.9210077 0.63698797,9.253986 1.4519834,8.7079969 2.4479772,8.2830092 4.1869603,9.2220036 5.6669437,10.081988 7.7689305,11.090989 8.0639258,11.23201 10.055913,12.143997 10.22591,12.136001 10.603912,12.115982 11.617896,10.918992 12.2419,10.401994 16.76185,6.6610023 23.254806,2.4390226 28.805753,0z"/>

9. Close

<rating:SfRating Path="M2.999979,0C3.8000264,0,4.4999763,0.30000305,5.1000115,0.90000927L15.999954,11.700012 26.899959,0.90000927C28.099967,-0.29998779 29.999927,-0.29998779 31.099961,0.90000927 32.299972,2.1000061 32.299972,4 31.099961,5.1000061L20.199958,16 31.099961,26.900009C32.299972,28.100006 32.299972,30 31.099961,31.100006 29.899951,32.300003 27.999931,32.300003 26.899959,31.100006L15.999954,20.200012 5.1000115,31.100006C3.9000017,32.300003 1.9999809,32.300003 0.90000743,31.100006 -0.30000248,29.900009 -0.30000248,28 0.90000743,26.900009L11.800011,16 0.90000743,5.1000061C-0.30000248,3.9000092 -0.30000248,2 0.90000743,0.90000927 1.4999818,0.30000305 2.1999928,0 2.999979,0z"/>

10. Soccer ball

<rating:SfRating Path="M15.9,27.2L12.8,28.4 12.4,30.4C14.8,31,17.4,31,19.7,30.4L19.6,28.3z M22.5,18.6L16.4,22.9 16.4,26.2 20.1,27.3 25.599999,23.4 25.4,19.6z M9.6999998,18.5L6.3999996,19.6 6.5,23.599999 12.2,27.5 15.3,26.3 15.3,22.9z M3,16.7L1.1999998,16.9C1.3999996,19.6,2.1999998,22.1,3.6999998,24.3L5.3999996,23.5 5.3000002,19.4z M29,16.1L26.5,19.4 26.7,23.3 28.4,24.4C30,22.1,30.9,19.4,31,16.6z M9.3999996,8.2999997L5.7999997,9.4000001 3.8000002,16 6,18.6 9.3999996,17.4 11.8,10.6z M22.3,7.7999997L20.4,10.5 22.9,17.5 25.7,18.5 28.099999,15.3 25.9,8.6999998z M19.4,4.3000002L12.5,4.3999996 10.3,7.6999998 12.6,10 19.6,10 21.5,7.2999997z M10.7,2.0999994C8.1999998,3.0999994,6,4.6999998,4.3000002,6.9000001L5.5999994,8.4000001 9.1999998,7.2999997 11.4,4z M21.2,2L20.2,3.5999994 22.4,6.6999998 26,7.6999998 27.5,6.5C25.8,4.5,23.7,3,21.2,2z M16,0C24.8,0 32,7.1999998 32,16 32,24.8 24.8,32 16,32 7.1999998,32 0,24.8 0,16 0,7.1999998 7.1999998,0 16,0z"/>

11. USD

<rating:SfRating Path="M12.61799,18.807996L12.61799,24.108986C14.800975,23.853981 15.893993,23.018991 15.893993,21.60798 15.893993,20.462993 14.800975,19.533001 12.61799,18.807996z M9.2749698,7.3460013C7.1519825,7.6410143 6.0919845,8.486015 6.0919845,9.8870141 6.0919845,11.086995 7.1519825,12.086994 9.2749698,12.892016z M9.2749698,0L12.61799,0 12.61799,3.1800203C15.839,3.3010222,18.245009,3.6960108,19.831984,4.3709981L19.831984,9.0959994C17.695019,8.1060101,15.291027,7.4959952,12.61799,7.275994L12.61799,13.906999C15.961986,14.831986 18.359023,15.882003 19.808974,17.068008 21.258988,18.253004 21.985001,19.682995 21.985001,21.362985 21.985001,23.29899 21.177018,24.859016 19.558974,26.044012 17.938977,27.229009 15.627025,27.948978 12.61799,28.203983L12.61799,32 9.2749698,32 9.2749698,28.308963C6.1749923,28.299015,3.291018,27.763981,0.61798145,26.69898L0.61798145,21.853006C1.5039684,22.402994 2.8250143,22.909006 4.5799596,23.379005 6.336003,23.844001 7.9010069,24.108986 9.2749698,24.178993L9.2749698,17.813001C5.7019693,16.797989 3.2639794,15.697007 1.9580092,14.51201 0.65197809,13.327014 7.8710173E-08,11.887012 0,10.181997 7.8710173E-08,8.3510053 0.84698553,6.7910091 2.541994,5.501002 4.2370026,4.2110249 6.4809615,3.4610257 9.2749698,3.2510037z"/>

12. Euro

<rating:SfRating Path="M22.92401,0C26.382994,0,29.291014,0.56800086,31.650999,1.709999L30.535002,5.6339994C28.269011,4.2140012 25.693999,3.5029987 22.81201,3.5029989 19.690001,3.5029987 17.067015,4.0740019 14.949004,5.2130018 13.68399,5.8899999 12.537994,6.843999 11.519988,8.0830007 10.475005,9.3639999 9.863006,10.583002 9.6749872,11.735002L28.699004,11.735002 27.943999,14.564001 9.2300103,14.564001C9.2109979,14.859003 9.2040094,15.141 9.2040094,15.408002 9.2040094,16.491003 9.2109979,17.138002 9.2300103,17.352003L27.187987,17.352003 26.408995,20.179002 9.817016,20.179002C10.597991,23.402004 12.475005,25.689003 15.450012,27.040004 17.588011,28.010002 19.902006,28.497005 22.390013,28.497005 25.869994,28.497005 28.587004,27.806003 30.535002,26.427002L30.535002,30.775001C28.213011,31.592002 25.647002,32 22.837004,32 14.434997,32 8.7569879,29.355003 5.8020018,24.063003 5.2070006,22.994003 4.692993,21.701004 4.2669981,20.179002L0,20.179002 0.77999879,17.352003 3.7120055,17.352003C3.6520081,16.761003 3.623993,16.12 3.6239928,15.429002 3.623993,15.148 3.6329957,14.859003 3.6520079,14.564001L0,14.564001 0.77999879,11.735002 4.0150145,11.735002C5.1679991,7.1479998 8.1719964,3.8550001 13.022003,1.8569984 16.016997,0.61899955 19.317015,0 22.92401,0z"/>

13. Yen

<rating:SfRating Path="M0,0L6.1860043,0 13.027984,10.141998C14.082,11.81601,14.871978,13.14502,15.660979,14.622009L15.858977,14.622009C16.515989,13.243011,17.371977,11.71701,18.489988,10.042999L25.596983,0 31.650999,0 19.871977,14.917023 28.427,14.917023 28.427,17.32901 18.161986,17.32901 18.161986,20.923004 28.427,20.923004 28.427,23.335999 18.161986,23.335999 18.161986,32 12.699981,32 12.699981,23.335999 2.4999994,23.335999 2.4999994,20.923004 12.699981,20.923004 12.699981,17.32901 2.4999994,17.32901 2.4999994,14.917023 11.121001,14.917023z"/>

14. Indian rupee

<rating:SfRating Path="M0.18400574,0L22.001011,0C22.125004,0.014984131,22.185001,0.074981689,22.185001,0.17498779L22.185001,2.1300049C22.185001,2.2449951,22.125004,2.2999878,22.001011,2.2999878L13.791002,2.2999878 13.791002,2.4750061C14.960008,3.0700073,15.867998,4.2850037,16.51201,6.1199951L16.604997,6.75 22.001011,6.75C22.125004,6.7649841,22.185001,6.8200073,22.185001,6.9199829L22.185001,8.875C22.185001,8.9899902,22.125004,9.0499878,22.001011,9.0499878L16.811998,9.0499878C16.811998,11.234985 15.390001,13.359985 12.546999,15.424988 10.024004,16.785004 8.2330025,17.464996 7.1719979,17.464996 7.1719979,17.524994 7.1110085,17.554993 6.9889992,17.554993L18.703005,31.829987 18.703005,32 14.253008,32C14.207002,32,9.6780108,26.475006,0.66999815,15.424988L0.66999815,15.339996 2.0760046,15.339996C7.0570076,15.339996 10.046999,13.654999 11.046999,10.285004 11.108003,9.8800049 11.139009,9.5549927 11.139009,9.3099976L11.139009,9.0499878 0.18400574,9.0499878C0.061996609,9.0499878,1.41692E-07,8.9899902,0,8.875L0,6.9199829C0.014999533,6.8049927,0.076995998,6.75,0.18400574,6.75L11.046999,6.75C10.678011,5.4349976 9.8930071,4.3649902 8.6940011,3.539978 7.0339974,2.7149963 5.5209969,2.2999878 4.1510018,2.2999878L0.18400574,2.2999878C0.061996609,2.2999878,1.41692E-07,2.2449951,0,2.1300049L0,0.17498779C0.014999533,0.059997559,0.076995998,0,0.18400574,0z"/>

15. Apple

<rating:SfRating Path="M18.981716,6.9006311C21.064487,6.9021536 26.552768,7.7438399 27.163088,14.461067 27.919075,22.765093 23.76407,27.995129 23.76407,27.995129 23.76407,27.995129 19.962034,33.684151 14.43397,31.501158 14.161996,31.395138 13.889959,31.275143 13.608951,31.126156 13.21698,31.274136 12.846982,31.39114 12.479974,31.486143 6.4149177,33.052158 3.5708988,27.995129 3.5708988,27.995129 3.5708988,27.995129 -0.51214518,22.765093 0.053838927,14.461067 0.5118507,7.7310244 5.9769256,6.901034 8.2139451,6.901034 8.3629329,6.901034 8.4979436,6.9040247 8.6159265,6.9100367 9.9569414,6.9780303 11.006939,7.4240466 12.339958,7.8140327L12.339958,11.091056C11.673937,10.891043 11.268965,10.607045 10.886943,10.224048 10.733926,10.071032 10.34696,10.083056 10.193943,10.237048 10.040927,10.391041 10.040927,10.662038 10.193943,10.817038 10.764931,11.388055 11.454941,11.846065 12.207938,12.070065 12.275931,12.128049 12.361931,12.262052 12.458977,12.262052L12.578974,12.262052C12.908932,12.262052 13.247986,12.371061 13.59296,12.371061 13.938971,12.371061 14.277963,12.262052 14.606946,12.262052L14.727979,12.262052C14.823989,12.262052 14.903946,12.128049 14.970962,12.070065 15.72396,11.846065 16.407011,11.339044 16.978975,10.768057 17.131016,10.613057 17.116977,10.366047 16.964998,10.212054 16.809969,10.058062 16.533964,10.058062 16.379972,10.212054 15.996973,10.595052 15.673972,10.891043 15.006974,11.090049L15.006974,7.5920469C16.339994,7.2850386 17.147007,6.9920379 18.613024,6.9100367 18.719148,6.9041621 18.842865,6.9005295 18.981716,6.9006311z M21.498058,1.9750153C23.040064,1.9830111,24.443031,2.4320184,25.191084,2.7219981L14.789992,6.8820216C15.31197,5.7750212 16.678985,3.3530129 19.035024,2.410015 19.843992,2.0870155 20.690008,1.9700106 21.498058,1.9750153z M14.339976,0L14.339976,11.595057 13.006956,11.595057 13.006956,0.42599709 13.006956,0.26199473 14.203988,0.26199473C14.248972,0.26199467,14.339976,0.0069885586,14.339976,0z M13.006956,0L13.006956,0.26199473 12.981931,0.26199473C12.936949,0.26199467,13.006956,0.0069885586,13.006956,0z"/>

16. Man

<rating:SfRating Path="M14.345001,0C14.345001,0.099975586 14.746002,0 15.348,0 16.451004,0 18.156998,0.20098877 18.959,1.4039917 18.959,1.4039917 26.181999,2.2070007 21.969002,9.8309937 21.969002,9.8309937 22.972,9.9309998 22.570999,11.033997 22.570999,11.033997 22.168999,13.140991 21.567001,13.441986 21.567001,13.441986 21.567001,16.450989 19.560997,18.759003L19.560997,18.858978C20.063004,21.968994 25.278999,23.171997 25.278999,23.171997 28.790001,24.074982 32,25.980988 32,25.980988L32,29.391998 0,29.391998 0,25.078003C0.099998474,24.677002 5.4169998,22.971985 5.4169998,22.971985 8.125,22.269989 9.2290039,21.667999 9.2290039,21.667999 9.2290039,21.46698 9.7300034,21.165985 9.7300034,21.165985 10.933998,20.965973 11.536003,19.460999 11.737,18.65799 11.536003,18.457977 10.132004,16.651978 10.030998,13.240997 10.030998,13.240997 9.5299988,13.040985 9.0279999,10.432983 9.0279999,10.432983 8.9280014,9.6299744 9.8310013,9.5299988 9.8310013,9.5299988 8.6269989,5.617981 9.5299988,3.2099915 9.5299988,3.2099915 10.933998,0.60198975 14.345001,0z"/>

17. Woman

<rating:SfRating Path="M14.2,0C15.3,0 16.1,0.19999981 16.1,0.19999981 21.9,-0.40000057 22.9,9.7999998 22.9,9.7999997 22.9,10.5 25,17 25,17 25.8,18.5 23.5,18.7 23.5,18.7 24.3,19.9 21.2,20.599999 20.2,20.8L20.1,20.8C21.099999,24 27.7,25.7 27.7,25.7 30.299999,26.3 32,28.7 32,28.7L32,30.999999 0,30.999999 0,27.499999C1.3000002,25.999999 3.1999998,25.7 3.1999998,25.7 9,24.2 10.5,21.8 10.9,20.8 9.9999998,20.8 8.6999998,20.3 8.6999998,20.3 6.6999998,19.4 7,18.599999 7,18.599999 7.2999997,18.5 7.3999996,18.2 7.3999996,18.2 6.6999998,18.3 6.1999998,18.099999 6.1999998,18.099999 4.8999996,17.7 5.6999998,16.4 5.6999998,16.4 7.5999999,11.7 7.7999997,8.7999998 7.7999997,8.7999997 7.8999996,6.2999997 8.2999997,4.5999999 8.2999997,4.5999999 9.5999999,0.80000019 12.4,0 14.2,0z"/>

18. Airplane

<rating:SfRating Path="M30.299999,0L29.700008,2.7000046C29.700008,2.8000031,29.700008,2.9000015,29.600002,3.0999985L29.600002,3.2000046C29.500012,3.4000015,29.299999,3.7000046,29.000012,4L21.700007,11.800003 25.900005,29 23.1,32 16.1,17.599998 10.6,23.5 11.1,28 9.0000011,30.300003 6.5000006,25.099998 1.7000046,22.400002 3.9000021,20.099998 8.2000056,20.700005 13.700006,14.800003 0,7.2000046 2.7000047,4.3000031 19.1,8.9000015 26.299999,1.2000046C26.600002,0.90000153,26.900005,0.70000458,27.200008,0.59999847L27.299999,0.59999847 27.600002,0.59999847z"/>

19. Leaf

<rating:SfRating Path="M3.0263408,0C7.2224015,5.0950343 18.711398,2.8970153 25.605466,11.989112 31.699485,20.081168 22.508409,25.176217 20.010414,24.877234 28.003425,29.672261 30.101455,28.673259 31.20046,28.973281 32.598476,29.372271 32.099449,31.271275 30.200456,31.071292 27.403447,30.571288 21.109416,26.975245 19.411413,25.776229 17.812408,24.67722 10.119385,19.382186 5.6243728,9.7910926 8.9204057,20.68118 16.314416,26.275225 17.413419,27.174252 16.713405,28.074254 15.314412,29.372271 12.01838,29.872275 5.1243709,30.871278 -5.1656462,22.879199 3.0263408,0z"/>

20. Flower

<rating:SfRating Path="M11.664001,10.46701C11.863007,10.966003 12.063019,11.463989 12.162018,11.963013 10.867004,13.058989 10.069,14.753997 10.069,16.548004 10.069,17.046997 10.169006,17.445007 10.268005,17.843994 9.8699951,18.143005 9.4710083,18.441986 8.9720154,18.740997 9.3710022,18.641998 9.6700134,18.641998 10.069,18.641998L10.567017,18.641998C11.365021,20.834989 13.359009,22.429991 15.851013,22.529997 16.000504,22.878492 16.10025,23.252241 16.162624,23.638491L16.189045,23.831411 16.259726,23.550848C16.338678,23.266422 16.436882,22.990751 16.549011,22.729002 18.84201,22.529997 20.736023,21.033995 21.53302,18.841003 21.733002,18.841003 22.032013,18.740997 22.231018,18.740997 22.529999,18.740997 22.729004,18.740997 23.029022,18.841003 22.630005,18.641998 22.131012,18.342987 21.832001,17.944 21.932007,17.545013 22.032013,17.046997 22.032013,16.64801 22.032013,14.753997 21.234009,13.158996 19.838013,12.062012 19.938019,11.664001 20.037994,11.36499 20.138,10.966003 19.838013,11.165008 19.539001,11.463989 19.240021,11.563995 18.343018,10.966003 17.147003,10.566986 15.951019,10.566986 14.753998,10.566986 13.757019,10.865997 12.860016,11.463989 12.462006,11.165008 12.063019,10.865997 11.664001,10.46701z M16.149994,0C19.539001,1.2808141E-07 22.330994,2.790985 22.330994,6.2799987 22.330994,7.0780028 22.131012,7.8749999 21.832001,8.5729979 22.929016,7.5759886 24.324005,6.9779967 25.820007,6.9779967 29.209015,6.9779967 32,9.7690123 32,13.259002 32,16.747986 29.209015,19.539001 25.820007,19.539001 25.520996,19.539001 25.321014,19.539001 25.022003,19.438995 27.016022,20.436003 28.412018,22.529997 28.412018,25.022001 28.412018,28.510984 25.619995,31.302 22.231018,31.302 19.265636,31.302 16.757345,29.165129 16.176605,26.293566L16.132391,26.043009 16.123413,26.093893C15.542673,28.966146 13.034382,31.102995 10.069,31.102995 6.6800232,31.102995 3.8880005,28.31201 3.8880005,24.821989 3.8880005,22.329985 5.2839966,20.236999 7.2780151,19.23999 6.9790039,19.339996 6.5800171,19.339996 6.1809998,19.339996 2.7920227,19.339996 0,16.548004 0,13.058989 0,9.5700072 2.7920227,6.7789916 6.1809998,6.7789916 7.9760132,6.7789916 9.4710083,7.5759886 10.667023,8.7730101 10.268005,8.1740111 10.069,7.2770079 10.069,6.2799987 10.069,2.790985 12.761017,1.2808141E-07 16.149994,0z"/>

21. Tree

<rating:SfRating Path="M14.700006,14.2L16.900006,16.9 15.900006,23.400001 18.700007,20 20.100008,21.2C20.100008,21.2,15.200006,27.300001,17.500007,28.900001L22.600008,30.400001 22.600008,32 7.3000021,32C7.3000021,32 9.2000031,29.900001 12.200005,29.1 12.300004,29.1 13.200005,16.6 14.700006,14.2z M14.300005,0C18.300007,0,21.600008,2.1000004,22.800009,5.1000003L22.800009,5.2000002 23.000009,5.2000002 23.200009,5.2000002C27.40001,5.2000002 30.800012,8.6000003 30.800012,12.8 30.800012,15.9 29.000011,18.6 26.30001,19.800001L26.20001,19.800001 26.30001,20C26.40001,20.4 26.40001,20.800001 26.40001,21.2 26.40001,23.800001 24.300009,25.900001 21.700008,25.900001 20.700008,25.900001 19.800007,25.6 19.000007,25L19.100007,24.900001C20.100008,23.1,21.300008,21,21.300008,21L18.700007,18.5 17.900007,19.6 18.100007,16.5 14.300005,11.5 14.000005,12.1C14.100005,13.3,12.200005,20.7,12.200005,20.7L10.700004,18.6 10.100004,19.800001 11.100004,21.9 11.100004,25C10.500004,25.2 9.9000034,25.400001 9.2000031,25.400001 6.5000019,25.400001 4.4000015,23.2 4.4000015,20.6L4.4000015,20.1 4.3000011,20.1C1.9000006,19.6 0,17.2 0,14.2 0,11 2.3000002,8.4000002 5.1000013,8.4000005L5.4000015,8.4000005 5.5000019,8.4000005C5.5000019,8.0000002 5.4000015,7.6000002 5.4000015,7.2000002 5.4000015,3.2000003 9.4000034,0 14.300005,0z"/>

22. Lion

<rating:SfRating Path="M23.277061,17.54599L23.878068,18.048004 25.081056,21.256012 26.686019,21.757996 27.187051,23.462006 24.179029,23.462006 23.678058,21.757996C23.477071,21.355988,22.274081,21.256012,22.274081,21.256012L21.97306,20.45401z M6.0312867,15.23999C6.0312867,15.742005,7.3342505,18.549011,7.3342505,18.549011L6.2322731,21.656983 8.2372551,21.958008 8.738226,23.763001 4.6272502,23.763001C4.3272658,23.260987,4.1262794,19.85199,4.1262794,19.85199z M6.6332698,7.9209902L5.9312511,8.9240114C4.9282723,9.023987 3.0233257,10.026001 3.0233257,10.026001 1.3193046,11.028992 0.71732172,14.238007 0.61734738,14.639008L0.71732148,14.639008C1.3193046,15.040009 1.5193144,16.243012 1.5193144,16.243012 1.5193144,17.647003 0.91830816,18.449005 0.91830828,18.449005 0.71732172,18.347992 0.21635088,17.346008 0.21635092,17.346008 -0.28565753,15.842011 0.21635088,14.938996 0.4162996,14.639008L0.4162996,14.537995C0.41629975,13.635987 1.1183181,11.730988 1.118318,11.730988 2.3213072,8.3219912 6.6332698,7.9209902 6.6332698,7.9209902z M28.790975,4.9129946C28.691001,5.2139894 29.091996,5.6149904 29.091996,5.6149904 29.39302,5.8150026 29.492993,5.5149843 29.492993,5.5149843 29.492993,5.2139894 28.790975,4.9129946 28.790975,4.9129946z M25.783013,2.3059999C25.382018,2.3059999 25.081056,2.7070009 25.081056,2.7070007 24.781072,3.5090029 25.282043,4.0109865 25.282043,4.0109865 25.282043,3.8099977 25.382018,3.208008 25.382018,3.208008 25.68304,2.2059938 26.786054,3.0079958 26.786054,3.007996L26.285022,2.5069887C26.184011,2.4060061,25.984061,2.3059999,25.783013,2.3059999z M24.179029,0L27.087014,0.40100126 29.091996,0.20098914 30.394961,2.105988C30.195012,2.0050051 28.490014,2.3059999 28.490014,2.3059999 28.891011,2.6069948 30.294986,2.7070009 30.294986,2.7070007L29.292983,3.6099855C29.993964,4.0109865 30.495973,5.2139894 30.495973,5.2139894 30.195012,6.6170046 31.999984,7.2189943 31.999984,7.2189943 31.096978,9.1239931 30.094975,9.3250124 30.094975,9.3250124 27.989043,10.126984 25.482053,7.3190004 25.482053,7.3190004 25.382018,8.5230104 28.490014,9.7259829 28.490014,9.7259829 28.290004,10.727997 25.182069,16.041992 25.182069,16.041992 25.282043,15.842011 24.981021,14.337982 24.981021,14.337982 24.781072,14.537995 24.580024,16.544007 24.580024,16.544007 24.079053,16.845001 23.778031,15.23999 23.778031,15.23999L23.377036,16.143006C22.9761,15.742005 21.372115,9.9259951 21.372115,9.9259951 21.271102,14.238007 23.176049,16.845001 23.176049,16.845001L23.076074,16.845001 23.076074,17.144989 21.372115,21.656983C21.372115,21.656983,23.277061,21.858002,23.377036,21.958008L23.978042,23.662995 19.667117,23.662995 19.166085,19.953003 19.767091,17.144989C19.767091,17.144989 19.366096,16.342987 18.163106,16.342987 18.163106,16.342987 13.150163,15.941986 11.646213,15.341004 11.646213,15.341004 14.153142,11.631012 13.651195,10.126984 13.651195,10.126984 11.646213,15.139984 9.7412052,17.144989L11.145181,21.457001 12.949177,21.958008 13.451184,23.662995 9.0392475,23.662995C9.0392475,23.662995 6.4322829,15.23999 6.3322478,14.537995 6.3322478,14.537995 5.3292685,9.023987 7.1342406,7.8209841 7.1342406,7.8209841 10.342212,6.7179873 17.762109,7.5199892L18.163106,7.5199892C18.664138,7.7200014,19.366096,6.0159914,19.366096,6.0159914L20.269099,2.9079895 21.171067,2.3059999z"/>

23. Elephant

<rating:SfRating Path="M7.5990569,21.292C7.5990569,21.292,9.0990689,21.592003,9.4990351,21.592003L10.198076,25.29101 6.3990357,25.991007C6.3990357,25.891,6.3990357,21.992012,7.5990569,21.292z M24.397159,11.696004C24.197145,11.696004,23.897155,11.795994,23.497127,12.095998L23.397151,12.095998C23.697141,12.396001,24.197145,13.095006,25.197152,13.495L25.297191,13.495C25.197152,12.895009 24.997138,12.295994 24.697149,11.696004 24.697149,11.795994 24.597173,11.696004 24.397159,11.696004z M22.097154,3.6990065C21.59715,3.6990065 21.29716,4.0990006 21.29716,4.4980027 21.29716,4.8979966 21.697126,5.2980063 22.097154,5.2980063 22.597158,5.2980063 22.897147,4.8979966 22.897147,4.4980027 22.897147,4.0990006 22.597158,3.6990065 22.097154,3.6990065z M14.398059,0L14.69811,0C15.398067,4.938272E-08 17.698133,0.099990928 19.497096,1.0999913 20.397128,0.5999911 23.197137,-0.40000926 25.697156,2.3990032 25.697156,2.399003 28.396213,5.097994 28.596166,11.996007L28.596166,14.095007C29.09617,14.095007 29.596174,13.995001 30.196214,13.89501 30.196214,13.89501 32.096193,13.194997 31.996215,13.89501 31.996215,13.89501 30.396228,15.594 28.696202,15.894003L28.596166,15.894003 28.596166,24.891C28.596166,24.891 29.39622,26.391 28.896217,26.590006 28.896217,26.590006 27.396205,27.390009 26.297199,26.989999 26.297199,26.989999 25.297191,26.790003 25.497142,25.691004 25.497142,25.691004 25.697156,18.094001 25.497142,15.894003 24.397159,15.694006 23.097162,15.295004 21.997115,14.39501L21.997115,14.595007C21.497112,16.594 20.897132,20.193001 20.697118,26.790003 20.697118,26.790003 15.798094,27.390009 15.798094,26.590006L15.798094,19.59301C15.798094,19.59301 11.398036,21.092003 8.0990612,20.09301 8.0990612,20.09301 6.5990493,19.793007 5.5990417,21.592003 5.5990417,21.592003 4.5990341,23.292001 4.5990341,26.690012 4.5990341,26.690012 0.09997635,26.989999 0,26.690012 0,26.690012 0,20.59301 2.1989913,17.994011 2.1989913,17.994011 1.8000015,16.694006 1.8000012,16.293997 1.8000015,16.293997 1.0000076,18.392997 0.099976149,16.793997 0.09997635,16.793997 1.3999741,11.196004 6.5990493,8.2969996 6.5990493,8.2969996 10.99807,6.4980037 13.598066,6.5979945 13.598066,6.5979945 10.498066,1.1999974 14.398059,0z"/>

24. Monkey

<rating:SfRating Path="M19.175898,17.899994C19.075894,17.899994,18.975898,18,18.875901,18.100006L18.875901,18.200012C18.575902,19.100006 15.475953,27.600006 15.175962,29.399994 14.975961,30.299988 14.775966,31.200012 14.375972,31.600006L15.175962,31.600006C15.475953,31.100006 15.675954,30.399994 15.775951,29.5 16.075942,27.700012 19.47589,18.399994 19.47589,18.299988 19.575887,18.100006 19.47589,18 19.275895,17.899994z M5.6761135,17.700012C5.4761117,17.799988 5.4761117,17.899994 5.4761117,18.100006 5.4761117,18.200012 8.4760645,27.5 8.7760628,29.399994 8.8760594,30.299988 9.0760535,31 9.3760518,31.5L10.076037,31.5C9.67605,31.100006 9.4760483,30.200012 9.3760518,29.299988 9.0760535,27.5 6.376099,18.899994 6.0761007,18L6.0761007,17.899994C6.0761007,17.799988,5.9761041,17.799988,5.77611,17.700012z M9.67605,17.399994C9.4760483,17.399994,9.3760518,17.600006,9.3760518,17.700012L11.876012,29.899994C11.876012,29.899994 12.17601,30.799988 11.876012,31.299988 11.876012,31.399994 11.776015,31.5 11.676018,31.5L12.975993,31.5C12.875995,31.399994 12.775999,31.299988 12.676002,31.200012 12.575997,31.100006 12.575997,31 12.575997,30.899994L12.575997,30.700012 12.575997,30.399994C12.575997,30.100006,12.676002,29.899994,12.676002,29.899994L15.375955,17.899994C15.375955,17.700012 15.275959,17.600006 15.175962,17.5 14.975961,17.5 14.875964,17.600006 14.775966,17.700012 14.775966,17.700012 12.875995,26.200012 12.276007,28.899994 11.676018,26.100006 9.9760407,17.700012 9.9760407,17.700012 9.8760432,17.5 9.7760466,17.399994 9.67605,17.399994z M17.575917,8.5C18.675906,9.2999878 21.175866,11.899994 20.475873,18.200012 20.475873,18.200012 21.875851,17.200012 23.575822,18 25.175803,18.799988 25.575791,21.299988 24.275815,23.700012L21.675858,29.899994C21.675858,29.899994 22.175851,30 22.675843,30.200012 23.275832,30.399994 23.875821,30.700012 23.875821,31.399994 23.875821,31.399994 23.875821,32 22.875836,32L21.475858,32 3.176153,32 2.1761688,32C1.1761849,32 1.1761849,31.399994 1.1761851,31.399994 1.0761804,30.799988 1.7761738,30.5 2.3761629,30.200012 2.8761547,30 3.3761469,29.899994 3.3761466,29.899994L0.77618971,23.700012C-0.5237926,21.299988 -0.12379746,18.700012 1.4761758,18 3.176153,17.200012 4.5761245,18.200012 4.5761245,18.200012 3.776142,12 6.1761053,9.3999939 7.2760862,8.6000061 7.9760722,10.299988 9.4760483,12.100006 12.476001,12.100006 15.57595,12 16.975928,10.100006 17.575917,8.5z M12.975993,8C13.175994,8 13.275991,8.1000061 13.275991,8.2999878 13.275991,8.5 13.175994,8.6000061 12.975993,8.6000061 12.775999,8.6000061 12.676002,8.5 12.676002,8.2999878 12.575997,8.1000061 12.775999,8 12.975993,8z M11.876012,8C12.076006,8 12.17601,8.1000061 12.17601,8.2999878 12.17601,8.5 12.076006,8.6000061 11.876012,8.6000061 11.676018,8.6000061 11.576013,8.5 11.576013,8.2999878 11.476017,8.1000061 11.676018,8 11.876012,8z M13.975977,4.5C14.275975,4.5 14.575966,4.7999878 14.575966,5.1000061 14.575966,5.3999939 14.275975,5.7000122 13.975977,5.7000122 13.675986,5.7000122 13.375988,5.3999939 13.375988,5.1000061 13.375988,4.7999878 13.675986,4.5 13.975977,4.5z M10.976024,4.5C11.276023,4.5 11.576013,4.7999878 11.576013,5.1000061 11.576013,5.3999939 11.276023,5.7000122 10.976024,5.7000122 10.676034,5.7000122 10.376036,5.3999939 10.376036,5.1000061 10.476032,4.7999878 10.676034,4.5 10.976024,4.5z M18.175914,4C18.975898,4.2000122 19.47589,5 19.47589,6 19.47589,7.1000061 18.775903,8 17.875916,8z M6.7760943,4L7.0760849,8C6.1761053,8 5.4761117,7.1000061 5.4761117,6 5.4761117,5 5.9761041,4.2000122 6.7760943,4z M12.476001,0C13.275991,0 15.675954,0 16.875932,2.3999939 17.975913,4.5 17.575917,6.6000061 17.275927,7.6000061 17.275927,7.6000061 16.475938,10.799988 13.775983,11.299988 14.175978,11.100006 14.275975,10.799988 14.375972,10.399994 14.575966,9.7000122 14.175978,9.1000061 14.375972,8.2000122 14.575966,7.3999939 14.775966,7.2999878 15.175962,6.8999939 15.475953,6.6000061 15.775951,6 15.775951,5.2000122 15.775951,2.8999939 13.175994,2.8999939 12.476001,2.8999939 11.776015,2.8999939 9.1760577,2.8999939 9.1760577,5.2000122 9.1760577,6 9.4760483,6.6000061 9.7760466,6.8999939 10.076037,7.2999878 10.376036,7.3999939 10.57603,8.2000122 10.77603,9 10.276039,9.6000061 10.57603,10.399994 10.676034,10.799988 10.876028,11.100006 11.176026,11.299988 9.3760518,10.799988 8.376067,9.5 7.8760751,8.2999878 7.8760751,8.2999878 6.476096,5.2000122 8.0760687,2.5 9.3760518,0.1000061 11.676018,0 12.476001,0z"/>

25. Horse

<rating:SfRating Path="M29.422973,0L28.325977,1.4950104 29.621952,8.1740112C29.721988,9.2709961,28.325977,9.3710022,28.325977,9.3710022L27.628948,9.1710205C27.129919,9.5700073,26.830967,7.9750061,26.830967,7.9750061L25.833946,6.1809998C25.734945,6.1809998 24.936903,5.9810181 24.936903,5.9810181 24.338936,7.4770203 24.936903,9.5700073 24.936903,9.5700073 25.933923,12.959991 25.335954,13.856995 25.335954,13.856995 27.927963,13.757019 29.621952,14.355011 29.621952,14.355011 30.818985,14.653992 30.818985,15.651001 30.818985,15.651001 30.917986,17.744995 30.419994,20.636017 30.419994,20.636017 30.021003,22.429993 28.126939,23.128021 28.126939,23.128021L27.727949,21.333008 28.525991,21.134003C28.525991,20.735016 28.924984,20.237 28.924984,20.237 29.223997,20.136993 29.322998,19.738007 29.322998,19.738007L28.924984,16.947021C28.824945,16.548004 28.525991,16.449005 28.525991,16.449005 28.126939,16.548004 26.730928,16.548004 26.730928,16.548004 25.036941,17.046997 23.540891,16.449005 23.540891,16.449005 23.341915,16.449005 23.0429,17.246002 23.0429,17.246002 22.244919,18.044006 21.148897,24.722992 21.148897,24.722992 20.948883,25.421021 21.447912,25.819 21.447912,25.819 21.846903,26.019012 23.0429,27.414001 23.0429,27.414001L20.948883,27.912994C20.64987,26.71701 20.151878,26.516998 20.151878,26.516998 19.453872,26.317993 19.752885,25.122009 19.752885,25.122009 19.952902,24.722992 20.051901,23.028015 20.051901,23.028015L19.952902,17.246002C17.360832,18.541992 12.973821,18.641998 12.973821,18.641998 13.073798,19.040009 12.874821,22.330017 12.874821,22.330017 12.674806,23.22702 13.173774,23.726013 13.272774,23.826019 13.372812,23.925018 18.357853,28.610992 18.357853,28.610992L15.964821,29.109009 15.565829,28.112C14.867823,28.112 14.568809,27.214996 14.568809,27.214996 13.173774,25.421021 10.581767,24.223999 10.581767,24.223999 9.9837376,24.223999 10.082738,22.928009 10.082738,22.928009 10.182775,20.536011 8.3887498,20.037018 8.3887498,20.037018 8.0897347,21.134003 6.2947327,23.22702 6.2947327,23.22702 5.4977271,24.223999 5.098736,25.321014 5.098736,25.321014 4.7997214,26.019012 4.6996833,29.209015 4.6996833,29.209015 4.6996833,29.807007 4.9986979,30.106018 4.9986979,30.106018 5.2977125,30.404999 6.1957323,31.502014 6.1957323,31.502014L4.2016923,32 4.0016781,31.003021C3.9026779,30.70401 3.7027246,30.70401 3.7027248,30.70401 3.0056955,30.304993 3.40371,29.308014 3.4037103,29.308014L3.5036868,25.720001C3.6037244,25.321014 3.3047098,24.324005 3.3047098,24.324005 3.0056955,23.826019 3.40371,23.22702 3.4037103,23.22702 4.4007303,22.231018 4.2016923,19.140015 4.2016923,19.140015 4.2016923,19.140015 3.9026779,17.046997 3.5036868,16.050018 3.2046723,15.35202 3.9026779,13.657013 4.4007303,12.76001L4.4007303,12.660004C2.5066666,13.657013 2.40669,15.35202 2.40669,15.35202 2.3076898,17.445007 3.3047098,21.234009 3.3047098,21.234009L0.51268754,21.931C-0.88234719,16.248993 1.0116552,14.056 1.0116551,14.056 2.40669,12.561005 3.8027012,12.360992 4.5007068,12.360992L4.5007068,12.261993C6.9927384,10.368011 9.9837376,10.167999 9.9837376,10.167999 14.668786,9.9689941 16.762863,9.0720215 16.762863,9.0720215 18.955881,8.3739929 20.251854,5.6820068 20.251854,5.6820068 20.749906,4.5859985 21.945903,2.9910126 21.945903,2.9910126 23.939943,0.39900208 26.830967,0.89700317 26.830967,0.89700317 27.428934,0.29901123 29.422973,0 29.422973,0z"/>

Refer to the following GIF image.

26. Thumbs up

<rating:SfRating Path="M19.399159,0.0002787064C22.20918,0.043278397 22.416182,2.2572923 22.593186,3.777288 22.356185,6.4943102 19.635154,9.1193216 19.635154,9.1193216L17.269137,12.113322C17.269137,12.113322 18.150141,12.074321 20.937167,12.195324 23.150182,12.291332 25.465203,11.97732 28.569232,12.712324 35.60928,15.475336 29.633237,17.410342 29.633237,17.410342 33.479275,19.574353 30.04724,21.877372 30.04724,21.877372 32.474263,25.285376 28.513232,25.994393 28.746236,26.022378 29.515238,26.11439 32.177262,28.279406 27.622218,30.167416 27.622218,30.167416 22.652177,31.872411 19.931161,31.872411 18.156153,32.101416 13.068099,32.148413 9.223067,30.904418 4.6670301,30.305417 3.786026,30.692412 0,31.245423L0.052994262,19.067363C0.052994061,19.067363 2.8330154,18.51435 5.3180363,15.935345 6.3240564,14.830344 7.2110569,12.804334 7.8620631,11.008322 8.4540632,9.9943255 8.2760675,9.533325 11.056089,8.6583212 12.831097,7.8763045 15.612126,6.2633064 16.85414,3.6842852 17.20914,2.5332945 16.707137,-0.030727048 19.399159,0.0002787064z"/>

27. Thumbs down

<rating:SfRating Path="M14.563856,7.4782818E-05C16.901871,-0.0049298852 20.132901,0.24006255 22.776919,1.096056 27.330958,1.6940566 28.21396,1.3080593 32.000003,0.75505637L31.946992,12.932931C31.946992,12.932931 29.166972,13.484928 26.680959,16.063895 25.677945,17.169884 24.789937,19.194872 24.136931,20.991848 23.544932,22.005816 23.722926,22.466839 20.943913,23.34183 19.168889,24.123803 16.386868,25.735785 15.144854,28.313759 14.788864,29.466763 15.292866,32.029723 12.600842,31.999724 9.7908218,31.956725 9.584812,29.74273 9.4048174,28.222758 9.6428106,25.505776 12.361842,22.880806 12.361842,22.880806L14.730864,19.886851C14.730864,19.886851 13.850853,19.925852 11.060821,19.80485 8.8498047,19.708844 6.5337918,20.021859 3.4307621,19.287857 -3.6092879,16.523896 2.3667584,14.589911 2.3667586,14.589911 -1.480273,12.425933 1.9527536,10.122965 1.9527537,10.122965 -0.47326861,6.7149977 3.4857631,6.0060057 3.2527669,5.9769992 2.4817572,5.886012 -0.18026696,3.7210271 4.376777,1.8330474 4.376777,1.8330474 9.3468187,0.12806426 12.068841,0.12806408 12.622845,0.056074086 13.500844,0.0020738221 14.563856,7.4782818E-05z"/>

28. Balloon

<rating:SfRating Path="M9.7999993,0C15.2,0 19.599998,5.3000031 19.599998,11.699997 19.599998,17.800003 15.800007,22.800003 10.8,23.400009L10.599988,23.400009 10.599988,23.800003 10.599988,23.900009 10.699994,23.900009 10.699994,24C10.8,24.100006 11.000013,24.199997 11.000013,24.199997 11.099989,24.199997 11.199995,24.5 11.199995,24.800003 11.199995,25.100006 11.500013,25 11.300001,25.100006 11.099989,25.199997 11.099989,25 10.599988,24.800003 10.099988,24.600006 10.400006,24.800003 10.199994,24.900009 10.000011,25 9.9000054,25 9.599987,25 9.2999993,25 9.4000054,24.699997 9.1999922,24.800003 9.0999861,24.800003 9.0000105,24.900009 9.0000105,24.900009 9.0000105,25.400009 9.0000105,26 9.4000054,26.699997 9.599987,27.100006 9.7999993,27.400009 10.000011,27.600006 10.400006,28.100006 10.400006,28.199997 10.3,29.199997 10.199994,29.900009 9.9000054,30.5 9.6999931,30.900009 9.599987,31.199997 9.4000054,31.5 9.5000115,31.600006L9.2999993,32C9.1999922,31.800003 9.2999993,31.5 9.5000115,31.100006 9.6999931,30.699997 9.9000054,30.100006 10.000011,29.400009 10.199994,28.5 10.099988,28.400009 9.7999993,27.900009 9.6999931,27.699997 9.5000115,27.400009 9.1999922,27 8.7999983,26.300003 8.7999983,25.699997 8.7999983,25.100006 8.7999983,25.100006 8.6999922,25.100006 8.5999861,25 8.2999973,24.800003 8.5000105,24.800003 8.7999983,24.600006 8.9000044,24.199997 9.0000105,24 9.0000105,24L9.0000105,23.900009 9.0999861,23.900009 9.0999861,23.699997 9.0999861,23.600006C4.0999804,23.100006 -1.4297257E-08,18 0,11.699997 -1.4297257E-08,5.3000031 4.3999992,0 9.7999993,0z"/>

29. Candle

<rating:SfRating Path="M0.49999999,16.899994L12.300024,19.700012 12.4,31.700012 0.6000061,32C0.39999404,32,-5.2263204E-08,31.799988,0,31.700012L0,17C-5.2263204E-08,17,0.30001839,16.899994,0.49999999,16.899994z M7.2000156,0C7.8000222,2.2000122 8.7000161,4 9.700017,6.1000061 10.399999,7.7000122 11.300024,9.5 11.500006,11.200012 11.800024,13.600006 11.000005,16.5 8.3000222,17 7.2000156,17.200012 6.3999968,17.100006 5.3999963,16.700012L5.0000024,16.399994C3.80002,15.700012 2.8999951,14.399994 2.7000137,13.200012 2.3999949,11.5 2.8999951,10.200012 3.8999959,8.8999939 4.7000142,7.7999878 5.8999968,6.7999878 6.3999968,5.5 7.1000095,3.7999878 7.2000156,1.7999878 7.2000156,0z"/>

30. Award

<rating:SfRating Path="M15.358993,18.785L15.358993,32 10.539992,28.890991 6.4960017,30.648995 6.4960017,20.027994C6.4960017,20.027994,11.274001,22.402994,15.358993,18.785z M3.098999,18.471996C3.0989988,18.471996,4.2649994,19.327999,5.0409999,19.562998L5.0409999,24.143999C5.0409999,24.143999,2.552002,21.272997,0.22299194,23.062998z M9.3329916,0C14.485,0 18.664,4.1340019 18.664,9.2379972 18.664,14.338001 14.485,18.471996 9.3329916,18.471996 4.1779938,18.471996 6.2046638E-08,14.338001 0,9.2379972 6.2046638E-08,4.1340019 4.1779938,0 9.3329916,0z"/>

31. Eagle

<rating:SfRating Path="M15.055819,7.3340033C15.280823,7.3340033 15.462797,7.517002 15.462797,7.7420004 15.462797,7.9669989 15.280823,8.1489981 15.055819,8.1489981 14.829809,8.1489981 14.647835,7.9669989 14.647835,7.7420004 14.647835,7.517002 14.829809,7.3340033 15.055819,7.3340033z M11.42885,6.3569983C11.958842,7.3340033 14.117812,7.9050025 14.117812,7.9050025 16.236804,9.900997 17.092782,7.4969977 17.092782,7.4969977 17.458774,5.9490012 16.399796,6.5200003 16.399796,6.5200003 13.873827,8.3940009 11.42885,6.3569983 11.42885,6.3569983z M5.6659212,4.0430029C6.7129054,4.0229987 7.9059143,4.3740042 8.8419075,5.6840018 8.8419075,5.6840018 9.8808651,8.0069998 9.3298778,10.328998 9.3298778,10.328998 4.0129571,9.3510016 2.3019798,11.674 2.30198,11.674 1.2629913,12.713001 2.667973,15.218998 2.6679728,15.218998 -3.6869595,10.328998 3.2189607,4.7059973 3.2189607,4.7059973 4.3209367,4.0679968 5.6659212,4.0430029z M20.881736,0L19.333751,0.89699904C19.333751,0.89699922,24.792699,1.1409987,27.156651,5.6229971L26.748668,5.6229971C26.748668,5.6229971 28.092645,9.229 28.826646,14.912998 28.826646,14.912998 30.538629,23.041004 31.210618,23.225002 31.210618,23.225002 32.249606,25.730999 31.94361,28.174999 31.94361,28.174999 30.965627,28.357998 27.482667,25.119999 27.482667,25.119999 27.543672,28.114002 26.748668,29.091999 26.748668,29.091999 23.876695,26.830997 23.814713,26.035999 23.814713,26.035999 23.203729,29.091999 22.408725,29.52 22.408725,29.52 20.880729,28.603001 19.964755,25.792003 19.964755,25.792003 19.169751,29.764004 17.947782,30.131 17.947782,30.131 17.031777,29.397999 15.869805,26.158001 15.869805,26.158001 15.136812,28.909 13.975816,29.580997 13.975816,29.580997 12.630832,28.420002 12.202858,25.486004 12.202858,25.486004 11.102865,28.114002 9.1468963,29.031002 9.1468963,29.031002 8.1689119,27.746998 8.2908888,25.913998 8.2908888,25.913998 6.8859076,27.258999 3.8299456,27.381 3.8299456,27.381 8.2299156,17.541004 8.4128961,14.241001 8.4128961,14.241001 6.7019191,11.674 2.973969,11.979 2.9739687,11.979 3.6459575,10.146 10.186861,11.124004 10.186861,11.124004 11.34685,6.3360022 8.4128961,3.9929997 8.4128961,3.9929999 11.34685,0.24499879 20.881736,0z"/>

32. Globe

<rating:SfRating Path="M10.215968,2.4824114C15.858958,2.4824116 20.43295,7.0553477 20.43295,12.698276 20.43295,18.340197 15.858958,22.914126 10.215968,22.914126 4.5729933,22.914126 3.0252465E-08,18.340197 0,12.698276 3.0252465E-08,7.0553477 4.5729933,2.4824116 10.215968,2.4824114z M17.507955,0.00044305106C17.610952,-0.0055611199,17.703954,0.051444941,17.703954,0.051445079L18.836946,0.79443079C18.836946,0.79443103 18.898958,0.8284272 18.945955,0.88443381 19.128953,1.0994272 19.021944,1.4614218 19.241945,1.6404201 24.896926,6.2373502 26.268934,14.462245 22.183937,20.690158 20.089948,23.885121 16.940956,25.971091 13.495973,26.793071 13.349962,26.828074 13.203967,26.858073 13.056963,26.885079 12.787967,26.936074 12.613971,27.188069 12.613971,27.461076L12.613971,28.74005C12.613971,29.01504,12.835971,29.236047,13.110964,29.236047L19.299943,29.236047C20.06294,29.236047 20.681943,29.85504 20.681943,30.618031 20.681943,31.382012 20.06294,32.000001 19.299943,32.000001L3.8829927,32.000001C3.1199942,32.000001 2.5009925,31.382012 2.5009923,30.618031 2.5009925,29.85504 3.1199942,29.236047 3.8829927,29.236047L10.066982,29.236047C10.341975,29.236047,10.563974,29.01504,10.563974,28.74005L10.563974,27.66606C10.563974,27.399066 10.351969,27.177068 10.08398,27.178075 9.606976,27.179066 9.1269812,27.160069 8.6479792,27.110068 6.8859901,26.927071 5.1359954,26.415086 3.4919872,25.555096 3.2469928,25.4261 2.9439921,25.584088 2.6899948,25.476102 2.6529927,25.461104 2.6139989,25.439101 2.5699925,25.410094 2.2769942,25.207093 1.8339946,24.925099 1.5709948,24.746102 1.2739986,24.544108 1.5379978,24.180115 1.5379977,24.180115 1.5379978,24.180115 2.0929966,23.325131 2.2739959,23.059129 2.4539957,22.794133 2.6949923,22.97313 2.6949921,22.97313L3.7879915,23.691123C3.7879918,23.691123 3.8509951,23.729117 3.8979916,23.794118 4.037991,23.991122 3.9989896,24.30812 4.2129936,24.418103 6.9349861,25.815087 9.9669757,26.165089 12.806964,25.574094 16.078958,24.893103 19.084947,22.970124 21.063945,19.955167 23.041936,16.938208 23.607944,13.414255 22.928945,10.141304 22.337944,7.3013465 20.809947,4.6613829 18.443958,2.7194083 18.222949,2.5384107 17.870962,2.7114048 17.646947,2.533406 17.646947,2.5334058 16.735954,1.9374132 16.51896,1.7984153 16.299951,1.6594172 16.419961,1.496425 16.419961,1.4964253 16.419961,1.496425 17.197959,0.30843762 17.330953,0.1064368 17.380956,0.03144094 17.445959,0.0044408803 17.507955,0.00044305106z"/>

33. Location

<rating:SfRating Path="M4.7000001,23.900024C4.899997,24.200012 5.2000001,24.600006 5.399997,24.900024 4.2999985,25.5 3.599998,26.400024 3.599998,27.300018 3.599998,29.200012 6.4999993,30.800018 9.799998,30.800018 13.099996,30.800018 15.999997,29.200012 15.999997,27.300018 15.999997,26.400024 15.300001,25.5 14.199995,24.900024 14.399999,24.600006 14.699995,24.300018 14.899999,23.900024 16.300001,24.800018 17.199995,25.900024 17.199995,27.300018 17.199995,29.900024 13.899999,32 9.799998,32 5.7000001,32 2.3999975,29.900024 2.3999977,27.300018 2.3999975,26 3.2999988,24.800018 4.7000001,23.900024z M9.799998,3.2000122C6.8999965,3.2000122 4.4999993,5.6000061 4.4999993,8.5 4.4999993,11.400024 6.8999965,13.800018 9.799998,13.800018 12.799997,13.800018 15.099996,11.400024 15.099996,8.5 15.199995,5.6000061 12.799997,3.2000122 9.799998,3.2000122z M9.8999965,0C15.300001,0 19.799999,4.4000244 19.799999,9.9000244 19.799999,15.300018 9.8999965,27.400024 9.8999965,27.400024 9.8999965,27.400024 2.3439225E-07,15.300018 0,9.9000244 2.3439225E-07,4.4000244 4.399997,0 9.8999965,0z"/>

34. Book

<rating:SfRating Path="M0,2.4680732L1.2969971,2.4680732 1.2969971,22.602019C3.4710083,22.732022 10.593994,23.55102 16.182983,28.579009 20.546021,23.964022 28.437012,22.854024 30.703003,22.630019L30.703003,2.4680732 32,2.4680732 32,23.834017 31.392029,23.872019C31.29303,23.879016,21.811035,24.566018,17.130981,29.481007L16.203979,30.388001C9.9730225,24.003016,0.73699951,23.874018,0.64501953,23.874018L0,23.87002z M28.973022,7.7122028E-05C29.328979,0.0010767093,29.689026,0.012078269,30.054016,0.035080785L30.054016,21.846024C30.054016,21.846024,22.893005,21.279023,16.541016,26.630007L16.541016,4.2520657C16.541016,4.2520657,21.744995,-0.020918781,28.973022,7.7122028E-05z M3.3510132,7.7122028E-05C10.578979,-0.020918781,15.78302,4.2520657,15.78302,4.2520657L15.78302,26.630007C9.4310303,21.279023,2.2700195,21.846024,2.2700195,21.846024L2.2700195,0.035080785C2.6350098,0.012078269,2.9960327,0.0010767093,3.3510132,7.7122028E-05z"/>

35. Smile

<rating:SfRating Path="M24.711975,18.737C24.217957,18.737 23.81897,19.123993 23.81897,19.60199 23.81897,19.625992 23.830994,19.647003 23.833984,19.671997 23.549988,23.422989 19.878967,25.996994 15.658997,25.996994 11.385986,25.996994 8.8889771,23.334 8.0979614,19.699997L8.065979,19.696991C7.9879761,19.302002 7.6599731,18.996994 7.2470093,18.996994 6.776001,18.996994 6.3939819,19.384003 6.3939819,19.862 7.0650024,24.127991 10.313965,27.658997 15.841003,27.658997 21.369995,27.658997 24.811951,24.365997 25.531006,20.358002 25.575989,20.106003 25.615967,19.850998 25.60199,19.608994L25.604004,19.60199 25.589966,19.530991C25.550964,19.087997,25.179993,18.737,24.711975,18.737z M23.586975,9.5930023C22.811951,9.5930023 22.187988,10.093994 22.187988,10.71199 22.187988,11.330994 22.811951,11.832001 23.586975,11.832001 24.357971,11.832001 24.984009,11.330994 24.984009,10.71199 24.984009,10.093994 24.357971,9.5930023 23.586975,9.5930023z M8.1350098,9.5930023C7.3599854,9.5930023 6.7349854,10.093994 6.7349854,10.71199 6.7349854,11.330994 7.3599854,11.832001 8.1350098,11.832001 8.9060059,11.832001 9.5310059,11.330994 9.5310059,10.71199 9.5310059,10.093994 8.9060059,9.5930023 8.1350098,9.5930023z M16,0C24.835999,0 32,7.1640015 32,16 32,24.83699 24.835999,32 16,32 7.1629639,32 0,24.83699 0,16 0,7.1640015 7.1629639,0 16,0z"/>

36. Alarm

<rating:SfRating Path="M9.3001308,7.4000008C9.3001308,7.4999993 9.200138,7.4999993 9.200138,7.5999978 10.800154,11.099998 13.300193,13.800002 15.800231,16.400001 15.700238,16.599998 15.600231,16.900001 15.600231,17.199996 15.600231,17.599998 15.700238,17.999999 16.000247,18.300002 15.100223,18.999999 14.500223,19.999999 13.900207,20.999999 13.300193,21.900001 12.400185,22.999999 12.500193,24.400001 13.700208,24.099998 14.400215,22.999999 15.100223,22.099998 15.800231,21.099998 16.400247,20.099998 16.900254,18.999999 17.100253,18.999999 17.200261,19.099998 17.400262,19.099998 18.400277,19.099998 19.200292,18.300002 19.200292,17.300002 19.200292,16.300002 18.400277,15.499999 17.400262,15.499999 17.000262,15.499999 16.700253,15.599998 16.400247,15.800002 14.400215,12.699996 12.300177,9.5999978 9.3001308,7.4999993 9.4001388,7.4000008 9.3001308,7.4000008 9.3001308,7.4000008z M15.500238,4.0999983L16.200246,4.0999983C20.400308,4.0999983 23.200354,5.799999 25.300378,7.9999993 27.200416,9.9999993 28.700438,12.999999 28.700438,16.599998 28.60043,20.199996 27.100408,23.099998 25.300378,25.099998 23.500361,26.999997 20.500316,28.699994 17.100253,28.899999L15.600231,28.899999C11.900177,28.699994 9.3001308,26.899999 7.4001078,24.999999 5.5000848,23.099998 4.0000614,19.999999 4.0000614,16.499999 4.0000614,12.800002 5.4000768,9.9999993 7.4001078,7.9000008 9.3001308,5.9000013 12.100177,4.299999 15.500238,4.0999983z M16.200246,0.59999833C17.000262,0.59999833 17.700269,1.299999 17.700269,2.0999983 17.700269,2.9000013 17.000262,3.5999983 16.200246,3.599998 15.40023,3.5999983 14.700223,2.9000013 14.700223,2.0999983 14.700223,1.299999 15.40023,0.59999833 16.200246,0.59999833z M6.1000847,0.40000141L7.2001075,0.40000141C9.200138,0.70000062,10.600154,1.4000013,11.600169,2.7000003L1.700023,11.400001C0.70000771,10.499999,0.20000002,9.2000001,0,7.5999978L0,6.4999993C0.60000006,2.9999998,2.6000308,0.90000138,6.1000847,0.40000141z M24.800368,0L25.900391,0C29.200446,0.40000141 31.900485,2.9000013 32.000491,6.4000008 32.100486,8.2999986 31.400477,9.7999986 30.400462,10.999999 27.000415,8.0999978 23.700362,5.2000006 20.400308,2.2999988 21.400323,1.0999983 22.800338,0.29999912 24.800368,0z"/>

37. Knight

<rating:SfRating Path="M14.399726,27.899994C15.49968,27.899994 16.499659,28.799988 16.499659,29.899994 16.499659,31 15.599713,31.899994 14.399726,31.899994L2.0999931,32C0.90000567,32 -1.5387559E-07,31.100006 0,30 -1.5387559E-07,28.899994 0.90000567,28 2.0999931,28z M13.899737,0C14.699708,0.20001221 13.799702,1.8999939 13.799702,2.6000061 17.099682,4.3999939 18.899634,8 18.599651,13.100006 18.499617,14.799988 18.099663,16.399994 17.599672,17.799988 16.799641,20.100006 15.699687,22.700012 16.099703,26.299988 10.899799,26.299988 5.7998678,26.200012 0.6000242,26.200012 -1.5387559E-07,23.600006 1.1000138,21.200012 2.29994,19.799988 4.4999067,17 8.4998237,15.899994 8.7998058,11 7.7998263,11.200012 6.6998736,10.899994 5.7998678,11.200012 4.4999067,11.600006 4.0999519,13.700012 2.1999663,13.200012 1.3999954,13 0.29998142,11.700012 0.2999816,10.600006 0.40001598,9.8999939 1.3999954,9 2.29994,8.1000061 3.8999435,6.5 5.1999046,5.1000061 6.9998552,3.8999939 7.9998342,3.2000122 9.0998479,3.1000061 10.099828,2.5 10.599817,2.2000122 10.999772,1.7000122 11.499762,1.2999878 12.299733,0.79998779 13.099766,0.3999939 13.899737,0z "/>

38. Rook

<rating:SfRating Path=" M1.3004287,0L6.2694741,0 6.2694741,2.7830048 10.045515,2.7830048 10.045515,0 14.120508,0 14.120508,2.7830048 17.896549,2.7830048 17.896549,0 22.865655,0C22.865655,0 22.666618,1.9880066 21.673626,3.3789978 20.679597,4.7700043 18.890577,5.8630066 18.890577,5.8630066L18.890577,5.9629974C19.685567,5.9629974 20.38162,6.4600067 20.38162,7.0559998 20.38162,7.6519928 19.685567,8.1490021 18.890577,8.1490021L18.592599,8.1490021C18.6916,9.2420044,20.083581,19.179993,20.182582,19.776001L21.076635,19.776001C21.772626,19.776001,22.26964,20.173996,22.26964,20.570999L22.26964,20.671005 22.26964,20.770004C22.170641,21.067993 21.871625,21.266998 21.474588,21.365997 21.573589,21.565002 24.257637,24.546997 24.356638,26.037003 24.455637,27.528 23.660646,28.820007 22.666618,29.813995 22.666618,29.912994 23.561645,30.608994 23.760622,31.005997 23.958623,31.404007 24.157661,32 24.157661,32L0.2073996,32C0.20739967,32 0.40637635,31.304001 0.60437654,30.906998 0.80341416,30.509003 1.5984053,29.912994 1.5984052,29.912994 0.70441412,28.919006 -0.090638089,27.626999 0.0083620455,26.136993 0.10736201,24.744995 2.8904109,21.962997 3.2884253,21.565002 2.8904109,21.565002 2.5924342,21.365997 2.3933967,21.266998L2.2943967,21.167999C2.2943964,21.167999 2.2943964,21.067993 2.1944201,21.067993 2.1944199,20.968994 2.0954197,20.968994 2.0954197,20.869995L2.0954197,20.770004C2.0954197,20.272995,2.5924342,19.975006,3.2884253,19.975006L3.9834397,19.975006C4.0834165,19.876007,4.0834165,19.677002,4.0834165,19.677002L5.6734596,8.2480011 5.573422,8.0500031 5.3754221,8.0500031C4.778431,8.0500031,4.1824165,7.7519989,3.9834397,7.3540039L3.9834397,7.2550049 3.9834397,6.9570007C3.9834397,6.3600006 4.580431,5.9629974 5.3754221,5.8630066 5.3754221,5.8630066 3.7844022,5.0679932 2.5924342,3.3789978 1.3994287,1.6889954 1.3004286,0 1.3004287,0z"/>

39. Pawn

<rating:SfRating Path=" M7.600003,0C10.100002,0 11.999994,2 11.999994,4.3999939 11.999994,5.8999939 11.200008,7.3000031 10.100002,8.1000061L9.8999893,8.1999969 11.700007,8.1999969C12.600001,8.1999969 13.399988,8.8000031 13.399988,9.5 13.399988,10.199997 12.700007,10.800003 11.700007,10.800003L9.6000015,10.800003 9.6000015,11.199997C10.300014,16.399994,12.999994,21.699997,13.200007,22L13.300013,22C13.600001,22 13.899988,22.300003 13.899988,22.600006 13.899988,22.899994 13.700007,23.100006 13.499994,23.199997L13.499994,23.399994C13.600001,23.5 14.200006,24.5 14.200006,24.5 15.399987,26.800003 14.999994,28.199997 14.999994,28.199997 14.899987,29.300003 14.300012,30.199997 14.200006,30.300003 14.300012,30.300003 14.399987,30.399994 14.399987,30.5 14.399987,30.600006 14.300012,30.699997 14.200006,30.699997L13.899988,30.699997C14.6,30.800003,15.1,31.300003,15.1,32L0,32C-1.9706749E-07,31.300003,0.60000564,30.699997,1.2000112,30.699997L0.89999344,30.699997C0.80001779,30.699997 0.70001169,30.600006 0.70001175,30.5 0.70001169,30.399994 0.80001779,30.300003 0.89999344,30.300003L0.99999954,30.300003 0.89999344,30.100006C0.300018,29.199997 0.20001193,28.100006 0.20001173,28.100006 -0.19998181,26.199997 1.1000055,24.399994 1.1000056,24.399994 1.4999991,23.800003 1.8000173,23.300003 1.8999929,23.100006L1.8000173,23.100006C1.4999991,23.100006 1.3000176,22.800003 1.3000173,22.5 1.3000176,22.100006 1.6000052,21.899994 1.8999929,21.899994L2.1000051,21.899994C3.7000105,18.199997,5.3000161,11.699997,5.4999973,10.800003L3.4999981,10.800003C2.6000049,10.800003 1.8000173,10.199997 1.8000173,9.5 1.8000173,8.8000031 2.4999988,8.1999969 3.4999981,8.1999969L5.3000161,8.1999969 5.20001,8.1000061C3.9999981,7.3000031 3.2000107,5.8999939 3.2000107,4.3999939 3.2000107,2 5.20001,0 7.600003,0z"/>

40. Paw print

<rating:SfRating Path=" M16.599524,16.686905C20.296603,16.686905 26.991711,24.28085 23.893643,29.076809 22.494633,31.274794 18.198548,27.177836 16.299532,27.177836 14.501531,27.177836 10.604438,31.074814 9.305407,29.076809 6.1073599,24.379849 12.80247,16.686905 16.599524,16.686905z M2.6102974,9.4919438C4.0093665,9.4919438 5.6083898,10.790916 6.807383,12.889902 8.4064059,15.886892 8.4064059,19.383879 6.9074211,20.782856 5.4083748,22.181866 2.8103127,20.882863 1.2112892,17.985878 -0.38669656,14.987911 -0.38669656,11.490923 1.111312,10.091946 1.6113198,9.591949 2.1113274,9.4919438 2.6102974,9.4919438z M29.38976,7.0939488C29.88873,7.0939488 30.488774,7.2939596 30.888745,7.6939511 32.386752,9.0929293 32.386752,12.589916 30.788767,15.587882 29.189744,18.584874 26.69172,19.783871 25.092696,18.384892 23.593649,16.985884 23.593649,13.488897 25.192673,10.491937 26.291689,8.3929515 27.990689,7.0939488 29.38976,7.0939488z M10.272758,0.59818277C12.008328,0.65690003 13.613994,3.1009969 14.001523,6.2949424 14.501531,9.7919297 13.402515,13.089913 11.503438,13.488897 9.7054372,13.888918 7.8064217,11.390918 7.3064141,7.7939563 6.807383,4.2969694 7.9063988,1.0989918 9.8044381,0.60000191L10.104431,0.60000191C10.160651,0.5968769,10.216772,0.59628884,10.272758,0.59818277z M20.296603,0L20.496617,0C22.394658,0.20001077 23.693627,3.2969758 23.394673,6.8939681 23.094618,10.491937 21.395619,13.188911 19.497578,12.989907 17.598563,12.789927 16.299532,9.6919245 16.599524,6.0949621 16.899518,2.5979752 18.497563,-1.6992999E-07 20.296603,0z"/>

41. Key

<rating:SfRating Path="M23.242747,2.7636242C22.718753,2.763999 22.194507,2.9639988 21.79601,3.3639984 20.996022,4.1629982 20.996022,5.4560013 21.79601,6.2599983 22.593982,7.0589981 23.887988,7.0579987 24.687976,6.262001L24.687976,6.2610016C25.49199,5.4550018 25.49199,4.1650009 24.687976,3.3610001 24.290484,2.9624996 23.766742,2.7632494 23.242747,2.7636242z M20.233022,0L20.236012,0C25.317004,0 29.433028,4.1199989 29.429,9.2019997 29.429,14.278999 25.309008,18.401001 20.231984,18.401001 19.186025,18.400002 18.179984,18.216999 17.239982,17.894001L15.907035,19.226002 13.098016,18.880001 13.665032,21.467003 10.743036,21.233002 11.143,23.992996 7.8829917,24.097 8.4509848,26.682999 5.4910248,26.488998 5.9880341,29.147003 3.1420275,32 1.0350337,27.487999 12.398003,16.125 11.684992,15.417999 0.58001708,26.523003 0,25.268997 11.991999,13.273998C11.387018,12.044998 11.033991,10.664001 11.033991,9.2019997 11.033991,4.1199989 15.150017,0.0019989014 20.233022,0z"/>

42. Pin

<rating:SfRating Path="M16.833997,0L14.443011,4.8720093 14.504962,12.14502 16.928966,12.127991 19.396001,16.953979 12.118983,17.018005 12.141993,19.437988 9.8739941,32 7.2920315,19.47998 7.2759797,17.054016 0,17.114014 2.3820119,12.247986 4.8080303,12.224976 4.7480328,4.9520264 2.2820363,0.11999512z"/>

43. Speaker

<rating:SfRating Path="M25.108002,9.7950144C26.164001,11.988008 26.654022,14.687014 26.352997,17.528995 26.151001,19.429996 25.615021,21.186007 24.835022,22.722018L22.322021,21.539004C22.971008,20.278995 23.421021,18.812015 23.587006,17.237002 23.83902,14.863008 23.406006,12.602999 22.513,10.83301z M30.25,7.7470102C31.640015,10.783998 32.281006,14.356997 31.884003,18.118991 31.615021,20.640994 30.895996,22.993991 29.852997,25.079989L27.34201,23.902011C28.255005,22.088992 28.882019,20.036014 29.117004,17.82001 29.46701,14.526003 28.89801,11.390993 27.671021,8.7749948z M19.613007,0L19.613007,31.379003 8.3120117,21.89899 0,21.89899 0,9.4800119 8.3160095,9.4800119z"/>

44. Microphone

<rating:SfRating Path=" M17.000021,13.300003C17.599999,13.300003,18.099999,13.800003,18.099999,14.400009L18.099999,15C18.099999,19.400009,15.000019,23,10.900039,23.800003L10.800001,23.800003 10.800001,30 14.599995,30 14.599995,32 3.4000287,32 3.4000287,30 7.0000088,30 7.0000088,23.900009C3.0000038,23,-2.0903099E-07,19.400009,0,15.100006L0,14.900009 0,14.800003C-2.0903099E-07,14.200012 0.50000045,13.700012 1.099977,13.700012 1.7000142,13.700012 2.2000148,14.200012 2.2000146,14.800003L2.2000146,15.200012C2.2000148,19 5.2999947,22.100006 9.0999872,22.100006 12.900041,22.100006 16.000021,19 16.000021,15.200012L16.000021,14.600006C15.900045,13.800003,16.400046,13.300003,17.000021,13.300003z M8.9000361,0C11.90004,0,14.300006,2.4000092,14.300006,5.4000092L14.300006,14.900009C14.300006,17.900009 11.90004,20.300003 8.9000361,20.300003 5.9000318,20.300003 3.5000043,17.900009 3.5000043,14.900009L3.5000043,12.400009 9.2999994,12.400009C9.5999882,12.400009 9.900037,12.200012 9.900037,11.800003 9.900037,11.5 9.7000248,11.200012 9.2999994,11.200012L3.5000043,11.200012 3.5000043,10 9.2999994,10C9.5999882,10 9.900037,9.8000031 9.900037,9.4000092 9.900037,9.1000061 9.7000248,8.8000031 9.2999994,8.8000031L3.5000043,8.8000031 3.5000043,7.8000031 9.2999994,7.8000031C9.5999882,7.8000031 9.900037,7.6000061 9.900037,7.2000122 9.8000004,7.2000122 9.5999882,7 9.2999994,7L3.5000043,7 3.5000043,5.8000031 9.2999994,5.8000031C9.5999882,5.8000031 9.900037,5.6000061 9.900037,5.2000122 9.900037,4.9000092 9.7000248,4.6000061 9.2999994,4.6000061L3.5999798,4.6000061C3.9000294,2.1000061,6.20002,0,8.9000361,0z"/>

45. Brightness

<rating:SfRating Path=" M14.758999,27.624996C15.167,27.668025 15.580998,27.692989 15.999001,27.692989 16.418999,27.692989 16.833,27.668025 17.240997,27.624996L17.240997,32.000001 14.758999,32.000001z M25.091,23.336997L28.191002,26.437007 26.437,28.191036 23.335999,25.090997C23.980999,24.569024,24.57,23.982017,25.091,23.336997z M6.9090006,23.336997C7.4300005,23.982017,8.0179979,24.569024,8.6629984,25.090997L5.5629999,28.191036 3.8079988,26.437007z M27.624001,14.758986L32,14.758986 32,17.241014 27.624001,17.241014C27.667999,16.832994 27.691998,16.418992 27.691998,16.000015 27.691998,15.581008 27.667999,15.167007 27.624001,14.758986z M0,14.758986L4.3759996,14.758986C4.3320009,15.167007 4.3079988,15.581008 4.3079988,16.000015 4.3079988,16.418992 4.3320009,16.832994 4.3759996,17.241014L0,17.241014z M15.999001,8.3100055L15.999001,23.689994C20.238999,23.689994 23.688999,20.241016 23.688999,16.000015 23.688999,11.75999 20.238999,8.3100055 15.999001,8.3100055z M15.999001,6.4350036C21.281998,6.4350036 25.565998,10.717997 25.565998,16.000015 25.565998,21.28301 21.281998,25.566034 15.999001,25.566034 10.717999,25.566034 6.4349977,21.28301 6.4349977,16.000015 6.4349977,10.717997 10.717999,6.4350036 15.999001,6.4350036z M26.437,3.8089939L28.191002,5.5640005 25.091,8.6640094C24.57,8.019997,23.980999,7.4310068,23.335999,6.9090031z M5.5629999,3.8089939L8.6629984,6.9090031C8.0179979,7.4310068,7.4300005,8.0179828,6.9090006,8.6640094L3.8079988,5.5640005z M14.758999,0L17.240997,0 17.240997,4.3759807C16.833,4.3320049 16.418999,4.3089946 15.999001,4.3089946 15.580998,4.3089946 15.167,4.3320049 14.758999,4.3759807z"/>

46. Gift

<rating:SfRating Path=" M14.072999,21.71989L14.173005,21.71989 23.954012,21.71989 23.954012,30.402982C23.954012,31.300994,23.255007,31.999997,22.356997,31.999997L14.072999,31.999997z M1.2980041,21.71989L11.178987,21.71989 11.178987,31.999997 2.8949892,31.999997C1.9960022,31.999997,1.2980041,31.300994,1.2980041,30.402982z M19.661989,3.2556945C19.06299,3.2556945,14.072999,7.3477336,12.975007,8.545744L12.975007,8.8447515C13.674012,8.6447526 15.670015,7.1477343 17.267,6.1497227 19.162996,5.0517112 19.962008,3.7546926 19.661989,3.2556945z M5.5889899,3.2556945C5.3899848,3.7546926 6.1879889,5.0517112 7.984986,6.2497221 9.4819957,7.2477342 11.578004,8.6447526 12.277009,8.9447509L12.277009,8.6447526C11.178987,7.3477336,6.287995,3.2556945,5.5889899,3.2556945z M17.864281,0.00017286225C18.476668,-0.0068490629 19.175909,0.19928326 19.962008,0.76066515 22.756014,2.6566814 22.656008,4.2536984 22.656008,5.2517105 22.157015,7.447733 19.463015,8.4457446 16.868014,8.9447509L23.355013,8.9447509C24.252993,8.9447509,24.951998,9.6427566,24.951998,10.541768L24.951998,13.235797C24.951998,13.834803,24.553011,14.433808,24.053988,14.633815L24.053988,19.723867 14.173005,19.723867 14.173005,9.3437568 13.574006,9.3437568 13.075013,9.3437568 12.675996,9.3437568 12.277009,9.3437568 11.578004,9.3437568 11.477998,9.3437568 11.178987,9.3437568 11.178987,19.723867 1.2980041,19.723867 1.2980041,14.732815C0.59899889,14.533815,-2.3291432E-07,13.934802,0,13.136797L0,10.441769C-2.3291432E-07,9.5437566,0.69900499,8.8447515,1.5969848,8.8447515L8.4840099,8.8447515C5.8890082,8.545744 3.0939943,7.447733 2.6950075,5.2517105 2.6950075,4.353706 2.5950014,2.7566885 5.3899848,0.76066515 6.0889899,0.261659 6.7869879,0.061659901 7.385987,0.061660053 8.9830028,0.061659901 10.080995,1.4586705 10.480012,1.8586761 10.878999,2.2576827 12.076997,4.452706 12.675996,6.6487285 13.274995,4.452706 14.471986,2.2576827 14.871003,1.8586761 15.301535,1.4281411 16.29929,0.018116923 17.864281,0.00017286225z"/>

47. House

<rating:SfRating Path=" M16.200012,6.9000092L27.899994,14.699997 27.899994,26.5 20.200012,26.5 20.200012,18.699997 11.700012,18.699997 11.700012,26.5 4.1000061,26.5 4.1000061,14.699997z M16.200012,0L32,10.800003 32,14.400009 16.200012,3.6000061 0,14.699997 0,11.100006z"/>

48. Tag

<rating:SfRating Path="M5.3999968,4C5.7999964,4 6.0999961,4.1999998 6.3999963,4.3999996 6.8999958,5 6.8999958,5.8999996 6.2999964,6.3999996 5.7999964,6.8999996 4.8999968,6.8999996 4.3999977,6.2999997 3.8999977,5.6999998 3.8999977,4.8999996 4.4999971,4.3999996 4.6999969,4.0999994 5.0999966,4 5.3999968,4z M5.3999968,3C4.7999973,3 4.1999969,3.1999998 3.7999973,3.5999994 2.7999983,4.5 2.6999979,5.9999995 3.5999975,6.9999995 4.4999971,7.9999995 5.9999962,7.9999995 6.9999957,7.1999998 7.9999952,6.2999997 7.9999952,4.7999992 7.0999956,3.7999992 6.699996,3.1999998 5.9999962,3 5.3999968,3z M5.6999965,0L12.799992,1 30.799981,20.599999 18.299989,31.999999 0.30000019,12.4 0,5.2999992z"/>

49. Water drop

<rating:SfRating Path=" M1.9970116,20.930969C2.0029928,20.982971 2.0579857,21.202942 2.1129784,21.532959 3.0109896,26.987 8.049021,30.115967 13.151016,28.540955 8.1690161,29.401978 3.1489903,25.559998 1.9970116,20.930969z M10.348035,0C13.466019,5.1989746 17.279012,10.396973 20.451013,15.485962 20.927026,16.29895 21.302028,17.178955 21.558009,18.107971 21.813014,19.037964 21.949001,20.015991 21.949001,21.026001 21.949001,27.086975 17.034993,32 10.974988,32 4.9140069,32 -1.935332E-07,27.086975 0,21.026001 -1.935332E-07,20.015991 0.1370239,19.037964 0.39196826,18.107971 0.64801081,17.178955 1.0219737,16.29895 1.4990248,15.485962 4.4559986,10.396973 7.2279746,5.1989746 10.348035,0z"/>

50. Snow

<rating:SfRating Path="M7.9500122,0L9.6599731,0 11.572021,3.2200022 13.182007,0.401978 14.893005,0.401978 15.697998,1.9119878 13.182007,6.2389849 16,11.069003 18.817993,6.2389849 16.302002,1.9119878 17.106995,0.401978 18.817993,0.401978 20.427979,3.2200022 22.339966,0 24.049988,0 24.85498,1.5090032 22.942993,4.7290051 26.263977,4.7290051 27.06897,6.2389849 26.263977,7.747988 21.333008,7.747988 18.515991,12.578983 24.049988,12.578983 26.565979,8.2509783 28.276978,8.2509783 29.08197,9.760989 27.471985,12.578983 31.195007,12.578983 32,14.087986 31.195007,15.596988 27.471985,15.596988 29.08197,18.414983 28.276978,19.923985 26.565979,19.923985 24.049988,15.596988 18.515991,15.596988 21.333008,20.427983 26.263977,20.427983 27.06897,21.936986 26.263977,23.446997 22.942993,23.446997 24.85498,26.666999 24.049988,28.176001 22.339966,28.176001 20.427979,24.956 18.817993,27.773993 17.106995,27.773993 16.302002,26.263984 18.817993,21.936986 16,17.106999 13.182007,21.936986 15.697998,26.263984 14.893005,27.773993 13.182007,27.773993 11.572021,24.956 9.6599731,28.176001 7.9500122,28.176001 7.1450195,26.666999 9.0570068,23.446997 5.7359619,23.446997 4.9309692,21.936986 5.7359619,20.427983 10.666992,20.427983 13.484009,15.596988 7.9500122,15.596988 5.434021,19.923985 3.7229614,19.923985 2.9179688,18.414983 4.5280151,15.596988 0.80499268,15.596988 0,14.087986 0.80499268,12.578983 4.5280151,12.578983 2.9179688,9.760989 3.7229614,8.2509783 5.434021,8.2509783 7.9500122,12.578983 13.484009,12.578983 10.666992,7.747988 5.7359619,7.747988 4.9309692,6.2389849 5.7359619,4.7290051 9.0570068,4.7290051 7.1450195,1.5090032z"/>

Refer to the following GIF image.

51. Battery

<rating:SfRating Path=" M2.5919805,24.821991C2.1929935,24.821991,1.8939823,24.921997,1.8939824,24.921997L1.8939824,29.806992C1.8939823,29.906998,2.1929935,29.906998,2.5919805,29.906998L10.966006,29.906998C11.364993,29.906998,11.664004,29.806992,11.664004,29.806992L11.664004,24.921997C11.664004,24.821991,11.364993,24.821991,10.966006,24.821991z M2.5919805,17.444992C2.1929935,17.444992,1.8939823,17.544998,1.8939824,17.544998L1.8939824,22.429993C1.8939823,22.529999,2.1929935,22.529999,2.5919805,22.529999L10.966006,22.529999C11.364993,22.529999,11.664004,22.429993,11.664004,22.429993L11.664004,17.544998C11.664004,17.444992,11.364993,17.444992,10.966006,17.444992z M2.5919805,10.069C2.1929935,10.069,1.8939823,10.167999,1.8939824,10.167999L1.8939824,15.052994C1.8939823,15.153,2.1929935,15.153,2.5919805,15.153L10.966006,15.153C11.364993,15.153,11.664004,15.052994,11.664004,15.052994L11.664004,10.167999C11.664004,10.069,11.364993,10.069,10.966006,10.069z M0.69799802,5.4830017L12.461001,5.4830017C12.859988,5.4830017,13.159,5.7819977,13.159,6.0809937L13.159,31.401993C13.159,31.701004,12.859988,32,12.461001,32L0.69799802,32C0.2990112,31.899994,-9.0753019E-08,31.600998,0,31.302002L0,6.0809937C-9.0753019E-08,5.6819916,0.2990112,5.4830017,0.69799802,5.4830017z M3.5889903,0L9.5700093,0C10.068972,0,10.46802,0.39900208,10.46802,0.89700317L10.46802,2.5919952C10.46802,3.0899963,10.068972,3.4889984,9.5700093,3.4889984L3.5889903,3.4889984C3.091004,3.4889984,2.6920172,3.0899963,2.6920172,2.5919952L2.6920172,0.89700317C2.6920172,0.39900208,3.091004,0,3.5889903,0z"/>

52. Wireless

<rating:SfRating Path="M16.79575,22.894002C17.695761,22.894002 18.295729,23.593984 18.295729,24.394002 18.295729,25.192983 17.695761,25.993001 16.79575,25.993001 15.895768,25.993001 15.295786,25.292989 15.295786,24.494008 15.295786,23.69399 15.995773,22.894002 16.79575,22.894002z M16.59577,17.096002L16.995758,17.096002C18.69474,17.096002 20.294724,17.895011 21.294708,19.194999 21.394682,19.395011 21.494688,19.594993 21.494688,19.795005 21.494688,20.395011 21.0947,20.895011 20.394697,20.895011L20.294724,20.895011C19.894705,20.895011 19.594721,20.694999 19.394711,20.395011 18.794745,19.594993 17.795734,19.094993 16.695776,19.194999 15.595785,19.295005 14.5958,19.795005 14.096798,20.694999L13.996809,20.895011C13.7968,21.093986 13.496816,21.193992 13.196817,21.293998 12.896818,21.293998 12.59682,21.193992 12.396826,20.99401 12.196832,20.795005 12.096827,20.594993 12.096827,20.295005 12.096827,20.094993 12.196832,19.795005 12.296821,19.594993 13.196817,18.194999 14.795794,17.195001 16.59577,17.096002z M16.095778,8.4980125C16.395762,8.5980186 16.695776,8.5980186 16.895754,8.5980186 20.594706,8.5980186 24.093649,10.296992 26.092613,13.09701 26.292624,13.39599 26.492632,13.696009 26.492632,14.096003 26.492632,15.096002 25.793636,15.895989 24.593641,15.895989 23.993645,15.895989 23.393677,15.596002 22.993658,14.995995 21.494688,12.997003 18.994722,11.896998 16.295773,11.997004 13.596806,12.097011 11.096841,13.596003 9.897853,15.696008L9.7978641,15.796014C9.7978641,15.895989 9.6978589,15.995995 9.59787,15.995995 9.2978707,16.395989 8.7978784,16.596002 8.297885,16.596002 7.2978998,16.696008 6.3989106,15.895989 6.3989106,14.995995 6.3989106,14.596002 6.4989153,14.196009 6.6989094,13.89599 8.5978843,10.697017 12.196832,8.6979942 16.095778,8.4980125z M15.49578,0L16.395762,0C22.693676,-2.2080167E-07 28.392599,3.2990097 31.591559,8.2980003 31.791538,8.5980186 31.991547,8.8980064 31.991547,9.2980003 32.091551,10.296992 31.291544,11.097011 30.191586,11.197017 29.49259,11.197017 28.992598,10.796992 28.592579,10.197017 25.793636,5.9980134 20.994694,3.2990097 15.695774,3.5989975 10.297856,3.8990154 5.6989237,7.0980191 3.1989594,11.896998 2.8999678,12.296991 2.3999749,12.59701 1.8999822,12.59701 0.89999626,12.697016 0.10000467,11.896998 0,10.896998 0,10.497004 0.10000467,10.097011 0.29999865,9.7969932 3.1989594,4.2990093 8.7978784,0.39999351 15.49578,0z"/>

53. Hand

<rating:SfRating Path="M11.399994,0C12.399994,0,13.199982,0.69999695,13.199982,1.6000061L13.199982,14.199997 13.399994,14.300003C13.600006,14.400009,13.899994,14.5,14.100006,14.699997L14.299988,14.800003 14.299988,3.6999969C14.299988,2.8000031 15.100006,2.1000061 16.100006,2.1000061 17.100006,2.1000061 17.899994,2.8000031 17.899994,3.6999969L17.899994,16.5 18.399994,16.300003C20.299988,13.699997 21.799988,12.900009 23,12.900009 24.600006,12.900009 25.5,14.300003 25.5,14.300003L20.5,20.900009C19.199982,25,17.5,27.5,15.899994,29L16,29.199997C15.600006,29.600006,15.100006,30,14.600006,30.300003L14.399994,30.400009 14.299988,30.5C13.5,31,13,31.199997,12.699982,31.300003L12.5,31.400009C11.5,31.800003 10.399994,32 9.2999878,32 4.1999817,32 0,27.800003 0,22.600006 0,22 0.1000061,21.5 0.1000061,20.900009L0.1000061,20.800003 0.1000061,20.699997 0.1000061,6.3000031C0.1000061,5.4000092 0.79998779,4.6999969 1.6999817,4.6999969 2.6000061,4.6999969 3.2999878,5.4000092 3.2999878,6.3000031L3.2999878,15.5 3.3999939,15.5C3.7999878,15.199997,4.1999817,14.900009,4.6999817,14.600006L4.7999878,14.5 4.7999878,2.6999969C4.7999878,1.8000031 5.6000061,1.1000061 6.6000061,1.1000061 7.6000061,1.1000061 8.3999939,1.8000031 8.3999939,2.6999969L8.3999939,13.300003 9.1999817,13.300003 9.3999939,13.300003 9.3999939,1.6000061C9.6000061,0.69999695,10.399994,0,11.399994,0z"/>

54. Timer

<rating:SfRating Path="M13.852997,10.320002C8.719002,10.320002,5.1340029,15.430001,6.4449999,20.539983L13.852997,17.694984z M13.852997,8.3099932C14.065003,8.3099932 14.277001,8.320003 14.486,8.3350023 15.529999,8.3999895 16.529,8.6300005 17.459999,8.9949907 17.832001,9.139995 18.193001,9.3099932 18.542,9.4999956 18.82,9.6499895 19.090996,9.8149981 19.353997,9.9900011 19.875,10.344996 20.362999,10.749995 20.807999,11.195002 22.588997,12.975 23.691002,15.430001 23.691002,18.150001 23.691002,20.864995 22.588997,23.324985 20.807999,25.104984 20.362999,25.549991 19.875,25.953983 19.353997,26.304996 19.090996,26.479984 18.821999,26.649997 18.542,26.794986 18.193001,26.989993 17.832001,27.155002 17.459999,27.298982 16.529,27.668977 15.529999,27.898988 14.486,27.963991 14.277001,27.974 14.065003,27.98398 13.852997,27.98398 12.154,27.98398 10.558998,27.554994 9.1640017,26.794986 8.8870013,26.649997 8.6159976,26.479984 8.3519976,26.304996 7.8310015,25.953983 7.3430026,25.549991 6.8980029,25.104984 5.1179965,23.324985 4.0159991,20.864995 4.0159991,18.150001 4.0159991,15.430001 5.1179965,12.975 6.8980029,11.195002 7.3430026,10.749995 7.8290026,10.344996 8.3519976,9.9900011 8.6159976,9.8149981 8.8840029,9.6499895 9.1640017,9.4999956 10.558998,8.7449907 12.154,8.3099932 13.852997,8.3099932z M13.852997,6.6450013C11.859001,6.6450013 9.9779971,7.1600002 8.3420031,8.0550045 7.3619997,8.5949968 6.4720004,9.264995 5.693001,10.055004 3.6279986,12.134989 2.3499987,14.994988 2.3499989,18.150001 2.3499987,24.494998 7.5110018,29.649995 13.852997,29.649995 20.197998,29.649995 25.357002,24.494998 25.357002,18.150001 25.357002,11.805003 20.197998,6.6450013 13.852997,6.6450013z M5.4440005,3.8699931C6.2170031,3.8699934 6.9229968,4.1499919 7.4649966,4.6199931 5.6139986,5.4949927 3.9729998,6.7459988 2.6320004,8.2660021 2.450001,7.8709983 2.3439982,7.4309963 2.3439984,6.9710049 2.3439982,5.2550024 3.7309992,3.8699934 5.4440005,3.8699931z M10.306999,0L17.398003,0C17.796997,0 18.120003,0.43000774 18.120003,0.94999645 18.120003,1.4750054 17.796997,1.899993 17.398003,1.8999929L16.197998,1.8999929 16.197998,4.499998C22.733002,5.6099981 27.707001,11.299998 27.707001,18.150001 27.707001,25.799991 21.503998,31.999999 13.852997,31.999999 6.2040026,31.999999 2.3576422E-07,25.799991 0,18.150001 2.3576422E-07,14.729988 1.2399981,11.609995 3.2889981,9.195003 4.6159976,7.6249966 6.2849963,6.3650026 8.1780016,5.5149969 9.2259982,5.0399908 10.342003,4.6950049 11.509003,4.499998L11.509003,1.8999929 10.306999,1.8999929C9.9109957,1.899993 9.5869982,1.4750054 9.5869982,0.94999645 9.5869982,0.43000774 9.9109957,0 10.306999,0z"/>

55. Shirt

<rating:SfRating Path="M11.100002,0L16.000002,4.1000023 20.900002,0 32.000004,1.1000004 32.000004,6.1000032 24.600003,6.1000032 24.600003,19.800012 7.4000015,19.800012 7.4000015,6.0000033 0,6.0000033 0,1z"/>

56. Boat

<rating:SfRating Path="M0,17.700007L32,17.700007C32,17.700007 29.799988,21.400002 28.699982,22.599999 27.899994,23.499991 24.5,25.9 24.5,25.9L0,25.9z M17.5,3.9000077C17.5,3.9000077 23,6.9999973 24.299988,8.4000055 25.699982,9.7999994 28.100006,14.999994 28.100006,14.999994L17.5,14.999994z M14.600006,0L14.600006,15.100001 0,15.100001z"/>

57. Car

<rating:SfRating Path="M5.5020646,22.087623C6.2020649,22.18662 6.9020647,22.18662 7.6010617,22.286609 7.5010632,22.786601 7.5010632,23.286592 7.1010622,23.386596 6.6020621,23.586589 6.0020641,23.286592 5.4020666,23.386596 5.4020666,22.98661 5.4020666,22.586606 5.5020646,22.087623z M26.490042,21.887614C26.490042,22.286609 26.590048,22.786601 26.590048,23.186603 25.991041,23.086598 25.291044,23.386596 24.791046,23.086598 24.392044,22.886605 24.392044,22.486617 24.292045,21.987619 25.091049,22.087623 25.791044,21.987619 26.490042,21.887614z M31.088035,18.888675C30.988037,20.288644 30.988037,21.687621 30.888039,23.186603 30.888039,23.686593 30.78804,24.185594 30.488039,24.285567 30.188043,24.385572 29.38904,24.285567 29.089037,24.285567 28.689045,24.285567 27.99004,24.385572 27.690044,24.285567 27.390041,24.185594 27.390041,23.586589 27.290043,23.186603 27.290043,22.686612 27.190044,22.286609 27.190044,21.787625 28.989038,21.387624 30.38804,20.487645 31.088035,18.888675z M0.90506959,18.888675C1.7040685,20.388648 3.0040702,21.387624 4.9030665,21.787625 4.9030665,22.286609 4.803068,22.686612 4.803068,23.186603 4.803068,23.586589 4.803068,24.185594 4.403067,24.285567 4.1030682,24.385572 3.3040692,24.285567 2.9040681,24.285567 2.5040706,24.285567 1.8040707,24.385572 1.5050714,24.285567 1.0050718,24.085589 1.1050701,22.486617 1.0050719,21.787625 1.0050718,21.287633 1.0050718,20.787643 0.90506959,20.388648z M26.091047,11.393811C24.991043,11.393811 24.292045,11.4938 23.492042,11.792807 22.893045,11.9928 21.993051,12.392787 21.893045,13.192776 21.893045,13.691759 22.193048,14.39176 22.59305,14.691742 22.992044,14.991739 23.692047,15.190742 24.392044,15.190742 26.091047,15.190742 27.790043,14.691742 28.789043,13.791764 29.089037,13.59177 29.589037,13.092772 29.489038,12.492791 29.489038,12.192793 29.189043,11.9928 28.989038,11.892796 28.389042,11.4938 27.390041,11.393811 26.490042,11.393811z M5.6020669,11.393811C4.9030665,11.393811 4.3030685,11.393811 3.7030667,11.592797 3.2040669,11.692802 2.6040691,11.9928 2.5040709,12.392787 2.4040686,12.892778 2.9040681,13.391777 3.2040666,13.691759 4.2030662,14.591753 6.0020641,15.090737 7.7010673,15.090737 8.1010608,15.090737 8.7010669,14.991739 9.0000619,14.89175 9.6000603,14.691742 10.300064,13.791764 10.200058,12.992782 10.100059,12.692784 9.800064,12.392787 9.5000619,12.192793 8.6010608,11.592797 7.4010648,11.393811 6.1020664,11.393811z M16.496055,1.4989818C15.597055,1.4989816 14.697055,1.4989816 13.798054,1.598986 11.299064,1.698975 9.1000603,1.698975 6.8020662,1.9989726 5.7020654,3.6979481 5.003065,5.7969099 4.3030685,7.8958717 11.99906,7.9948693 19.894049,7.9948693 27.690044,7.8958717 27.190044,6.1968966 26.690046,4.7969275 25.991041,3.1979566 25.791044,2.997948 25.391043,1.9989727 25.091049,1.8989684 24.991043,1.7989794 24.691048,1.8989684 24.392044,1.7989796 21.993051,1.698975 19.195051,1.4989816 16.496055,1.4989818z M16.696052,2.7739588E-10C18.29505,-1.2416422E-07 19.894049,0.20000856 21.393047,0.29999776 23.09205,0.49999105 24.891045,0.69999971 25.891043,1.6989749 26.191046,1.9989727 26.490042,2.4989639 26.690046,2.9979478 27.49004,4.2979284 28.090046,5.7969099 28.689045,7.3958808 28.789043,5.9969035 31.78804,5.8968988 31.987038,7.2958766 32.087036,7.7958675 31.588035,8.0948582 31.188042,8.2948666 30.78804,8.3948556 30.188043,8.4948607 29.789041,8.3948556 29.489038,8.2948666 29.089037,7.9948693 28.989038,8.1948624 28.88904,8.2948666 29.189043,8.4948607 29.289041,8.5948497 29.689043,8.9948512 29.989038,9.2948495 30.38804,9.6948357 30.78804,10.19382 31.388039,10.793816 31.588035,11.393811 31.78804,12.092789 31.588035,13.29278 31.488037,13.991757 31.388039,14.791746 31.388039,15.690733 31.28804,16.490722 31.088035,18.988679 29.789041,20.487645 27.690044,21.08764 26.990042,21.287633 26.191046,21.287633 25.291044,21.387624 23.792045,21.487628 22.293047,21.587632 20.69405,21.587632L20.594051,21.587632 11.699057,21.587632 11.599058,21.587632C10.000061,21.587632 8.3010653,21.487628 6.8020662,21.387624 5.9020661,21.287633 5.1030668,21.287633 4.403067,21.08764 2.3040701,20.487645 1.0050718,19.088668 0.80507118,16.490722 0.80507124,15.690733 0.60507065,14.791746 0.60507089,13.991757 0.5050723,13.192776 0.40507013,12.192793 0.60507089,11.4938 0.80507124,10.793816 1.3050706,10.293824 1.7040683,9.7938338 2.2040681,9.2948495 2.7040674,8.894847 3.1040686,8.3948556 2.8040696,8.1948624 2.6040691,8.3948556 2.3040701,8.4948607 1.3050706,8.4948607 -0.094929334,8.1948624 0.0050729644,7.1958872 0.20507339,5.9969035 3.1040686,5.9969035 3.3040689,7.2958766 3.9030675,5.7969099 4.403067,4.197939 5.3020681,2.8979588 5.5020646,2.4989639 5.8020676,1.9989727 6.1020664,1.6989749 7.1010622,0.69999971 8.6010608,0.49999105 10.300064,0.40000196 11.199057,0.29999765 11.99906,0.20000856 12.898061,0.20000837 13.798054,0.20000856 14.697055,0.10000421 15.597055,0.10000418 15.996056,-1.2416422E-07 16.296053,-1.2416422E-07 16.696052,2.7739588E-10z"/>

58. Bus

<rating:SfRating Path="M24.799996,18.100006C23.000008,18.100006 21.500008,19.400009 21.500008,20.900009 21.500008,22.5 23.000008,23.700012 24.799996,23.700012 26.599986,23.700012 28.099986,22.400009 28.099986,20.900009 28.099986,19.300003 26.599986,18.100006 24.799996,18.100006z M5.6999533,18.100006C3.8999651,18.100006 2.3999644,19.400009 2.3999644,20.900009 2.3999644,22.5 3.8999651,23.700012 5.6999533,23.700012 7.5000031,23.700012 9.0000036,22.400009 9.0000036,20.900009 8.899967,19.300003 7.5000031,18.100006 5.6999533,18.100006z M3.7999893,5.5L3.7999893,15.200012 25.899974,15.200012 25.899974,5.5z M8.399967,1.7000122C7.399966,1.7000122,7.5000031,4,8.399967,4L21.799996,4C23.19996,4,23.000008,1.7000122,21.799996,1.7000122z M0,0L30.299998,0 30.299998,5.4000092 30.299998,22.700012 30.299998,28.200012 28.00001,28.200012C28.00001,28.200012 28.099986,32 24.500008,32 20.799996,32 21.000008,28.200012 21.000008,28.200012L15.299993,28.200012 15.000006,28.200012 9.2999914,28.200012C9.2999914,28.200012 9.399967,32 5.79999,32 2.0999766,32 2.2999888,28.200012 2.2999888,28.200012L0,28.200012 0,22.700012 0,5.4000092z"/>

59. Tram

<rating:SfRating Path=" M4.2000038,31L21.199971,31C21.499959,31 21.699971,31.199982 21.699971,31.5 21.699971,31.799988 21.499959,32 21.199971,32L4.2000038,32C3.9000167,32 3.700005,31.799988 3.700005,31.5 3.700005,31.199982 3.9000167,31 4.2000038,31z M20.599998,22.599976C19.699975,22.599976 18.999963,23.299988 18.999963,24.199982 18.999963,25.099976 19.699975,25.799988 20.599998,25.799988 21.499959,25.799988 22.199969,25.099976 22.199969,24.199982 22.199969,23.299988 21.499959,22.599976 20.599998,22.599976z M4.8000395,22.599976C3.9000167,22.599976 3.2000059,23.299988 3.2000059,24.199982 3.2000059,25.099976 3.9000167,25.799988 4.8000395,25.799988 5.7000009,25.799988 6.4000122,25.099976 6.4000122,24.199982 6.4000122,23.299988 5.7000009,22.599976 4.8000395,22.599976z M4.8000395,10.399994L3.9000167,18.299988 21.399984,18.299988 20.599998,10.399994z M0,10.399994L2.2000079,10.399994 2.2000079,15.299988 0,15.299988z M23.099992,10.299988L25.3,10.299988 25.3,15.199982 23.099992,15.199982z M8.1000206,7.0999756L8.1000206,9.1999817 17.199979,9.1999817 17.199979,7.0999756z M9.4999821,0.69998169L11.800026,5.0999756 13.60001,5.0999756 15.99997,0.69998169z M6.4999873,0L18.899987,0 18.899987,0.69998169 16.499969,0.69998169 14.199985,5.0999756 14.899996,5.0999756 14.899996,6 18.899987,6C20.599998,6,21.999957,7.3999939,21.999957,9.0999756L23.599992,25.399994C23.599992,27.099976,22.199969,28.5,20.499961,28.5L4.9000151,28.5C3.2000059,28.5,1.8000452,27.099976,1.8000451,25.399994L3.4000177,9.1999817C3.4000177,7.5,4.8000395,6.0999756,6.4999873,6.0999756L10.49998,6.0999756 10.49998,5.0999756 11.300027,5.0999756 8.9000074,0.69998169 6.4999873,0.69998169z"/>

60. Van

<rating:SfRating Path="M25.400024,21L25.400024,23.700012 28.400024,23.700012 28.400024,21z M3.8000183,20.5L3.8000183,23.200012 6.8000183,23.200012 6.8000183,20.5z M3.7000122,3.6000061L2.3000183,11.800018 29.600006,11.800018 28.200012,3.6000061z M2.5,0L29.5,0 32,13.600006 32,27.5 29.400024,27.5 29.400024,32 25,32 25,27.399994 7.1000061,27.399994 7.1000061,32 2.6000061,32 2.6000061,27.399994 0,27.399994 0,13.600006z"/>

61. Butterfly

<rating:SfRating Path="M1.9706379,1.5620572E-10C2.1706531,-8.4716817E-08,2.2706299,-8.4716817E-08,2.4706447,0.10000744L3.67165,0.30000659C3.6716497,0.30000673 9.574744,2.4010309 11.775761,5.4030672 11.775761,5.4030672 14.377786,9.0051171 15.177846,11.006142L15.277822,11.206141 15.477837,11.206141 15.477837,10.806135 15.3778,10.706135C15.277822,10.606135 15.177846,10.406136 15.177846,10.306129 15.177846,10.106129 15.277822,10.00513 15.3778,9.90513L15.477837,9.805123 13.276819,4.903061 13.476773,4.8030616 15.577815,9.7051236 15.778806,9.7051236C15.878844,9.7051236,15.978821,9.7051236,16.078858,9.805123L18.279877,4.903061 18.479892,5.0030686 16.278813,10.00513 16.37885,10.106129C16.478827,10.206129 16.478827,10.306129 16.478827,10.506136 16.478827,10.606135 16.478827,10.806135 16.37885,10.906142L16.278813,11.006142 16.278813,11.406149 16.578866,11.406149 16.678843,11.206141C17.478841,9.2051169 20.080865,5.6030747 20.080865,5.6030747 22.281945,2.6010381 28.184977,0.50000616 28.184977,0.50000622L29.386042,0.30000659C29.585997,-8.4716817E-08 29.786011,-8.4716817E-08 29.986028,1.5620572E-10 32.28806,-8.4716817E-08 31.987031,3.8020495 31.987031,3.8020495 30.787062,5.103068 30.086003,10.706135 30.086003,10.706135 28.886037,13.607173 23.582927,12.907167 23.582927,12.907167 26.584004,14.308185 28.785998,17.209216 28.785998,17.209216 28.085,24.213309 25.483952,27.515343 25.483952,27.515343 22.481898,29.916375 19.680898,23.313296 19.680898,23.313296 18.879861,21.512271 18.279877,19.711253 17.879847,18.010228L17.77987,17.710221 17.679833,17.410222C17.378863,16.60921,16.978835,15.809204,16.778819,15.508197L16.778819,18.710232C16.778819,19.11024 16.478827,19.411246 16.078858,19.411246 15.678829,19.411246 15.3778,19.11024 15.3778,18.710232L15.3778,15.609196C15.277822,15.709196,14.877793,16.109202,14.377786,17.410222L14.377786,17.510222 14.277809,17.710221C13.87778,19.411246 13.176781,21.31227 12.376783,23.313296 12.376783,23.313296 9.574744,29.916375 6.5737269,27.515343 6.5737269,27.515343 4.0716794,24.213309 3.2716806,17.209216 3.2716809,17.209216 5.472699,14.308185 8.4747532,12.907167 8.4747532,12.907167 3.171643,13.607173 1.9706379,10.706135 1.9706382,10.706135 1.2706166,5.103068 0.069611577,3.8020495 -0.030365108,3.8020495 -0.3303569,-8.4716817E-08 1.9706379,1.5620572E-10z"/>

62. Bear

<rating:SfRating Path="M3.6219788,0.70399866C3.5209961,0.70399854 3.42099,0.70399854 3.3200073,0.80500469 3.3200073,0.80500464 3.0180054,1.3080056 3.3200073,1.4090039 3.5084343,1.409004 4.2277241,1.0548032 4.4001317,1.0105278L4.4123874,1.0084635 4.4003515,1.0014259C4.2823601,0.93069146,3.9234848,0.70399854,3.6219788,0.70399866z M4.9299927,0C5.5339966,2.0925199E-07 6.1369934,0.10099865 6.84198,0.3020039 6.84198,0.30200372 8.4509888,0.20099764 10.363007,1.3080055 10.363007,1.3080056 13.984985,2.2140084 15.09198,2.3140076 15.09198,2.3140073 17.606995,2.0120116 18.311981,1.8110062 18.311981,1.8110065 22.638,0.50300113 26.661987,2.3140076 26.661987,2.3140073 31.893982,3.8230179 31.994995,8.150043 31.994995,8.150043 32.095978,10.061049 31.390991,11.168057L31.592987,11.571059C31.794006,12.07406 31.794006,12.677067 31.794006,13.180069 31.692993,14.18607 31.492004,15.092073 31.190002,15.998084 30.787994,17.507085 30.585999,21.129106 28.674988,21.330112 27.869995,21.43111 27.869995,21.43111 26.763,21.229105 26.763,21.229105 25.253998,20.626106 26.259979,19.821102 26.259979,19.821102 29.277985,18.613094 26.561981,16.098083 26.561981,16.098083 24.751007,14.790077 24.347992,13.58307 23.140991,13.482071 22.033997,13.180069 20.927979,12.979063 19.518982,12.677067 18.613007,13.180069 19.518982,14.690071 19.518982,14.690071 20.324005,18.613094 19.115997,20.4241 19.115997,20.4241 19.21698,22.135116 17.606995,22.034111 17.104004,22.034111 16.199005,22.135116 15.393982,22.034111 15.393982,22.034111 13.583008,21.129106 15.79599,20.525108 16.298981,20.324102 16.399994,19.3181 16.501007,19.117096 16.701996,18.211092 16.199005,17.406087 15.897003,16.601083 15.695984,16.199081 15.595001,15.69608 15.493988,15.193079 15.493988,15.092073 15.393982,14.18607 15.292999,14.086071 15.292999,14.086071 13.682983,12.979063 13.583008,12.375063 13.583008,12.375063 13.381989,17.809089 13.079987,18.010095 13.079987,18.010095 12.375,19.9211 10.664978,20.92811 9.9609985,21.229105 8.6529846,21.028108 7.6470032,21.229105 7.6470032,21.229105 4.9299927,20.827102 7.7469788,19.3181L7.8479919,19.217094C8.0489807,19.217094 9.3569946,19.016096 9.3569946,16.903087 9.3569946,16.903087 7.947998,10.061049 8.552002,8.4520393 8.552002,8.4520393 8.8540039,7.3450389 4.9299927,6.037026 4.9299927,6.037026 3.7229919,5.5340252 2.917999,4.7290206 2.9179993,4.7290206 1.6099854,3.9240163 0.50299078,3.8230181 0.50299072,3.8230179 0,3.1190119 0,2.4150136L0,2.3140076C0.20098877,2.3140073 0.40197754,2.2140084 0.60400397,2.0120118 0.80499268,1.8110065 0.80499268,1.509003 0.70397955,1.3080055L0.80499279,1.3080055C0.90499878,1.1070081 1.1069946,1.0060021 1.3079835,0.9060031 1.3079834,0.9060031 2.8169861,2.0925199E-07 4.9299927,0z"/>

63. Cat

<rating:SfRating Path="M20.344451,11.600006C19.744452,11.600006 19.344451,12 19.344451,12.600006 19.344451,13.199997 19.744452,13.600006 20.344451,13.600006 20.944449,13.600006 21.344451,13.199997 21.344451,12.600006 21.344451,12 20.844451,11.600006 20.344451,11.600006z M15.444448,11.400009C14.84445,11.400009 14.444448,11.800003 14.444448,12.400009 14.444448,13 14.84445,13.400009 15.444448,13.400009 16.044448,13.400009 16.444449,13 16.444449,12.400009 16.444449,11.800003 15.944448,11.400009 15.444448,11.400009z M7.3444479,0C7.9444463,0 8.3444479,0.1000061 8.3444479,0.1000061 11.844449,0.69999695 12.944447,2.5 12.944447,2.5 13.044446,5.5 10.944447,4 10.944447,4 7.9444463,1.6000061 4.9444454,4 4.9444454,4 2.4444449,6.6000061 4.7444484,8.8000031 4.7444484,8.8000031L5.0444443,8.6999969C6.6444504,8.1000061 8.6444509,7.8000031 10.944447,8.8000031 10.944447,8.8000031 9.4444463,13.600006 12.344449,16.600006 12.344449,16.600006 14.144453,19.100006 16.844451,18.400009L16.944449,18.400009C15.34445,18 13.344449,16.800003 12.544446,13.100006 12.544446,13.100006 12.344449,9.9000092 13.044446,7.9000092 13.044446,7.9000092 13.344449,7.1000061 13.544446,7 13.544446,7 15.044447,7.6000061 16.644454,10.100006 16.644454,10.100006 17.844451,9.6000061 19.944449,10.400009 19.944449,10.400009 22.244452,8.4000092 22.944449,8.1000061 22.944449,8.1000061 23.744452,7.5 23.844451,8.6000061 23.844451,8.6000061 25.144456,16.300003 19.344451,18.400009 19.344451,18.400009 19.144454,18.5 18.744452,18.5L15.84445,30.699997C15.644453,31.300003 15.044447,31.800003 14.34445,31.800003 13.544446,31.800003 12.844449,31.100006 12.844449,30.300003L12.844449,30 12.844449,29.900009 13.74445,25C13.544446,25.100006 13.24445,25.199997 13.044446,25.199997 12.74445,25.199997 12.444447,25.100006 12.144452,24.900009L12.044446,24.800003 10.944447,30.5C10.844449,31.199997 10.24445,31.800003 9.5444448,31.800003 8.8444479,31.800003 8.2444494,31.300003 8.1444509,30.699997L8.1444509,30.600006 8.1444509,30.5 8.1444509,30.400009 8.1444509,22.5 5.7444489,22 5.7444489,30.199997 5.7444489,30.300003 5.7444489,30.5C5.7444489,31.400009 5.0444443,32 4.14445,32 3.2444482,32 2.5444436,31.300003 2.5444434,30.5 2.5444436,29.699997 -0.055555589,17.199997 0.044443004,16.900009 0.044442907,16.900009 -0.35555109,13.900009 1.2444476,11.400009L1.3444465,11.300003 1.3444465,11.199997C-1.5555559,6.8000031 1.2444477,2.9000092 1.2444476,2.9000092 3.3444467,0.40000916 5.9444459,0 7.3444479,0z"/>

64. Deer

<rating:SfRating Path="M9.1000061,23.5C9.4000244,23.5,9.7000122,23.5,10,23.600006L10.100006,23.600006 10.100006,23.699997C9,25.5 7,27.199997 7,27.199997 6.3000183,28.300003 7.4000244,31.199997 7.7000122,32L6.4000244,32C6,30.300003 5.4000244,27.600006 5.4000244,27.600006 6,26.400009 6.4000244,25.400009 6.5,24.5L6.6000061,24.5C7.1000061,24,8,23.5,9.1000061,23.5z M24.600006,0C26.100006,3.1999969,25.600006,6.6999969,23.600006,8.6999969L23.700012,8.6999969C24,8.6000061 24.200012,8.5 24.200012,8.5 24.600006,7.6999969 25.600006,7.6999969 25.600006,7.6999969 25.800018,8.5 24.600006,9.6000061 24.600006,9.6000061L24.700012,10.600006C25.200012,10.900009 26,11.900009 26,11.900009 25.900024,12.800003 25,12.900009 25,12.900009 24.400024,13 23.200012,13 23.200012,13 22.700012,20.600006 19.800018,25.199997 19.800018,25.199997 19.300018,29.5 19.600006,31.199997 19.800018,32L18.400024,32C18.400024,30.300003 17.800018,24.5 17.800018,24.5 17.200012,25.400009 16.900024,30.400009 16.800018,32L15.700012,32C15.600006,29.900009 15.300018,23.800003 15.300018,23.800003 14.200012,24.199997 12.700012,24 11.400024,23.5L11,23.5C10.900024,23.400009,10.700012,23.400009,10.600006,23.300003L10.5,23.300003 10.400024,23.300003 10.300018,23.300003 10.200012,23.300003C8.6000061,22.900009 7.3000183,23.5 6.5,24 6.3000183,24.100006 6.2000122,24.199997 6.1000061,24.300003L6,24.300003 5.9000244,24.300003C4.6000061,25.199997 3.3000183,25.699997 3.2000122,25.900009 3.1000061,26.400009 3,30.199997 2.9000244,32L1.7000122,32C2.3000183,28.800003 1.6000061,25 1.6000061,25 3.3000183,23.5 4,21.400009 4,21.400009 3.8000183,21.100006 3.4000244,20.400009 3,19.699997L2.9000244,19.699997C1.4000244,20.400009 0,20.699997 0,20.699997 0.5,18.800003 2.7000122,17.199997 2.7000122,17.199997 3.1000061,16.900009 3.5,16.699997 3.9000244,16.400009 5.6000061,15.5 7.4000244,15.199997 7.4000244,15.199997 9,14.800003 15.700012,15.199997 15.700012,15.199997 20.400024,15.199997 19.800018,10.199997 19.800018,10.199997 18.100006,9.5 17.700012,7.5 17.700012,7.5 18.800018,7.6000061 20.400024,8.8000031 20.400024,8.8000031L20.5,8.8000031 20.300018,8.6000061C19.700012,8 19.200012,7.3000031 18.900024,6.5 18.100006,4.6999969 17.900024,2.5 18.400024,0.40000916L18.700012,0.5C18.200012,2.5 18.800018,4.6000061 19.600006,6.1999969 20.200012,7.3000031 21,8.3000031 22,8.8000031L22.100006,8.8000031 22.200012,8.8000031 22.300018,8.8000031C24.800018,7.3000031,25.900024,3.4000092,24.400024,0.1000061z"/>

65. Camel

<rating:SfRating Path="M12.930873,0L13.331869,0C14.233836,0.099999062 15.436824,0.70199945 16.238817,1.2030015 16.940834,1.6040043 19.54676,2.6060084 20.148803,3.2080162 20.849783,3.9090162 21.651775,6.0150295 23.155725,5.8140245 24.057752,5.7140256 24.358713,4.3100191 24.659734,3.3080154 25.059692,2.2050053 25.26074,1.7040034 25.360715,0.50100227 25.861684,0.60100105 26.463729,0.19999804 27.064674,0.30099665 27.26572,0.30099647 27.465669,0.50100204 27.766691,0.60100105 29.470649,1.1030024 32.277624,0.30099647 31.976661,2.5060094 31.776653,2.5060094 30.673639,2.3060113 30.473629,2.205005 29.971681,2.3060113 31.475631,2.7070068 31.375656,3.0070113 30.673639,3.2080162 30.473629,3.0070113 29.971681,3.3080154 29.270641,3.6090117 29.069654,4.5110165 28.167688,4.711022 27.766691,6.9170347 26.76469,8.6210376 24.959718,9.7240477 24.358713,10.024045 22.052772,10.22505 21.651775,10.22505 20.148803,10.325049 20.549799,14.134066 20.849783,15.538073 20.949758,16.23908 21.55174,18.244086 21.55174,18.545091 21.651775,19.8481 21.952735,20.851102 22.553741,21.552102 23.055749,22.254109 23.957716,22.354108 24.458747,23.256114 23.656755,23.45711 22.353733,23.657117 21.55174,23.357112 21.55174,23.156114 21.050769,20.450099 20.549799,19.347097 20.148803,18.545091 18.844802,13.032063 17.942775,11.428051 17.140844,11.929053 16.639812,12.831058 16.038806,13.733063 15.536859,14.535069 14.534857,17.041078 14.434822,17.242084 14.233836,17.944083 13.532856,18.345086 13.231834,18.946094 12.930873,19.447097 12.529877,20.349101 12.529877,21.151099L12.529877,22.354108C12.529877,22.855109 13.030847,23.056115 13.131859,23.45711 12.228856,23.557117 10.925892,23.557117 10.424923,23.156114 10.524896,22.555106 11.727885,20.049096 12.028906,19.24709 12.329867,18.345086 12.930873,16.039075 13.131859,15.738078 13.83284,14.535069 14.133861,13.032063 14.734868,11.829054 14.634832,11.929053 13.932875,11.728056 12.529877,11.328052 11.727885,11.127054 9.7229038,10.826051 8.4199415,11.428051 7.3169275,11.929053 6.9159318,13.433066 6.7159219,13.934068 6.5149355,14.636067 6.4149609,16.139081 6.3149257,17.142085 6.2149511,19.147092 6.7159219,21.953105 7.7179237,22.555106 8.2199321,22.855109 8.9209123,22.655112 8.9209123,23.45711 8.1189199,23.45711 7.2169533,23.657117 6.4149609,23.45711 6.3149257,22.154111 5.8139554,20.650098 5.3129845,19.347097 5.0119629,18.545091 4.4099804,17.342082 4.3099452,16.640082 4.3099452,16.23908 4.6109667,14.836073 4.8109766,13.934068 4.5109926,14.235065 4.0089846,14.535069 3.8089748,14.836073 2.8059962,16.039075 2.0040041,17.643087 2.0040038,19.648093 2.0040041,20.049096 2.1050158,20.349101 2.0040038,20.750104 1.9040295,21.252105 1.402998,21.452104 1.3030236,21.953105 1.2029883,22.354108 1.402998,22.555106 1.1020371,23.056115 0.1000354,23.056115 0,22.054103 0,21.051101 0.1000354,20.851102 0.9020276,19.948098 1.0020022,19.347097 1.1020374,18.645089 1.1020374,17.843083 1.1020371,17.142085 1.0020019,16.440078 0.9020276,15.638071 1.0020022,15.137069 1.1020374,14.535069 2.6059864,13.533065 3.0069826,13.132062 3.908949,12.129059 4.5109926,10.726051 4.6109667,8.922042L4.6109667,8.8210431 4.5109926,7.9190384C4.4099804,7.4180365 4.3099452,6.9170347 4.3099452,6.3150264 3.507953,6.6160303 3.507953,7.7190328 3.507953,8.8210431 3.507953,10.927049 2.405,11.829054 1.0020022,12.831058 0.80199217,12.530062 1.5030335,12.029059 1.70402,11.829054 3.0069824,10.927049 2.6059864,9.0220404 2.7059606,7.31803 2.8059962,5.8140245 3.8089748,5.4130216 4.9119888,4.9120198 5.5129333,4.3100191 5.612969,3.7090183 6.2149511,3.3080154 7.1169177,2.7070068 10.223875,1.002004 10.925892,0.60100105 11.326889,0.19999804 12.028906,8.9426806E-08 12.930873,0z"/>

66. Frog

<rating:SfRating Path="M28.776301,13.482967C27.066284,13.482967 23.444245,14.287965 19.016199,19.921951 19.016199,19.921951 24.752259,13.884966 29.883313,13.683967 29.883313,13.582967 29.481309,13.482967 28.776301,13.482967z M4.326045,2.5149937C3.9240408,2.5149937 3.6220379,2.7169933 3.5210371,3.0189924 3.320035,3.4209914 3.7230387,4.0249898 4.326045,4.3269892 5.0310526,4.6279886 5.7350597,4.5279887 5.9360619,4.0249901 6.137064,3.6219912 5.7350597,3.0189924 5.1310539,2.7169933 4.8290501,2.6159935 4.5280476,2.5149937 4.326045,2.5149937z M6.2380648,0C6.8420715,0 7.4450779,0.30199909 7.9480834,1.2069969 7.9480834,1.2069969 10.967115,1.8109956 12.677133,2.8169928 12.677133,2.8169928 15.29416,3.9239902 16.602174,4.2259898 16.602174,4.2259896 19.821208,3.3199916 21.632227,5.8359857 21.632227,5.8359857 26.66328,7.0429826 28.977304,9.3569767 28.977304,9.356977 30.990325,10.161975 28.977304,12.17497L29.279307,13.180968C29.279307,13.180968 33.908356,13.482967 31.090326,17.104959 31.090326,17.104959 28.575299,20.42495 26.864282,21.833946 26.864282,21.833946 20.526215,25.455937 16.501173,25.254939L16.602174,24.348941 13.080137,24.650939 16.400172,23.342943 13.684143,23.040944 16.501173,22.336946C16.501173,22.336946 12.979136,20.32495 17.708186,16.601959 17.708186,16.601959 15.193159,16.701959 13.583142,15.896961 13.583142,15.896961 12.074126,18.211955 9.659101,19.619952 9.659101,19.619952 8.0490842,21.229948 3.5210371,19.418953L5.9360619,18.814954 4.9300518,17.708957 6.7410707,18.412955C6.7410707,18.412955 8.1500854,17.708957 9.156096,16.29996 9.156096,16.29996 9.9611044,15.695961 8.0490842,13.381967L6.8420715,14.790964 7.2440758,12.777968 4.6280479,13.784966 6.137064,12.07397 4.9300518,11.771971 7.2440758,10.564974C7.2440758,10.564974 6.2380648,9.8599757 5.0310526,9.3569767 4.2260437,8.5519789 0.40200424,4.4269891 0.40200424,4.4269891 0.40200424,4.4269891 0.10000038,4.0249898 0,3.5219913L0,3.4209914 0.10000038,3.5219913C1.0060101,4.2259896,1.9110203,4.5279887,1.9110203,4.5279889L0,2.1129947 0.10000038,2.0119948C0.40200424,1.6099958 0.90500927,1.3079967 1.9110203,1.2069969 3.1190329,1.106997 3.82304,0.90599775 4.5280476,0.60399818 5.1310539,0.20099926 5.634059,0 6.2380648,0z"/>

67. Fly

<rating:SfRating Path="M13.767894,9.8228018C13.767895,9.8228018,13.767895,9.9217997,13.866894,9.9217994L13.965893,9.9217994C13.866894,9.9217997,13.767895,9.8228018,13.767894,9.8228018z M24.88081,0L24.979809,0C25.078809,0 25.177808,0 25.277807,0.09899807 25.376806,0.19799519 25.277807,0.29799366 25.177808,0.39699173 23.391821,0.9919796 22.399829,2.2819538 21.705834,3.571928 21.605835,3.9689198 21.506835,4.3659115 21.506835,4.7629037 21.308837,5.9528799 21.109838,7.1438556 19.720849,8.0368376 19.720849,8.1358356 19.720849,8.1358356 19.819849,8.2358336L19.919848,8.2358336C20.117846,8.3348317 20.216846,8.4338298 20.415844,8.5328274 20.712842,8.5328276 20.91184,8.6328256 21.208838,8.6328254 22.697826,8.9298198 24.284814,9.1288157 25.574804,9.8228018 26.070801,10.021798 26.567797,10.318792 26.963794,10.517788 27.857787,11.013778 28.650781,11.509768 29.742773,11.708764 30.436768,11.90676 31.230762,12.204754 31.925756,12.601746 32.024755,12.700744 32.024755,12.799742 31.925756,12.89874 31.826756,12.89874 31.826756,12.997738 31.726758,12.997738 31.627758,12.997738 31.528759,12.997738 31.528759,12.89874 30.932764,12.601746 30.238769,12.303752 29.543775,12.104756 28.353784,11.90676 27.46079,11.41077 26.567797,10.814782 26.1708,10.517788 25.674804,10.318792 25.177808,10.120796 23.888817,9.5258076 22.300829,9.2278137 20.91184,8.9298198L20.812841,8.9298198C21.308837,9.4258096 21.804833,10.021798 22.300829,10.715784 22.796826,11.013778 23.193823,11.211774 23.689819,11.509768 23.888817,11.608766 23.987817,11.708764 24.185815,11.807762 24.88081,12.303752 25.277807,12.799742 25.674804,13.295732 26.1708,13.89072 26.567797,14.486708 27.360791,14.8837 27.658789,15.081696 27.956786,15.280692 28.253784,15.379689 29.047778,15.776682 29.841772,16.272672 30.337769,16.86766 30.436768,16.966658 30.337769,17.066656 30.238769,17.165654L30.13977,17.165654C30.03977,17.165654 29.940771,17.165654 29.841772,17.066656 29.345776,16.570666 28.650781,16.073676 27.857787,15.677684 27.55979,15.478688 27.261791,15.280692 26.963794,15.180694 26.070801,14.684704 25.574804,14.089716 25.177808,13.494728 24.781811,12.997738 24.384813,12.501748 23.788818,12.104756 23.59082,12.005758 23.49182,11.90676 23.292822,11.807762 23.193823,11.708764 23.094823,11.708764 22.995824,11.608766 23.59082,12.40275 24.086816,13.196734 24.483813,13.692724 26.368798,16.073676 26.666796,20.34059 24.384813,21.134574 22.498828,21.729562 19.62185,19.745602 17.537866,17.760642 17.04187,18.058636 16.545873,18.256632 15.950878,18.256632 15.354882,18.256632 14.858886,18.058636 14.46189,17.760642 12.377905,19.8446 9.4019279,21.928557 7.5159426,21.33257 5.2339602,20.638584 5.5319576,16.272672 7.4169426,13.89072 7.9129391,13.295732 8.607934,12.104756 9.500927,11.013778 9.4019279,11.112776 9.2029295,11.112776 9.10393,11.211774 7.714941,11.90676 6.8219481,12.700744 6.6229486,13.494728 6.1269531,14.38771 5.2339602,15.280692 4.0439692,16.073676 3.9439697,16.173674 3.8449707,16.173674 3.7459707,16.272672 3.5469723,16.37167 3.2499752,16.470668 3.1509752,16.669664 3.0509768,16.768662 2.9519768,16.768662 2.8529778,16.768662L2.6539793,16.768662C2.5549803,16.669664 2.4559813,16.570666 2.5549803,16.470668 2.7539787,16.272672 3.0509768,16.173674 3.2499752,15.974678 3.3489742,15.974678 3.4479733,15.87568 3.5469723,15.87568 4.6389647,15.081696 5.4329586,14.287712 5.9289541,13.494728 6.2269526,12.601746 7.1199455,11.807762 8.706933,11.013778 8.9059315,10.91478 9.10393,10.814782 9.3019285,10.715784 9.500927,10.616786 9.7989249,10.517788 9.9969234,10.41879 10.39392,9.9217997 10.691918,9.5258076 11.088915,9.227814 9.500927,9.1288157 8.0129385,9.4258096 6.8219481,10.021797 6.3259516,10.219794 5.9289541,10.517788 5.4329586,10.715784 4.5399647,11.211774 3.6469717,11.708764 2.4559813,12.005758 1.7609863,12.204754 1.0669918,12.40275 0.4709959,12.799742 0.37199688,12.799742 0.37199688,12.89874 0.2729969,12.89874 0.17399788,12.89874 0.074998856,12.89874 0.074998856,12.799742 -0.024999619,12.700744 -0.024999619,12.601746 0.074998856,12.501748 0.66999435,12.104756 1.5629873,11.807762 2.2579823,11.608766 3.3489742,11.41077 4.1429682,10.91478 5.0359612,10.41879 5.5319576,10.219794 6.0279541,9.9217997 6.5239496,9.7238038 7.81394,9.0288177 9.4019279,8.7318237 10.889916,8.5328274 11.088915,8.5328276 11.286913,8.4338298 11.484912,8.4338298 11.584911,8.3348317 11.68391,8.3348317 11.78291,8.2358336 11.881909,8.1358356 12.080907,8.1358356 12.179907,8.1358356 12.179907,7.9378395 12.278906,7.7398438 12.377905,7.5408478 12.080907,6.8458619 11.385913,6.2508736 10.691918,5.6558857 9.8979239,5.1598959 9.2029295,4.6639056 8.8059325,3.9689198 8.706933,3.6709261 8.706933,3.47293 8.607934,3.2739334 8.607934,3.0759373 8.5089345,2.8779421 8.4089355,2.7779436 8.1119375,2.2819538 7.615942,1.785964 7.0199461,1.2899733 6.9209471,1.1909752 6.7229481,1.1909752 6.6229486,1.0909777 6.3259516,0.89298153 5.9289541,0.79398346 5.7299557,0.4959898 5.6309566,0.39699173 5.7299557,0.29799366 5.8299551,0.19799519 5.9289541,0.09899807 6.1269531,0.19799519 6.2269526,0.29799366 6.4249506,0.4959898 6.7229481,0.59498787 7.0199461,0.79398346 7.1199455,0.89298153 7.3179436,0.9919796 7.5159426,1.0909777 8.1119375,1.5879679 8.706933,2.0839577 9.004931,2.6789455 9.10393,2.8779421 9.2029295,3.0759373 9.2029295,3.2739334 9.2029295,3.47293 9.3019285,3.6709261 9.4019279,3.8699217 9.6989255,4.5639076 10.39392,5.0598979 11.088915,5.6558857 11.68391,6.1518755 12.278906,6.6478658 12.675903,7.2428536 12.973901,6.6478658 13.370898,6.2508736 13.767894,5.9528799 12.179907,5.7548838 12.675903,5.1598959 13.370897,4.5639076 13.171899,4.4649096 13.0729,4.2669134 13.0729,3.9689198 13.0729,3.47293 13.568896,3.1749353 14.263891,3.1749353L14.560889,3.1749353C14.957886,2.5799475 15.354882,2.2819538 15.950878,2.7779436 16.644873,2.3809519 16.94287,2.5799475 17.339867,3.1749353L17.736864,3.1749353C18.430859,3.1749353 18.926855,3.571928 18.926855,3.9689198 18.926855,4.1669159 18.728857,4.4649096 18.529859,4.5639076 19.026855,5.1598959 19.323852,5.5568876 18.728857,5.7548838 18.529858,5.9528799 18.33186,5.9528799 18.033862,6.0528779 18.629858,6.5488677 19.026855,7.0448575 19.323852,7.5408478 20.415844,6.7468638 20.613842,5.7548838 20.712842,4.6639056 20.812841,4.2669134 20.812841,3.8699217 21.010839,3.47293 21.804833,2.0839577 22.895825,0.69498539 24.88081,0z"/>

68. Cow

lt;rating:SfRating Path="M5.9088897,0C6.1088866,7.3422598E-08 6.6088862,0.10000616 6.9088892,1.8990018 6.9088892,1.8990019 8.3078832,2.9980008 10.907888,2.9980011 10.907888,2.9980008 20.804879,2.9980008 24.503882,1.8990018 24.503882,1.8990019 29.802876,0.3000031 31.102878,4.9960015 31.102878,4.9960015 31.102878,5.1959984 31.202868,5.4960015L31.202868,5.5960076C31.202868,5.5960076 31.701877,10.492004 31.402881,11.990996 31.402881,11.990996 32.601869,13.490004 31.60187,15.488005 31.60187,15.488005 30.202868,15.089003 30.902881,12.290999 30.902881,12.290999 31.102878,9.4930107 30.902881,7.9940026L30.902881,8.0940087C30.702868,8.6930077 30.502871,9.2929985 30.102878,9.8919976 30.102878,9.8919976 29.002873,12.690001 28.902883,14.689009L28.70287,19.684995 28.102879,21.284009 26.50388,21.284009C26.50388,21.284009 26.703877,20.184995 27.303883,19.885007 27.303883,19.885007 27.50388,16.486997 27.103871,15.988005 27.103871,15.988005 26.303883,17.587003 26.303883,18.986005L25.603873,20.583997 24.403876,20.583997C24.403876,20.583997 24.703879,19.785001 25.103873,19.484998 25.103873,19.484998 25.503882,17.486997 25.403876,15.587996 25.403876,15.587996 24.003882,14.189009 23.504874,12.790007 23.504874,12.790007 19.904885,15.488005 13.506878,13.988997 13.506878,13.988997 12.706891,18.885999 12.906888,19.984998L12.406888,21.384 10.807882,21.384C10.807882,21.384 11.207883,20.583997 11.707883,20.184995 11.707883,20.184995 11.107884,15.788008 10.807882,15.587996 10.807882,15.587996 10.307882,19.684995 10.407888,19.984998 10.507887,20.285001 10.007887,20.884 10.007887,20.884L8.7078847,20.884C8.7078847,20.884 9.1078853,20.285001 9.5078868,19.984998 9.5078868,19.984998 9.8078822,15.988005 9.5078868,14.889006 9.5078868,14.889006 6.4088897,12.790007 5.8088836,9.0930016 5.6088866,8.5930016 5.4088902,8.3939965 5.1088871,8.2940056 4.4088906,7.8939965 3.4098903,7.6939995 2.9098906,6.8950035 2.9098906,6.8950035 0.40989183,6.6950066 0.10988902,5.9950096 0.10988893,5.9950096 -0.4891098,4.8960106 1.1098887,4.0969999 1.1098885,4.0969999 3.9098901,2.5980069 4.1088876,1.299011 4.1088876,1.2990111 4.7088856,0.20001225 5.8088836,0.99900834 5.8088836,1.098999 6.0088882,0.40000917 5.9088897,0z"/>

69. Crab

<rating:SfRating Path="M19.499915,26.1C19.499915,26.1 22.699901,29 22.099903,32 22.099903,32 19.699914,28.3 18.19992,27.9z M21.699904,24.1C21.699904,24.1 24.799891,26.7 27.599879,26.1 27.599879,26.1 24.899891,29.2 20.099912,25.8 20.099912,25.8 20.899908,24.2 21.699904,24.1z M6.7999701,22.3L6.8999696,24.6C5.3999763,24.2 1.3999939,25.9 1.3999939,25.9 2.4999886,22.9 6.7999701,22.3 6.7999701,22.3z M29.999868,21.5C29.999868,21.5,27.199881,27.1,22.299902,23.6L24.599892,22.2C24.699892,22.2,27.49988,23.5,29.999868,21.5z M0,17.8C1.9999914,19.9 5.9999738,19.4 5.9999738,19.4 6.5999708,19.9 6.399972,21.7 6.399972,21.7 0.49999809,21.9 0,17.8 0,17.8z M18.099921,14.2C17.699923,14.2 17.399924,14.5 17.399924,14.9 17.399924,15.3 17.699923,15.6 18.099921,15.6 18.499919,15.6 18.799918,15.3 18.799918,14.9 18.799918,14.6 18.499919,14.2 18.099921,14.2z M13.999938,13C13.59994,13 13.299942,13.3 13.299942,13.7 13.299942,14.1 13.59994,14.4 13.999938,14.4 14.399937,14.4 14.699935,14.1 14.699935,13.7 14.699935,13.4 14.399937,13 13.999938,13z M0.49999809,12.6C1.4999933,15.7,4.5999799,16.1,4.5999799,16.1L5.7999744,18.6C-0.29999924,18.8,0.49999809,12.6,0.49999809,12.6z M14.599936,11L14.899935,11C17.899921,11.1 19.599914,12.8 19.599914,12.8 21.999904,14.4 24.499892,21.5 24.499892,21.5 23.599896,21.6 19.999912,24.9 19.999912,24.9 17.799922,27.5 16.599927,27.8 16.599927,27.8 11.699949,28 7.699966,24.6 7.699966,24.6 7.699966,21.2 5.3999763,15.9 5.3999763,15.9 7.2999678,13.7 12.699944,11.2 12.699944,11.2 13.299942,11.1 13.999938,11 14.599936,11z M21.199907,9.8999996C21.599905,10.4,23.799895,10.8,23.799895,10.8L23.299898,12.5C21.299907,11.2,21.199907,9.8999996,21.199907,9.8999996z M24.458458,7.4987192C27.771192,7.5426264 29.999868,12 29.999868,12 31.999859,19.4 24.899891,21.5 24.899891,21.5L24.599892,19.7C29.099873,16.1 23.899895,12.5 23.899895,12.5 25.999886,7.8000002 21.199907,8.8999996 21.199907,8.8999996 22.399901,7.8999996 23.399898,7.6000004 24.299893,7.5 24.353018,7.4984379 24.405874,7.4980221 24.458458,7.4987192z M15.199933,5.3999996C16.199929,7.1999998 18.899917,6.6999998 18.899917,6.6999998 16.299929,9 13.69994,8 13.69994,8 13.799939,6 15.199933,5.3999996 15.199933,5.3999996z M11.499949,0L11.899948,0C19.599914,0.10000038 19.399915,5.3000002 19.399915,5.3000002 17.399924,3.1000004 15.699931,4.1000004 15.699931,4.1000004 12.799944,5 12.699944,7.8000002 12.699944,7.8000002 10.399954,7 7.8999653,8 7.8999653,8 4.3999805,9.8000002 6.2999725,14.3 6.2999725,14.3L4.7999787,15.5C2.7999878,13.7 2.1999903,10.1 2.1999903,10.1 1.6999922,2.1000004 8.6999617,0.20000076 8.6999617,0.20000076 9.6999574,0.10000038 10.599953,0 11.499949,0z"/>

70. Bug

lt;rating:SfRating Path="M16.351013,22.37C15.447998,22.37 14.645996,23.172002 14.645996,24.075002 14.645996,24.978002 15.447998,25.780995 16.351013,25.780995 17.253967,25.780995 18.057007,24.978002 18.057007,24.075002 18.057007,23.071996 17.253967,22.37 16.351013,22.37z M20.263,15.748999C19.360962,15.748999 18.557983,16.551999 18.557983,17.454999 18.557983,18.356999 19.360962,19.160001 20.263,19.160001 21.166016,19.160001 21.968994,18.356999 21.968994,17.454999 21.968994,16.551999 21.166016,15.748999 20.263,15.748999z M12.138,15.247999C11.234985,15.247999 10.432983,16.05 10.432983,16.953 10.432983,17.856 11.234985,18.658002 12.138,18.658002 13.041016,18.658002 13.843018,17.856 13.843018,16.953 13.742981,15.950003 13.041016,15.247999 12.138,15.247999z M3.7119751,3.5110011C4.4140015,3.5110011 4.9160156,4.1129985 4.9160156,4.7150035 4.9160156,8.727004 6.4199829,10.533004 7.6239624,11.436004L7.723999,11.436004C8.9279785,11.836997 11.435974,13.541998 16.049988,13.541998 19.159973,13.541998 21.266968,12.840002 22.770996,12.339003L22.872009,12.339003C22.971985,12.237997 23.07196,12.237997 23.172974,12.237997 23.372986,12.237997 27.184998,11.135001 27.184998,4.815002 27.184998,4.1129985 27.786987,3.6109996 28.388977,3.6109996 29.091003,3.6109996 29.593018,4.2130046 29.593018,4.815002 29.593018,10.030997 27.385986,12.539 25.679993,13.743002L25.580017,13.743002 25.580017,13.843 25.580017,15.950003 30.795959,15.950003C31.498962,15.950003 32,16.551999 32,17.153996 32,17.755002 31.39801,18.356999 30.795959,18.356999L25.380005,18.356999 25.380005,18.457997C25.278992,18.958997,25.179016,19.460996,24.977966,19.961995L24.977966,20.063001 25.278992,20.162999C27.987976,21.165998 30.896973,23.472997 30.896973,28.188001 30.896973,28.889997 30.294983,29.391995 29.692993,29.391995 28.990967,29.391995 28.489014,28.789998 28.489014,28.188001 28.489014,24.375997 25.880981,22.870999 24.075012,22.37L23.974976,22.37 23.875,22.570996C22.369995,25.078,20.062988,26.983998,17.354004,27.787L14.846985,27.787C12.138,26.983998,9.8309937,25.078,8.3259888,22.570996L8.2260132,22.37 8.0249634,22.469998C6.2199707,23.071996 3.8120117,24.577001 3.8120117,28.287999 3.8120117,28.991002 3.2099609,29.492002 2.6079712,29.492002 1.9060059,29.492002 1.4049683,28.889997 1.4049683,28.287999 1.4049683,23.574002 4.3139648,21.265996 7.0219727,20.262998L7.1220093,20.063001 7.0219727,19.861997C6.8219604,19.360997,6.7210083,18.858998,6.6209717,18.356999L6.6209717,18.257001 1.2039795,18.257001C0.60198975,18.257001 0,17.755002 0,17.052999 0,16.351003 0.60198975,15.849997 1.2039795,15.849997L6.4199829,15.849997 6.4199829,13.743002C4.7149658,12.539 2.5079956,10.030997 2.5079956,4.815002 2.5079956,4.013 3.0100098,3.5110011 3.7119751,3.5110011z M15.950012,0C18.657959,1.8776518E-09,20.765015,1.5050048,20.765015,3.5110011L20.765015,3.6109996 20.86499,3.7119975C22.27002,4.5139995 23.172974,5.6180034 23.172974,7.3229971 23.172974,10.633002 21.567993,12.038 15.950012,12.038 10.33197,12.038 8.7269897,10.633002 8.7269897,7.3229971 8.7269897,5.8180003 9.6300049,4.6139979 10.833984,3.9120021L10.93396,3.8120036 10.93396,3.6109996C11.13501,1.5050048,13.242004,1.8776518E-09,15.950012,0z"/>

71. Dog

<rating:SfRating Path="M1.8969812,6.5870018C2.1959782,6.5870018,2.395977,6.6870022,2.5949745,6.7860022L2.6949739,6.7860022 2.6949739,6.8860016C2.7949734,6.986002,2.8949718,7.0860019,2.8949718,7.1860023L5.4889469,11.277003 17.864829,11.178003 24.550765,15.768004 24.05177,16.966004 24.05177,28.543007 24.05177,28.643007C23.951771,29.441007 23.253778,30.040008 22.355786,30.040008 21.456795,30.040008 20.758801,29.441007 20.658803,28.643007L20.658803,28.543007 20.658803,22.355005C20.658803,22.355005,12.474881,22.255005,8.882915,19.860005L4.4909563,22.655005 3.1939688,28.443007 3.1939688,28.543007C3.0939703,29.341007 2.395977,29.940007 1.5969839,29.940007 0.69899273,29.940007 0,29.241007 0,28.443007 0,28.243007 0,28.144007 0.099998474,27.944007L0.099998474,27.844007 1.1979885,20.359005C1.1979885,20.359005,3.8929625,18.363004,3.6929646,15.369004L0.99798965,8.1840024C0.89899063,7.9840021 0.79899216,7.7840023 0.79899216,7.5850019 0.79899216,7.0860019 1.297987,6.5870018 1.8969812,6.5870018z M22.255787,1.3970003C22.654783,1.3970003,22.953781,1.5970011,23.153779,1.7960005L23.153779,1.8960009 23.153779,1.9960012C23.153779,2.0960007,23.153779,2.0960007,23.253778,2.1960011L24.15177,4.5910015 26.047751,5.5890017 26.047751,5.788002C26.047751,6.0880022 26.347749,6.387002 26.646746,6.387002 26.846744,6.387002 27.045742,6.2870016 27.145741,6.0880022L30.738707,8.084002C30.738707,8.084002,32.335691,8.5830026,31.935696,10.379003L31.237701,12.176003C31.237701,12.176003,30.937704,12.874003,29.840715,12.974003L26.047751,12.874003 25.548756,13.972004 19.061818,9.6810026 21.656793,5.788002 21.257797,2.6950006 21.257797,2.5950012 21.257797,2.295001C21.157798,1.7960005,21.656793,1.3970003,22.255787,1.3970003z M1.1979885,0L1.3979864,0 17.564832,8.6830025C17.76483,8.7820024,17.864829,8.9820023,17.76483,9.1820025L17.564832,9.6810026C17.464833,9.8800025,17.265835,9.9800029,17.065837,9.8800025L0.79899216,1.1980009C0.59899426,1.0980005,0.49899483,0.79800034,0.59899426,0.69900036L0.79899216,0.20000076C0.89899063,0.10000038,1.0979891,0,1.1979885,0z"/>

72. Fish

<rating:SfRating Path="M4.2018349,7.8610336C3.5058265,7.8610336 2.9088185,8.4580523 2.9088185,9.1550471 2.9088185,9.8510643 3.5058265,10.448053 4.2018349,10.448053 4.8988426,10.448053 5.4958508,9.8510643 5.4958508,9.1550471 5.4958508,8.4580523 4.8988426,7.8610336 4.2018349,7.8610336z M12.659947,4.8760325C11.16793,4.8760325 10.072915,5.4730207 10.072915,5.4730207 9.9739149,5.5720202 10.271915,5.7710263 10.271915,5.7710263 13.853963,4.8760325 16.840002,7.6620275 16.840002,7.6620275 17.039003,7.9610402 17.13801,7.6620275 17.13801,7.6620275 15.744987,5.4730207 14.052963,4.8760325 12.659947,4.8760325z M14.749979,0C15.446986,-1.2671717E-07,16.242994,0.29901268,16.341995,1.4930192L16.441995,4.0800077C16.441995,4.0800077,22.412075,5.2740141,24.004099,6.8660332L29.776171,3.6820261C29.776171,3.6820261,32.86022,2.5870191,31.766203,5.9700324L29.875179,9.05504C29.875179,9.05504 32.263212,12.339054 31.467195,15.225086 31.467195,15.225086 30.373178,16.916074 24.900106,11.642059L24.004099,12.239078C24.004099,12.239078 24.303098,16.120079 22.313074,16.120079 22.313074,16.120079 20.42205,15.225086 19.626043,14.030072L16.641002,14.827074C16.641002,14.827074 17.437011,19.105112 13.754963,17.712099 13.754963,17.712099 11.366931,15.921074 10.968922,15.125079 10.968922,15.125079 3.7048266,13.831066 1.3167985,11.941072 1.3167983,11.941072 -0.47522514,10.548059 0.12178312,9.5530592 0.12178289,9.5530592 2.1128104,5.4730207 10.470915,3.5820192L13.256955,0.39801227C13.356954,0.29901268,14.052963,-1.2671717E-07,14.749979,0z"/>

73. Octopus

<rating:SfRating Path="M14.098166,17.345885C14.098166,17.345885,15.594171,20.236866,17.986179,17.545883z M19.083182,11.563923C18.48518,11.563923 17.887178,12.06292 17.887178,12.759915 17.887178,13.358912 18.38518,13.956907 19.083182,13.956907 19.681184,13.956907 20.279186,13.457911 20.279186,12.759915 20.279186,12.06292 19.781185,11.563923 19.083182,11.563923z M13.002162,11.065927C12.30416,11.065927 11.706158,11.663923 11.706158,12.361918 11.706158,13.059914 12.30416,13.657909 13.002162,13.657909 13.700164,13.657909 14.298166,13.059914 14.298166,12.361918 14.298166,11.663923 13.700164,11.065927 13.002162,11.065927z M15.993172,1.3959908C14.796168,1.3959908 9.7121506,1.7939882 8.9151478,7.57695 8.9151478,7.5769498 9.2141495,7.8759478 9.4131498,7.4769505 9.4131498,7.4769505 11.507157,2.7909818 16.192173,1.8939877 16.192173,1.8939877 16.391173,1.4949903 16.192173,1.3959908z M16.192173,0C19.681184,0,22.772194,1.6949887,24.167199,4.2869716L24.2672,4.5859699C24.865201,5.7819617,26.261206,9.2709386,23.071196,13.856908L22.772194,14.155906 22.772194,14.255906C22.273193,15.950894 22.173193,18.242879 25.164203,19.239872 25.164203,19.239872 27.756211,19.738869 28.952215,17.246885 28.952215,17.246885 30.049219,15.252899 28.055212,13.457911 28.055212,13.457911 26.460207,11.862921 28.853215,11.463924 28.853215,11.463924 31.345223,12.361918 31.943225,15.351898 31.943225,15.351898 32.741228,19.937868 28.354213,22.031854 28.354213,22.031854 26.061205,23.227846 23.071196,22.529851 23.071196,22.529851 25.762205,26.517824 28.653214,25.819828 28.653214,25.819828 30.14922,25.420832 30.248219,26.816822 30.248219,26.816822 30.049219,29.109806 25.862205,28.411812 25.862205,28.411812 21.47619,27.21582 18.186179,22.928848 18.186179,22.928848 17.089175,21.632856 15.59417,21.732856L15.49417,21.732856 15.39417,21.732856C14.497167,22.031854 13.799165,22.828848 13.799165,22.828848 10.510154,27.21582 6.1231394,28.311811 6.1231394,28.311811 1.9361248,29.009808 1.7371235,26.716824 1.7371235,26.716824 1.8361244,25.321833 3.3321295,25.71983 3.3321295,25.71983 6.2231388,26.417824 8.9151478,22.430851 8.9151478,22.430851 6.023139,23.028847 3.6311302,21.931854 3.6311302,21.931854 -0.65588379,19.937868 0.042118073,15.351898 0.042118073,15.351898 0.64012146,12.261919 3.1321287,11.463924 3.1321287,11.463924 5.4251366,11.763922 3.8301315,13.457911 3.8301315,13.457911 1.8361244,15.1529 2.9331284,17.246885 2.9331284,17.246885 4.1291323,19.738869 6.7211409,19.239872 6.7211409,19.239872 10.011152,18.14388 9.6121502,15.451898 8.9151478,13.756909L8.8151484,13.55791 8.8151484,13.457911C8.6151476,13.158913,8.4161463,12.660916,8.2171459,12.261919L8.2171459,12.16192 8.2171459,12.06292C7.4191437,10.168933,6.7211409,7.5769498,7.8181448,5.0839664L7.8181448,4.9849669 7.8181448,4.8849679C9.1141491,2.093986,12.40416,0,16.192173,0z"/>

74. Rabbit

<rating:SfRating Path="M21.648985,8.7939641C21.248991,8.7939641 20.849973,9.0939509 20.849973,9.592941 20.849973,9.9929635 21.148985,10.392955 21.648985,10.392955 22.048981,10.392955 22.447998,10.092939 22.447998,9.592941 22.348968,9.0939509 22.048981,8.7939641 21.648985,8.7939641z M15.053971,0.89898257C15.552965,0.89898251 17.35198,1.2990051 20.349972,6.5949699 20.349972,6.5949699 26.146004,6.4949643 27.044992,13.390927 27.044992,13.390927 27.144998,13.789942 26.944986,14.389915L25.146978,13.789942 26.646005,15.089924C26.245979,15.788926 25.345983,16.488904 23.747989,16.887919 23.747989,16.887919 25.146978,24.282874 20.549984,27.480857L20.449978,30.678839 20.449978,30.778845C20.449978,31.377841 19.84997,31.877839 19.150965,31.877839 18.450981,31.877839 17.85198,31.377841 17.85198,30.778845L17.85198,28.279864C17.85198,28.279864,17.85198,27.680867,17.05196,27.580863L13.554975,27.780873C13.554975,27.780873,14.853958,28.279864,15.053971,29.379864L15.053971,31.977845 8.1579607,31.977845C8.1579607,31.977845 4.7609508,32.377835 3.1619485,29.778849 3.1619485,29.778849 1.7629283,30.678839 1.0629451,29.079848 1.0629452,29.079848 -1.0350511,28.179858 0.66392676,26.181882 0.663927,26.181882 1.1629515,24.282874 3.0619424,25.282868 3.0619421,25.282868 4.1609433,15.988907 16.851978,13.390927 16.851978,13.390927 16.352985,11.291938 17.151968,9.3929602 17.151968,9.3929602 12.055948,3.7969789 14.953965,0.9989882 14.853958,0.99898814 14.953965,0.89898251 15.053971,0.89898257z M20.249965,0C22.048981,0,22.447998,5.8959681,22.447998,5.8959681L20.94998,5.6959569C20.849973,4.9969856 18.650963,2.0989889 18.650963,2.0989889 19.150965,0.60000323 19.949978,0.10000563 19.949978,0.10000563 20.049984,0 20.14999,0 20.249965,0z"/>

75. Parachute

lt;rating:SfRating Path="M26.499985,11.199997C24.999985,11.199997,23.699997,12,23.099993,13.199997L22.999987,13.300003 16.499991,28.600006 16.599997,28.699997C16.700003,28.800003,16.800009,28.899994,16.800009,29L29.999981,13.100006 29.899977,13C29.199995,12,27.999983,11.199997,26.499985,11.199997z M18.899983,11.199997C17.300007,11.199997,15.899984,12,15.300009,13.199997L15.200003,13.300003 15.300009,28 15.399984,28C15.700003,28.100006,15.899984,28.199997,16.099997,28.300003L22.499987,13.199997C21.899981,12,20.499987,11.199997,18.899983,11.199997z M11.399987,11.199997C9.8999883,11.199997,8.6000005,12,7.9999954,13.199997L14.099998,28.100006 14.200004,28.100006C14.399985,28,14.700004,27.899994,14.899984,27.899994L14.999991,27.899994 14.899984,13.300003 14.899984,13.199997C14.200004,12,12.899986,11.199997,11.399987,11.199997z M3.8999914,11C2.3000168,11,0.89999325,11.699997,0.20001174,12.899994L13.30001,28.800003 13.399985,28.699997C13.499992,28.600006,13.599998,28.5,13.700004,28.399994L7.6000015,13.399994 7.4999954,13.300003C6.8999897,12.100006,5.4999968,11,3.8999914,11z M15.200003,0C23.499987,0,30.299999,6,30.299999,13.300003L30.299999,13.399994 30.299999,13.600006 30.199993,13.600006 30.199993,13.5 16.999991,29.399994C16.999991,29.600006 17.099997,29.699997 17.099997,29.899994 17.099997,31 16.200003,32 14.999991,32 13.899985,32 12.899986,31.100006 12.899986,29.899994 12.899986,29.600006 12.999992,29.300003 13.099999,29.100006L0,13.199997 0.1000061,13 0.1000061,12.699997C0.30001802,5.6999969,6.9999958,0,15.200003,0z"/>

Refer to the following GIF image.

76. Coffee

<rating:SfRating Path="M25.008985,17.204142C24.885023,19.22412 24.629041,21.3091 24.080028,23.244078 27.098035,22.874087 27.560987,21.794095 27.589002,20.204114 27.614027,18.799121 27.21803,17.714131 25.008985,17.204142z M3.030031,13.979166C3.030031,13.979166 1.7470103,22.469092 8.1699872,27.395041 8.1699872,27.395041 5.2000151,19.174117 6.9589877,13.979166z M0,12.029187L25.122999,12.029187C25.122999,12.889179 25.120008,13.80917 25.104017,14.764162 29.04103,15.424152 30.820999,17.584136 30.820999,20.144109 30.820999,23.094086 28.464002,25.505059 23.167003,25.719062 22.44099,27.270043 21.442028,28.635035 20.072031,29.690026 23.13203,29.925017 25.122999,30.300013 25.122999,30.720015 25.122999,31.430007 19.497995,32.000003 12.562018,32.000003 5.6240263,32.000003 2.0707012E-07,31.430007 0,30.720015 2.0707012E-07,30.300013 1.9879773,29.925017 5.0499906,29.690026 0.0059816551,25.799056 2.0707012E-07,17.644133 0,12.029187z M26.430006,1.4902836C26.802015,1.4912829 27.203992,1.730279 27.266004,2.2002762 27.544996,4.3652566 26.382032,5.7752474 24.343029,6.365238 22.447032,6.9152358 19.476022,6.9552367 18.807016,9.2142103 18.534006,10.1342 17.098032,9.7442043 17.370981,8.8202169 17.97999,6.7752378 19.758005,5.9402464 21.705028,5.480244 23.706005,5.0102551 26.115003,4.8152569 25.779005,2.2002762 25.71803,1.723283 26.057996,1.4882845 26.430006,1.4902836z M22.273998,0.00029942672C22.580028,-0.0077037629 22.893993,0.14429525 23.023998,0.50829032 25.104017,6.3822363 15.117012,4.1172579 14.616035,8.6422174 14.512031,9.5872085 13.021002,9.5972107 13.129035,8.6422174 13.388983,6.2772415 15.146003,5.0922473 17.266,4.3822549 19.031991,3.792264 22.500988,3.4822693 21.588024,0.90828803 21.398021,0.36729276 21.827037,0.012300323 22.273998,0.00029942672z"/>

77. Cheese

<rating:SfRating Path="M24.343038,13.597992C24.011039,13.595978,23.662042,13.669983,23.328042,13.829987L23.321039,13.834991C23.141033,13.894989 22.968044,13.973999 22.788036,14.070984 21.468049,14.819977 20.898044,16.334991 21.528047,17.452972 22.15805,18.572998 23.74903,18.871979 25.076038,18.122986 26.411023,17.372986 26.974025,15.858978 26.344022,14.738983 26.096023,14.307983 25.714034,14.002991 25.256028,13.827972 24.990024,13.681 24.675037,13.600983 24.343038,13.597992z M15.001064,4.7549744C14.697064,4.7579956 14.372068,4.7989808 14.040068,4.8799744 12.712071,5.2070008 11.775078,6.0669861 11.955085,6.7999878 12.135077,7.5329895 13.357072,7.8629761 14.692074,7.5369873 16.020072,7.2109986 16.950061,6.3509827 16.770068,5.617981 16.635061,5.0679932 15.913062,4.7449952 15.001064,4.7549744z M0.296133,3.5099793C2.9521132,11.979981,8.7880891,15.218994,10.671093,16.062988L12.831073,30.056C-0.7688655,21.337982,-0.46887887,8.6059876,0.296133,3.5099793z M32.000005,1.2709963L30.942012,17.448975 14.904064,30.037994 12.699086,15.78598 15.332071,13.809998C15.812064,14.763001 17.132068,15.084991 18.310056,14.523987 19.510049,13.958984 20.095054,12.704987 19.63006,11.723999 19.49505,11.435974 19.278055,11.210999 19.015056,11.041992L23.561044,7.6169739C24.12403,8.4119873 25.331025,8.6549988 26.426023,8.1349793 27.612024,7.5679932 28.204015,6.3129883 27.739021,5.3320008 27.634027,5.1229859 27.492029,4.9440003 27.319024,4.79599z M30.277006,0C26.077026,3.1569825 12.202078,13.595978 11.445077,14.164978 9.7270969,13.384979 3.9901038,10.179993 1.8381192,1.423981L1.7931211,1.2369997 7.8530954,0.9729921 7.8451002,1.0649721C7.8750985,1.9029847 8.9400972,2.5409851 10.237089,2.4979859 11.527078,2.4549866 12.555073,1.7459717 12.525075,0.91198746L12.50208,0.77197276 19.717048,0.45898445 19.695045,0.61999522C19.725044,1.4539795 20.797046,2.0950013 22.087035,2.0509947 23.385034,2.0089722 24.405034,1.2979737 24.382039,0.46298225L24.337026,0.25497441z"/>

78. Candy

<rating:SfRating Path="M4.9696375,16.311769C2.496643,16.317781 0.31558351,16.785762 1.3785861,19.362723 2.464599,19.968734 3.5786275,19.76674 4.4186655,20.376718 6.4836956,21.876699 5.1346785,26.736652 9.4847123,25.892636 11.082756,25.163673 11.445737,23.199679 11.51074,20.938722 11.013724,20.460731 10.567734,19.930739 9.9347302,19.587726 9.1516997,20.267711 8.757713,21.33871 7.4586841,21.501702 6.5336839,20.090741 8.8106924,20.129712 8.6966769,18.799743 8.1537005,18.491733 6.6607,19.487722 6.5576712,18.349736 6.7786824,17.67076 7.8136693,17.804761 8.6966769,17.786756 8.8617178,17.419755 8.2356726,17.009757 8.24672,16.43576 7.278689,16.401763 6.0936757,16.308778 4.9696375,16.311769z M16.914805,13.621801C16.115782,16.354768 12.952777,17.779767 9.5976902,17.223775 11.157708,19.842729 14.149752,22.183702 18.490815,21.2767 18.574799,18.332738 18.99784,14.69979 16.914805,13.621801z M22.768885,7.7678734C20.487851,9.2018758 17.413834,9.8418513 16.801827,12.945815 20.730834,12.994825 22.551903,15.15178 23.331881,18.349736 25.771918,15.928778 25.375916,9.674862 22.768885,7.7678734z M17.364823,5.178918C12.46577,5.1949092 10.022745,7.6668921 8.9217163,11.482852 10.843739,12.372825 13.79379,14.701804 16.464785,13.283823 14.528786,11.159827 15.684807,7.3678847 16.914805,5.8538972 17.055798,5.6799184 17.722798,5.4489037 17.364823,5.178918z M26.466933,1.1109781C25.266905,1.126969 24.25792,2.4319447 23.6699,3.1519364 23.059907,3.8989359 22.568871,4.7989183 22.09389,5.6289245 22.502892,6.2329203 23.042876,6.705906 23.6699,7.0928946 24.101912,6.2869054 24.44591,5.3919278 25.357911,5.0659128 25.573916,5.2629319 25.762944,5.4869281 25.808905,5.8538972 25.5199,6.6528979 24.636893,6.8579122 24.682913,7.9928766 25.312926,8.2358848 26.559952,6.8158899 26.934958,8.1048747 26.550919,8.6968776 25.752934,8.8748837 24.907891,9.0058642 25.192929,9.9968482 25.745915,10.718854 25.808905,11.932828 26.65993,12.897811 30.497018,13.303812 30.875012,11.707825 31.157975,10.511856 29.841979,9.6168481 29.299002,8.5548812 28.728987,7.442896 28.79094,5.6119262 28.622967,4.389927 28.465983,3.2429386 27.871981,1.2819657 26.708941,1.1259618 26.627947,1.1149758 26.546952,1.1099709 26.466933,1.1109781z M26.258923,0L26.708941,0C27.90494,0.30999357 28.854966,1.2039638 29.297965,2.3639523 29.932007,4.0189296 29.383965,6.190898 30.086001,7.8798715 30.633982,9.1958638 31.928982,9.6578637 32.000027,11.032846L32.000027,12.045833C31.360982,13.935792 28.042943,14.190794 26.033944,13.396829 25.993905,20.534705 19.050818,24.421678 12.524731,21.614709 12.376718,23.204684 12.335764,24.239675 11.736757,25.329656 10.755726,27.111646 8.1667019,27.680638 6.3326928,26.342643 5.8856651,26.015651 5.3746721,25.19065 5.094639,24.540666 4.5776645,23.344697 4.4956318,21.874715 3.7436079,21.2767 3.0946123,20.760715 1.7626243,20.741704 1.0416064,20.488715 0.26858581,19.797715 -0.11142416,18.714751 0.028592223,17.111775 1.1456117,15.0338 4.8156434,14.97478 7.7967016,15.422772 6.3816434,7.4148813 13.866789,1.7139669 21.192876,5.0659128 22.380881,2.875939 23.773905,0.89296326 26.258923,0z"/>

79. Cupcake

<rating:SfRating Path="M27.035044,20.609985L25.706009,28.519012C25.706009,30.440002 20.910071,32 14.995058,32 9.0780921,32 4.2841067,30.440002 4.2841067,28.519012L3.1421439,21.717987C3.317131,21.766998 3.497123,21.809998 3.6910917,21.838989 3.8831076,21.867004 4.0811047,21.881989 4.2751345,21.881989 5.2031092,21.881989 5.9991259,21.562012 6.6980977,21.277985 7.2060909,21.072998 7.6841163,20.878998 8.1310744,20.84201 8.2181105,20.835999 8.3050847,20.832001 8.3891301,20.832001 9.5901131,20.832001 10.602072,21.522003 11.775101,22.319 12.320082,22.690002 12.883068,23.071991 13.496102,23.401001 14.532048,23.958984 15.650084,24.229004 16.914055,24.229004 17.60607,24.229004 18.348071,24.145996 19.17906,23.977997 20.466042,23.718994 21.388035,23.002991 22.20401,22.371002 22.479033,22.158997 22.737029,21.959991 23.007046,21.774994 23.788048,21.240997 24.493002,20.981995 25.60701,20.81601 25.753006,20.79599 25.904007,20.778992 26.057021,20.759003 26.354016,20.725006 26.690014,20.68399 27.035044,20.609985z M7.2981314,4.8160095C8.1421218,4.8049927 8.9681067,5.0599976 9.720118,5.6470032 11.95308,7.3880005 12.105056,10.760986 14.951052,10.760986 17.78307,10.760986 17.943043,7.3930054 20.181071,5.6900024 24.569052,2.3500061 29.320008,10.127991 29.320008,13.796997 29.320008,15.23999 29.111023,17.007996 28.113041,18.131012 27.450997,18.875 26.352002,18.867004 25.43001,19.002991 24.251059,19.177002 23.333033,19.470001 22.327057,20.157013 21.200047,20.924988 20.316018,21.894989 18.939072,22.174988 17.258049,22.514008 15.617065,22.550995 14.067084,21.71701 12.093093,20.65799 10.462119,18.822998 8.0340905,19.019012 6.5680933,19.136993 5.3701005,20.25 3.8721211,20.024994 2.5161092,19.820984 1.8030996,18.877014 1.0681173,17.79599 0.68811431,17.235992 0.51215073,16.630005 0.31213929,15.993011 -1.229846,11.076996 3.2331471,4.8670044 7.2981314,4.8160095z M14.95209,0C17.006035,0 18.671067,1.6659851 18.671067,3.7200012 18.671067,5.7749939 17.006035,7.4400024 14.95209,7.4400024 12.897106,7.4400024 11.232074,5.7749939 11.232074,3.7200012 11.232074,1.6659851 12.897106,0 14.95209,0z"/>

80. Burger

<rating:SfRating Path="M2.0828958,18.889008L29.917918,18.889008 29.917918,22.449 2.0828958,22.449z M10.487925,11.233014C12.553904,11.220013 14.56489,13.395975 15.999888,12.045025 17.581919,10.554975 20.844919,12.790019 22.274912,12.790019 23.702891,12.790019 25.273936,11.598004 27.703928,11.332989 30.131907,11.067976 30.417918,13.833962 31.559946,14.561989 32.703928,15.290991 31.416941,16.665013 29.988901,17.634005 29.050913,18.26999 27.128916,16.819003 26.241892,15.873997L26.237925,15.869969 26.240916,15.866978C26.423899,15.57102 26.345896,15.314977 25.988901,15.174964 25.63093,15.03501 25.747935,15.317968 26.121897,15.741979L26.237925,15.869969 26.177927,15.957005C25.682932,16.595006 24.041941,17.376986 21.416941,17.598971 17.415903,17.936005 17.13093,15.770971 17.13093,15.770971 17.13093,15.770971 16.13093,16.069005 12.702891,17.295993 9.2739356,18.52298 7.9879248,15.621984 7.9879248,15.621984 7.9879248,15.621984 5.9869483,16.962985 3.1309302,17.260958 0.27393559,17.558993 2.416941,15.920018 1.1298926,14.876013 -0.15508052,13.833962 -0.58305904,14.131019 1.1298926,12.194988 2.8449195,10.257003 4.1309302,12.194988 4.1309302,12.194988 4.1309302,12.194988 7.5589087,11.895977 9.845896,11.314007 10.059946,11.259991 10.273936,11.234967 10.487925,11.233014z M15.944895,0C22.142893,-1.0193253E-07,27.402903,2.3309898,29.917918,5.7499906L29.917918,9.960982 2.0828958,9.960982 2.0828958,5.7499906C4.5979102,2.3309898,9.746897,-1.0193253E-07,15.944895,0z"/>

81. Doughnut

<rating:SfRating Path="M29.97699,11.942003C30.627991,11.949999,31.241028,12.098008,31.798035,12.322007L31.962036,12.392015 31.953003,12.486985C31.325012,18.473977 24.423035,23.189 16,23.189 7.8530273,23.189 1.1290283,18.777993 0.12902832,13.072006L0.10900879,12.947983 0.32299805,12.863022C0.69403076,12.728013 1.1260376,12.63701 1.5960083,12.658982 2.651001,12.710984 3.6619873,13.319016 4.6010132,14.467025 7.6140137,18.150004 9.5220337,17.413005 11.054016,16.821025 11.197021,16.765971 11.338989,16.710979 11.47998,16.660991 13.132996,16.069989 16.083984,16.09599 17.419983,18.558023 17.442993,18.613015 18.01001,19.897988 19.346008,20.017005 19.411011,20.022987 19.476013,20.025977 19.541992,20.025977 21.04303,20.025977 22.794983,18.523965 24.754028,15.556012 26.337036,13.158005 28.093994,11.942003 29.97699,11.942003z M16,6.5410081C12.679016,6.5410081 9.9860229,8.0950223 9.9860229,10.010975 9.9860229,11.926989 12.679016,13.480026 16,13.480026 19.320984,13.480026 22.014038,11.926989 22.014038,10.010975 22.014038,8.0950223 19.320984,6.5410081 16,6.5410081z M16,0C24.837036,-1.1221346E-07,32,5.191034,32,11.595018L31.999023,11.647997 31.939026,11.62401C31.348022,11.400011 30.708008,11.254992 30.039001,11.246996 27.880981,11.225023 25.910034,12.541001 24.174011,15.17198 21.819031,18.738992 20.283997,19.390969 19.414001,19.32499 18.492004,19.246987 18.062012,18.291972 18.044983,18.254985 16.488037,15.379988 13.125,15.333967 11.246033,16.006024 11.098999,16.058026 10.952026,16.114972 10.804016,16.171979 9.3439941,16.738017 7.8339844,17.319987 5.1390381,14.027022 4.0709839,12.720994 2.8900146,12.027024 1.6309814,11.963976 1.0629883,11.934984 0.54699707,12.038011 0.10498047,12.196031L0.023986816,12.228013 0.020996094,12.191026C0.007019043,11.994005 0,11.795031 0,11.595018 0,5.191034 7.1630249,-1.1221346E-07 16,0z"/>

82. Cake

<rating:SfRating Path="M31.575012,19.010061L31.219971,24.517019 6.3109741,24.716007 4.6300049,19.75505z M32,12.412107L31.651001,17.812072 4.2310181,18.56907 2.3359985,12.982109C12.327026,14.407101,26.648987,13.024117,32,12.412107z M13.682007,2.0002048L31.580017,11.192131C25.572021,11.823122,11.765015,13.053108,2.7249756,11.825121L5.9719849,8.9141495C6.6389771,9.4481423 7.4829712,9.7701304 8.4039917,9.7701304 10.549988,9.7701304 12.288025,8.0311463 12.288025,5.8851674 12.288025,5.1161764 12.062012,4.4021781 11.676025,3.799186z M1.7849731,0.00022094523C3.9299927,0.026221808,6.0369873,2.1772053,6.934021,3.2211878L7.0599976,3.1441925C8.5239868,2.3781924 10.330017,2.9431901 11.096008,4.4061759 11.862,5.8691614 11.296997,7.6731474 9.8339844,8.4401391 8.3709717,9.2061398 6.565979,8.6421492 5.8010254,7.1791632 5.2540283,6.1341584 5.3880005,4.9171732 6.039978,4.0261891 5.0789795,2.9181964 2.5009766,0.287206 0.67498779,1.536204L0,0.54921264C0.58099365,0.1522126,1.184021,-0.006782684,1.7849731,0.00022094523z"/>

83. Camera

<rating:SfRating Path="M16.199967,8.1999993C19.599988,8.1999993 22.399972,11.000001 22.399972,14.399995 22.399972,17.799996 19.599988,20.599999 16.199967,20.599999 12.800007,20.599999 10.000021,17.799996 10.000021,14.399995 10.000021,13.899995 10.099996,13.299997 10.199972,12.799997 10.699972,14.000001 11.899982,14.799997 13.300006,14.799997 15.199967,14.799997 16.699965,13.299997 16.699965,11.399995 16.699965,10.000002 15.899978,8.7999978 14.699968,8.2999978 15.199967,8.1999993 15.699967,8.1999993 16.199967,8.1999993z M16.199967,5.6999998C11.399983,5.6999998 7.5000235,9.6000009 7.5000235,14.399995 7.5000235,19.199997 11.399983,23.099999 16.199967,23.099999 21.00001,23.099999 24.89997,19.199997 24.89997,14.399995 24.89997,9.6000009 21.00001,5.6999998 16.199967,5.6999998z M3.200009,5.4000006C2.4999976,5.4000006 1.999998,5.999999 1.999998,6.5999975 1.999998,7.1999993 2.4999976,7.6999993 3.1000034,7.6999993 3.6999781,7.6999993 4.1999776,7.1999993 4.1999776,6.5999975 4.3000142,5.999999 3.8000147,5.4000006 3.200009,5.4000006z M10.800008,0L21.399974,0C22.399972,4.9414894E-08,23.199959,0.79999911,23.199959,1.7999988L23.500008,3.599998 23.500008,3.6999998 32.000001,3.6999998 32.000001,25.499999 0,25.499999 0,3.599998 8.5999982,3.599998 8.5999982,3.4999995 9.0000216,1.7000003C9.0999972,0.79999911,9.8000094,4.9414894E-08,10.800008,0z"/>

84. Fan

<rating:SfRating Path="M4.3999673,11.899994C4.8999678,11.899994 5.3999683,12.199997 5.3999683,12.199997 6.5999819,13 9.3999721,13.099991 9.3999721,13.099991 9.6999599,16.5 12.899976,16.5 12.899976,16.5 12.099987,22.5 8.8999721,21.399994 8.8999721,21.399994 4.2999918,20.099991 3.2999908,15 3.2999906,15 2.7999903,12.399994 3.5999788,11.899994 4.3999673,11.899994z M19.199968,11C22.199972,11 22.399985,13.099991 22.399985,13.099991 23.099997,17.699997 18.899981,20.699997 18.899981,20.699997 15.199966,23.299988 15.399978,20 15.399978,20 15.59999,18.599991 14.599989,16 14.599989,16 17.599993,14.299988 16.300003,11.399994 16.300003,11.399994 17.500017,11.099991 18.399981,11 19.199968,11z M12.899976,10.099991C14.399977,10.099991 15.699966,11.299988 15.699966,12.899994 15.699966,14.399994 14.500013,15.699997 12.899976,15.699997 11.399974,15.699997 10.099985,14.5 10.099985,12.899994 10.199961,11.299988 11.399974,10.099991 12.899976,10.099991z M13.000013,3.0999908C15.09999,3.0999908 16.800003,3.8999939 16.800003,3.8999939 20.899983,5.6999969 18.000017,7.1999969 18.000017,7.1999969 16.699967,7.6999969 14.899978,9.8999939 14.899978,9.8999939 11.899975,8.1999969 10.099985,10.699997 10.099985,10.699997 5.6999566,6.5999908 8.5000078,4.6999969 8.5000078,4.6999969 9.8999731,3.5 11.599986,3.0999908 13.000013,3.0999908z M12.799999,1.5C6.5999819,1.5 1.5999769,6.5 1.599977,12.699997 1.5000013,19 6.5999819,24 12.799999,24 19.000017,24 24.000023,19 24.000023,12.799988 24.000023,6.5999908 19.000017,1.5 12.799999,1.5z M12.799999,0C19.899983,0 25.600001,5.6999969 25.600001,12.799988 25.500025,19 21.000019,24.299988 15.000014,25.299988L14.899978,25.299988 14.899978,29 15.699966,29 15.699966,28.099991C15.699966,28,15.800002,27.899994,15.899979,27.899994L17.699968,27.899994C17.800005,27.899994,17.899981,28,17.899981,28.099991L17.899981,29 20.300007,29C20.69997,29,21.099995,29.399994,21.099995,29.799988L21.099995,32 4.2999918,32 4.2999918,29.799988C4.2999918,29.399994,4.6999556,29,5.0999805,29L7.5999829,29 7.5999829,28.099991C7.5999829,28,7.6999585,27.899994,7.7999951,27.899994L9.5999843,27.899994C9.6999599,27.899994,9.7999965,28,9.7999965,28.099991L9.7999965,29 10.50001,29 10.50001,25.299988 10.399973,25.299988C4.500004,24.299988 -1.4709076E-07,19 0,12.799988 -1.4709076E-07,5.6999969 5.6999566,0 12.799999,0z"/>

85. Telephone

<rating:SfRating Path="M16,9.7999933C14,9.7999933 12.299988,11.500007 12.299988,13.500008 12.299988,15.500009 14,17.200023 16,17.200023 18,17.200023 19.699982,15.500009 19.699982,13.500008 19.699982,11.4 18,9.7999933 16,9.7999933z M16,7.2000168C21.199982,7.2000168,25.399994,11.4,25.399994,16.600015L25.399994,20.800001 6.5999756,20.800001 6.5999756,16.600015C6.5999756,11.4,10.799988,7.2000168,16,7.2000168z M16,0C23.799988,1.6716149E-07 30.299988,2.5000017 31.899994,8.0000046 32,8.1000107 32,8.2000168 32,8.3999995 32,9.2999933 30.399994,9.9000004 28.399994,9.9000004 26.399994,9.9000004 24.799988,9.2000178 24.799988,8.3999995 23.399994,4.8999971 20,4.1000088 16,4.1000088 12,4.1000088 8.5999756,4.8999971 7.1999817,8.3999995 7.1999817,9.2999933 5.5999756,9.9000004 3.5999756,9.9000004 1.5999756,9.9000004 0,9.2000178 0,8.3999995 0,8.2000168 0,8.1000107 0.099975586,8.0000046 1.6999817,2.5000017 8.1999817,1.6716149E-07 16,0z"/>

86. Headphones

<rating:SfRating Path="M28.889999,20.665009L28.889999,20.764999 29.090004,20.665009 28.990005,20.665009z M16.150002,0C23.874001,0,30.094002,6.0190125,30.495003,13.542007L30.495003,13.643005C31.398003,14.345001 32,15.549011 32,16.853012 32,18.35701 31.297005,19.661011 30.194,20.263L30.094002,20.263C29.592003,21.969009,27.183998,27.887009,19.159,29.292007L19.059002,29.292007 19.059002,29.391998C18.758003,30.897003 17.454002,32 15.949001,32 14.144001,32 12.739002,30.596008 12.739002,28.790009 12.739002,26.984009 14.144001,25.580002 15.949001,25.580002 17.253002,25.580002 18.357002,26.281998 18.858002,27.386002L18.959003,27.486008C19.962002,27.285004,23.874001,26.182007,26.382004,23.072006L26.482002,22.972 26.382004,22.972C25.078003,22.871002,23.973999,21.868011,23.973999,20.464005L23.973999,13.041C23.973999,11.636002 25.078003,10.533005 26.482002,10.533005 26.884003,10.533005 27.285004,10.633011 27.686005,10.834 25.479004,6.2190094 21.065002,3.0090027 15.949001,3.0090027 10.532001,3.0090027 5.9180031,6.6210022 3.9120026,11.737L3.9120026,11.837006 4.012001,11.636002C4.413002,11.235001 5.1160011,10.934006 5.8180008,10.934006 7.2220001,10.934006 8.3260002,12.03801 8.3260002,13.442001L8.3260002,20.865005C8.3260002,22.270004 7.2220001,23.373001 5.8180008,23.373001 4.5140038,23.373001 3.4100037,22.37001 3.3100014,20.966003L3.3100014,20.865005 3.2100029,20.865005C1.4040031,20.764999 0,19.060013 0,16.953003 0,15.447998 0.80200195,14.144012 1.9050026,13.442001L2.0060005,13.442001 2.0060005,13.141006C2.507,5.8180084,8.7270012,0,16.150002,0z"/>

87. Game controller

<rating:SfRating Path="M24.200012,9.9000071C23.599976,9.9000071 23.099976,10.600004 23.099976,11.400007 23.099976,12.199995 23.599976,12.900007 24.200012,12.900007 24.799988,12.900007 25.299988,12.199995 25.299988,11.400007 25.299988,10.600004 24.799988,9.9000071 24.200012,9.9000071z M26.599976,6.9999989C26,6.9999989 25.5,7.6999959 25.5,8.4999989 25.5,9.300002 26,9.999998 26.599976,9.999998 27.200012,9.999998 27.700012,9.300002 27.700012,8.4999989 27.700012,7.600005 27.200012,6.9999989 26.599976,6.9999989z M5.7000122,6.100005L5.7000122,8.600005 3.7999878,8.600005 3.7999878,11.100004 5.7000122,11.100004 5.7000122,13.600004 7.5999756,13.600004 7.5999756,11.100004 9.5,11.100004 9.5,8.600005 7.5999756,8.600005 7.5999756,6.100005z M6.7000122,0L25.299988,0C29,1.1649172E-07 32,4.4000086 32,9.9000071 32,15.400006 29,19.799999 25.299988,19.799999 22,19.799999 19.299988,16.400007 18.700012,11.800001L13.299988,11.800001C12.700012,16.300001 10,19.799999 6.7000122,19.799999 3,19.699993 0,15.3 0,9.9000071 0,4.4000086 3,1.1649172E-07 6.7000122,0z"/>

88. Light bulb

<rating:SfRating Path="M12.400003,30C12.800004,30 13.1,30.300018 13.1,30.600006 13.1,31 12.900003,31.300018 12.500001,31.399994L7.2000052,32 7.0999991,32C6.7000052,32 6.4000021,31.700012 6.4000021,31.399994 6.4000021,31 6.5999991,30.700012 7.0000006,30.600006z M14.1,27.399994C14.500002,27.399994 14.800005,27.700012 14.800005,28 14.800005,28.399994 14.600001,28.700012 14.200006,28.800018L5.5000006,29.800018 5.4000021,29.800018C5.0000006,29.800018 4.7000052,29.5 4.7000052,29.200012 4.7000052,28.800018 4.9000021,28.5 5.3000037,28.399994z M14.1,25C14.500002,25 14.800005,25.300018 14.800005,25.600006 14.800005,26 14.600001,26.300018 14.200006,26.399994L5.5000006,27.399994 5.4000021,27.399994C5.0000006,27.399994 4.7000052,27.100006 4.7000052,26.800018 4.7000052,26.399994 4.9000021,26.100006 5.3000037,26z M9.5000011,2.5C5.8000037,2.5 2.9000017,5.5 2.9000014,9.1000061 2.9000017,9.5 3.2000047,9.8999939 3.700005,9.8999939 4.0999986,9.8999939 4.5000006,9.6000061 4.5000006,9.1000061 4.5000006,7.7000122 5.0999991,6.3999939 6.0000006,5.5 6.8000037,4.6000061 8.0000011,4 9.5000011,4 9.9000026,4 10.300004,3.7000122 10.300004,3.2000122 10.300004,2.7000122 9.9000026,2.5 9.5000011,2.5z M9.8000042,0C15.200007,0 19.600001,4.3999939 19.600001,9.7000122 19.600001,13.300018 16.300004,16.600006 16.300004,16.600006 15.500002,17.399994 14.800005,19.100006 14.800005,20.200012L14.800005,20.5C14.800005,21.700012,13.800004,22.600006,12.700006,22.600006L6.9000021,22.600006C5.7000052,22.600006,4.8000037,21.600006,4.8000037,20.5L4.8000037,20.200012C4.8000037,19 4.0999986,17.399994 3.300003,16.600006 3.3000032,16.600006 -1.4722355E-07,13.300018 0,9.7000122 -1.4722355E-07,4.3999939 4.4000017,0 9.8000042,0z"/>

89. Sun

<rating:SfRating Path="M14.255,27.812979C14.853,27.912979 15.352,27.912979 15.95,27.912979 16.548,27.912979 17.047,27.912979 17.645,27.812979L17.645,30.205976C17.645,31.102976 16.947,31.899975 15.95,31.899975 15.053,31.899975 14.255,31.201977 14.255,30.205976z M23.227,25.42098L24.424,27.513979C24.822001,28.311978 24.623,29.307978 23.825,29.806976 23.028,30.205976 22.031,30.005978 21.533,29.208978L20.336,27.11498C21.433,26.71698,22.33,26.11798,23.227,25.42098z M8.473,25.220981C9.3710001,25.918981,10.268,26.51698,11.265,26.915979L9.9689999,29.008978C9.47,29.806976 8.473,30.005978 7.6760001,29.606977 6.878,29.108977 6.6790001,28.111979 7.0780001,27.31498z M27.014999,20.435985L29.209,21.731983C30.006001,22.230983 30.305,23.226982 29.806999,24.024981 29.308001,24.821981 28.311001,25.120981 27.514,24.622981L25.321,23.426982C26.019,22.429983,26.617001,21.432983,27.014999,20.435985z M4.8850002,20.236985C5.283,21.233984,5.7820001,22.230983,6.48,23.127982L4.2860003,24.323981C3.4889998,24.722981 2.4919996,24.522982 1.9940004,23.725982 1.5950003,22.927982 1.8940001,21.930984 2.691,21.532984z M27.712999,14.254989L30.305,14.254989C31.202,14.254989 32,14.952989 32,15.949988 32,16.846987 31.302,17.644987 30.305,17.644987L27.813,17.644987C27.913,17.145987 27.913,16.647987 27.913,16.149988 27.813,15.451988 27.813,14.853989 27.712999,14.254989z M1.6949997,14.254989L4.2860003,14.254989C4.1870003,14.853989 4.1870003,15.451988 4.1870003,16.049988 4.1870003,16.547987 4.1870003,17.046987 4.2860003,17.544987L1.6949997,17.544987C0.69799995,17.644987 0,16.846987 0,15.949988 0,15.052989 0.69799995,14.254989 1.6949997,14.254989z M28.410999,7.2769947C29.009001,7.2769947 29.607,7.5759945 29.906,8.0749941 30.305,8.8719931 30.106001,9.8689926 29.308001,10.367992L27.014999,11.663991C26.617001,10.666992,26.019,9.6699927,25.42,8.7729936L27.712999,7.4769945C27.913,7.3769946,28.112,7.2769947,28.410999,7.2769947z M3.5890002,7.1779947C3.888,7.1779947,4.0869999,7.2769947,4.3860002,7.3769946L6.6789999,8.6729932C5.9809999,9.5699928,5.3829999,10.466992,4.9840002,11.563991L2.691,10.267992C1.9940004,9.7689927 1.6949997,8.7729936 2.0930004,7.9749942 2.4919996,7.4769945 2.9900002,7.1779947 3.5890002,7.1779947z M15.95,5.9809957C21.533,5.9809957 26.019,10.466992 26.019,16.049988 26.019,21.631984 21.533,26.11798 15.95,26.11798 10.367,26.11798 5.881,21.631984 5.881,16.049988 5.881,10.466992 10.367,5.9809957 15.95,5.9809957z M23.327,1.9939985L23.427,1.9939985C23.726,1.9939985 23.925,2.0929985 24.224,2.1929979 25.022,2.6919975 25.221,3.6879969 24.822001,4.4859962L23.427,6.778995C22.529,6.0809956,21.632,5.482996,20.536,5.0839958L21.931,2.8909979C22.23,2.2929983,22.729,2.0929985,23.327,1.9939985z M8.8720002,1.8939981C9.47,1.8939981,10.068,2.1929979,10.367,2.6919975L11.663,4.9839964C10.666,5.3829961,9.6700001,5.9809957,8.7720003,6.5789952L7.4759998,4.2869968C6.9780002,3.4889975 7.2770002,2.4919977 8.0749998,2.0929985 8.3740001,1.8939981 8.5730001,1.8939981 8.8720002,1.8939981z M15.95,0C16.847,0,17.645,0.69799995,17.645,1.6949987L17.645,4.3859968C17.146,4.2869968 16.548,4.2869968 15.95,4.2869968 15.352,4.2869968 14.853,4.2869968 14.255,4.3859968L14.255,1.6949987C14.255,0.69799995,15.053,0,15.95,0z"/>

90. Shopping cart

<rating:SfRating Path="M25.600006,25.600006C27.400024,25.600006 28.800018,27 28.800018,28.800018 28.800018,30.600006 27.400024,32 25.600006,32 23.800018,32 22.400024,30.600006 22.400024,28.800018 22.400024,27 23.800018,25.600006 25.600006,25.600006z M9.6000061,25.600006C11.400024,25.600006 12.800018,27 12.800018,28.800018 12.800018,30.600006 11.400024,32 9.6000061,32 7.8000183,32 6.4000244,30.600006 6.4000244,28.800018 6.4000244,27 7.8000183,25.600006 9.6000061,25.600006z M0,0L5.3000183,0 6.7000122,3.2000122 30.400024,3.2000122C31.400024,3.2000122 32,3.8000183 32,4.8000183 32,5.1000061 32,5.3000183 31.700012,5.6000061L25.900024,16C25.400024,17,24.5,17.600006,23.200012,17.600006L11.400024,17.600006 10,20.300018 10,20.5C10,20.700012,10.200012,20.800018,10.300018,20.800018L28.900024,20.800018 28.900024,24 9.6000061,24C7.8000183,24 6.4000244,22.600006 6.4000244,20.800018 6.4000244,20.300018 6.6000061,19.700012 6.7000122,19.200012L9,15.400024 3.2000122,3.2000122 0,3.2000122z"/>

91. Clipboard

<rating:SfRating Path="M1.0000004,2.6999969L5.2999904,2.6999969 5.2999904,5.2999954C5.2999904,6.0999985,6.0000031,6.7999954,6.7999914,6.7999954L16.000007,6.7999954C16.799995,6.7999954,17.500009,6.0999985,17.500009,5.2999954L17.500009,2.6999969 21.799999,2.6999969C22.399975,2.6999969,22.799999,3.1999969,22.799999,3.6999969L22.799999,31C22.799999,31.599998,22.299999,32,21.799999,32L1.0000004,32C0.39996377,32,2.0614243E-07,31.5,0,31L0,3.7999954C2.0614243E-07,3.1999969,0.50000045,2.6999969,1.0000004,2.6999969z M11.399969,0C12.599982,0,13.500006,0.8999939,13.500006,2L16.000007,2C16.399971,2,16.699959,2.2999954,16.699959,2.6999969L16.699959,5.3999939C16.699959,5.6999969,16.399971,6,16.000007,6L6.7999914,6C6.3999665,6,6.0999787,5.6999969,6.0999787,5.3999939L6.0999787,2.6999969C6.0999787,2.2999954,6.3999665,2,6.7999914,2L9.2999924,2C9.2999924,0.8999939,10.199957,0,11.399969,0z"/>

92. Binoculars

<rating:SfRating Path="M18.701,5.9999995L28.1,5.9999995 32,22.599999 32,30.899999C32,31.2 31.9,31.499999 31.701,31.7 31.5,31.899999 31.201,31.999999 31,31.999999L22,31.999999C21.6,31.999999,21.4,31.599999,21.4,30.899999L21.4,19.3 20,19.3 19.9,19.2C19.6,19.2 19.3,19.099999 19.1,18.8 18.9,18.599999 18.701,18.3 18.701,18z M14.701,5.9999995L17.301,5.9999995 17.301,17.3 14.701,17.3z M3.8999996,5.9999995L13.3,5.9999995 13.3,18.099999C13.3,18.4 13.201,18.7 12.9,18.9 12.701,19.099999 12.4,19.3 12.099999,19.3L12,19.3 10.599999,19.3 10.599999,30.999999C10.599999,31.7,10.4,31.999999,9.8999996,31.999999L1,31.999999C0.70100021,31.999999 0.5,31.899999 0.29999924,31.7 0.10000038,31.499999 0,31.2 0,30.999999L0,22.599999z M18.701,0L25.301,0 25.301,4.6999998 18.701,4.6999998z M7.3999996,0L13.4,0 13.4,4.6999998 7.3999996,4.6999998z"/>

93. CCTV

<rating:SfRating Path="M26.599999,11.100002C25.2,11.100002 24.000001,12.300003 24.000001,13.700003 24.000001,15.100003 25.2,16.300004 26.599999,16.300004 28.099999,16.300004 29.2,15.100003 29.2,13.700003 29.3,12.300003 28.099999,11.100002 26.599999,11.100002z M24.400001,9.4000015C24.7,9.4000018,25.000001,9.4000018,25.2,9.5000019L25.3,9.5000019 27.400001,10.200002 27.500001,10.200002C29.099999,10.600002 30.2,12.000002 30.2,13.700003 30.2,15.700003 28.599999,17.400004 26.500001,17.400004 26.000001,17.400004 25.599999,17.300004 25.099999,17.100004L25.000001,17.100004 23.2,16.500003C23.1,16.500003 23,16.400003 22.900001,16.400003 21.6,15.800004 20.8,14.600003 20.8,13.100003 20.8,11.000002 22.400001,9.4000018 24.400001,9.4000015z M19,7.3000011C18.1,7.3000014,17.3,8.1000016,17.3,9.0000014L17.3,17.000003C17.3,17.900004,18.1,18.700004,19,18.700004L29.7,18.700004C30.599999,18.700004,31.400001,17.900004,31.400001,17.000003L31.400001,9.0000014C31.400001,8.1000016,30.599999,7.3000014,29.7,7.3000011z M3.5999999,0L11.6,0 11.9,0 12.1,0 12.2,0 30.099999,5.8000011 30.3,5.8000011C31.3,6.0000011,32.000001,6.8000013,32.000001,7.6000014L32.000001,17.900004C32.000001,18.900004,30.900001,19.800004,29.599999,19.800004L18.3,19.800004C17.6,19.800004,16.900001,19.500004,16.5,19.100004L13,17.400004 13,20.600004 0,28.900006 0,24.400006 8.9000003,18.800004 8.9000003,15.300004 3,12.500002 2.9000001,12.500002C2.3000002,12.200002,1.9000001,11.600002,1.9000001,10.900002L1.9000001,1.7000003C1.9000001,0.80000019,2.7000003,0,3.5999999,0z"/>

94. Film roll

<rating:SfRating Path="M21,20.699982C19.200012,20.699982 17.700012,22.199982 17.700012,24 17.700012,25.799988 19.200012,27.299988 21,27.299988 22.800003,27.299988 24.300003,25.799988 24.300003,24 24.300003,22.199982 22.800003,20.699982 21,20.699982z M10.300003,20.699982C8.5,20.699982 7,22.199982 7,24 7,25.799988 8.5,27.299988 10.300003,27.299988 12.100006,27.299988 13.600006,25.799988 13.600006,24 13.600006,22.199982 12.100006,20.699982 10.300003,20.699982z M16,14.100006C15,14.100006 14.100006,14.899994 14.100006,16 14.100006,17 14.900009,17.899994 16,17.899994 17,17.899994 17.900009,17.100006 17.900009,16 17.900009,15 17,14.100006 16,14.100006z M25,11.299988C23.200012,11.299988 21.700012,12.799988 21.700012,14.600006 21.700012,16.399994 23.200012,17.899994 25,17.899994 26.800003,17.899994 28.300003,16.399994 28.300003,14.600006 28.300003,12.699982 26.800003,11.299988 25,11.299988z M7,11.299988C5.2000122,11.299988 3.7000122,12.799988 3.7000122,14.600006 3.7000122,16.399994 5.2000122,17.899994 7,17.899994 8.8000031,17.899994 10.300003,16.399994 10.300003,14.600006 10.300003,12.699982 8.8000031,11.299988 7,11.299988z M15.600006,4.6999817C13.800003,4.6999817 12.300003,6.1999817 12.300003,8 12.300003,9.7999878 13.800003,11.299988 15.600006,11.299988 17.400009,11.299988 18.900009,9.7999878 18.900009,8 18.900009,6.1000061 17.400009,4.6999817 15.600006,4.6999817z M16,0C24.800003,0 32,7.1999817 32,16 32,24.799988 24.800003,32 16,32 7.2000122,32 0,24.799988 0,16 0,7.1999817 7.2000122,0 16,0z"/>

95. Bluetooth

<rating:SfRating Path="M12.799973,18.599998L15.69996,21.5 12.799973,24.399994z M12.799973,7.5L15.69996,10.399994 12.799973,13.299995z M10.599981,2.2999954L10.599981,13.299995 5.9999857,8.5999985 4.299993,10.299995 9.9999761,16 4.299993,21.699997 5.8999801,23.399994 10.599981,18.699997 10.599981,29.799995 18.899949,21.5 13.299972,16 18.899949,10.399994z M11.099979,0L11.799975,0C16.999959,0.099998474 19.69995,1.7999954 21.399959,5.0999985 23.099936,8.2999954 24.399951,17.5 22.599936,23.899994 20.799954,30.299995 17.099965,31.899994 11.599978,32L10.799977,32C5.6999836,31.899994 2.899987,29.599998 1.2999997,25.699997 0.39999296,23.699997 0.10000588,21 0,18.199997L0,15C0.10000588,13.099998 0.19999649,11.099998 0.39999293,9.1999969 0.80000113,3.3999939 4.9999881,0.099998474 11.099979,0z"/>

96. Tool

<rating:SfRating Path="M5.5803752,0C7.1813383,0 8.8833761,0.6000061 10.084373,1.8009948 11.785374,3.5029907 12.285377,5.8049927 11.685397,7.9060059L24.094478,20.31601C26.096505,19.714996 28.398524,20.216003 30.099524,21.916992 31.500535,23.317993 32.101552,25.320007 31.901538,27.121002L28.998504,24.118988C27.69753,22.817993 25.496465,22.817993 24.094478,24.118988 22.693467,25.519989 22.693467,27.622009 24.094478,29.02301L26.997514,31.924988C25.195498,32.225006 23.194447,31.625 21.793437,30.123993 20.191436,28.522003 19.591456,26.119995 20.191436,24.118988L7.7823553,11.709015C5.6803512,12.309998 3.3783338,11.80899 1.6773333,10.108002 0.37629925,8.7070007 -0.224718,6.8049927 0.076309212,5.0039978L2.978307,7.9060059C4.2793407,9.2070007 6.4813823,9.2070007 7.8823928,7.9060059 9.2834034,6.605011 9.2834034,4.4030151 7.8823928,3.0020142L4.9803342,0.10000607C5.1803479,0,5.3803615,0,5.5803752,0z"/>

97. Gas pump

<rating:SfRating Path="M4.1999965,2.5L4.1999965,12.300003 17.3,12.300003 17.3,2.5z M2,0L19.699994,0 19.699994,17.199997 22.100003,17.199997 22.100003,24.100006C24.600003,23.900009 26.499997,20.699997 26.499997,16.699997 26.499997,12.5 24.3,8.9000092 21.900006,8.9000092L21.699994,8.9000092 21.699994,7.9000092 21.900006,7.9000092C25.100003,7.9000092 27.8,11.800003 27.8,16.600006 27.8,21.400009 25.199994,25.300003 21.900006,25.300003L20.8,25.300003 20.8,18.400009 19.699994,18.400009 19.699994,28.800003 21.999997,28.800003 21.999997,32 0,32 0,28.900009 2,28.900009z"/>

98. Trophy

<rating:SfRating Path="M24.47601,5.7179999C24.376011,9.9310001 23.57301,12.74 22.57001,14.846 25.580011,12.74 28.389012,10.433 28.890013,5.7179999z M2.5080004,5.7179999C2.9090014,10.433 5.7180023,12.84 8.8270035,14.846 7.8240032,12.74 7.0220032,9.9310001 6.9210024,5.7179999z M15.749007,2.1070004C10.934004,2.1070004 9.0280037,4.1130004 9.0280037,4.8150001 9.0280037,5.5170002 10.934004,7.5240002 15.649007,7.5240002 20.464009,7.5240002 22.26901,5.618 22.26901,4.8150001 22.370009,4.1130004 20.464009,2.1070004 15.749007,2.1070004z M15.749007,0C20.865009,0,23.37301,1.7049999,24.276011,3.21L30.294013,3.21C30.997013,3.21 31.498013,3.7120004 31.498013,4.414 31.498013,11.937 26.783011,15.047 22.87101,17.555 19.762009,19.661 17.856008,21.066 17.856008,23.574L17.856008,25.881001C21.166009,26.282001 23.57301,27.486 23.57301,28.89 23.57301,30.596 20.062008,32.000001 15.849007,32.000001 11.536005,32.000001 8.1250033,30.596 8.1250033,28.89 8.1250033,27.486 10.533004,26.182 13.843006,25.881001L13.843006,23.574C13.843006,21.066 11.937005,19.661 8.8270035,17.555 4.8150015,15.147 0,11.937 0,4.414 0,3.7120004 0.60200024,3.21 1.2040005,3.21L7.222003,3.21C8.025003,1.7049999,10.633004,0,15.749007,0z"/>

99. Setting

<rating:SfRating Path="M15.799988,7.9000244C11.400024,7.9000244 7.7999878,11.5 7.7999878,15.900024 7.7999878,20.300018 11.400024,23.900024 15.799988,23.900024 20.200012,23.900024 23.799988,20.300018 23.799988,15.900024 23.799988,11.400024 20.299988,7.9000244 15.799988,7.9000244z M12.600037,0L15.5,4.1000061 16.900024,4.1000061 17.100037,4.1000061 20.100037,0.20001221 24.600037,2.2000122 23.799988,7.1000061 23.900024,7.2000122C24.200012,7.6000061,24.600037,8,25,8.4000244L25.100037,8.6000061 30.200012,7.9000244 32,12.5 27.700012,15.600006 27.700012,17 31.799988,20.100006 29.799988,24.600006 24.700012,23.700012 24.600037,23.800018 23.900024,24.5 23.700012,24.700012 24.400024,30.100006 19.700012,32 16.700012,27.700012 16.5,27.700012 15.200012,27.700012 14.799988,27.700012 11.5,31.900024 7,29.900024 7.9000244,24.700012 7.7999878,24.600006C7.5,24.400024,7.2999878,24.100006,7.1000366,23.900024L6.9000244,23.600006 1.7999878,24.300018 0,19.700012 4,16.800018 4,16.5 4,14.800018 0,11.700012 2,7.2000122 7,8C7.5,7.5,8,7,8.5,6.6000061L8,1.8000183z"/>

100. Praying hands

<rating:SfRating Path="M30.903999,21.033991C31.402,21.033991,31.801001,21.432991,31.801001,21.831991L32,30.703986C32,31.201987,31.601,31.600987,31.202999,31.600987L28.81,31.002988C28.312,31.002988,27.913,30.603988,27.913,30.205987L27.813,22.52999C27.813,22.030991,28.212,21.63199,28.611,21.63199z M0.99699974,21.033991L3.3889999,21.63199C3.8879995,21.63199,4.1870003,22.030991,4.1870003,22.52999L4.0869999,30.205987C4.0869999,30.703986,3.6890001,31.002988,3.1899996,31.002988L0.79800034,31.600987C0.29899979,31.600987,0,31.201987,0,30.703986L0.19900036,21.831991C0.19900036,21.432991,0.59799957,21.033991,0.99699974,21.033991z M13.857,0C14.654,0,15.551,1.1959991,15.851,2.0929995L15.851,2.1929989C16.15,1.2959995 17.147,0 17.944,0 18.442,0 18.841,0.39900017 19.041,1.5949993 19.34,3.2899981 20.337,7.9749966 21.234,11.164995 22.53,15.451993 22.131,19.438992 23.128,20.535991 24.922,22.32999 26.617,22.32999 26.617,22.32999L26.617,30.205987C23.526999,30.902987 21.832,30.703986 20.237,30.304988 17.047,29.606988 16.05,26.317989 15.95,25.619989 15.751,26.317989 14.854,29.606988 11.664,30.304988 9.9689999,30.703986 8.2740002,30.902987 5.184,30.205987L5.184,22.32999C5.184,22.32999 6.8789997,22.32999 8.6729999,20.535991 9.6700001,19.538992 9.2709999,15.451993 10.567,11.164995 11.564,7.9749966 12.461,3.2899981 12.76,1.5949993 12.96,0.39900017 13.358,0 13.857,0z"/>

Refer to the following GIF image.

Get shape paths from Syncfusion Metro Studio

With a collection of over 7,000 flat and wireframe icon templates, Syncfusion’s Metro Studio offers a wide range of customization options to create unique icons. The 100 icons listed above are just a small sample of what Metro Studio offers.

In addition to custom icons, Metro Studio also supports the creation of icon font packages, enabling designers to create and use their own sets of icons. With its comprehensive collection and customization options, Syncfusion Metro Studio is a valuable tool for designers looking to elevate their design game.

Conclusion

Thanks for reading! In this blog, we have seen the 100 types of ready-to-use custom shapes available in the Syncfusion .NET MAUI Rating control. Try them out and elegantly design a rating UI in your .NET MAUI application.

You can download the free trial of Essential Studio for .NET MAUI to evaluate this control.

If you need any clarification, please mention it in the comments section below! You can also contact us through our support forum, support portal, or feedback portal. We are always happy to assist you!

Related blogs

• Syncfusion .NET MAUI 2023 Roadmap
• Get Realistic Digital Signatures with the .NET MAUI SignaturePad
• Easily Replicate a Card Checkout UI in .NET MAUI
• Syncfusion .NET MAUI Control Demos Are Now Available at App Stores

View Details

Due March 31, from Packt

Very excited about this book. Feedback is very welcome at jesseliberty@gmail.com.

Thanks!

View Details

In 2023, the life of a C# iOS developer is pretty good. We have apple silicon, and dotnet supports it. The legacy Xamarin toolchain is not arm64 friendly and probably never will be, but once you migrate to the new stuff, you'll find yourself in an all-arm64 development nirvana, where builds zip away silently, and the hot, noisy days of intel past are but a faint memory.

Everything is as it should be 🏝️💻 . . .

...

...

...

Or is it? In this post we'll learn how to identity and replace some of the pesky intel binaries that sit between us and a trip to csrutil disable to remove Rosetta for good^, and speed up iOS publishes along the way.

an al-arm-ing discovery

You can follow along if you're on an M1, or just take my word for it:

Open Activity Monitor, sort the process list by Kind.
If you don't have the Kind column, you should 😤
(you can turn it on by right-clicking the column headers)

Open Terminal and get yourself to a dotnet ios/maui project on your machine somewhere.
If you don't have one, dotnet new maui -o gathering\_intel && cd gathering\_intel will get you set up with a starter project

Then kick off a publish
dotnet publish -c:Release -f:net7.0-ios -r:ios-arm64 -p:EnableCodeSigning=false -v:n

Before long, you'll start to see the mono-aot-cross invocations fill the terminal. They start off like this:

Tool /usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.ios-arm64/7.0.3/Sdk/../tools/mono-aot-cross execution started with arguments: ...

Take note of the path to mono-aot-cross for later. Now switch back to Activity Monitor, and try not to audibly gasp.

Just to be sure:

find /usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.ios-arm64/7.0.3/Sdk/../tools/ | grep cross/ios-arm64/ | xargs file | grep executable

/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.ios-arm64/7.0.3/Sdk/../tools/llc: Mach-O 64-bit executable x86\_64/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.ios-arm64/7.0.3/Sdk/../tools/opt: Mach-O 64-bit executable x86\_64/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.ios-arm64/7.0.3/Sdk/../tools/mono-aot-cross: Mach-O 64-bit executable x86\_64

Yes it's true: even in our arm64 dotnet install, mono-aot-cross, llc and opt - the bits that handle AOT compilation and optimisation - currently ship as x86\_64 binaries and are run under Rosetta.

eh, this only affects publishing, it's no big deal!

That's fair - most of the time, we don't care that much about how long release builds take. Because of changes to the build approach in dotnet ios, or maybe just because of most everything else being arm64 on apple silicon, the development-time experience is pretty zippy (I still make heavy use of tbc though).

But what about when you're gearing up for release and start to focus on bundle size, or things like startup performance? That's the thing: The only way to know the true impact of a change with respect to bundle size or performance is to perform a release build. So at some point in your project you might just find yourself in an 'inner-dev-loop' of release builds, and at that time, build times might matter.

I went in search and found that unsurprisingly, the dotnet team already identified this gap in the arm64 binaries, and this issue tracked it. The scope of that issue was eventually narrowed and the remainder (including macos arm64) is tracked here. That means that this should eventually get resolved, maybe even in a future net8 preview, and you could just wait for that. But what if you're doing size/performance optimisation work NOW? You'll have to get your hands dirty, but is possible to solve this for yourself (for some definition of solve).

how much faster is using native AOT binaries over rosetta

So you can decide whether it's worth doing this, I've run some highly un-scientific speed tests. Here's a chart of my findings:

I tried four projects - dotnet new ios, dotnet new maui, eshop mobile client (from here) and one of my own. I added -clp:PerformanceSummary to the publish invocation to get the timings for the AOTCompile task.

On my machine, the aot compilation time reduction ranged from 30-35% across the projects - let's call it a third. Apple says the M2 gives up to 20% faster CPU performance than the M1, so if like me you have an M1 and sometimes have irresponsible thoughts about an M2, this basically saves you six to eight thousand australian dollarydoos.

how to (high level)

We saw in the github issue that the dotnet team ran into issues doing this - how can we expect to be able to make it work? We can make it work because we have simpler goals. The dotnet team has to worry about pesky things like "passing build pipelines", "architectures other than arm64", "solutions that don't just work on one person's machine" and other realities of shipping an sdk and runtime. We don't need to concern ourselves with those kinds of hassles.

We just want to take our arm64 mac and produce arm64 aot compiler binaries that aot for ios-arm64, and then somehow have them be used by the build. For that, we can build our own out of dotnet/runtime, and then just overwrite the the intel binaries we originally got from official sources with our bootleg ones. What could possibly go wrong?

Just like back in the day when we were rolling our own reflection-emit-enabled Xamarin.iOS versions, it goes without saying that you should exercise caution when replacing core parts of the dotnet build pipeline with custom built tools. It's true that we are building off tagged ("blessed") commits, but the reality is that arm64 aot compiling binaries aren't officially produced right now and the use case may not have been through the same testing rigour that supported use cases have. I haven't had any issues (yet?), but it's probably best to limit use of these binaries use to the aforementioned 'inner-release-loop' scenarios only, and use the official binaries for builds you actually want to ship. No warranties provided, proceed at your own risk, etc. etc.

how to (in detail)

With disclaimers out of the way, if you're still on board we're ready to start making a mess. With any luck, this process should only take 10-20 minutes.

First, clone dotnet/runtime:

git clone https://github.com/dotnet/runtime.git && cd runtime

Then, check out the tag that matches the version of the sdk you're using to build. You can see it in the path of the aot invocation from earlier. In this post, the invocation was:

Tool /usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.ios-arm64/7.0.3/Sdk/../tools/mono-aot-cross execution started with arguments: ...

so we want 7.0.3. In dotnet/runtime, the version tags are preceded by a 'v', so:

git checkout v7.0.3

(It's important to build off the tag matching the version of the dotnet sdk you're using. If not, you may run into errors due to differneces between versions. For example, you can't build off the tip of main, which right now is .net8, then use the outputs with a .net7 sdk; things will go badly. An implication of this is that when you update dotnet, or if you have different projects pinned to different versions of dotnet, you'll likely need to need to follow these steps and build binaries for each of them individually. Basically let's just hope arm64 binaries start shipping soon)

Ok, now we're ready to build things. There are flags you can pass to the runtime build script to isolate the build of the AOT cross compiler, but I didn't get great results with various combinations of these (either only some binaries came out arm64, or the build just didn't work - which is maybe what the updated issue tracks). So let's keep it simple:

./build.sh -s mono+libs -os ios -arch arm64 -c Release

This should take somewhere between 5-10 minutes, and complete without issues. It's pretty impressive really (go look in artifacts to see all the things we built with one command and no shenanigans).

Now make sure that we got what we wanted:

find . | grep cross/ios-arm64/ | xargs file

You should see:

./artifacts/bin/mono/iOS.arm64.Release/cross/ios-arm64/llc: Mach-O 64-bit executable arm64./artifacts/bin/mono/iOS.arm64.Release/cross/ios-arm64/opt: Mach-O 64-bit executable arm64./artifacts/bin/mono/iOS.arm64.Release/cross/ios-arm64/mono-aot-cross: Mach-O 64-bit executable arm64

Yes! arm64 all the things!

All that's left to do is to overwrite the official binaries with our own ones. Once again, the invocation from earlier tells us where these need to go. Just in case, let's keep a copy of the original bits around (also useful if you want to do comparisons).

(Remember to substitute the 7.0.3s here and below for your version if necessary)

sudo cp -R /usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.ios-arm64/7.0.3/Sdk/../tools/ /usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.ios-arm64/7.0.3/Sdk/../tools/backup

That put all the original binaries under a subdirectory called backup. Now copy our new files over.

sudo cp artifacts/bin/mono/iOS.arm64.Release/cross/ios-arm64/* /usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.ios-arm64/7.0.3/Sdk/../tools/

And that's it! Let's run another publish and see how it goes.

Now we're cooking with charcoal. Enjoy your 33% faster builds!
^(Only one intel binary left!)
(it's m l a u n c h)

bonus thoughts: other factors affecting build time

Switching from x64 to arm64 binaries is a nice 'free' build time improvement. There are a couple of other things that you can look at.

💡 Linking/Trimming

The less code you have, the less code needs to be AOT compiled. Using the linker will reduce the time spent in AOTCompile (and the output binary size). Some of it will be moved to the ILLink task, but the net effect should be a faster build and a happier user.

💡 Dealing with AOT-unfriendly assemblies

In the chart from earlier, "my app"'s AOT time went from ~120s to ~80s when switching to arm64 binaries. But when I first started looking at the build time, the non-arm64 AOT time was around 800s 🤯. Watching CPU usage and looking at build output made it clear - one assembly in the project took several times longer to AOT than all of the others.

The way the AOT step works is that the build system basically spawns an AOT process per assembly, for all assemblies at once, and lets the operating system manage their resource allocation. That's why in the screenshots of Activity Monitor in this post, you see a large number of processes using a small fraction of a cpu core - there are some 100+ processes trying to get their slice of 10 cores. Each of the AOT processes appears to operate on a single thread, which is fine in the beginning when there are more processes than cores and the cpu is oversubscribed. But if a single process takes much longer than the others, eventually it will be left running on it's own on a single thread, which is not very optimal. Scraping the output, I was able to see this behaviour in my own build (names removed to protect the innocent):

(n.b. Because of the probably indeterminate nature of oversubscription, it's not truly fair to compare any of the specific numbers in the above diagram, but for general magnitudes we can use it)

Essentially, the AOT of one assembly is responsible for blowing out the build time by 10+minutes. In my case, the functionality being used in that library was something that could be replicated natively without too much hassle, so I switched to that and removed the assembly. Another option would have likely been to link aggressively on that assembly to remove more of the code causing the AOT work (my guess - heavy use of generics).

💡 Opting to interpret some assemblies

This is more of a build size vs performance tip, and that should be your driving factor for this (not release build time), but I'll include it anyway. For a while now, we've had access to the interpreter option which enables various scenarios. In new dotnet ios, having it enabled is currently something you probably need to do because it is easy to unintentionally trigger code-gen (my theory is we had some special BCL assemblies in Xamarin days that avoided code-gen in certain methods but now that we share with dotnet you can hit it more easily). But don't just enable it and interpret everything!

Don't: (enable the interpreter and interpret all our assemblies)

<UseInterpreter>true</UseInterpreter> 

Do: (enable the interpreter and interpret none of our assemblies, but be ready to interpret any codegen)

<UseInterpreter>true</UseInterpreter> <MTouchInterpreter>-all</MTouchInterpreter> 

Doing the first one will skip AOTing everything, so I guess in the spirit of this blogpost it's going to make your release builds super fast and your outputs super small, but it's also going to make things much slower.

Consider: (enable the interpreter and interpret specific assemblies)

<UseInterpreter>true</UseInterpreter> <MTouchInterpreter>-all,AssemblyToNotAOT1,AssemblyToNotAOT2</MTouchInterpreter> 

Here we name AssemblyToNotAOT1 and AssemblyToNotAOT2 as assemblies that will be interpreted at run-time, so they won't be AOT-compiled at build time. This will reduce output size and release build time

💡 Getting an M2

No no... just do some of the above 😎

By combining the use of arm64-specific binaries and maybe a few build tips, hopefully you can see an improvement in your release-build times like I did, plus better battery life and an improvement in your general health and wellbeing.

Finally, everything as it should be 🏝️💻 . . .

View Details

Syncfusion is gearing up for the first major release of this year with Essential Studio 2023 Volume 1. The upcoming release promises many new and exciting features to enhance the user experience. You can expect the release by the end of March and we are confident that it will exceed users’ expectations.

This article gives you a sneak peek at some of the new features that will be included in the Syncfusion Xamarin.Forms suite in the 2023 Volume 1 release.

PDF Viewer

The Xamarin.Forms PDF Viewer will offer the following new features in the upcoming Volume 1 release.

Crop box calculation of PDF pages

The crop box is like the margin and padding feature available on a PDF page. Previously, this wasn’t considered while adding annotations and highlighting a search result. Thus, it resulted in some alignment mismatches in the PDF documents.

We have overcome this issue by considering the crop box value for the calculation while adding annotations and highlighting the searched text.

PDFium custom rendering (UWP)

PDFium is a third-party custom renderer. We had a scenario with a particular PDF document in which the images weren’t properly rendered with the native rendering APIs.

The PDFIum support helps us return the proper PDF pages’ images for rendering. Currently, we have this support only in the Android platform. From the 2023 Volume 1 release on, you can also enjoy this support in the UWP platform. 

Preserve original order in rendered annotations

Previously, if we added annotations one over the other in an overlapping manner in other PDF viewers and loaded them in the Syncfusion PDF Viewer, they would not render in their original order. The annotation at the bottom would be on top, and the one on top would be in the middle.

From the upcoming release, you can render and save the annotations in their original order using our Xamarin.Forms PDF Viewer.

Add and modify form field values

The support to programmatically add, modify, and clear form data in a PDF document will be included. 

Enable and disable editing in form fields

With this feature, you will be able to enable or disable the editing features of the form fields in a PDF document.

Change the bounds of ink and signature annotations

This feature will let you programmatically modify the ink’s bounds and signature annotations. 

Render existing digital signatures

Users will be able to render flattened digital signatures in a PDF document to avoid data loss.

Adjust selector padding

You will be able to adjust the selector padding of annotations while selecting them in a PDF document.

Adjust the eraser thickness

This feature will allow you to adjust the ink eraser thickness in the Xamarin.Forms PDF Viewer.

Rich Text Editor

From 2023 Volume 1 on, the Xamarin.Forms Rich Text Editor will provide support to move the cursor positions (programmatically) to the beginning or end of the content.

Conclusion

Thanks for reading! Along with these updates, you can enjoy other exciting new features and bug fixes in our Syncfusion Xamarin.Forms suite in the 2023 Volume 1 release. You can check them out once the release is launched. It will not be long!

Stay tuned to our official Twitter, Facebook, and LinkedIn pages for announcements about the release. Please let us know in the comments section below if you have any feedback.

You can also reach us through our support forums, support portal, or feedback portal. We are always happy to assist you!

Related blogs

• Lazy Load JSON Data in Xamarin.Forms ListView: An Overview
• Easily Lock and Unlock Annotations Using Xamarin.Forms PDF Viewer
• View PDF Annotations as a List and Navigate Using Xamarin.Forms PDF Viewer
• Step-by-Step Guide: Downloading PDFs from SharePoint and Displaying Them in a Xamarin App

View Details

Writing mobile apps usually brings along its fair share of application logic run on the device. When writing code, it is paramount to test it. How else will you know if it is working as expected? The answer is testing. And since we are developers, we like to automate mundane tasks. So Unit Testing our logic can be a great way to test our logic. If you know how to set up unit tests, skip to the TL;DR; marker. 🙃 Unit Tests allow us to test the logic parts of our app. This will enable us to try most of our apps except the views. The most popular testing frameworks to the date of writing this post are XUnit, NUnit and MS Test. All three are solid choices and mostly have the same functionality. They mainly differ in how tests are written. For my Unit Tests, I usually like to go with XUnit. Ensure that the .NET MAUI and test projects use the same .NET version. In this example, it will be .NET 7. Given an existing .NET MAUI application, we can add a new testing project to the solution and choose XUnit as the testing framework. To have some code, we can test, I have rewritten the .NET MAUI hello world app to use a ViewModel (using the Community Toolkit MVVM framework). Doing so gives us the following ViewModel code. public partial class MainViewModel : ObservableObject { [ObservableProperty] public int _count; [ObservableProperty] public string _text = "Click me"; [RelayCommand] public void CounterClicked() { Count++; if (Count == 1) Text = $"Clicked {Count} time"; else Text = $"Clicked {Count} times"; } } We can test this logic by writing a Test that calls the command method in the well-known Arrange/Act/Assert pattern: public class MainViewModelShould { [Fact] public void IncrementcountOnCounterClicked() { // Arrange var sut = new MainViewModel(); // Act sut.CounterClickedCommand.Execute(null); // Assert Assert.Equal(1, sut.Count); } } This will require us to add a project reference from the test project to the .NET MAUI project. <Project Sdk="Microsoft.NET.Sdk"> <!-- ... --> <ItemGroup> <ProjectReference Include="..\MauiTesting101\MauiTesting101.csproj" /> </ItemGroup> </Project> TL;DR; Up to this point, we just followed the usual steps for setting up a Unit Test project. If you put your app logic in the .NET MAUI app project, you will get a weird error when compiling the test project. To make the compiler happy, we will have to change the .NET MAUI .csproj file as follows: <OutputType Condition="'$(TargetFramework)' != 'net7.0'">Exe</OutputType> Note that we have to add a condition to the <OutputType> or else you will get an error that there is no main method when executing the test. If you are using a different .NET version i.e. .NET 6 you would have to write the condition as follows <OutputType Condition="'$(TargetFramework)' != 'net6.0'">. And for .NET 8 we would have to replace number with an 8 and so forth. Note that we have to add a condition to the <OutputType>, or else you will get an error that there is no primary method when executing the test. If you are using a different .NET version, i.e. .NET 6, you would have to write the condition as follows <OutputType Condition="'$(TargetFramework)' != 'net6.0'">. And for .NET 8, we would have to replace the number with an 8. And for .NET 9, we … you get the point. 😉 With these changes, we can start running the tests from your IDE or via the command line using dotnet test . You can find the complete example on GitHub. HTH

View Details

View Details

This blog provides show notes for our March 9, 2023, webinar, “Developing a Temperature Monitor UI in .NET MAUI.” The webinar is presented and hosted by Syncfusion Senior Project Manager Suresh M. If you miss it or want to watch it again, you’ll find the recording on our YouTube channel or embedded below.

Overview

During this webinar, I will walk you through developing a temperature monitor UI using the Syncfusion Radial Gauge control in .NET MAUI.

Time Stamps

• [00:00] Introduction
• [4:50] Implementing the Radial Gauge Control
• [11:45] Customizing the Radial Gauge
• [30:30] Deploying the Application
• [31:27] Output

Q&A

The following are answers to questions we received from attendees during the webinar.

Does the Radial Gauge tool offer labeling and naming?

The .NET MAUI Radial Gauge supports customizing and formatting the axis labels. Please refer to the .NET MAUI Radial Gauge axis label customization documentation.

What was the code included in MauiProgram.cs before modifying MainPage.xaml?

That was code to register the handlers. Please refer to registering the handler for .NET MAUI Radial Gauge documentation.

How do I migrate from Xamarin to MAUI?

The following documentation will help you migrate Syncfusion controls from a Xamarin.Forms application to a .NET MAUI application.

So all these tools would need to integrate with MVVM and possibly have to do some complex bindings. What would you suggest we read up on to better understand more complex bindings?

You can get started with learning to bind from the following documentation.

When are all Syncfusion Xamarin controls expected to be ported to MAUI?

You can have a glance at our plan here.

The documentation is great, but if we need a tad more info within those docs, where could we possibly make suggestion or at least let you know where we are getting stuck?

If you have any suggestions and questions, you can reach us through our support forum, support portal, or feedback portal. We are always happy to assist you!

Conclusion

During this webinar, we created a temperature monitor UI with the Syncfusion Radial Gauge control for .NET MAUI and covered some introductory tips for MAUI development. We hope you enjoyed this webinar and will keep an eye out for our future webinars on .NET MAUI.

Related blogs

• Migrating Syncfusion Xamarin.Forms Controls to .NET MAUI
• Get Realistic Digital Signatures with the .NET MAUI SignaturePad
• Easily Replicate a Card Checkout UI in .NET MAUI
• Easily Design a Group Box View in .NET MAUI

View Details

Medical Service — MAUI App Implementation. Phase #1 — Implementing Page in XAML with inline data.

Under this phase, we will implement page UI with static data sources in XAML, using only a few converters and local models.

Hi Folks 👋. This time we will use only XAML to implement the entire UI according to the Dribbble design from Phase #0:

Medical Service — MAUI App Implementation. Phase #0 — Review Design

What you will find here:

• Implementation of each control, step-by-step.
• Using Converters for Selectable Components.
• Using Code-Behind as the resolver for events callback.

What we don’t focus on at this stage:

• Duplicated Code
• Resources for Styles and Colors

It’s terrible, but I created it to show you later how to refactor such crappy code into “good enterprise quality” code.

Source Code with GitKraken

Link to source code at GitHub:

GitHub - bbenetskyy/MAUI-Medical-service: Implementation of Medical Services Page

If you made it in MacOS, I strongly recommend using GitKraken. Using it will simplify branch managing; you can quickly review my changes or yours if you try to modify something. Also, later with the subsequent phases, you can see critical differences before and after merging branches.

Page Header Section

There are a few elements here, so we will focus on creating two Ellipses. The first will be used to Clip the profile image into a circle, while the second one will be to create a notification on the bell icon:

Main Additional Actions

As you can see, they are similar, and we will create a control for them later. We will pass into control the icon, text and background colour. But for now, we have duplicated our code twice. So here I will show the code for only one of them:

General Question Zone

We are lucky because we can reuse the same code for all selectable buttons. After all, they use the same radius, style and behaviour. An exception is “Yes-No” questions because we need to invalidate each button according to the questions.

Let’s start with creating models, they are needed to convert Background Color if an item is selected.

Now, we need to create converters. They will be used to change text and background colour. Separate for Selectable Model, where we will bind only IsSelected Property and separate for Questionable Model, where we will bind current answer and required one to match answers:

After all, that changes will get something like this in our Solution Explorer:

The next step is to create a selectable button and a “Yes-No” Quiz Card; place them into StackLayout with Bindable Item Source and Template. Values we also will bind in XAML. I know that it’s pretty rare and better to bind them from View Model. And it will be done in that way later, but now you can learn how to do it in XAML 😇, what a lovely day 🫠

And final thing — Tapped event Callback at Code Behind. We need to see which model was sent to us and who the sender is in the “Yes-No” Card Buttons case.

During refactoring, we will move dumb text-checking logic into control and replace it with enum checking, but for now, it’s more than enough for us.

Multi-Column Question Zone

Why did I name it? — All because we can’t just use Collection View(cause of scroll bug in MAUI) or Flex Layout(cause of not perfect alignment) and need sticky goes with three Stack Layouts inside one Grid with ColumnDefinitions="*,*,*", so all columns are the same; if we use the same layout inside Stacks, no matter which text we will place there 🥹. Later in the real app, we may get only a problem with data, but if we move it into custom control — we may add a special Data Manager who will be requested to solve it for us.

I’ll only insert one of the three stacks here because they’ll be the same:

Submit Quiz Form Button

There is nothing special here at the moment, but later we need to add validations and maybe make this button always visible on the screen — but this depends on business requirements and hard to identify it just by Dribbble Shot.

Thanks for reading, and see you in the next implementation Phase 😛

Medical Service — MAUI App Implementation. Phase #1 — Implementing Page in XAML with inline data. was originally published in Nerd For Tech on Medium, where people are continuing the conversation by highlighting and responding to this story.

View Details

Digital signatures have become increasingly important in today’s world, where electronic documents are widely used.

Syncfusion’s .NET MAUI SignaturePad control is a user interface tool for capturing and storing signatures on mobile applications. Its simple yet essential functions allow users to save and export signatures.

In this blog, we will highlight the key features of the .NET MAUI SignaturePad control and how to get started with it.

.NET MAUI Signature Pad

The .NET MAUI Signature Pad control is user-friendly and customizable, enabling developers to tailor it to their specific needs.

It has the following key features:

• Supports customizing the stroke thickness and color and performing clear and undo operations.
• Easily captures signatures using touchscreens with touch gestures.
• Saves drawn signatures as an images and embeds them into PDFs and other documents with formats that support image signatures.
• Its unique stroke-rendering algorithm considers the speed of drawn gestures to produce a more authentic, handwritten look and feel to the signature.

Overall, these features make the .NET MAUI SignaturePad control an essential tool for developers looking to integrate signature-capturing functionality into their apps.

Getting Started with the .NET MAUI SignaturePad

Let’s see how to incorporate the .NET MAUI SignaturePad control into your project and customize its basic features.

Step 1: First, create a new .NET MAUI application in Visual Studio.

Step 2: Syncfusion .NET MAUI components are available on the NuGet Gallery. To add the SfSignaturePad to your project, open the NuGet package manager in Visual Studio, search for Syncfusion.Maui.SignaturePad, and install it.

Step 3: In the MauiProgram.cs file, register the handler for Syncfusion Core.

using Syncfusion.Maui.Core.Hosting; namespace SignaturePadGettingStarted { public static class MauiProgram { public static MauiApp CreateMauiApp() { var builder = MauiApp.CreateBuilder(); builder .UseMauiApp<App>() .ConfigureSyncfusionCore() .ConfigureFonts(fonts => { fonts.AddFont("OpenSans-Regular.ttf", "OpenSansRegular"); }); return builder.Build(); } } }

Step 4: Then, import the Syncfusion.Maui.SignaturePad namespace and initialize the SignaturePad as shown in the following code.

<ContentPage . . . xmlns:signaturePad="clr-namespace:Syncfusion.Maui.SignaturePad;assembly=Syncfusion.Maui.SignaturePad"> <Grid> <signaturePad:SfSignaturePad /> </Grid> </ContentPage>

Step 5: Here, we’ll customize the stroke color of the SignaturePad control using the StrokeColor property. The default stroke color is Colors.Black.

<signaturePad:SfSignaturePad StrokeColor="Blue" />

Step 6: We customize the thickness of the stroke by setting the MinimumStrokeThickness and MaximumStrokeThickness properties. The strokes will be drawn based on the speed and impression we provide through gestures within the minimum and maximum stroke thickness range. This way, the signature will be more realistic.

Refer to the following code example.

<signaturePad:SfSignaturePad MinimumStrokeThickness="1" MaximumStrokeThickness="6" />

Step 7: Finally, let’s save the signature drawn in the SignaturePad as an image using the ToImageSource() method. The stored signature image can further be synchronized with our devices and documents that need the signature.

Refer to the following code example.

<signaturePad:SfSignaturePad x:Name="signaturePad" /> <Button Text="Save" Clicked="OnSaveButtonClicked" />

private void OnClearButtonClicked(object? sender, EventArgs e) { ImageSource? source = signaturePad.Clear(); }

Conclusion

Thanks for reading! In this blog, we have seen the significant features of the Syncfusion .NET MAUI Signature Pad control. Try out this user-friendly control and share your feedback in the comments section below.

Also, check out our .NET MAUI control demos on GitHub.

Customers can download the latest Essential Studio version from the License and Downloads page. If you are not a Syncfusion customer, you can try our 30-day free trial to see how our controls can enhance your projects.

For questions, you can reach us through our support forum, support portal, or feedback portal. We are always happy to assist you!

Related blogs

• Easily Design a Group Box View in .NET MAUI
• Exploring the Features of the .NET MAUI Calendar Control
• OCR in .NET MAUI: Building an Image Processing Application
• Designing Effective Data Entry Forms in .NET MAUI: A Step-by-Step Guide

View Details

Have you ever wondered how to cache images in your app? .NET MAUI already includes this functionality! In this article, we will quickly learn how to use it and adapt it to our specific needs.

The explanation will be divided into the following points:

  How does image caching work?

  Learning about its structure

  Properties available 

Let’s start!

How does image caching work?

In .NET MAUI, downloaded images are cached by default for one day. This functionality is in action whenever you download an image from a URL.

Let’s learn about its structure:

Properties available

You can experiment with different values using the properties provided by the UriImageSource class. Let’s explore each one of these properties:

URL: The URI of the image is provided, allowing it to be downloaded for display – It receives a Uri as value.

CachingEnabled: Determines whether the image cache is enabled or disabled. – It receives a Bool data type and its default value is True.

CacheValidity: The value entered here will decide how long the image is saved on the local device. Keep in mind that the default value is set with one day as value. – It receives a TimeSpan as value.

If you send a single number, it will be interpreted as the number of days you want the cache to store the data. Since this property is of type TimeSpan, you can format it in XAML and pass a value like this:

Now that we understand the structure and properties, let’s dive into the code implementation:

And done!!  From now on, you are ready to works your Images with cache .NET MAUI I hope you like it!

<Label Text=”Thanks for ready!  ” /> Spanish article:

Spanish post:

• https://es.askxammy.com/almacenamiento-de-imagenes-en-cache-en-net-maui/

References:

• https://learn.microsoft.com/en-us/dotnet/maui/user-interface/controls/image?view=net-maui-7.0?WT.mc\_id=DT-MVP-50033

View Details

View Details

Medical Service — MAUI App Implementation. Phase #0 — Review Design

This is a start of a journey to implement Apps in an accurate Enterprise way actual applications are made.

Hi Folks, I started with you a new journey about implementing mobile applications in .NET MAUI. We would implement one single page of Medical Service from a dribble.

Still, we will make it from a simple stupid showcase of implementing UI to a complete Enterprise application with controls, bindings and validations. All this will be done in separate blog posts and describe one thing in one post, so later, you can search for an exciting part of this story more easily.

Medical service

Also, I would film all that process with some of my comments, hoping that will be useful for somebody.

Here is a list of future blogs; I will add links later after writing:

• Phase #1 — Implementing Page in XAML with inline data.
• Phase #2 — Adding View Model.
• Phase #3 — Adding Validation.
• Phase #4 — Adding Services with Mock Data.
• Phase #5 — Refactor XAML, creating custom controls.
• Phase #6 — Adding Unit Tests.
• Phase #7 — Adopt UI for Small/Large Screens.

Phase #0 — Review Design

In the real world, you will get this high-fidelity design from your designer in some web app, like Figma or Adobe or Zeplin. And you will have access to all details like font, font-size, colour, margins between, icons in SVG format and other crucial things. Here we have only one image, which is unacceptable in Enterprise development but may be a deal sometimes in some freelance development. Anyway, we got this; what should be our next steps now?

First, we should determine all margins and colours we would use and create Colors.xaml and Dimensions.xaml with all values we found there. This will be done in Phase #5 because I would like to show you how we can eject it from the raw XAML code. In Phase #1, we will use them all in our XAML.

I’m not a designer, but in an exemplary design, there should be a magic “x” value, and all margins and padding should re-use that “x” with some multiplier, like 2x, 4x, and 5x. And if that “x” is less, than 4px it is not so good.

I’m using Figma for such measuring because it’s free and ideal for the simple things we will do with that image. So, what are we doing here? — We first created a couple of squares of 16 or 24 pixels and checked how they fit. Later create more if they are needed. But, it’s essential to try not to make a difference between your “boxes” of 1 pixels, and if that is possible, also try to avoid all odd numbers of pixels.

And we were going to do this for all elements on the screen. After that, we need to pick up all colours we see there.

That’s it. The initial — preparation phase is done. Now we are going to move this UI to .NET MAUI, where we are going to use XAML for everything because I would like to show how raw XAML becomes an actual Enterprise Mobile app, see you folks 🙃 😉

Medical Service — MAUI App Implementation. Phase #0 — Review Design was originally published in Nerd For Tech on Medium, where people are continuing the conversation by highlighting and responding to this story.

View Details

Practicing is always the best way to strengthen our knowledge. In this article, we will enhance your XAML skills by replicating a card checkout UI inspired by this Dribble design.

Let’s break down the creation of the UI into three steps. Each creates a set of visual elements that make up the UI. So, you can concentrate on each portion of the code and have a straightforward and faster understanding of XAML.

Refer to the following image.

Skills you’ll develop

In addition to strengthening your XAML skills, you will learn to implement the following .NET MAUI features in this article:

• Syncfusion .NET MAUI Tab View: An interface for tabbed browsing in mobile and desktop apps, where users can switch among different tabs.
• Syncfusion’s .NET MAUI ListView: Show your information in a list in portrait or landscape orientation.
• Borders: Add a border to the desired visual elements.
• Grid: Design the main layout.
• Appearance mode: To develop the UI for both light and dark modes, we’ll use the AppThemeBinding markup extension in some properties.

Let’s start coding!

Easily build cross-platform mobile and desktop apps with the flexible and feature-rich controls of the Syncfusion .NET MAUI platform.

Explore Now

General settings

Configuring the Tab View

To get started, we’ll build the CheckOutPage.xaml page. To design it, we are going to use the Syncfusion .NET MAUI Tab View. It will contain all the visual elements that were shown in the previous image.

First, refer to the Getting started with .NET MAUI Tab View documentation. Then, follow these steps to implement the Tab View control:

1. Add the Syncfusion.Maui.TabView NuGet package.
   

2. Go to the MauiProgram.cs file and register the handler for the Syncfusion .NET MAUI Tab View. To do this, navigate to the CreateMauiApp method and then, just before the line return builder.Build(); method, add the .ConfigureSyncfusionCore() method.
3. Now, add the Syncfusion.Maui.TabView namespace in the XAML page.

   xmlns:tabView="clr-namespace:Syncfusion.Maui.TabView;assembly=Syncfusion.Maui.TabView" 

4. Finally, in the XAML page, add the Tab View control inside a layout, in this case, a VerticalStackLayout.

   <VerticalStackLayout> <tabView:SfTabView x:Name="tabView" IndicatorBackground="Silver"> <tabView:SfTabView.Items> <tabView:SfTabItem Header="Cards" FontAttributes="Bold" TextColor="{AppThemeBinding Light=Black, Dark=White}"> <tabView:SfTabItem.Content> <!--1. First page: Add the code of your first page here --> </tabView:SfTabItem.Content> </tabView:SfTabItem> <tabView:SfTabItem Header="New Cards" FontAttributes="Bold" TextColor="{AppThemeBinding Light=Black, Dark=White}"> <tabView:SfTabItem.Content> <!--2. Second page: Add the code of your second page here --> </tabView:SfTabItem.Content> </tabView:SfTabItem> </tabView:SfTabView.Items> </tabView:SfTabView></VerticalStackLayout>

In the previous code example, you will find comments indicating where to add the first (steps 1 and 2) and second (step 3) pages. Keep this in mind so that you‘ll know where to add the code in the following explanations.

In the following, we can see how the Tab View will be rendered in both light and dark modes.

We have configured the initial setup. Let’s start designing the first page of our UI, Cards.

Syncfusion’s .NET MAUI controls suite is the expert’s choice for building modern mobile apps.

Explore Now

Step 1: Card list

We are going to render the following UI elements:

• Main layout
• Card list
• New card button
• Separator

Main layout

To design the main layout, use a DataGrid control. Refer to the following code example.

<Grid RowDefinitions="Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto" ColumnDefinitions="Auto,*" VerticalOptions="Start" Margin="30,0"> <!-- Add here all the code explained in steps 1 and 2 --> </Grid>

Card list

As I said before, to show the list of cards, we are going to use the Syncfusion .NET MAUI ListView control. The cards will be organized horizontally.

First, refer to the Getting started with .NET MAUI ListView documentation. Then, follow these steps to implement the control:

1. Add the Syncfusion.Maui.ListView NuGet package.
   

2. Go to the MauiProgram.cs file and register the handler for the Syncfusion .NET MAUI ListView. To do so, navigate to the CreateMauiApp method and then, just before the line return builder.Build();, add the builder.ConfigureSyncfusionListView(); method.

3. Now, add Syncfusion.Maui.ListView namespace in the XAML page.

   xmlns:syncfusion="clr-namespace:Syncfusion.Maui.ListView;assembly=Syncfusion.Maui.ListView"

4. Finally, add the following code in the XAML page.

   <!-- Card list--> <syncfusion:SfListView Grid.Row="0" Grid.Column="0" Grid.ColumnSpan="2" ItemsSource="{Binding Cards}" ItemSize="350" ItemSpacing="5" ScrollBarVisibility="Never" HeightRequest="250" Orientation="Horizontal" VerticalOptions="Start" HorizontalOptions="Start"> <syncfusion:SfListView.ItemTemplate> <DataTemplate> <Image Source="{Binding Picture}" Aspect="AspectFit" /> </DataTemplate> </syncfusion:SfListView.ItemTemplate></syncfusion:SfListView> <!-- Add here all the code explained in the following code block -->

Note: The Card designs were obtained from this Dribbble design.

Rendering Add new card button

Next, we render the Add new card button with dashed border lines by following these steps:

1. First, add a border with dashed lines.

   <Border Grid.Row="1" Grid.Column="0" Grid.ColumnSpan="2" Margin="0,0,0,20" Stroke="#dadada" HorizontalOptions="FillAndExpand" StrokeThickness="3" StrokeDashArray="1.5" StrokeDashOffset="2" StrokeShape="RoundRectangle 10,10,10,10" HeightRequest="50"> <!-- Add the Button here --> </Border>

2. Then, inside the border, add the Button element.

   <!-- Button: Add new Card--> <Button Text="Add new card" FontSize="15" ImageSource="{AppThemeBinding Light=add\_black, Dark=add\_white}" TextColor="{AppThemeBinding Light=#505050, Dark=white}" BackgroundColor="Transparent"/> <!-- Add here all the code explained in the following code block -->

Separator

Now, let’s simulate a separator below the Add new card button using the BoxView.

<!-- Separator--> <BoxView Grid.Row="2" Grid.Column="0" Grid.ColumnSpan="2" HorizontalOptions="FillAndExpand" HeightRequest="1" Color="#f4f3f4" Margin="0,5,0,30"/> <!-- Add here all the code explained in the following code block -->

Note: You can also render the separator using lines.

After executing the previous code examples, our UI will look like the following image.

Every property of the Syncfusion .NET MAUI controls is completely documented to make it easy to get started.

Read Now

Step 2: Card details

We have finished designing the UI for the card list. Let’s next design the UI for the card details with the following elements:

• Address and date
• Invoice details
• Pay button

Address and date

We’ll display the card holder’s address and date details with the following visual elements:

• An image within a border with a background color and rounded edges.
• A label with detailed information.

Refer to the following code example.

<!-- Details: Address & Date--><!-- Address --><Border Grid.Row="3" Grid.Column="0" Margin="0,0,0,20" Stroke="Transparent" HorizontalOptions="Start" BackgroundColor="#f2f2f2" HeightRequest="65" WidthRequest="65" StrokeShape="RoundRectangle 10,10,10,10"> <Image Source="location" HeightRequest="40" WidthRequest="40"/></Border><Label Grid.Row="3" Grid.Column="1" FontSize="15" TextColor="#777777" Text="10506 - 4904 Deans Lane - Bedford Village - New York - US"/><!-- Date --><Border Grid.Row="4" Grid.Column="0" Margin="0,0,0,20" Stroke="Transparent" HorizontalOptions="Start" BackgroundColor="#f2f2f2" HeightRequest="65" WidthRequest="65" StrokeShape="RoundRectangle 10,10,10,10"> <Image Source="truck" HeightRequest="40" WidthRequest="40"/></Border><Label Grid.Row="4" Grid.Column="1" FontSize="15" TextColor="#777777" Text="Wednesday 04:00 PM"/> <!-- Add here all the code explained in the following code block --> 

Invoice details

Let’s use the Syncfusion .NET MAUI ListView control to render an invoice with the following information:

• Subtotal
• Postage
• Tax

Then, we’ll render the total price with a Label control, as shown in the following code example.

 <!-- Invoice information--><syncfusion:SfListView Grid.Row="5" Grid.Column="0" Grid.ColumnSpan="2" ItemsSource="{Binding Invoice}" ScrollBarVisibility="Never" ItemSize="30" HeightRequest="110" HorizontalOptions="FillAndExpand" Orientation="Vertical"> <syncfusion:SfListView.ItemTemplate> <DataTemplate> <Grid ColumnDefinitions="*,*"> <Label Grid.Column="0" Text="{Binding Description}" TextColor="#7e7e7e" FontSize="16" /> <Label Grid.Column="1" Text="{Binding Price}" FontSize="16" HorizontalTextAlignment="End"/> </Grid> </DataTemplate> </syncfusion:SfListView.ItemTemplate></syncfusion:SfListView><!-- Total Price--><Label Grid.Row="6" Grid.Column="0" Text="Total Price" FontSize="20" FontAttributes="Bold"/><Label Grid.Row="6" Grid.Column="1" Text="235.35$" FontSize="20" HorizontalTextAlignment="End"/> <!-- Add here all the code explained in the following code block --> 

Pay button

Refer to the following code example to design the Pay button.

 <!-- Add Button--> <Button Grid.Row="7" Grid.Column="0" Grid.ColumnSpan="2" HeightRequest="50" CornerRadius="10" Margin="0,25,0,0" BackgroundColor="#333333" Text="Pay" TextColor="White"/>

After executing these code examples, our UI will look like the following image.

To make it easy for developers to include Syncfusion .NET MAUI controls in their projects, we have shared some working ones.

Explore Now

Step 3: New cards

Let’s design the second page of our UI, New Cards.

Do you remember when we implemented the Tab View? Go to the comment that says ‘’<!–2. Second page: Add the code of your second page here –>“. In this space, we need to add all the code that will be explained in this step.

We’ll design the UI with the following elements:

• Main layout
• Card information
• Add button

Main layout

Let’s use a DataGrid to design the main layout.

<Grid RowDefinitions="Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto,Auto" ColumnDefinitions="*,*" ColumnSpacing="10" RowSpacing="10" Margin="30,30,30,0" VerticalOptions="CenterAndExpand"> <!-- Add here all the code explained in step 3 --> </Grid>

Then, replicate the main image for the card using the following code example.

<!-- Main image--> <Image Grid.Row="0" Grid.Column="0" Grid.ColumnSpan="2" Source="ccardbase" Aspect="AspectFit" HeightRequest="250" /><!-- Add here all the code explained in the following code block --> 

Card information

This section involves designing the UI to collect the following card information.

Card name and number

Refer to the following code example to get the card name and number details from the user.

<!--Card information--><!--Card Name--><Label Grid.Row="1" Grid.Column="0" Grid.ColumnSpan="2" Text="Card Name"/><Entry Grid.Row="2" Grid.Column="0" Grid.ColumnSpan="2" Placeholder="My VISA Card" PlaceholderColor="Silver"/><!--Card Number--><Label Grid.Row="3" Grid.Column="0" Grid.ColumnSpan="2" Text="Card Number"/><Entry Grid.Row="4" Grid.Column="0" Grid.ColumnSpan="2" Placeholder="4000-1234-5678-9010" PlaceholderColor="Silver"/> <!-- Add here all the code explained in the following code block --> 

Expiration date and CVV

Refer to the following code example to collect the card expiration date and CVV details.

<!--Exp. Date--><Label Grid.Row="5" Grid.Column="0" Text="Exp. Date"/><Entry Grid.Row="6" Grid.Column="0" /><!--CVV--><Label Grid.Row="5" Grid.Column="1" Text="CVV"/><Entry Grid.Row="6" Grid.Column="1" /><!-- Add here all the code explained in the following code block -->

Password

Then, design the UI to set the password (optional) for the users’ cards.

<!--Password--><Label Grid.Row="7" Grid.Column="0" Grid.ColumnSpan="2"> <Label.FormattedText> <FormattedString> <Span Text="Password " TextColor="{AppThemeBinding Light=#505050, Dark=white}" /> <Span Text=" (Optional)" TextColor="Silver"/> </FormattedString> </Label.FormattedText></Label><Entry Grid.Row="8" Grid.Column="0" Grid.ColumnSpan="2" IsPassword="True"/> <!-- Add here all the code explained in the following code block --> 

Syncfusion .NET MAUI controls allow you to build powerful line-of-business applications.

Explore Now

Add button

Refer to the following code example to render the Add button.

<!--Add Button--> <Button Grid.Row="9" Grid.Column="0" Grid.ColumnSpan="2" HeightRequest="50" CornerRadius="10" Margin="0,10,0,0" BackgroundColor="#333333" Text="Add" TextColor="White"/>

Finally, let’s see the result of this step in both light and dark modes!

That is all! We have now finished the development of our Card Check Out UI in .NET MAUI!

GitHub reference

To see the complete code structure of this project, see our demo for Card Check Out UI in .NET MAUI on GitHub.

Conclusion

Thanks for reading! In this blog, we enhanced your XAML knowledge by teaching you how to replicate a card checkout UI using Syncfusion .NET MAUI controls. Try out the steps outlined in the post and leave your thoughts in the comments section below.

Syncfusion’s .NET MAUI controls were created from the ground up using .NET MAUI, which makes them feel like native framework controls. These controls are optimized to manage large amounts of data, making them ideal for building top-notch, cross-platform mobile and desktop applications.

If you have any questions or need assistance, don’t hesitate to reach us through our support forum, support portal, or feedback portal. We are always available to help you!

Related blogs

• Easily Design a Group Box View in .NET MAUI
• Easily Develop a Travel Destination Listing UI In .NET MAUI
• Learn Performing Animation in .NET MAUI: Part 2
• Designing Effective Data Entry Forms in .NET MAUI: A Step-By-Step Guide

View Details

A sign-up form allows users to create an account in an application by providing details such as name, email address, and password. Usually, such a form is used for registration or membership subscription.

The Syncfusion .NET MAUI DataForm allows developers to create data entry forms. This control also supports validating user input. By validating the input, users will be prompted to provide only correct values into the form, maintaining the integrity and consistency of the data stored in the database to prevent errors, inconsistencies, and security threats.

In this article, we’ll see how to create a sign-up form and validate the data entered using the Syncfusion .NET MAUI DataForm control.

Note: Refer to the .NET MAUI DataForm documentation before getting started.

Creating a sign-up form using the .NET MAUI DataForm control

First, create a sign-up form using the .NET MAUI DataForm control.

Initialize the .NET MAUI DataForm control

Follow these steps to initialize the .NET MAUI DataForm control:

1. Create a new .NET MAUI application in Visual Studio.
2. Syncfusion .NET MAUI components are available in the NuGet Gallery. To add the DataForm to your project, open the NuGet package manager in Visual Studio, search for Syncfusion.Maui.DataForm, and then install it.
3. Import the control’s namespace Syncfusion.Maui.DataForm in the XAML or C# code.
4. Initialize the SfDataForm control in the XAML page.

   <ContentPage> ….. xmlns:dataForm="clr-namespace:Syncfusion.Maui.DataForm;assembly=Syncfusion.Maui.DataForm" ….. <dataForm:SfDataForm/></ContentPage>

5. The NuGet package Syncfusion.Maui.Core is a dependent package for all Syncfusion .NET MAUI controls. In the MauiProgram.cs file, register the handler for the Syncfusion core assembly.

   builder.ConfigureSyncfusionCore()

Create the data form model

Let’s create the data form model for the sign-up form. This consists of fields to store specific information such as names, addresses, phone numbers, and more. You can also add attributes to the data model class properties for efficient data handling.

Refer to the following code example.

public class SignUpFormModel{ [Display(Prompt = "Enter your first name", Name = "First name")] public string FirstName { get; set; } [Display(Prompt = "Enter your last name", Name = "Last name")] public string LastName { get; set; } [Display(Prompt = "Enter your email", Name = "Email")] public string Email { get; set; } [Display(Prompt = "Enter your mobile number", Name = "Mobile number")] public double? MobileNumber { get; set; } [Display(Prompt = "Enter your password", Name = "Password")] public string Password { get; set; } [Display(Prompt = "Confirm password", Name = "Re-enter Password")] [DataType(DataType.Password)] public string RetypePassword { get; set; } [DataType(DataType.MultilineText)] [Display(Prompt = "Enter your address", Name = "Address")] public string Address { get; set; } [Display(Prompt = "Enter your city", Name = "City")] public string City { get; set; } [Display(Prompt = "Enter your state", Name = "State")] public string State { get; set; } [Display(Prompt = "Enter your country", Name = "Country")] public string Country { get; set; } [Display(Prompt = "Enter zip code", Name = "Zip code")] public double? ZipCode { get; set; }}

Create the sign-up form with editors

By default, the data form auto generates the data editors based on the primitive data types such as string, enumeration, DateTime, and TimeSpan in the DataObject property.

The .NET MAUI DataForm supports built-in editors such as text, password, multiline, combo box, autocomplete, date, time, checkbox, switch, and radio group.

Refer to the following code example. In it, we set the data form model (SignUpFormViewModel) to the DataObject property to create the data editors for the sign-up form.

XAML

<Grid.BindingContext> <local:SignUpFormViewModel/></Grid.BindingContext><dataForm:SfDataForm x:Name="signUpForm" DataObject="{Binding SignUpFormModel}"/>

C#

public class SignUpFormViewModel{ /// <summary> /// Initializes a new instance of the <see cref=" SignUpFormViewModel " /> class. /// </summary> public SignUpFormViewModel() { this.SignUpFormModel = new SignUpFormModel(); } /// <summary> /// Gets or sets the sign-up model. /// </summary> public SignUpFormModel SignUpFormModel { get; set; } }

Validating the data in the sign-up form using the .NET MAUI DataForm control

We have created the sign-up form. Let’s proceed with the validation processes.

Validate the data using the validation attributes

The .NET MAUI DataForm control provides the attributes to handle data validation. In our example, we’ll add the following validation checks to our sign-up form:

• Required fields validation: Ensures that all required fields, such as name, email, and password, are filled out before submitting the form.

• Email validation: Checks whether the email data is in the correct format. The email data should include the @ character (e.g., example@domain.com).

• Password strength validation: Ensures that the provided password satisfies certain criteria, such as minimum length and the inclusion of special characters.

• Confirm password validation: Ensures that the confirmed password matches the provided password.

• Phone number validation: Ensures that the phone number provided is valid and is in the correct format.

Refer to the following code example.

[Display(Prompt = "Enter your first name", Name = "First name")][Required(ErrorMessage = "Please enter your first name")][StringLength(20, ErrorMessage = "First name should not exceed 20 characters")]public string FirstName { get; set; } [Display(Prompt = "Enter your last name", Name = "Last name")][Required(ErrorMessage = "Please enter your last name")][StringLength(20, ErrorMessage = "First name should not exceed 20 characters")]public string LastName { get; set; } [Display(Prompt = "Enter your email", Name = "Email")][EmailAddress(ErrorMessage = "Please enter your email")]public string Email { get; set; } [Display(Prompt = "Enter your mobile number", Name = "Mobile number")][StringLength(10, MinimumLength = 6, ErrorMessage = "Please enter a valid number")]public double? MobileNumber { get; set; } [Display(Prompt = "Enter your password", Name = "Password")][DataType(DataType.Password)][DataFormDisplayOptions(ColumnSpan = 2, ValidMessage = "Password strength is good")][Required(ErrorMessage = "Please enter the password")][RegularExpression(@"^(?=.*[a-z])(?=.*[A-Z])[a-zA-Z\d]{8,}$", ErrorMessage = "A minimum 8-character password should contain a combination of uppercase and lowercase letters.")]public string Password { get; set; } [Display(Prompt = "Confirm password", Name = "Re-enter Password")][DataType(DataType.Password)][Required(ErrorMessage = "Please enter the password")]public string RetypePassword { get; set; } [DataType(DataType.MultilineText)][Display(Prompt = "Enter your address", Name = "Address")][Required(ErrorMessage = "Please enter your address")]public string Address { get; set; } [Display(Prompt = "Enter your city", Name = "City")][Required(ErrorMessage = "Please enter your city")]public string City { get; set; } [Display(Prompt = "Enter your state", Name = "State")][Required(ErrorMessage = "Please enter your state")]public string State { get; set; } [Display(Prompt = "Enter your country", Name = "Country")]public string Country { get; set; } [Display(Prompt = "Enter zip code", Name = "Zip code")][Required(ErrorMessage = "Please enter your zip code")]public double? ZipCode { get; set; }

Show validation success message

If the input values are correct, show the successful validation message. This will show the users that their provided data is in the required format.

Refer to the following code example. Here, we will display the valid message Password strength is good at the bottom of the Password field upon successful validation.

[Display(Prompt = “Enter your password”, Name = “Password”)][DataType(DataType.Password)][DataFormDisplayOptions(ColumnSpan = 2, ValidMessage = “Password strength is good”)][Required(ErrorMessage = “Please enter the password”)][RegularExpression(@”^(?=.*[a-z])(?=.*[A-Z])[a-zA-Z\d]{8,}$”, ErrorMessage = “A minimum 8-character password should contain a combination of uppercase and lowercase letters.”)]public string Password { get; set; }

Set validate modes in the DataForm

The .NET MAUI DataForm control supports the following validation modes to denote when the value should be validated:

• LostFocus: This is the default validation mode, and the input value will be validated when the editor loses focus.
• PropertyChanged: The input value will be validated immediately when it is changed.
• Manual: Use this mode to manually validate the values by calling the Validate method.

Refer to the following code example. Here, we have set the validation mode as PropertyChanged.

<dataForm:SfDataForm x:Name="signUpForm" DataObject="{Binding SignUpFormModel}" ValidationMode="PropertyChanged" CommitMode="PropertyChanged"/>

Validate the data using IDataErrorInfo

We can implement the IDataErrorInfo interface in the data object class to validate the sign-up form.

Refer to the following code example. Here, we implement the IDataErrorInfo validation in the RetypePassword field.

public class SignUpFormModel : IDataErrorInfo{ [Display(Prompt = "Enter your password", Name = "Password")] [DataType(DataType.Password)] [DataFormDisplayOptions(ColumnSpan = 2, ValidMessage = "Password strength is good")] [Required(ErrorMessage = "Please enter the password")] [RegularExpression(@"^(?=.*[a-z])(?=.*[A-Z])[a-zA-Z\d]{8,}$", ErrorMessage = "A minimum 8-character password should contain a combination of uppercase and lowercase letters.")] public string Password { get; set; } [Display(Prompt = "Confirm password", Name = "Re-enter Password")] [DataType(DataType.Password)] [Required(ErrorMessage = "Please enter the password")] [DataFormDisplayOptions(ColumnSpan = 2)] public string RetypePassword { get; set; } [Display(AutoGenerateField = false)] public string Error { get { return string.Empty; } } [Display(AutoGenerateField = false)] public string this[string name] { get { string result = string.Empty; if (name == nameof(RetypePassword) && this.Password != this.RetypePassword) { result = string.IsNullOrEmpty(this.RetypePassword) ? string.Empty : "The passwords do not match"; } return result; } }}

Validate the data using INotifyDataErrorInfo

You can also validate the data by implementing the INotifyDataErrorInfo interface in the data object class.

Refer to the following code example. Here we implemented INotifyDataErrorInfo validation in the Country field.

public class SignUpFormModel : INotifyDataErrorInfo{ [Display(Prompt = "Enter your country", Name = "Country")] public string Country { get; set; } [Display(AutoGenerateField = false)] public bool HasErrors { get { return false; } } public event EventHandler<DataErrorsChangedEventArgs> ErrorsChanged; [Display(AutoGenerateField = false)] public IEnumerable GetErrors(string propertyName) { var list = new List<string>(); if (propertyName.Equals("Country") && string.IsNullOrEmpty(this.Country)) list.Add("Please select your country"); return list; } }

Validate the form before signing up

Finally, we’ll validate the complete form when the Sign-up button is clicked by using the Validate method.

Refer to the following code example.

private async void OnSignUpButtonClicked(object? sender, EventArgs e){ if (this.dataForm != null && App.Current?.MainPage != null) { if (this.dataForm.Validate()) { await App.Current.MainPage.DisplayAlert("", "Signed up successfully", "OK"); } else { await App.Current.MainPage.DisplayAlert("", "Please enter the required details", "OK"); } }}

After executing the previous code example, we will get the output shown in the following images.

GitHub reference

Check out the complete code example to create and validate a sign-up form using the .NET MAUI DataForm on GitHub.

Conclusion

Thanks for reading! In this blog, we have learned how to create and validate a sign-up form using the .NET MAUI DataForm control. Try out the steps in this blog and leave your feedback in the comments section below.

For current Syncfusion customers, the newest version of Essential Studio is available from the license and downloads page. If you are not a customer, try our 30-day free trial to check out these new features.

You can also contact us through our support forums, feedback, or support portal. We are always happy to assist you!

Related blogs

• Authenticate the .NET MAUI App with Azure AD
• Designing Effective Data Entry Forms in .NET MAUI
• Easily Develop a Travel Destination Listing UI in .NET MAUI
• OCR in .NET MAUI: Building an Image Processing Application

View Details

View Details

In this first part of my post, I will focus on how to use the OpenAI APIs through HTTP POST requests, both to get text responses (completions) and to generate images with OpenAI technology. I want to emphasize that all the information presented in this publication is due to the valuable talk given by Luis Beltran, PhD, who gave us taught how to build a ChatGPT in .NET MAUI with the OpenAI APIs...

View Details

Franks heads back to create apps for games from the 1990s with .NET MAUI

Follow Us

• Frank: Twitter, Blog, GitHub
• James: Twitter, Blog, GitHub
• Merge Conflict: Twitter, Facebook, Website, Chat on Discord
• Music : Amethyst Seer - Citrine by Adventureface

⭐⭐ Review Us ⭐⭐

Machine transcription available on http://mergeconflict.fm

Sponsored By:

• Syncfusion: Syncfusion offers the largest selection of controls for .NET MAUI, Xamarin, WPF, Windows Form, Win UI, Flutter, Blazor, ASP.NET Core, and more! Check out our components on NuGet and don’t forget to download their free e-books.

Support Merge Conflict

Links:

• praeclarum/ThreeDO

View Details

This is a short article with a solution to a problem I couldn’t find on the internet. I upgraded VS for Mac to version 17.4.5 recently, and upgraded Xcode to the appropriate version as stated in the docs (https://learn.microsoft.com/en-us/visualstudio/releases/2022/mac-release-notes). As it happens often, I had a bad surprise after this. I tried uploading an app […]

READ MORE

The post Uploading Your Xamarin or MAUI iOS app to the App Store Without VS for Mac appeared first on Doumer's Blog.

View Details

An Avatar is a graphical representation that is associated with a specific user for identification purposes. This is widely used in our everyday applications, and that is why it’s important that you have the tools at hand that will help you achieve it.. In this article we will learn how to implement the .NET Maui Community Toolkit AvatarView in very simple and quick steps!  

We will learn to integrate it in a simple way! The explanation will be divided into the following points:

.NET MAUI Community Toolkit: Implementation

 Preparing your XAML to add the AvatarView

 Knowing the AvatarView’s properties

Let’s start!

.NET MAUI Community Toolkit: Implementation

The key to achieve drawing in our App is to use Community.ToolKit.Maui NuGet package, let’s see its definition and how to implement it.

What is .NET MAUI Community Toolkit??

It’s a collection of reusable elements such as animations, behaviors  converters, among others, for developing applications for iOS, Android, macOS and WinUI using MAUI.

Let’s implement it:

• • Add from NuGet Package: Community.Toolkit.Maui

• • Now let’s initialize: Go to your MauiProgram.cs file

 In the CreateMauiApp method, place in the .UseMauiApp<App>() line and just below it add the following line of code:

Don’t forget to add the using CommunityToolkit.Maui;at the top of the class.

Preparing your XAML to add the AvatarView

What is AvatarView?

AvatarView is a control provided by Community.Toolkit.Maui which is responsible for providing  a user’s avatar image or their initials. This one can be text, colores or shaped. And all with support for shadows and gestures.

To continue, add the following namespace on your XAML:

Then, you have to add the DrawingView tag with the properties that you need:

Knowing the DrawingView’s properties

It has different useful properties, let’s know some of them:

BackgroundColor: Sets the background color that the AvatarView will have.

BorderColor and BorderWidth: Are responsible of establishing the color and width of the border respectively, which the AvatarView will have.

Text and TextColor: Allow us to establish text and color of the letters respectively.

CornerRadius: Determines the shape of the control.

You can also add an image using the ImageSource property.

The CornerRadius Property, beside allowing us to set a single value to round all smooth edges, also allows us to add separate values ​​for the top left, top right, bottom left, and bottom right of the control.

Keep in mind that if you add an image, you won’t be able to display the text.

 Additional information

The default value for the AvatarView’s WidthRequest and HeightRequest properties is 48. Unless the AvatarView is constrained by its design or the value of these properties is specified.

Spanish article: https://es.askxammy.com/agregando-un-avatar-con-net-maui-community-toolkit/

References: https://learn.microsoft.com/en-us/dotnet/communitytoolkit/maui/views/avatarview?view=net-maui-7.0?WT.mc\_id=DT-MVP-50033

View Details

View Details

Join Syncfusion developer Chad Church and JetBrains developer advocate Khalid Abuhakmeh as they collaborate on a .NET MAUI mobile app for building personal cookbooks. You’ll be able to snap a picture of a recipe anywhere, annotate it, and pull it up whenever you need it. By the end, you’ll have the functionality to sort your cookbook for specific kinds of recipes, too.

This free webinar will take place on Thursday, March 16, at 11 a.m. EDT. Register now and see firsthand how .NET MAUI makes mobile development fast and efficient, putting powerful features at your fingertips.

Register for Webinar

Related Links

• Essential Studio for .NET MAUI
• Syncfusion .NET MAUI Control Demos Are Now Available at App Stores
• Syncfusion .NET MAUI 2023 Roadmap

View Details

The Syncfusion .NET MAUI Calendar control allows users to select a single date, multiple dates, or a range of dates easily. It provides month, year, decade, and century views so you can quickly navigate to your desired date.

In this blog, we’ll explore the significant features of the .NET MAUI Calendar.

Calendar views

The .NET MAUI Calendar control supports month, year, decade, and century views. You can use them to navigate to and select a desired date quickly. The Calendar control also supports programmatic navigation.

Multiple Views in the .NET MAUI Calendar Control

Selection modes

There are three different selection modes in the .NET MAUI Calendar to select dates:

• Single selection: The most basic selection mode, it allows you to select a single date on the calendar.
• Multiple selection: This mode allows you to select multiple dates on the calendar.
• Range selection: You can select a range of dates by specifying the start and end dates on the calendar.

Date Selection Modes in the .NET MAUI Calendar Control

Range selection modes

You can extend the date-range selection with the following range selection modes in the .NET MAUI Calendar:

• Default: The basic type of range selection. It allows you to select different ranges once the current range is completed.
• Forward: Extend the date range’s end date farther into the future.
• Backward: Move the start date earlier to extend the date range.
• Both: Extending the date range both to start earlier and end later.
• None: Restrict the selection once the range is completed.

Date Range Selection Modes in the .NET MAUI Calendar Control

Managing the number of weeks in a month view

You can customize the number of weeks displayed in the Calendar. The month view rows will be rendered based on the specified number of weeks.

Week number view

The .NET MAUI Calendar also supports displaying the week numbers (of the year) in the month view in a separate column before the month cells.

Customizing your date selection limits

Restrict interaction and navigation beyond the specified date limit by setting the minimum and maximum dates.

First day of the week

Not all calendar systems begin the week on Sunday. You can easily customize the first day of the week in the .NET MAUI Calendar’s monthly view to fit your needs.

Restricting date selection

You can restrict date selection in the .NET MAUI Calendar using any of the following features:

• Minimum and maximum dates: Configure the minimum and maximum dates to prevent selection outside the date range.
• Selectable day predicate (BlackoutDates): Disable specific dates on the calendar view to prevent selection of them.
• Disable dates in the past: Disable the dates before today on the calendar view to prevent selection of them.

Restricting Date Selection in the .NET MAUI Calendar Control

Customizing the holidays

The .NET MAUI Calendar allows users to configure special dates like holidays and weekend days. Customize the background color and text style to highlight any date and every weekend in a month as special days.

Customizing the Holidays and Weekends in the .NET MAUI Calendar

Personalize the appearance of your calendar

You can customize the appearance of calendar elements such as the header, month, year, decade, century, selected dates, trailing and leading dates, and disabled cells.

Right-to-left (RTL) support

The .NET MAUI Calendar includes right-to-left (RTL) rendering support to display the calendar views.

Globalization

You can display the .NET MAUI Calendar views based on global date and time formats. This will help you to reach out to a global audience easily.

Conclusion

Thanks for reading! In this blog, we have seen the significant features of the Syncfusion .NET MAUI Calendar control. Try out this user-friendly control and share your feedback in the comments section below.

Also, check out our .NET MAUI controls demos on GitHub.

If you are not a Syncfusion customer, you can try our 30-day free trial to see how our components can enhance your projects.

For questions, you can reach us through our support forum, support portal, or feedback portal. We are always happy to assist you!

Related blogs

• Introducing the New .NET MAUI Text Input Layout
• Create Project Planning and Resource Management Calendar in .NET MAUI
• Introducing the New .NET MAUI Funnel Charts
• Syncfusion .NET MAUI 2023 Roadmap

View Details

Earlier this week, the .NET SDK and Runtimes received some updates. Together with that, also Visual Studio for Mac was updated. Once I got past the installation of all updates, both Visual Studio and Rider were no longer restoring the required NuGet packages for my .NET MAUI project running on .NET 6.

I eventually fixed that issue by cleaning up all the .NET SDKs, Runtimes, workloads and NuGet caches on my MacBook Pro. Read on to learn about the tools I used.

.NET uninstall tool

I have been using the .NET uninstall tool in the past. Unlike on Windows, you have to download the executable from GitHub in its zipped form.

While the releases page shows some terminal commands to unpack and run the tool, they never worked for me as stated there. While I was able to make the new directory with the mkdir command, the unpacking always shows an error. So I opened up Finder and unzipped it manually with the Archive Utility app that ships with macOS.

After switching to the folder in Terminal, the tool is supposed to show the help. Instead, I got an error showing me that I am not allowed to run this app for security reasons. The OS blocks the execution. If the same happens for you, right click on the extracted executable and select “Open With” followed by “Terminal.app (default)“. This will prompt you with this screen:

Once you click on “Open“, a new Terminal window appears. Close this window, it is unusable as we are already in the exited state. Instead, open a new Terminal and change to the installation folder and call the help command:

cd ~/dotnet-core-uninstall./dotnet-core-uninstall -h

Now that we are able to run the tool, let’s have a look what we have installed by running the dotnet --list command. We need to call the command twice, once for the installed -sdks and once for the installed -runtimes:

dotnet --list-sdksdotnet --list-runtimes

You may be as surprised (I was, at least) how many versions you are accumulating over time. They never get removed by newer versions (it’s by design, according to Microsoft). To get rid of all versions except the latest, run the following commands with the uninstall tool (again once for — sdk, once for –runtime):

sudo ./dotnet-core-uninstall remove --all-but-latest --sdksudo ./dotnet-core-uninstall remove --all-but-latest --runtime

After uninstalling all previous versions, you may have to reinstall the latest .NET 6 SDK again. You could also use the –-all-but [Versions] command to specify the versions explicitly. No matter which way you’re going, if you run the dotnet --list commands again, you should see something similar to this:

Download: https://github.com/dotnet/cli-lab/releases

Documentation: https://learn.microsoft.com/en-us/dotnet/core/additional-tools/uninstall-tool?tabs=macos#step-3—uninstall-net-sdks-and-runtimes

dotnet workload command

As I had problems getting the required NuGet packages for my MAUI app, I decided to uninstall all .NET MAUI workloads as well. First, I had a look what is installed with the list command:

dotnet workload list

Once you have that list, you need to call the uninstall command for every single installed workload:

sudo dotnet workload uninstall macos maui-maccatalyst maui-ios maui-android ios maccatalyst maui tvos android

Once they are uninstalled, I cleared the Terminal and installed them all again using the install command:

sudo dotnet workload install macos maui-maccatalyst maui-ios maui-android ios maccatalyst maui tvos android

Now we have the latest .NET MAUI workload installed as well as the platform specific workloads as well.

Documentation: https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-workload

dotnet nuget locals

The final clean-up step involves all NuGet caches on your machine. Yes, you read that right, multiple caches. To see them all, run the following command:

dotnet nuget locals all --list

This will get you something like this:

Now let’s get rid of all those old NuGet packages:

sudo dotnet nuget locals all --clear

If you’re lucky, you will see this message:

My first attempt was not that successful. I needed to open the global packages’ folder in Finder and delete some remaining packages manually. Only after that, I was able to run the clear command with success.

Conclusion

Neither Visual Studio nor the .NET installer perform clean-up tasks on macOS. Until Microsoft changes their mind here, we will have to clean-up old packages manually to keep our system smoothly running. Luckily, there are at least CLI tools around to help us with that job. As always, I hope this blog post will be helpful for some of you.

Until the next post, happy coding, everyone!

The post How to use the .NET CLI clean-up tools on macOS appeared first on MSicc's Blog.

View Details

Have you had the need to add drawing functionality to your .NET MAUI apps? .. Probably yes, .. but beyond drawing… Have you required the user of your banking App to sign through it? In this article, we learn how to do it with the .NET MAUI Community Toolkit.

We will learn to integrate it in a simple way! The explanation will be divided into the following points:

.NET MAUI Community Toolkit: Implementation

 Preparing your XAML to add the DrawView

 Knowing the DrawingView’s properties

 Cleaning the DrawView

Showing the image from DrawView

Let’s start!

.NET MAUI Community Toolkit: Implementation

The key to achieve drawing in our App is to use Community.ToolKit.Maui NuGet package, let’s see its definition and how to implement it.

What is .NET MAUI Community Toolkit??

It’s a collection of reusable elements such as animations, behaviors  converters, among others, for developing applications for iOS, Android, macOS and WinUI using MAUI.

Let’s implement it:

• Add from NuGet Package: Community.Toolkit.Maui

• Now let’s initialize: Go to your MauiProgram.cs file

 In the CreateMauiApp method, place in the .UseMauiApp<App>() line and just below it add the following line of code:

Don’t forget to add the using CommunityToolkit.Maui;at the top of the class.

Preparing your XAML to add the DrawView

What is DrawingView?

Is a class provided by Community.Toolkit.Maui which is responsible for providing a surface that allows drawing lines through touch or mouse interaction.

To continue, add the following namespace on your XAML:

Then, you have to add the DrawingView tag with the properties that you need:

Knowing the DrawingView’s properties

It has different useful properties, let’s know some of them:

WidthRequest and HeightRequest: These properties help to set the width and height respectively. Keep in mind that you must add both properties to your DrawingView in order for it to be displayed correctly in your app.

LineColor: It’s the color that the drawing line will have.

LineWidth: It’s the width that the drawing line will have.

IsMultiLineModeEnabled: By default, the DrawingView allows only one stroke to be drawn at a time. The IsMultiLineModeEnabled property allows you to change this and draw multiple lines at once. It receives Bool values. To activate it you need to set the value to True.

Cleaning the DrawView

If you want to clear the DrawView, do the following:

Add a button with a Click event.

Go to CodeBehind and in the Button event, add the following:

You can also do this with MMVM.

Showing the image from DrawView

Add an Image control to your XAML.

We will use the DrawingLineCompleted event for the DrawingView.

Finally, develop the event:

You can also do this with MMVM.

And done! You are ready to draw and sign in your .NET MAUI applications!

View Details

There has never been a better time to update & migrate your Xamarin.iOS and Xamarin.Android apps to the latest version of .NET. The update process for most apps should be quick and when you are finished you will be able to take advantage of the latest features of .NET 7 including C# 11 and the new project system. In addition, iOS & Android apps built against .NET 6 and .NET 7 have large performance improvements and developer productivity features as they take advantage of build system enhancements. The team has just released upgrade documentation for apps, so go head over there for a full walkthrough. In this blog, I will walk you through some tips & tricks to get started with your update.

If you are looking to update and migrate your Xamarin.Forms based applications then skip this blog and follow the self-guided documentation that outlines out to manually update or take advantage of the .NET Upgrade Assistant.

Work in a Branch

Before you start your update process it is a good idea to work in a branch if you are using git! This will ensure you can easily roll back and iterate over time if you have a complex project.

Analyze NuGet Packages

The first step in the upgrade process is to check your NuGet packages in your projects. You will need to ensure that they have been updated and re-compiled against .NET 6 or .NET 7 for iOS and Android.

Consider my Xamarin.Android app that I am looking to update, it has references to AndroidX, Material Design, Xamarin.Essentials, and a few of my own libraries:

<ItemGroup> <PackageReference Include="Xamarin.AndroidX.AppCompat" Version="1.6.0.1" /> <PackageReference Include="Xamarin.Google.Android.Material" Version="1.7.0.2" /> <PackageReference Include="Xamarin.Essentials" Version="1.7.4" /> <PackageReference Include="Plugin.InAppBilling" Version="6.7.0" /> <PackageReference Include="MonkeyCache.FileStore" Version="1.5.2" /></ItemGroup>

You can browse NuGet.org to find your packages and see what frameworks they support. In the case of Xamarin.AndroidX.AppCompat we can see that it supports both monoandroid12.0 (Xamarin.Android) and net6.0-android31.0 (compiled against .NET 6).

Note: For Xamarin.Android projects it is recommended to migrate from Android Support Libraries as they are not supported in .NET 6+ Android projects. You can do this by migrating to AndroidX by following the migration guide documentation.

In this case, this library is fully compatible with the latest versions of .NET for Android. If the version of a NuGet package isn’t compatible with the latest framework you may need to update to a new version or find a replacement. Monkey Cache for example only supports only supported Xamarin apps in version 1.5.2, but version 2.0.1 was recompiled against .NET 6 and will be compatible.

Update Project Files

Android and iOS are now integrated directly into .NET. This means that they have have new Target Framework Monikers of net7.0-android and net7.0-ios. They also use the new .NET SDK project style. This means the configuration inside of your projects .csproj has been greatly simplified. The next step in the process is to unload your Android and iOS Projects. The easiest thing to do is delete all of the content inside of it and add the new base SDK style project settings:

Android:

<Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFramework>net7.0-android</TargetFramework> <OutputType>Exe</OutputType> </PropertyGroup></Project>

iOS:

<Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFramework>net7.0-ios</TargetFramework> <OutputType>Exe</OutputType> </PropertyGroup></Project>

Notice here that there is no longer the need to manually reference individual files, resources, or compilation settings for Debug or Release. The project system is automatically configured to use defaults. You can always update these settings with the new project settings dialog.

Before reloading the project it is a good idea to manually delete the obj and bin folders for the project.

Android: Delete Resource.designer.cs

In Xamarin.Android projects a Resource.designer.cs file was generated when resources changed and added into the Resources folder. This file is no longer needed and can be deleted as they are auto generated as a code generation step.

Delete AssemblyInfo.cs

Similar to the Resource.designer.cs the AssemblyInfo.cs file is automatically generated based on project settings. These files can be deleted from the Properties folder for both iOS and Android.

Note: You may have had permission settings in your Android project’s AssemblyInfo.cs file. You can leave these and remove everything else, or move them to another file.

Xamarin.Essentials to .NET MAUI Essentials

Xamarin.Essentials was a fundamental library for nearly every Xamarin application. If you were using this NuGet package, you will want to remove it as Xamarin.Essentials is now part of .NET MAUI. The team has worked hard to ensure that while it comes pre-configured with every .NET MAUI application, it is still available to all iOS and Android apps built with .NET.

<PropertyGroup> <UseMauiEssentials>true</UseMauiEssentials></PropertyGroup>

Once you update to .NET MAUI Essentials, you will need to update any using Xamarin.Essentials; using statements to the new .NET MAUI Essentials namespaces, which you can find in the documentation.

Add & Update NuGet Packages

Going back to the NuGet packages that we previously analyzed, now we can add them back into our project. For our Android app we will move over and update the packages to the latest versions that are compatible, and remove the reference to Xamarin.Essentials:

<ItemGroup> <PackageReference Include="Xamarin.AndroidX.AppCompat" Version="1.6.0.1" /> <PackageReference Include="Xamarin.Google.Android.Material" Version="1.7.0.2" /> <PackageReference Include="Plugin.InAppBilling" Version="6.7.0" /> <PackageReference Include="MonkeyCache.FileStore" Version="2.0.1" /></ItemGroup>

Project References

If you reference any other .NET Standard libraries you can add them as a project reference. Any Xamarin.iOS or Xamarin.Android class library or binding library will also need to be updated to the new formats and then added back as references. You may want to consider updating your .NET Standard libraries to .NET 6 or .NET 7 to take advantage of the latest features of .NET and C#!

Use New Features

There are several enhancements to the project system that help you easily manage app settings. Now, you can manage your app versions, supported platform versions, app identifiers, and more!

Here are a few settings you can add to your ProjectGroup in your project:

<ApplicationTitle>MyApp</ApplicationTitle><SupportedOSPlatformVersion>21</SupportedOSPlatformVersion><ApplicationId>com.companyname.myapp</ApplicationId><ApplicationVersion>1</ApplicationVersion><ApplicationDisplayVersion>1.0</ApplicationDisplayVersion>

Once these are added you can remove them from your AndroidManifest.xml and Info.plist. Additionally, you can remove the <uses-sdk/> node from the AndroidManifest.xml as these are now outlined with these settings. There are many more options that you can find on documentation for Android and documentation for iOS

Additionally, you may want to consider turning on implicit usings and enabling nullable reference types

 <Nullable>enable</Nullable> <ImplicitUsings>enable</ImplicitUsings>

Summary

I hope that you found this upgrade guide nifty on getting your Xamarin.iOS and Xamarin.Android apps updated to the latest version of iOS & Android for .NET. I tried to cover a lot of tips & tricks, but be sure to read the full migration documentation for even more.

For more information on the performance improvements be sure to browse through the amazing blog posts from Jonathan Peppers on .NET 6 improvements and .NET 7 improvements.

I also have uploaded full before and after code samples available on my GitHub.

Don’t forget to read through the Xamarin support policy to make sure you plan your upgrade and migration.

The post Tips & Tricks on Upgrading Xamarin.iOS & Xamarin.Android to .NET for iOS & Android appeared first on Xamarin Blog.

View Details

As you know, Android is always adding features in its new versions and now the Post Notifications permission has been introduced from Android 13. In this blog, we are going to explore how to request it in our Xamarin.Android projects.

Sample Project

1. Let’s set Android 13.0 as the Target framework.

Open your project settings by right-clicking on your Android project then then selecting -> Properties -> Application. This is required because this permission is only supported in API versions starting with 33, which means Android version 13 or later.

Next, Select Android Manifest -> Set Target Android version.

2. Let’s add the Post Notification permission on Android Manifest

Go to the Android project then right-click -> Properties -> Android Manifest

3. Let’s install the Xamarin.Essentials NuGet Package

We have to initialize Xamarin.Essentials in our Android project, so let’s add this code in the MainActivity.cs file:

protected override void OnCreate(Bundle savedInstanceState){ base.OnCreate(savedInstanceState); Xamarin.Essentials.Platform.Init(this, savedInstanceState); global::Xamarin.Forms.Forms.Init(this, savedInstanceState); LoadApplication(new App());}public override void OnRequestPermissionsResult(int requestCode, string[] permissions, [GeneratedEnum] Android.Content.PM.Permission[] grantResults){ Xamarin.Essentials.Platform.OnRequestPermissionsResult(requestCode, permissions, grantResults); base.OnRequestPermissionsResult(requestCode, permissions, grantResults);}

4. Let’s create an Interface in the shared project

For this example, we are going to create the file IPostNotificationPermissionService.cs, and then we’ll implement it in each platform.

Add the following code to the file:

public interface IPostNotificationPermissionService{ Task<bool> CheckAndRequestPermissions();}

5. Let’s implement IPostNotificationPermissionService in the Android project

We need to request the Post Notifications permission and show the prompt, but how do we do that? We added Xamarin.Essentials to allow us to extend permissions. You can see the detailed documentation on permissions in Xamarin.Essentials here.

internal class PostNotificationsPermission : BasePlatformPermission{ public override (string androidPermission, bool isRuntime)[] RequiredPermissions => new List<(string androidPermission, bool isRuntime)> { (Manifest.Permission.PostNotifications, true) }.ToArray();}

Now we can use PostNotificationsPermission to implement our IPostNotificationPermissionService interface.

public class PostNotificationPermissionService : IPostNotificationPermissionService{ public async Task<bool> CheckAndRequestPermissions() { // Tiramisu is Android v13 if (Build.VERSION.SdkInt >= BuildVersionCodes.Tiramisu) { var status = await CheckStatusAsync<PostNotificationsPermission>(); if (status == PermissionStatus.Granted) { return true; } status = await RequestAsync<PostNotificationsPermission>(); return status == PermissionStatus.Granted; } return true; }}

6. Let’s inject PostNotificationsPermission

We are going to add the Xamarin Dependency Injection.

[assembly: Dependency(typeof(PostNotificationPermissionService))]namespace NotificationApp.Droid{ // Extend Xamarin Essentials internal class PostNotificationsPermission : BasePlatformPermission { // ... } // Implementing PostNotificationPermission public class PostNotificationPermissionService : IPostNotificationPermissionService { // ... }}

7. Let’s use PostNotificationsPermission

We are going to override the OnAppearing method in the MainPage.xaml.cs

protected override async void OnAppearing(){ base.OnAppearing(); var service = DependencyService.Get<IPostNotificationPermissionService>(); await service.CheckAndRequestPermissions();}

8. Let’s run the app

As you can see, that’s all it takes to implement a new Android permission in Xamarin. Easy, right?

All of my code is available on GitHub for you to review. Happy coding!

References

• Android Post Notifications permission
• Xamarin.Forms DependencyService

The post Adding a New Android Permission in a Xamarin App appeared first on Trailhead Technology Partners.

View Details

View Details

Nuke image caching library for dotnet MAUI.

GitHub - roubachof/Maui.Nuke: Maui version of the Nuke iOS image caching native library

Maui version of the Nuke iOS image caching native library - GitHub - roubachof/Maui.Nuke: Maui version of the Nuke iOS image caching native library

GitHubroubachof

Get it from NuGet:

Before, in Xamarin.Forms, to speed up our image loading we could use GlideX on Android, and Xamarin.Forms.Nuke on iOS.

With this solution, we achieved a perfect efficient native image caching solution for both platform.

But since MAUI, the Android platform has integrated the Glide native library. No need to use GlideX now.
Unfortunately on, iOS, there is no integrated native caching...

It means the caching and performance of using images on iOS is not so great in terms of speed and memory usage.

But rejoice!

Maui.Nuke is here to repair this injustice by implementing image caching with the fastest and most popular ios native caching library: Nuke \o/

Moreover, once installed, it is completely transparent to the user, you use your Image views just like before, all the work is done under the hood.

This project is using the NukeProxy library, which is a Swift .net6 proxy to the nuke native library. The new binding and the packaging has been done by the great @cheesebaron. Hail to the Cheese!

Current version of the Nuke library is 10.3.1.

Installation

public static MauiApp CreateMauiApp(){ var builder = MauiApp.CreateBuilder(); builder .UseMauiApp<App>() .UseNuke(showDebugLogs: false);}

BOOM

You just achieved 90%+ memory reduction when manipulating Image views.

View Details

The .NET team focused on delivering several major updates and improvements to the .NET Framework for version 7. These included a unified codebase, a single base class library (BCL) for all supported platforms, and native support for ARM64. The team also enhanced .NET support for Linux and continued work on performance improvements and developer productivity upgrades.

One of the major themes of these updates was the emphasis on modern and cloud-native app development—the ability to build cross-platform mobile and desktop apps from the same codebase and support container-first workflows. The team also aimed to ease the development and deployment of distributed cloud-native apps using. NET.

In addition to these updates, the team also worked on simplifying the development process and making it easier for developers to write code. It introduced C# 11, which aims to reduce the amount of code needed to perform everyday tasks, and improved HTTP/3 and minimal APIs to support cloud-native app development.

Overall, the updates and improvements focused on making .NET a powerful and flexible framework for building modern, cloud-native applications and making it easier for developers to write and maintain their code. Let’s cover these updates in more detail.

Easily build cross-platform mobile and desktop apps with the flexible and feature-rich controls of the Syncfusion .NET MAUI platform.

Explore Now

A single base class library

The .NET team focused on delivering a unified codebase and a single base class library (BCL) for all supported platforms in the .NET 7 release. This means developers can use the same tools and libraries to build many applications, including cloud, web, mobile, and gaming apps. Developers will find it easier to work across different platforms and be confident that their code is consistent and portable. This change also makes it easier for developers to take advantage of new features and improvements in the .NET Framework, as they are available across all supported platforms.

Multiple platform support

The .NET 7 Framework supports multiple platforms, including Android, iOS, macOS, and Windows. Developers can use the same codebase to build applications on any platform. Additionally, the .NET Framework supports multiple CPU architectures, including x64, x86, ARM64, and ARM32, meaning  developers can build applications that run on various devices, from phones to desktop computers.

The .NET Framework also includes tools and libraries that make it easy for developers to build applications that run on multiple platforms. It supports cross-platform APIs and tools for building, deploying, and debugging applications on different platforms. This makes it easier for developers to build applications that can run on any device, regardless of its operating system or CPU architecture.

Syncfusion .NET MAUI controls are well-documented, which helps to quickly get started and migrate your Xamarin apps.

Read Now

Performance improvements for ARM64 using 64-bit IBM support

The .NET 7 Framework includes native support for ARM64, which enables applications to take advantage of the performance benefits of 64-bit processing on ARM-based devices. This feature can improve the overall performance of applications and can also help reduce power consumption on such devices.

The .NET team worked closely with IBM to support 64-bit ARM architectures in the .NET Framework. Their efforts included optimizing the .NET runtime and core libraries for ARM64 and implementing support for new features in the IBM POWER9 processor. This collaboration helped ensure that the .NET Framework can take full advantage of the performance and power-saving capabilities of 64-bit ARM architectures.

Native support for ARM64 in the .NET 7 Framework improves the performance and efficiency of applications running on ARM-based devices. This can help reduce power consumption and extend battery life. This makes the .NET Framework a powerful and flexible tool for building applications that run on various devices, including those with low-power processors.

Enhanced .NET support on Linux

The .NET 7 Framework includes enhanced support for Linux, delivering improvements to the .NET runtime, core libraries, and new tools and libraries for building, deploying, and debugging .NET applications on Linux.

Developers now have an easier time building and deploying .NET applications on Linux-based systems, such as servers, cloud environments, and IoT devices. The improvements positively affect the performance and reliability of such applications and make it easier for developers to take advantage of the unique features and capabilities of Linux-based systems.

To make it easy for developers to include Syncfusion .NET MAUI controls in their projects, we have shared some working ones.

Explore Now

New target framework moniker

The .NET 7 Framework introduces a new target framework moniker (TFM) for specifying the version of the .NET Framework that an application targets. The new TFM is net7.0, which replaces the previous TFM of net6.0 used in the previous stable version of the .NET Framework.

The new TFM is used in an application’s project file to specify which version of the .NET Framework the application targets. This allows developers to take advantage of new features and improvements in the .NET 7 Framework while still being able to build and run their applications on previous versions of the .NET Framework.

For example, a developer can specify the net7.0 TFM in their application’s project file, enabling the application to use new features and improvements in the .NET 7 Framework. However, the application will still be able to run on earlier versions of the .NET Framework, such as .NET 6.0, as long as it does not use any features or APIs that are not available in those earlier versions.

Overall, this can help improve the performance and reliability of .NET applications and make it easier for developers to maintain and upgrade their applications over time.

Built for cloud-native apps and mobile clients

The .NET MAUI (Multi-platform App UI) framework is specifically designed for building cloud-native and mobile applications. It is a cross-platform framework that enables developers to build applications that run on various platforms, including mobile devices, desktop computers, and cloud environments.

Syncfusion .NET MAUI controls allow you to build powerful line-of-business applications.

Explore Now

The .NET MAUI framework includes several features and tools that make it well-suited for building cloud-native and mobile applications. For example, it supports modern app development patterns, such as microservices and containers, and provides tools for building and deploying applications to the cloud. It also includes cross-platform APIs and controls for building user interfaces that can adapt to different screen sizes and resolutions, which is essential for building applications that run on a wide range of devices.

Developers can create scalable, reliable, and high-performance applications with .NET MAUI that run on any platform, and use the framework to better maintain and update their applications over time.

Conclusion

Thank you for reading! Syncfusion’s support for .NET MAUI is a continuous process, and we’ve just released our sixth set of controls and updates for the platform. More information about our MAUI controls and other features in Essential Studio 2022 Volume 4 can be found on our Release Notes and What’s New pages. Try out the upgrades and share your thoughts in the comment section below!

You can get in touch with us via our support forum, support portal, or feedback portal. We are always delighted to help!

Related blogs

• Arm: The Future of Software Development
• 4 Impressive Features of .NET MAUI in .NET 7
• Syncfusion Mobile and Desktop Controls are Now Compatible with .NET 7
• 5 Important Things to Make Your Cross-Platform (.NET MAUI) App Accessible

View Details

The Syncfusion .NET MAUI DataGrid control displays and manipulates data in a tabular view. It was built from the ground up in .NET MAUI to achieve the best possible performance, even when loading a huge volume of data. It supports various built-in column types based on the data object bound to it.

The following table shows the supported data types and their corresponding column types.

Note: For the remaining data types, a Text Column will be created.

You can generate columns either automatically or manually. The .NET MAUI DataGrid creates columns automatically based on the bindable property AutoGenerateColumnsMode. The columns are generated based on the type of individual properties in the underlying collection set in the ItemsSource.

For more details, refer to the different modes of autogenerating columns in .NET MAUI DataGrid documentation.

Let’s explore the different column types in the .NET MAUI DataGrid control with code examples.

Types of columns

The .NET MAUI DataGrid supports the following built-in column types:

• Text column
• Checkbox column
• Image column
• Template column
• Numeric column
• Date column

Each column has properties to handle different kinds of data. For this demo, we will display business data with the dealer’s name and ID, the shipped date, and more with these column types.

Note: If you’re new to our .NET MAUI DataGrid, please refer to its getting started documentation.

Text column

The text column hosts the text content in the record cells. Each record cell displays text based on the MappingName property that associates the column with a property in the data source.

Refer to the following code example to display the dealers’ names.

<syncfusion:SfDataGrid x:Name="dataGrid" ItemsSource="{Binding DealerInformation}" AutoGenerateColumnsMode="None"> <syncfusion:SfDataGrid.Columns> <syncfusion:DataGridTextColumn HeaderText="Name" MappingName="DealerName"> </syncfusion:DataGridTextColumn> </syncfusion:SfDataGrid.Columns></syncfusion:SfDataGrid>

Checkbox column

A checkbox column holds Boolean values in its cells. We will load the .NET MAUI CheckBox framework control as the content of the record cells and the checkboxes then respond to the Boolean value changes. Based on changes in the data source, the values in the checkbox will be toggled.

Refer to the following code example. We render checkboxes to denote the online status of the dealers.

<syncfusion:SfDataGrid x:Name="dataGrid" ItemsSource="{Binding DealerInformation}" AutoGenerateColumnsMode="None"> <syncfusion:SfDataGrid.Columns> <syncfusion:DataGridCheckBoxColumn HeaderText="Is Online" MinimumWidth="{StaticResource minimumWidth}" MappingName="IsOnline"> </syncfusion:DataGridCheckBoxColumn> </syncfusion:SfDataGrid.Columns></syncfusion:SfDataGrid>

Image column

An image column displays images in its record cells. We will load the .NET MAUI Image framework control to display the grid cell content.

Refer to the following code example to display the dealers’ images.

<syncfusion:SfDataGrid x:Name="dataGrid" ItemsSource="{Binding DealerInformation}" AutoGenerateColumnsMode="None"> <syncfusion:SfDataGrid.Columns> <syncfusion:DataGridImageColumn HeaderText="Dealer" MappingName="DealerImage" CellPadding="8"> </syncfusion:DataGridImageColumn> </syncfusion:SfDataGrid.Columns></syncfusion:SfDataGrid>

Template column

You can display the column values with your desired view using the CellTemplate property. By default, the underlying record is BindingContext for CellTemplate. So, we should define the template for each column to display values based on the MappingName property.

Refer to the following code example.

<syncfusion:SfDataGrid x:Name="dataGrid" ItemsSource="{Binding DealerInformation}" AutoGenerateColumnsMode="None"> <syncfusion:SfDataGrid.Columns> <syncfusion:DataGridTemplateColumn MappingName="Name" MinimumWidth="200" MaximumWidth="{StaticResource nameColumnWidth}"> <syncfusion:DataGridTemplateColumn.HeaderTemplate> <DataTemplate> <Label Text="Product Details" FontFamily="Roboto-Medium" FontSize="14" FontAttributes="Bold" HorizontalOptions="Start" VerticalOptions="Center" Margin="{OnPlatform WinUI='0,16,0,15', MacCatalyst='0,16,0,15', Android='10,8,0,7', iOS='10,8,0,7'}"></Label> </DataTemplate> </syncfusion:DataGridTemplateColumn.HeaderTemplate> <syncfusion:DataGridTemplateColumn.CellTemplate> <DataTemplate> <ContentView VerticalOptions="Start"> <StackLayout Orientation="Horizontal"> <StackLayout HeightRequest="84" Margin="{OnPlatform WinUI='0,8,4,8', iOS='8,8,4,8',Android='8,8,4,8', MacCatalyst='0,8,4,8'}" HorizontalOptions="End" VerticalOptions="Start"> <Label Margin="0,3,0,1" LineBreakMode="WordWrap" HorizontalTextAlignment="End" FontSize="14" Text="ID :" TextColor="Black"> </Label> <Label LineBreakMode="WordWrap" FontSize="14" VerticalOptions="Start" Margin="0,3,0,1" HorizontalTextAlignment="End" Text="No :" TextColor="Black"> </Label> <Label LineBreakMode="WordWrap" FontFamily="Roboto" FontSize="14" VerticalOptions="Start" Margin="0,3,0,1" HorizontalTextAlignment="End" Text="Price :" TextColor="Black"> </Label> </StackLayout> <StackLayout HeightRequest="84" HorizontalOptions="Start" Margin="0,8,0,8" VerticalOptions="Start"> <Label LineBreakMode="WordWrap" Margin="0,3,0,1" Text="{Binding ProductID}" TextColor="Black"> </Label> <Label LineBreakMode="WordWrap" Margin="0,3,0,1" Text="{Binding ProductNo}" TextColor="Black"> </Label> <Label LineBreakMode="WordWrap" Margin="0,3,0,1" Text="{Binding ProductPrice, StringFormat='{0:C}'}" TextColor="Black"> </Label> </StackLayout> </StackLayout> </ContentView> </DataTemplate> </syncfusion:DataGridTemplateColumn.CellTemplate> </syncfusion:DataGridTemplateColumn> 
 </syncfusion:SfDataGrid.Columns></syncfusion:SfDataGrid>

Numeric column

A numeric column displays numeric values in the record cells. To create a numeric column, the property corresponding to the column in the underlying collection must be of type numeric.

Refer to the following code example to display the dealers’ IDs in the DataGrid.

<syncfusion:SfDataGrid x:Name=”dataGrid” ItemsSource=”{Binding DealerInformation}” AutoGenerateColumnsMode=”None”> <syncfusion:SfDataGrid.Columns> <syncfusion:DataGridNumericColumn Format=”D” HeaderText=”ID” MappingName=”ProductID”> </syncfusion:DataGridNumericColumn> </syncfusion:SfDataGrid.Columns></syncfusion:SfDataGrid>

Date column

With this column type, you can display date information as the content in a column. To create a date column, the property corresponding to the column in the underlying collection must be DateTime.

Refer to the following code example to display shipped dates.

<syncfusion:SfDataGrid x:Name="dataGrid" ItemsSource="{Binding DealerInformation}" AutoGenerateColumnsMode="None"> <syncfusion:SfDataGrid.Columns> <syncfusion:DataGridDateColumn HeaderText="Shipped Date" MinimumWidth="{StaticResource minimumWidth}" MappingName="ShippedDate"> 
 </syncfusion:SfDataGrid.Columns></syncfusion:SfDataGrid>

References

For more details, refer to different column types in the .NET MAUI DataGrid GitHub demo and documentation.

Conclusion

Thanks for reading! In this blog, we’ve seen the various column types in the .NET MAUI DataGrid with code examples. You can also enjoy the data binding, sorting, filtering, customization, and other features in the .NET MAUI DataGrid. Try them out and leave your feedback in the comments below!

Customers can download the latest Essential Studio version from the License and Downloads page. If you are not yet a Syncfusion customer, you can always download our free evaluation to examine all our controls.

For questions, you can contact us through our support forums, support portal, or feedback portal. We are delighted to help you!

Related blogs

• Authenticate a .NET MAUI App with Azure AD
• Agenda View in .NET MAUI Scheduler: A Perfect Tool for Modern-Day Office Management
• Achieve Outlook-Like Swiping Using .NET MAUI ListView
• Replicating an Invoice Page UI in .NET MAUI
• How to Draw 2D Graphics in .NET MAUI’s GraphicsView

View Details

As a mobile developer, it is essential to prioritize the creation of a simple and uncluttered user interface that enhances the overall usability of the application. One way to achieve this is by grouping the UI elements based on their purpose and function. A group box view can be helpful in this regard, as they allow developers to group related UI elements with a frame UI.

In this blog, we will explore using group box views on the .NET MAUI platform to organize and simplify the UI of a mobile application. By utilizing group box views, developers can improve the usability and clarity of their applications for users.

What is a .NET MAUI group box view?

A .NET MAUI group box view is a layout element in user interface design. It is a container that contains multiple controls within it. A .NET MAUI group box view aims to group related controls and provide a frame around them with an optional title.

Why a .NET MAUI group box view?

A .NET MAUI group box view organizes and categorizes related controls, making it easier for users to comprehend the controls’ purpose and function. In user interfaces, .NET MAUI group boxes are widely used to group controls that perform similar functions, such as input fields for a form or buttons for controlling a particular component of the program. They can help reduce clutter and improve the overall usability of an interface.

In addition to providing a visual grouping for controls, a .NET MAUI group box view can also be used to enable or disable a group of controls at once, allowing users to easily control the functionality of the controls within the group box. Overall, a group box is a useful tool for organizing and categorizing controls in user interfaces, helping improve the usability and clarity of the interface for users.

Where can I get a .NET MAUI group box view?

You can create a .NET MAUI group box view with the features mentioned by using Syncfusion’s .NET MAUI Text Input Layout.

Creating a .NET MAUI group box view

To create a group box view UI, you must configure the .NET MAUI Text Input Layout (SfTextInputLayout) control with a floating label. Follow these steps:

Steps to Add .NET MAUI Text Input Layout

Step 1: The Syncfusion .NET MAUI controls are available on NuGet.org. To add .NET MAUI Text Input Layout to your project, open the NuGet package manager in Visual Studio, search for Syncfusion.Maui.Core, and then install it.

Step 2: In the MauiProgram.cs file, register the handler for Syncfusion Core.

using Microsoft.Maui;using Microsoft.Maui.Hosting;using Microsoft.Maui.Controls.Compatibility;using Microsoft.Maui.Controls.Hosting;using Microsoft.Maui.Controls.Xaml;using Syncfusion.Maui.Core.Hosting;namespace TextInputLayoutSample{ public static class MauiProgram { public static MauiApp CreateMauiApp() {var builder = MauiApp.CreateBuilder();builder.UseMauiApp<App>().ConfigureSyncfusionCore().ConfigureFonts(fonts =>{ fonts.AddFont("OpenSans-Regular.ttf", "OpenSansRegular");});return builder.Build(); } }}

Step 3: Add the following namespace to add the .NET MAUI Text Input Layout.

xmlns:groupBoxView ="clr-namespace:Syncfusion.Maui.Core;assembly=Syncfusion.Maui.Core"

Step 4: Add the SfTextInputLayout control.

< groupBoxView:SfTextInputLayout/>

Creating a .NET MAUI group box view layout on a page

The code below defines a user interface for an application using the Syncfusion library’s SfTextInputLayout (for the group box view) and SfAvatarView components. The interface includes a SfAvatarView element for displaying a profile picture, a label for displaying a name, a SfTextInputLayout (for the group box view) segment with a text field and label for displaying information about the user, and two SfTextInputLayout elements with HorizontalStackLayout elements and SfAvatarView elements for displaying lists of friends. Some style properties are also applied to various elements, such as corner radius and stroke color.

<ContentPage xmlns="http://schemas.microsoft.com/dotnet/2021/maui" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" xmlns:groupBoxView="clr-namespace:Syncfusion.Maui.Core;assembly=Syncfusion.Maui.Core" x:Class="GroupBoxViewApp.MainPage"> <ScrollView> <VerticalStackLayout WidthRequest="310" Padding="30,0" VerticalOptions="Center"> <groupBoxView:SfAvatarView ContentType="Custom" CornerRadius="75" Stroke="#ce04d1" ImageSource="selvaganapathy.png" WidthRequest="150" HeightRequest="150"/> <Label Text="Selva Ganapathy Kathiresan" Margin="0,10" FontSize="16" FontAttributes="Bold" HorizontalOptions="Center"/> <groupBoxView:SfTextInputLayout Hint="About" Stroke="#ce04d1" ContainerType="Outlined" ContainerBackground="White"> <groupBoxView:SfTextInputLayout.HintLabelStyle> <groupBoxView:LabelStyle TextColor="#d10489"/> </groupBoxView:SfTextInputLayout.HintLabelStyle> <VerticalStackLayout Margin="5"> <Label FontSize="10" Text="Selva Ganapathy Kathiresan is a Senior Product Manager at Syncfusion and a Microsoft MVP (2014), who sees through the development of Layout and Editors."/> <Grid ColumnDefinitions="Auto,*" Margin="0,10,0,0"> <Label Background="Transparent" Text="Follow" TextColor="#d10489" FontSize="12"/> <Label Grid.Column="1" Background="Transparent" HorizontalTextAlignment="End" HorizontalOptions="End" Text="Add Friend" TextColor="#ce04d1" FontSize="12"/> </Grid> </VerticalStackLayout> </groupBoxView:SfTextInputLayout> <groupBoxView:SfTextInputLayout Hint="Friends" Padding="-10,0" Stroke="#ce04d1" ContainerType="Outlined" ContainerBackground="White"> <groupBoxView:SfTextInputLayout.HintLabelStyle> <groupBoxView:LabelStyle TextColor="#d10489"/> </groupBoxView:SfTextInputLayout.HintLabelStyle> <VerticalStackLayout> <HorizontalStackLayout BindableLayout.ItemsSource="{Binding GroupMembers}" > <BindableLayout.ItemTemplate> <DataTemplate> <groupBoxView:SfAvatarView Margin="5,5,0,0" HeightRequest="70" WidthRequest="70" CornerRadius="35" ContentType="Custom" ImageSource="{Binding Picture}"/> </DataTemplate> </BindableLayout.ItemTemplate> </HorizontalStackLayout> <HorizontalStackLayout BindableLayout.ItemsSource="{Binding GroupMembers1}" > <BindableLayout.ItemTemplate> <DataTemplate> <groupBoxView:SfAvatarView Margin="5,5,0,0" HeightRequest="70" WidthRequest="70" CornerRadius="35" ContentType="Custom" ImageSource="{Binding Picture}"/> </DataTemplate> </BindableLayout.ItemTemplate> </HorizontalStackLayout> <HorizontalStackLayout BindableLayout.ItemsSource="{Binding GroupMembers2}" > <BindableLayout.ItemTemplate> <DataTemplate> <groupBoxView:SfAvatarView Margin="5,5,0,0" HeightRequest="70" WidthRequest="70" CornerRadius="35" ContentType="Custom" ImageSource="{Binding Picture}"/> </DataTemplate> </BindableLayout.ItemTemplate> </HorizontalStackLayout> </VerticalStackLayout> </groupBoxView:SfTextInputLayout> </VerticalStackLayout> </ScrollView></ContentPage>

Resources

For more information, refer to the .NET MAUI Group Box View project on GitHub.

Conclusion

Thank you for your time! This article showed how to use the Syncfusion .NET MAUI Text Input Layout control to construct a group box control in a .NET application. This control makes it simple to add a text field and label to your interface and apply other style settings such as stroke color and corner radius. Overall, the Syncfusion.NET MAUI library offers a variety of valuable components for creating user interfaces and is worth checking out.

Are you already a Syncfusion user? You can download the product setup here. If you are not yet a Syncfusion user, you can download a 30-day free trial.

Please contact us via our support forum, support portal, or feedback portal, if you have any queries or issues. We are always happy to assist!

Related blogs

• Introducing the New .NET MAUI Rating Control
• Introducing the Sixth Set of .NET MAUI Controls
• Authenticate the .NET MAUI App with Azure AD
• Agenda View In .NET MAUI Scheduler: A Perfect Tool For Modern-Day Office Management
• Achieve Outlook-Like Swiping Using .NET MAUI ListView

View Details

View Details

Show NotesIn addition to some good natured ribbing - James, Matt & David talk about the latest and greatest in .NET MAUI development.

Latest Releases* .NET MAUI Latest * Visual Studio 17.5 Previews + Markdown + Sticky Scroll + Dev tunnels + Spell checking * .NET MAUI Community Toolkit * .NET Community Toolkit

Latest News* MVVM in WinForms * Updates to the podcast app

Azure News* Azure Developers YouTube * Azure CosmosDB Conf

Azure Service of the Month* Azure OpenAI

Follow Us:

• James: Twitter, Blog, GitHub, Merge Conflict Podcast
• Matt: Twitter, Blog, GitHub
• David: Twitter, Github

View Details

Assume your application needs to display a list of tourist attractions in a city on a vertical list based on the city selected from a horizontal list. Here comes the Syncfusion .NET MAUI ListView to help you easily implement this in your .NET MAUI application.

The Syncfusion .NET MAUI ListView control is a list-like interface that renders a set of data in vertical and horizontal orientation with easy customization.

By customizing the Orientation property of the .NET MAUI ListView, you can easily configure the ListView to be horizontal or vertical.

Let’s get started with the development of this application.

Data population for a vertical and horizontal list

As we know, the .NET MAUI ListView is a data-bound control, and we must create a data model to bind to the ListView.

Creating a data model

Create a model class to hold the data values, such as the place’s name, image, and collection, which holds data for the vertical list.

Refer to the following code example.

public class PlaceInfo : INotifyPropertyChanged{ #region Fields private string? name; private string? description; private ImageSource? image; private ObservableCollection<PlaceInfo> touristPlaces; #endregion #region Constructor public PlaceInfo() { } #endregion #region Properties public string? Name { get { return name; } set { name = value; OnPropertyChanged("Name"); } } public string? Description { get { return description; } set { description = value; OnPropertyChanged("Description"); } } public ImageSource? Image { get { return image; } set { image = value; OnPropertyChanged("Image"); } } public ObservableCollection<PlaceInfo> TouristPlaces { get { return touristPlaces; } set { touristPlaces = value; OnPropertyChanged("TouristPlaces"); } } #endregion #region Interface Member public event PropertyChangedEventHandler? PropertyChanged; public void OnPropertyChanged(string name) { if (this.PropertyChanged != null) this.PropertyChanged(this, new PropertyChangedEventArgs(name)); } #endregion}

Populate model collection in ViewModel

Create an ObservableCollection of PlaceInfo named Places to hold the data for the horizontal ListView. Each PlaceInfo will have a collection of PlaceInfo named TouristPlaces, which holds data for the vertical list to show the travel places.

Refer to the following code.

public class ListViewOrientationViewModel : INotifyPropertyChanged{ #region Fields private ObservableCollection<PlaceInfo>? places; private PlaceInfo selectedItem; #endregion #region Constructor public ListViewOrientationViewModel() { var placesRepository = new PlaceInfoRepository(); Places = placesRepository.GeneratePlaces(); SelectedItem = Places[0]; } #endregion #region Properties public PlaceInfo SelectedItem { get { return selectedItem; } set { selectedItem = value; OnPropertyChanged("SelectedItem"); } } public ObservableCollection<PlaceInfo>? Places { get { return places; } set { this.places = value; OnPropertyChanged("Places"); } } #endregion #region INotifyPropertyChanged public event PropertyChangedEventHandler? PropertyChanged; private void OnPropertyChanged(string name) { if (PropertyChanged != null) PropertyChanged(this, new PropertyChangedEventArgs(name)); } #endregion}

Now, bind the ViewModel’s Places collection to the horizontal ListView control on the XAML page.

<ContentPage x:Class="ListViewMaui.HorizontalOrientation" xmlns="http://schemas.microsoft.com/dotnet/2021/maui" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" xmlns:local="clr-namespace:ListViewMaui" xmlns:ListView="clr-namespace:Syncfusion.Maui.ListView;assembly=Syncfusion.Maui.ListView" BackgroundColor="White"> <ContentPage.BindingContext> <local:ListViewOrientationViewModel x:Name="viewModel"/> </ContentPage.BindingContext> <ListView:SfListView x:Name="listView" Grid.Row="1" ItemsSource="{Binding Places}" Orientation="Horizontal"> </ListView:SfListView> </ContentPage.Content></ContentPage>

Defining horizontal ListView’s ItemTemplate

Once the ItemsSource is bound, the ListView control will display only the business objects (like PlaceInfo) as the content of the ListView items. We must update them by defining the ItemTemplate.

By defining the ItemTemplate, you can easily set custom views to display the data items.

Refer to the following code.

<ListView:SfListView x:Name="listView" Grid.Row="1" ItemsSource="{Binding Places}" ScrollBarVisibility="Never" SelectionMode="Single" Orientation="Horizontal" SelectionBackground="Transparent" ItemSize="{OnPlatform Android=120,Default=130}" Margin="8,0,0,0" HeightRequest="180" SelectedItem="{Binding SelectedItem}"> <ListView:SfListView.ItemTemplate> <DataTemplate> <Grid Margin="8,0,8,0"> <Grid.RowDefinitions> <RowDefinition Height="130"/> <RowDefinition Height="Auto"/> </Grid.RowDefinitions> <Border Padding='{OnPlatform UWP="-5,-5,5,5"}' Stroke="#FFFDFD" StrokeThickness="6" HorizontalOptions="Center"> <Border.StrokeShape> <RoundRectangle CornerRadius="6"/> </Border.StrokeShape> <Image Grid.Row="0" Source="{Binding Image}" HeightRequest="130" WidthRequest="110" Aspect="Fill" Margin='{OnPlatform MacCatalyst=-3,iOS=-3}'/> </Border> <Label Grid.Row="1" Text="{Binding Name}" LineBreakMode="WordWrap" HorizontalTextAlignment="Center" HorizontalOptions="Center" VerticalTextAlignment="Center" FontFamily="Roboto-Regular" VerticalOptions="Center" HeightRequest="40" WidthRequest="110" TextColor="#99000000" FontSize="14"> </Label> </Grid> </DataTemplate> </ListView:SfListView.ItemTemplate> <ListView:SfListView.SelectedItemTemplate> <DataTemplate> <Grid Margin="8,0,8,0"> <Grid.RowDefinitions> <RowDefinition Height="130"/> <RowDefinition Height="Auto"/> </Grid.RowDefinitions> <Border Padding='{OnPlatform UWP="-5,-5,5,5"}' Stroke="#1899EF" StrokeThickness="6" HorizontalOptions="Center"> <Border.StrokeShape> <RoundRectangle CornerRadius="6"/> </Border.StrokeShape> <Image Grid.Row="0" Source="{Binding Image}" HeightRequest="130" WidthRequest="110" Aspect="Fill" Margin='{OnPlatform MacCatalyst=-3,iOS=-3}'/> </Border> <Label Grid.Row="1" Text="{Binding Name}" LineBreakMode="WordWrap" HorizontalTextAlignment="Center" HorizontalOptions="Center" VerticalTextAlignment="Center" FontFamily="Roboto-Regular" VerticalOptions="Center" HeightRequest="40" WidthRequest="110" TextColor="#99000000" FontSize="14"> </Label> </Grid> </DataTemplate> </ListView:SfListView.SelectedItemTemplate></ListView:SfListView>

Now the application will look like the following screenshot.

Data binding for vertical ListView

Now, selecting a city from the horizontal list will display the list of travel destinations by changing the ViewModel’s SelectedItem, which is bound to the horizontal ListView’s SelectedItem by using the bound property ItemsSource in the vertical ListView.

<ListView:SfListView x:Name="verticalListView" Grid.Row="3" ItemsSource="{Binding Path=SelectedItem.TouristPlaces, Source={x:Reference listView}}" ItemSize="60" ItemSpacing="16,8,16,8" SelectionMode="None"/>

Defining vertical ListView’s ItemTemplate

Here, we are showing the details of travel places by using their name, description, and image in custom views defined within the ItemTemplate property.

<ListView:SfListView x:Name="verticalListView" Grid.Row="3" ItemsSource="{Binding Path=SelectedItem.TouristPlaces, Source={x:Reference listView}}" ItemSize="60" ItemSpacing="16,8,16,8" SelectionMode="None"> <ListView:SfListView.ItemTemplate> <DataTemplate> <Grid> <Grid.ColumnDefinitions> <ColumnDefinition Width="76"/> <ColumnDefinition Width="*"/> </Grid.ColumnDefinitions> <Frame HorizontalOptions="Start" CornerRadius="3" IsClippedToBounds="True" Padding="0" Margin="0" HasShadow="False" HeightRequest="60" WidthRequest="60"> <Image Grid.Column="0" HorizontalOptions="Start" Source="{Binding Image}" Aspect="Fill" HeightRequest="60" WidthRequest="60"/> </Frame> <Grid Grid.Column="1" VerticalOptions="Center"> <Grid.RowDefinitions> <RowDefinition Height="Auto"/> <RowDefinition Height="*"/> </Grid.RowDefinitions> <Label Grid.Row="0" Text="{Binding Name}" FontSize="14" TextColor="#666666" FontFamily="Roboto-Regular" CharacterSpacing="0.25"/> <Label Grid.Row="1" Text="{Binding Description}" FontSize="14" FontFamily="Roboto-Regular" TextColor="#DE000000" LineBreakMode="WordWrap" CharacterSpacing="0.15" Margin="0,5,0,0"/> </Grid> </Grid> </DataTemplate> </ListView:SfListView.ItemTemplate></ListView:SfListView>

After executing this code example, we will get output like in the following GIF image. Tapping on the items in the horizontal ListView dynamically updates the content of the vertical ListView.

Resources

For more details, refer to the complete sample of Travel Place Listing UI in .NET MAUI in the GitHub repository.

Conclusion

Thanks for reading! I hope you now have a good idea of how to use the .NET MAUI ListView to display tourist places in a vertical list based on the city selected from a horizontal list. Try creating this sample project and share your feedback in the comment section below.

For questions, contact us through our support forum, support portal, or feedback portal. We are always happy to assist you!

Related blogs

• Create Group Chat Profile View in .NET MAUI App
• Replicating an Immersive UI in .NET MAUI
• Learn Performing Animation in .NET MAUI: Part 1
• Add Busy Notifications to Your .NET MAUI Application

View Details

Welcome to the second part of our blog on animation in .NET MAUI! In Part 1, we covered the basics of animation and how to add simple animations to your .NET MAUI application. Now, it’s time to take it to the next level and explore custom animation in .NET MAUI.

Custom animation allows you to create more complex and tailored animations. This blog will teach you how to create custom animations in your .NET MAUI apps.

Custom animation in .NET MAUI

The .NET Multi-Platform App UI, or .NET MAUI, is a framework for building cross-platform applications using the .NET ecosystem. One of the powerful features of .NET MAUI is the ability to add animations to your app to enhance the user experience and make it more visually appealing.

The Animation class is the foundation for all .NET MAUI animations. The ViewExtensions class provides the extension methods for creating one or more animation objects. When creating an animation object, we should specify the number of parameters, including the beginning and end values for the animated property and a callback function to update the property’s value as the animation progresses.

In addition to animating a single property, the Animation class allows you to create and synchronize child animations. This will enable you to create more complex animations that involve multiple properties and elements within your app.

To run an animation created with the Animation class, we need to call the Commit method and specify the duration of the animation. You can also specify a callback function to control whether the animation should repeat, as well as other parameters, such as easing functions, to control the speed and smoothness of the animation.

Easily build cross-platform mobile and desktop apps with the flexible and feature-rich controls of the Syncfusion .NET MAUI platform.

Explore Now

Create a custom animation

We will create an animation for a Cody image that appears to be moving and blocked by a brick wall. Cody then thinks and jumps over the wall with a flip. After successfully flipping over the wall, Cody will celebrate a jump before moving away.

We can achieve this animation with several different animation objects. Each one is responsible for animating a specific aspect of the Cody image.

For example, the movingLeftAnimation object is responsible for animating Cody’s movement from left to right, while the rotateJumpAnimation object is responsible for animating Cody’s rotation as it jumps over the wall.

Then, we need to add the animation objects to a parentAnimation object, which controls the overall flow of the animation. The parentAnimation object specifies the start and end times for each animation object, allowing them to be sequenced together to create the desired animation.

Finally, the parentAnimation object is committed to the screen using the Commit method. This method specifies the length of the animation (in our case, it is 10,000 milliseconds) and a flag to indicate that the animation should repeat indefinitely.

Refer to the following code example to initialize the UI.

<ContentPage xmlns="http://schemas.microsoft.com/dotnet/2021/maui" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" x:Class="CustomAnimation.MainPage"> <Grid WidthRequest="700" Margin="10"> <Image x:Name="imageView" Source="cody.png" HeightRequest="100" HorizontalOptions="Start" VerticalOptions="End"/> <Image WidthRequest="50" Margin="125,0,0,0" Source="bricks.png" VerticalOptions="End" HeightRequest="100"/> </Grid> </ContentPage>

Refer to the following code to create a visually appealing animation of the Cody image that moves and jumps over a brick wall.

var parentAnimation = new Animation();var movingLeftAnimation = new Animation(v => imageView.TranslationX = v, 0, 250);var movingLeftBackAnimation = new Animation(v => imageView.TranslationX = v, 250, 200);var movingRightAnimation = new Animation(v => imageView.TranslationX = v, 500, 700); var rotateJumpAnimation = new Animation(v => imageView.Rotation = v, 0, 360);var movingJumpAnimation = new Animation(v => imageView.TranslationX = v, 200, 500);var movingJumpUpAnimation = new Animation(v => imageView.TranslationY = v, 0, -200);var movingJumpDownAnimation = new Animation(v => imageView.TranslationY = v, -200, 0); var jumpUpAnimation = new Animation(v => imageView.TranslationY = v, 0, -30);var jumpDownAnimation = new Animation(v => imageView.TranslationY = v, -30, 0);var jumpUpAnimation2 = new Animation(v => imageView.TranslationY = v, 0, -30);var jumpDownAnimation2 = new Animation(v => imageView.TranslationY = v, -30, 0); parentAnimation.Add(0, 0.15, movingLeftAnimation);parentAnimation.Add(0.25, 0.35, movingLeftBackAnimation); parentAnimation.Add(0.35, 0.65, rotateJumpAnimation);parentAnimation.Add(0.35, 0.65, movingJumpAnimation);parentAnimation.Add(0.35, 0.5, movingJumpUpAnimation);parentAnimation.Add(0.5, 0.65, movingJumpDownAnimation); parentAnimation.Add(0.7, 0.75, jumpUpAnimation);parentAnimation.Add(0.75, 0.8, jumpDownAnimation);parentAnimation.Add(0.8, 0.85, jumpUpAnimation2);parentAnimation.Add(0.85, 0.9, jumpDownAnimation2); parentAnimation.Add(0.9, 1, movingRightAnimation); parentAnimation.Commit(this, "ChildAnimations", 16, 10000, null, null,repeat:()=>true);

Syncfusion .NET MAUI controls are well-documented, which helps to quickly get started and migrate your Xamarin apps.

Read Now

Custom animation with ViewExtensions class

The ViewExtensions class in .NET MAUI allows us to animate a property from its current value to the specified value. However, this will be difficult when creating a color-changing animation method that animates a color property from one value to another, as different controls have different color properties.

To solve this problem, the PaintTo method can be written with a callback method that passes the interpolated color value back to the caller and takes the start and end color arguments.

Refer to the following code example.

public static class ViewExtensions{ public static Task<bool> PaintTo(this VisualElement element, Color startColor, Color endColor, Action<Color> callback, uint length = 250, Easing easing = null) { Func<double, Color> transform = (t) => Color.FromRgba(startColor.Red + t * (endColor.Red - startColor.Red), startColor.Green + t * (endColor.Green - startColor.Green), startColor.Blue + t * (endColor.Blue - startColor.Blue), startColor.Alpha + t * (endColor.Alpha - startColor.Alpha)); return ChangePaint(element, "ChangePaint", transform, callback, length, easing); } public static void Cancel(this VisualElement self) { self.AbortAnimation("ColorTo"); } static Task<bool> ChangePaint(VisualElement element, string animation, Func<double, Color> transform, Action<Color> callback, uint length, Easing effect) { effect = effect ?? Easing.Linear; var source = new TaskCompletionSource<bool>(); element.Animate<Color>(animation, transform, callback, 16, length, effect, (v, c) => source.SetResult(c)); return source.Task; }}

Reference

For more details, refer to the custom animation in the .NET MAUI documentation.

To make it easy for developers to include Syncfusion .NET MAUI controls in their projects, we have shared some working ones.

Explore Now

Conclusion

Thanks for reading! In this blog, we have seen how to create custom animations in your .NET MAUI applications. With these animations, you can provide a wonderful user experience in your apps!

Syncfusion .NET MAUI controls were built from scratch using .NET MAUI, so they feel like framework controls. They are fine-tuned to work with a vast volume of data. Use them to build your cross-platform mobile and desktop apps!

The Essential Studio for .NET MAUI suite is available from the License and Downloads page. If you are not a Syncfusion customer, you can always download our free evaluation to see all our controls.

For questions, you can contact us through our support forum, support portal, or feedback portal. We are always happy to assist you!

Related blogs

• Introducing the New .NET MAUI Text Input Layout
• Create Project Planning and Resource Management Calendar in .NET MAUI
• Introducing the New .NET MAUI Funnel Charts
• Syncfusion .NET MAUI 2023 Roadmap

View Details

I finally ported sharpnado's xamarin.forms collection view to dotnet MAUI \o/

	Sharpnado's MAUI CollectionView on Github

• Performance oriented
• Horizontal, Grid, Carousel or Vertical layout
• Header, Footer and GroupHeader
• Reveal custom animations
• Drag and Drop
• Column count
• Infinite loading with Paginator component
• Snapping on first or middle element
• Padding and item spacing
• Handles NotifyCollectionChangedAction Add, Remove and Reset actions
• View and data template recycling
• RecyclerView on Android
• UICollectionView on iOS

Installation

• In Core project, in MauiProgram.cs:

public static MauiApp CreateMauiApp(){ var builder = MauiApp.CreateBuilder(); builder .UseMauiApp() .UseSharpnadoCollectionView(loggerEnabled: false);}

Usage

<!-- As a Grid --><sho:GridView x:Name="HorizontalListView" CollectionPadding="30" ColumnCount="3" EnableDragAndDrop="True" HeightRequest="390" HorizontalOptions="Fill" ItemHeight="110" ItemsSource="{Binding Logo, Mode=OneTime}" /><!-- As a List with groups --><sho:CollectionView CollectionLayout="Vertical" CollectionPadding="0,30,0,30" CurrentIndex="{Binding CurrentIndex}" ItemHeight="120" ItemTemplate="{StaticResource HeaderFooterGroupingTemplateSelector}" ItemsSource="{Binding SillyPeople}" ScrollBeganCommand="{Binding OnScrollBeginCommand}" ScrollEndedCommand="{Binding OnScrollEndCommand}" TapCommand="{Binding TapCommand}" /><!-- As a carousel --><sho:CarouselView /><!-- As a HorizontalListView --><sho:HorizontalListView />

Docs

Please find all the available documentation and a full maui app sample here:

GitHub - roubachof/Sharpnado.CollectionView: A performant list view supporting: grid, horizontal and vertical layout, drag and drop, and reveal animations.

A performant list view supporting: grid, horizontal and vertical layout, drag and drop, and reveal animations. - GitHub - roubachof/Sharpnado.CollectionView: A performant list view supporting: grid...

GitHubroubachof

View Details

View Details

I’m speaking about .NET MAUI in Prague on March 23 and 24. If you’re in the neighborhood…

https://maui.updatedays.cz/speakers/en?langChange=en

https://maui.updatedays.cz/#about/en

View Details

I’ve been eager to rewrite some of my personal apps from Xamarin.Forms to .NET MAUI, but since all of them are dependant on map functionality, I had to wait until the arrival of .NET 7, since the .NET 6 release of MAUI didn’t ship with map support. Since .NET 7 shipped in November 2022, I was able to start rewriting my apps. I started with the most simple one, which is a single-page application (not that kind) that shows the different parking zones in my local municipality. The parking zones are drawn on a map as polygons. When you click on a zone, it gets highlighted and some info about the zone is shown in an info overlay. I posted on Twitter about my progress, but I wanted to do a full post about my experience with trying to migrate to .NET MAUI.

NOTE: Your milage may vary – my experience with the migration may differ greatly from yours. This is just to highlight the pain points that I had during my attempt. Having a machine with preview releases probably did not help me here.

The TL;DR:

Positives:

• Easy to copy over pages and convert namespaces
• Eliminated the need for a couple of plugins

Negatives:

• Workloads are a hassle
• Trying to migrate while .NET 7 was in preview was a mistake
• Lots of “smoke and mirrors”/yak-shaving
• Project file would randomly break
• App would crash in Release mode on iOS without reporting error to App Center

I’ll go into more detail on the different points as I go through my process.

Initial migration

My initial attempt was to have a go at migrating while .NET MAUI was still on .NET 6, so even though maps weren’t ready yet, I could still migrate the “outlining” project and just comment out the code that didn’t work. I converted the XAML namespaces, the using statements and the packages that were either redundant or had an update for them. Turns out a lot of it didn’t work since I didn’t have a working map (shocker), so the project laid dorment for a while.

.NET 7

When .NET 7 hit preview, I updated Visual Studio 2022 Preview and tried to upgrade the project. I cleaned the bin/obj folder, but I got some random build errors for Android. After restarting VS, they were gone for a while, but after doing some changes and building a couple of times they would come back so restarts of VS were frequent.

After this, I pulled in the NuGet package for MAUI maps and was able to comment back my code. After some code changes, the polygons were properly drawn on the map, at least for Android (as shown in the previous Twitter link). I hadn’t looked at when you click on the zones yet, as I had issue on iOS when drawing the polygons.

Polygons + iOS =

In the app, I set the fill color of the different parking zones to be transparent, so that you can actually see the different street names. On iOS, the transparency only seemed to take effect on one of the several drawn polygons. I tried isolating what might be the error here, but it was so time consuming that I ended up leaving the project for a while and betting on that it would get fixed in a patch release of the MAUI maps package.

Oops, my project broke

After not having done much work on the project for a while, I picked it back up to see if I could isolate the problem with iOS further. But this time my project wouldn’t build. I tried clean/rebuild, delete bin/obj, restart VS, restart VS again. Nothing. I also tried updating my maui workloads via the CLI. For a while here, I was only able to build clean .NET 7 MAUI projects and not .NET 6 MAUI projects. After having given up completely, I created a clean new .NET 7 MAUI project and copied everything over to it and was able to build. But, I was still stuck with the polygon iOS problem. Sigh.

Smoke and mirrors

I was also thrown for a loop a couple of times during my process, which wasn’t related to MAUI at all. The API I used to fetch data about the different parking zones for altered the structure of the data without notice. I spent more time than I want to admit figuring this one out. Like I said, I was testing this out while the .NET 7 version of MAUI was in preview so a lot of stuff would randomly work or not work. Another one was a setting I applied to Visual Studio, which led to some hours of yak-shaving. At this point, I was pretty fed up with this whole process.

Update ALL the packages

After having put down the migration for a second time, I picked it up again later to see if my issue was magically resolved. After updating the MAUI maps NuGet package, it was working on iOS! After double checking that it was working on both platforms, I was ready to start publishing.

As I usually do, I start publishing on Android because I know this process is way faster and less error-prone than what it is for iOS. If I have an app that needs to be rolled out on both platforms simultaneously, I might start with iOS to make sure everything works. This time I wanted to save the “best” for last.

Certificates… Why’d it have to be certificates?

Anyone who’s worked with publishing apps for iOS has had to deal with the nightmare process that is certificates and provisioning profiles. Even after having worked with this process for eight years, I still never get it right on the first try. This time was no different. When trying to build the app for iOS in release, I got an error along the lines of that the self-signed certificate was not trusted. Turns out that XCode doesn’t ship with the latest intermediate signing certificate that you need, so you have to download that from the Apple Developer site. Also, there are three different types of them with varying expiration date, just to make you wonder which is the correct one you should choose. Delightful.

After spending an evening fixing this issue, I was finally able to create an ipa file I could upload to App Store Connect.

Submit for review

After submitting my update for review in App Store Connect, I got it back with them claiming the app crashed instantly on startup. Weird, since I remember testing the app on a physical device. I checked App Center and there was one crash report along the lines of: Attempting to JIT compile method […] while running in aot-only mode. Googling the error gave me some indication that this could happen when running a MAUI iOS app in Release mode.

I tried to distribute the app through App Center so that I would be able to reproduce the bug, but when trying to start the app on my iPad, I got the error that the app’s integrity could not be verified. Great. This usually indicates that something is wrong with the certificate and/or the provisioning profile, and I thought I had just gotten it right. After a lot of back and forth, it looks like I had to use an Ad-Hoc provisioning profile to sign the app to explicitly include my iPad for testing. More time spent.

After finally getting the app to work on my iPad, I reproduced the bug and the app instantly crashed on start. Never been so glad to see my app crash. I went to App Center in hopes of seeing my recent crash being reported, but nothing. I went to Twitter to ask for help on how to move along here, but honestly, I am so tired of trying to get this to work that I might put this whole thing on pause again.

Conclusion

I’m happy that I am just trying to do this with one of my personal apps and not for a client project. I will say, most of the time spent here has been caused by smoke and mirrors plus Apple’s provisioning nightmare, but a lot of time has been spent on tooling as well. I thought about rewriting another app I have that is a bit more complex, but I’m glad I waited off on it. I might give it a shot now, but this experience did leave a bad taste in my mouth when I had so much trouble with such a simple app. I hope you have a far better experience than I did, but I just wanted to share how my journey was.

The post My experience with migrating my app from Xamarin.Forms to .NET MAUI appeared first on Andreas Nesheim.

View Details

Welcome to the complete guide to distribution certificates, .p12 files, and provisioning profiles on iOS! Publishing and distributing apps on the Apple App Store requires a number of steps and technical requirements. These include creating a distribution certificate, a .p12 file, and a valid provisioning profile.

If you’re an iOS developer or trying to publish and distribute your first app on the App Store, this guide is for you. We’ll explain how to create and use each of these essentials in a detailed, easy-to-follow way.

Let’s start!

What you need to know

The steps below will guide you through the process of creating an iOS distribution certificate and .p12 file.

• A distribution certificate identifies your team/organization within a distribution provisioning profile and allows you to submit your app to the Apple App Store.
• A .p12 file contains the certificates that Apple needs to create and publish apps.
• A provisioning profile is a collection of information that links an application ID to signing certificates and authorized devices. It is used to control and authorize the devices on which the application can run and the Apple services that it can access (such as iCloud or In-App Payment).

We will also be using

• A CertificateSigningRequest (CSR) is a file that contains a public/private key pair.

NOTE:
These certificates are also useful for automating application distribution processes regardless of the framework you use. For example, these certificates are used in App Center and you can use fremework such as Xamarin, .NET MAUI, React Native, among others.

To learn more about certificates and how they work in the Apple App Store, visit the iOS Dev Center and see Apple’s official documentation.

Before you start

• You need a Mac to generate the certificates.
• Make sure you sign up for an iOS developer account.
• Make sure you’ve created an app ID in the iOS developer portal.

How to create a Distribution Certificate

Creating the Signing Certificate Request

• On your Mac, go to the Applications > Utilities folder and open Keychain Access. You can also use the search engine and directly type “Keychain Access”.

• Go to Keychain Access > Certificate Wizard > Request a certificate from a certificate authority.

• Fill in the information window Certificate Information as specified below and click “Continue”.
  • In the User email address field, enter the email address that you want to identify with this certificate.
  • In the Common Name field, type your name.
  • In the Request group, click on the “Save to disk” option

• Save the file to your hard drive.

The wizard creates a certificate signing request (CSR) file that contains a public/private key pair.

Creating the Distribution Certificate

• Sign in to your iOS Developer Console https://developer.apple.com
• Click on “Certificates, identifiers and profiles”.

• Go to Certificates and click the “+” button to add a new certificate.

•  Select “App Store and Ad Hoc” from the production options and click “Continue”.

NOTE:
To use your certificates, you must have the intermediate signing certificate in your OS X system keychain. Xcode installs it automatically. However, if you need to reinstall the intermediate signing certificate, click the link at the bottom of the page.

• Click “Continue” again.
  • Since you already created your CSR file in the previous steps, you don’t need to create another one.
• Click “Choose File” and select the CSR file you created earlier and then click “Continue”.

• Click the “Download” button to download a .cer file to your machine and then click “Done”.

• Double-click the .cer file to install it under Keychain Access.

It will have the name “iPhone Distribution <first name> <last name>” and will expire one year from the date of creation.

Exporting a distribution certificate as a .p12 file

A .p12 file is a special-formatted, encrypted file that contains the distribution certificate. It’s embedded in your app when you build it. iTunes Connect checks this file when you submit an app and will only accept the app if it contains a .p12 file that matches what you’ve set up in your iTunes Connect account.

• On your Mac, launch Keychain Access, select the certificate entry, and right-click on it to select “Export”.

All the certificates you have installed will be in the “login” keychain (Label 1) in the “My certificates” category (Label 2).

• In the window that appears, make sure the file format is set to “Personal Information Exchange (.p12)” and click “Save” to save it to your machine.

• When prompted for a password, you can leave it blank or assign one, then click “OK”.

• When prompted for the computer password, enter it and click “Allow”.

• Your .p12 file will be saved to the specified location.

Provisioning profiles (.mobileprovision)

Uploading an app to App Store Connect requires an app registration registered with an explicit app ID. You can create your own App Store provisioning profile with an explicit app ID to use when you upload your app to App Store Connect.

Creating a provisioning profile

• Under Certificates, IDs, and Profiles, click Profiles in the sidebar, then click the Add (+) button in the top left.

• Under Distribution, select an App Store distribution profile for your platform, then click Continue.
  • App Store: For iOS and watchOS apps and App Clips.
  • tvOS App Store: For tvOS apps.
  • Mac App Store: For macOS apps, including those configured with Mac Catalyst.

• Choose the app ID you used for development (the app ID that matches your package ID) from the App ID pop-up menu, then click Continue.
  
  If you use autosignature during development, choose one of the following:
  • XC Wildcard if it is the only option.
  • The explicit application ID managed by Xcode that starts with XC and contains its package ID.
  • The ID of the app you registered and matches your package ID.

• Select your distribution certificate, then click Continue.
  
  An App Store provisioning profile contains a single distribution certificate.
  

• Enter a profile name, then click Generate.

• Click Download.

Conclusion

Creating and using distribution certificates, .p12 files, and provisioning profiles are essential elements for publishing and distributing apps to the Apple App Store. This article gives you a detailed and easy-to-follow guide to creating and using these elements effectively. Now, you’re ready to publish and distribute your iOS apps with confidence and success.

Good luck in your app development!

The post Distribution certificates, .p12 files, and provisioning profiles with iOS appeared first on Luis Matos.

View Details

¡Bienvenidos a la guía completa sobre certificados de distribución, archivos .p12 y perfiles de aprovisionamiento en iOS! La publicación y distribución de aplicaciones en la App Store de Apple requiere de una serie de pasos y requisitos técnicos. Entre ellos, la creación de un certificado de distribución, un archivo .p12 y un perfil de aprovisionamiento válido.

Si eres un desarrollador de iOS o estás tratando de publicar y distribuir tu primera aplicación en la App Store, esta guía es para ti. Te explicaremos cómo crear y usar cada uno de estos elementos esenciales de manera detallada y fácil de seguir.

¡Empecemos!

Lo que necesitas saber

Los pasos a continuación lo guiarán a través del proceso de creación de un certificado de distribución de iOS y un archivo .p12.

• Un certificado de distribución identifica a su equipo/organización dentro de un perfil de aprovisionamiento de distribución y le permite enviar su aplicación a Apple App Store.
• Un archivo .p12 contiene los certificados que Apple necesita para crear y publicar aplicaciones.
• Un perfil de aprovisionamiento es una recopilación de información que vincula un ID de aplicación con certificados de firma y dispositivos autorizados. Se utiliza para controlar y autorizar los dispositivos en los que se puede ejecutar la aplicación y los servicios de Apple a los que puede acceder (como iCloud o In-App Payment).

También estaremos utilizando

• Un CertificateSigningRequest (Solicitud de Firma de Certificado) (CSR) es un archivo que contiene un par de claves pública/privada.

NOTA:

Estos certificados son útiles también para automatizar los procesos de distribución de aplicativo sin importar el framework que uses. Por ejemplo, en App Center se utilizan estos certificados y puedes usar fremework como Xamarin, .NET MAUI, React Native, entre otros.

Para obtener más información sobre los certificados y cómo funcionan en la App Store de Apple, visite el Centro de desarrollo de iOS y consulte la documentación oficial de Apple.

Antes de iniciar

• Necesitas un Mac para generar los certificados.
• Asegúrese de registrarse para obtener una cuenta de desarrollador de iOS.
• Asegúrese de haber creado un ID de aplicación en el portal para desarrolladores de iOS.

Como crear un Certificado de Distribución

Creando la Solicitud de Certificado de Firma

• En su Mac, vaya a la carpeta Aplicaciones > Utilidades y abra Acceso a Llaveros (Keychain Access). También puedes utilizar el buscador y escribir directamente «Keychain Access».

• Vaya a Acceso a Llaveros > Asistente de certificados > Solicitar un certificado de una autoridad de certificación.

• Complete la información en la ventana Información del certificado como se especifica a continuación y haga clic en «Continuar».
  • En el campo Dirección de correo electrónico del usuario, introduzca la dirección de correo electrónico que desea identificar con este certificado.
  • En el campo Nombre común, escriba su nombre.
  • En el grupo Solicitud, haga clic en la opción «Guardado en disco»

• Guarde el archivo en su disco duro.

El asistente crea un archivo de solicitud de firma de certificado (CSR) que contiene un par de claves pública/privada.

Creando el Certificado de Distribución

• Inicia sesión en tu iOS Developer Console https://developer.apple.com
• Haga clic en «Certificados, identificadores y perfiles».

• Ve a Certificados y haga clic en el botón «+» para agregar un nuevo certificado.

•  Seleccione «App Store y Ad Hoc» de las opciones de producción y haga clic en «Continuar».

NOTA:
Para usar sus certificados, debe tener el certificado de firma intermedio en su llavero del sistema OS X. Xcode lo instala automáticamente. Sin embargo, si necesita reinstalar el certificado de firma intermedio, haga clic en el enlace en la parte inferior de la página.

• Haga clic en «Continuar» nuevamente.
  • Como ya creaste tu archivo CSR en los pasos anteriores, no necesitas crear otro.
• Haga clic en «Elegir archivo» y seleccione el archivo CSR que creó anteriormente y luego haga clic en «Continuar».

• Haga clic en el botón «Descargar» para descargar un archivo .cer a su máquina y luego haga clic en «Listo».

• 12. Haga doble clic en el archivo .cer para instalarlo en Acceso a Llaveros.

Tendrá el nombre «iPhone Distribution <nombre> <apellido>» y caducará un año a partir de la fecha de creación.

Exportando un certificado de distribución como un archivo .p12

Un archivo .p12 es un archivo con formato especial y cifrado que contiene el certificado de distribución. Está incrustado en tu aplicación al compilarla. iTunes Connect comprueba este archivo cuando envías una app y solo aceptará la app si contiene un archivo .p12 que coincida con lo que has configurado en tu cuenta de iTunes Connect.

• En su Mac, inicie Acceso a Llaveros, seleccione la entrada del certificado y haga clic derecho sobre ella para seleccionar «Exportar».

Todos los certificados que haya instalado estarán en el llavero «login» (Etiqueta 1) en la categoría «Mis certificados» (Etiqueta 2).

• En la ventana que aparece, asegúrese de que el formato de archivo esté configurado en «Intercambio de información personal (.p12)» y haga clic en «Guardar» para guardarlo en su máquina.

• Cuando se le solicite una contraseña, puedes dejarla en blanco o asignar una, luego haga clic en «Aceptar».

• Cuando se le solicite la contraseña de la computadora, ingrésela y haga clic en «Permitir».

• 5. Su archivo .p12 se guardará en la ubicación especificada.

Perfiles de aprovisionamiento (.mobileprovision)

Cargar una aplicación en App Store Connect requiere un registro de aplicación registrado con un ID de aplicación explícita. Puede crear su propio perfil de aprovisionamiento de App Store con un ID de aplicación explícita para usar cuando cargue su aplicación en App Store Connect.

Creando un perfil de aprovisionamiento

• En Certificados, identificadores y perfiles, haga clic en Perfiles en la barra lateral, luego haga clic en el botón Agregar (+) en la parte superior izquierda.
  

• En Distribución, seleccione un perfil de distribución de App Store para su plataforma, luego haga clic en Continuar.
  • App Store: para aplicaciones iOS y watchOS y App Clips.
  • Tienda de aplicaciones tvOS: para aplicaciones tvOS.
  • Mac App Store: para aplicaciones macOS, incluidas las configuradas con Mac Catalyst.

• Elija el ID de la aplicación que usó para el desarrollo (el ID de la aplicación que coincide con su ID de paquete) en el menú emergente ID de la aplicación, luego haga clic en Continuar.
  
  Si utiliza la firma automática durante el desarrollo, elija uno de los siguientes:
  • XC Wildcard si es la única opción.
  • El ID de aplicación explícito administrado por Xcode que comienza con XC y contiene su ID de paquete.
  • El ID de la aplicación que registró y coincide con su ID de paquete.

• Seleccione su certificado de distribución, luego haga clic en Continuar.
  
  Un perfil de aprovisionamiento de App Store contiene un solo certificado de distribución.
  

• Ingrese un nombre de perfil, luego haga clic en Generar.

• Haz clic en Descargar.

Conclusión

La creación y uso de certificados de distribución, archivos .p12 y perfiles de aprovisionamiento son elementos esenciales para la publicación y distribución de aplicaciones en la App Store de Apple. Este artículo te brinda una guía detallada y fácil de seguir para crear y usar estos elementos de manera efectiva. Ahora, estás listo para publicar y distribuir tus aplicaciones de iOS con confianza y éxito.

¡Buena suerte en el desarrollo de aplicaciones!

The post Certificados de distribución, archivos .p12 y perfiles de aprovisionamiento con iOS appeared first on Luis Matos.

View Details

Most sought after feature of CommunityToolkit now available to play Audio/Video in a .NET MAUI app.

View Details

View Details

The Syncfusion .NET MAUI DataForm (SfDataForm) is used to gather, edit, and display data in a user-friendly interface. It supports built-in and custom data editors to create data entry forms such as contact, employee, sign-in, and sign-up forms. This control is available with the 2022 Volume 4 release.

This blog will explain how to create a contact form using the .NET MAUI DataForm control and its basic features in mobile and desktop applications from a single shared codebase.

Note: Refer to the .NET MAUI DataForm documentation before getting started.

Step 1: Initializing the .NET MAUI DataForm control

1. First, create a new .NET MAUI application in Visual Studio.
2. Syncfusion .NET MAUI controls are available in the NuGet Gallery. To add the SfDataForm to your project, open the NuGet package manager in Visual Studio, search for Syncfusion.Maui.DataForm, and then install it.
3. Import the control namespace Syncfusion.Maui.DataForm in your XAML page.
4. Now, initialize the SfDataForm.

   <ContentPage> ….. xmlns:dataForm="clr-namespace:Syncfusion.Maui.DataForm;assembly=Syncfusion.Maui.DataForm" ….. <dataForm:SfDataForm/></ContentPage>

5. The Syncfusion.Maui.Core NuGet is a dependent package for all Syncfusion .NET MAUI controls. So, in the MauiProgram.cs file, register the handler for the Syncfusion core assembly. Refer to the following code.

   builder.ConfigureSyncfusionCore();

Step 2: Adding a model class to create a contact form

Let’s create the data form model class (ContactFormModel), which contains fields that store specific information such as names, addresses, and phone numbers. You can also use attributes to the data model class properties to effectively handle data.

Refer to the following code example.

public class ContactFormModel{ [DataFormDisplayOptions(ColumnSpan = 2, ShowLabel = false)] public string ProfileImage { get; set; } [Display(Prompt = "First name")] public string Name { get; set; } [Display(Prompt = "Last name")] public string LastName { get; set; } [Display(Prompt = "Mobile")] public double? Mobile { get; set; } [Display(Prompt = "Landline")] public double? Landline { get; set; } [Display(Prompt = "Address")] [DataFormDisplayOptions(ColumnSpan = 2)] public string Address { get; set; } [Display(Prompt = "City")] [DataFormDisplayOptions(ColumnSpan = 2)] public string City { get; set; } [Display(Prompt = "State")] public string State { get; set; } [Display(Prompt = "Zip code")] [DataFormDisplayOptions(ShowLabel = false)] public double? ZipCode { get; set; } [Display(Prompt = "Email")] public string Email { get; set; }}

Step 3: Defining the editors

By default, the .NET MAUI DataForm autogenerates editors based on primitive data types such as string, enumeration, DateTime, and TimeSpan in the DataObject property.

Some of the built-in editors are text, password, multi-line, combo box, autocomplete, date, time, checkbox, switch, and radio group.

Refer to the following code to set the data form model (ContactFormModel) to the DataObject property.

XAML

<Grid.BindingContext> <local:ContactFormViewModel/></Grid.BindingContext><dataForm:SfDataForm x:Name="contactForm" DataObject="{Binding ContactFormModel}" />

C#

public ContactFormViewModel(){ this.ContactFormModel = new ContactFormModel();}/// <summary>/// Gets or sets the contact form model./// </summary>public ContactFormModel ContactFormModel { get; set; }

Step 4: Grouping the editors in the contact form

The .NET MAUI DataForm allows you to group or categorize related data. For example, we can create a Name group with the first and last name fields.

Refer to the following code example. In it, we have created the Name and Address groups.

<dataForm:SfDataForm x:Name="contactForm" DataObject="{Binding ContactFormModel}" AutoGenerateItems="False" > <dataForm:SfDataForm.Items> <!--Name group--> <dataForm:DataFormGroupItem Name="Name"> <dataForm:DataFormGroupItem.Items> <dataForm:DataFormTextItem FieldName="Name" Padding="0, 10, 10, 10" /> <dataForm:DataFormTextItem FieldName="LastName" Padding="0, 10, 10, 10"/> </dataForm:DataFormGroupItem.Items> </dataForm:DataFormGroupItem> <!--Address group--> <dataForm:DataFormGroupItem Name="Address"> <dataForm:DataFormGroupItem.Items> <dataForm:DataFormMultilineItem FieldName="Address" RowSpan="2" Padding="0, 10, 10, 10"/> <dataForm:DataFormTextItem FieldName="City" Padding="0, 10, 10, 10"/> <dataForm:DataFormTextItem FieldName="State" Padding="0, 10, 10, 10"/> </dataForm:DataFormGroupItem.Items> </dataForm:DataFormGroupItem> </dataForm:SfDataForm.Items></dataForm:SfDataForm>

Step 5: Creating image-based labels

Let’s add custom fonts to the labels. To do so, we have to add the font file (.ttf) in the Fonts folder. Then, register the custom font in the CreateMauiApp method in the MauiProgram.cs file.

Refer to the following code example.

C#

builder .UseMauiApp<App>() .ConfigureFonts(fonts => { fonts.AddFont(“OpenSans-Regular.ttf”, “OpenSansRegular”); fonts.AddFont(“OpenSans-Semibold.ttf”, “OpenSansSemibold”); //// Register custom font. fonts.AddFont(“InputLayoutIcons.ttf”, “InputLayoutIcons”); });

XAML

<dataForm:SfDataForm.Items> <dataForm:DataFormGroupItem Name="Name"> <dataForm:DataFormGroupItem.Items> <dataForm:DataFormTextItem FieldName="Name" Padding="0, 10, 10, 10" > <!--Add custom font to label--> <dataForm:DataFormTextItem.LeadingLabelIcon> <FontImageSource Glyph="F" Color="#79747E" FontFamily="InputLayoutIcons" Size="18" /> </dataForm:DataFormTextItem.LeadingLabelIcon> </dataForm:DataFormTextItem> <dataForm:DataFormTextItem FieldName="LastName" LeadingLabelIcon="" Padding="0, 10, 10, 10"/> </dataForm:DataFormGroupItem.Items> </dataForm:DataFormGroupItem> …</dataForm:SfDataForm.Items>

Step 6: Adding a custom image editor

You can also add a custom image editor in the DataForm to display the person’s image in the contact form.

Refer to the following code example.

<dataForm:SfDataForm.Items> <!--Custom image editor added--> <dataForm:DataFormCustomItem FieldName="ProfileImage"> <dataForm:DataFormCustomItem.EditorView> <Image Source="people.png" HeightRequest="80"/> </dataForm:DataFormCustomItem.EditorView> </dataForm:DataFormCustomItem> ….</dataForm:SfDataForm.Items>

Step 7: Validating the data fields

The .NET MAUI DataForm supports validating the user input. Validation will make sure the users enter only correct values in the data form.

It supports the following data validations:

• Required field validation: To check whether all the required data has been entered. For example, the form can be submitted only after filling in all the data fields.
• Input format validation: To check that the data being entered is in the correct format. For example, email address data should include the @ character.
• Date range validation: To check that the data being entered is within the specific range. For example, dates should be selected within a specific date range.

We are going to add the required field validation to the phone number field in the contact form.

XAML

<dataForm:SfDataForm x:Name="contactForm" DataObject="{Binding ContactFormModel}" ColumnCount="1" AutoGenerateItems="False" ValidationMode="PropertyChanged"/>

C#

dataForm.ValidateProperty += this.OnDataFormValidateProperty; private void OnDataFormValidateProperty(object? sender, DataFormValidatePropertyEventArgs e){ if (e.PropertyName == nameof(ContactFormModel.Mobile) && !e.IsValid) { e.ErrorMessage = e.NewValue == null || string.IsNullOrEmpty(e.NewValue.ToString()) ? "Please enter the mobile number" : "Invalid mobile number"; }}

Step 8: Committing the data to the database

Now, you can save or submit the entered data in the underlying database with the help of the following  commit modes in the .NET MAUI DataForm:

• LostFocus: The default commit mode, it commits the value to the underline data object when the editor loses focus.
• PropertyChanged: Immediately commits the value to the underline data object when the value changes.
• Manual: Manually commits the value by calling the Commit method.

Note: For more details, refer to the data committing in the .NET MAUI DataForm control documentation.

Step 9: Designing the contact form with layouts

You can elegantly design the contact form with the following layouts in the .NET MAUI DataForm control:

• Grid layout: To arrange the editors in the form in a grid-like pattern with rows and columns.
• Linear layout: To arrange the editors in a single column.

In this demo, I have added the grid layout to the Address group of the contact form.

<dataForm:DataFormGroupItem Name="Address" ColumnCount="2"> <dataForm:DataFormGroupItem.Items> <dataForm:DataFormMultilineItem FieldName="Address" RowSpan="2" Padding="0, 10, 10, 10"> <dataForm:DataFormMultilineItem.LeadingLabelIcon> <FontImageSource Glyph="C" Color="#79747E" FontFamily="InputLayoutIcons" Size="20" /> </dataForm:DataFormMultilineItem.LeadingLabelIcon> </dataForm:DataFormMultilineItem> <dataForm:DataFormTextItem FieldName="City" LeadingLabelIcon="" Padding="0, 10, 10, 10"/> <dataForm:DataFormTextItem FieldName="State" LeadingLabelIcon="" Padding="0, 10, 10, 10"> <dataForm:DataFormTextItem.DefaultLayoutSettings> <dataForm:DataFormDefaultLayoutSettings LabelWidth="{OnIdiom Desktop=0.2*, Phone=0.3*}" EditorWidth="{OnIdiom Desktop=0.8*, Phone=0.7*}"/> </dataForm:DataFormTextItem.DefaultLayoutSettings> </dataForm:DataFormTextItem> <dataForm:DataFormCustomItem FieldName="ZipCode" Padding="0, 10, 10, 10" /> </dataForm:DataFormGroupItem.Items> </dataForm:DataFormGroupItem>

GitHub reference

For more details, refer to the creating a contact form using the .NET MAUI DataForm control GitHub demo.

Conclusion

Thanks for reading! In this blog, we have seen how to create a contact form easily using the Syncfusion .NET MAUI DataForm control. Try out the steps in this blog and leave your feedback in the comments section below!

For current Syncfusion customers, the newest version of Essential Studio is available from the license and downloads page. If you are not yet a customer, you can try our 30-day free trial to check out these features.

If you have any questions, you can contact us through our support forums, feedback portal, or support portal. We are always happy to assist you!

Related blogs

• Create a Project Planning and Resource Management Calendar in .NET MAUI
• Syncfusion .NET MAUI Control Demos Are Now Available at App Stores
• Introducing the Sixth Set of .NET MAUI Controls
• OCR in .NET MAUI: Building an Image Processing Application

View Details

View Details

The .NET MAUI Scheduler is a tool for scheduling events in a .NET MAUI application. It supports scheduling recurring events, which are regularly or periodically occurring appointments or events. Scheduler’s API has been designed with simplicity and ease of use in mind, so that anyone can add recurring events to their project with just a few API calls. Supported by a robust internal scheduling engine, Scheduler gives you all the APIs you need to build simple and easy-to-maintain schedules.

Let’s see how to create and customize recurrence appointments in the .NET MAUI Scheduler.

Note: If you are new to this control, refer to the .NET MAUI Scheduler getting started documentation before proceeding.

Recurrence Rule

The Scheduler control uses the recurrence rule (string) to specify the recurrence details of an appointment. The recurrence rule specifies the recurrence frequency, interval, range, and position details.

Recurrence pattern

The pattern specifies the frequency or type of appointment: daily, weekly, monthly, and yearly.

Interval

Specify the interval between consecutive occurrences of the recurring appointment.

Range

The time range in which an appointment recurs. The range value is determined by the recurrence rule’s number of instances (count) or the end date (until). The recurring appointment is considered a never-ending appointment when the range is not specified.

Position details

The position (the day of the week, week of the month, month of the year) is specified and used on weekly, monthly, and yearly recurrence types.

Recurrence Types

Recurrence is the base term describing a repeating pattern. Business people use the concept of regular assignment of tasks or recurring events on certain days of the week, month, or even annually, like Jan. 1 every year.

Daily recurrence type

An appointment repeats daily with a specified day interval within a set date range. Following are some examples of daily recurrences.

Weekly recurrence type

An appointment repeats on a specified weekday with a specified week interval within the specified date range. Following are some examples of weekly recurrences.

Monthly recurrence type

An appointment repeats on a specified day of the month or weekday of a specified week position with a specified month interval within a set date range. Following are some examples of monthly recurrences.

Yearly recurrence type

Schedule and repeat an appointment on a specified day of a month or weekday of specified week position of a month with a specified year interval within a specified date range.

Example

SfScheduler scheduler = new SfScheduler();scheduler.View = SchedulerView.Week;var appointment = new ObservableCollection<SchedulerAppointment>();//Adding scheduler appointment in the scheduler appointment collection.appointment.Add(new SchedulerAppointment(){ StartTime = DateTime.Today.Date.AddHours(9), EndTime = DateTime.Today.Date.AddHours(11), Subject = "Daily scrum meeting", RecurrenceRule = "FREQ=DAILY;INTERVAL=1;COUNT=10"});//Adding the scheduler appointment collection to the AppointmentsSource of .NET MAUI Scheduler.scheduler.AppointmentsSource = appointment;this.Content = scheduler;

Note: For more details, refer to the Recurrence appointments in the .NET MAUI Scheduler documentation.

Recurrence Exception Appointment

The Scheduler control provides support to restrict (change start time, end time, and appointment details) occurrences and remove an occurrence of a repeating appointment with a recurrence exception.

Deleting a recurring appointment

The RecurrenceExceptionDates property in an appointment is used to remove the occurrence on specified dates.

Refer to the following code example.

SfScheduler scheduler = new SfScheduler();scheduler.View = SchedulerView.Week;var appointment = new ObservableCollection<SchedulerAppointment>();//Adding scheduler appointment in the scheduler appointment collection.appointment.Add(new SchedulerAppointment(){ StartTime = DateTime.Today.Date.AddHours(9), EndTime = DateTime.Today.Date.AddHours(11), Subject = "Daily scrum meeting", RecurrenceRule = "FREQ=DAILY;INTERVAL=1;COUNT=10", RecurrenceExceptionDates = new ObservableCollection<DateTime> { DateTime.Today.AddDays(1) },});//Adding the scheduler appointment collection to the AppointmentsSource of .NET MAUI Scheduler.scheduler.AppointmentsSource = appointment;this.Content = scheduler;

Modifying an occurrence of an appointment

The RecurrenceExceptionDates and RecurrenceId properties in an appointment are used to change the occurrence appointment details without removing the appointment on a specified date.

Refer to the following code example.

SfScheduler scheduler = new SfScheduler();scheduler.View = SchedulerView.Week;var appointment = new ObservableCollection<SchedulerAppointment>();//Adding scheduler appointment in the scheduler appointment collection.appointment.Add(new SchedulerAppointment(){ Id = 1, StartTime = DateTime.Today.Date.AddHours(9), EndTime = DateTime.Today.Date.AddHours(11), Subject = "Daily scrum meeting", RecurrenceRule = "FREQ=DAILY;INTERVAL=1;COUNT=10", RecurrenceExceptionDates = new ObservableCollection<DateTime> { DateTime.Today.AddDays(1) },});//Adding exception appointment in the scheduler appointment collection.Appointment.Add(new SchedulerAppointment(){ Id = 2, StartTime = DateTime.Today.AddDays(1).Date.AddHours(11), EndTime = DateTime.Today.AddDays(1).Date.AddHours(13), Subject = "Scrum meeting - Changed", RecurrenceId=1,});//Adding the scheduler appointment collection to the AppointmentsSource of .NET MAUI Scheduler.scheduler.AppointmentsSource = appointment;this.Content = scheduler;

Conclusion

Thank you for your time! This blog post showed how to set a recurring appointment in the .NET MAUI Scheduler. You can explore other features in the Scheduler control in the documentation, where you can find detailed explanations of each with code examples.

If you are not a Syncfusion customer, you can try our 30-day free trial to see how our components can enhance your projects.

Please feel free to try out the samples available in our .NET MAUI sample location and share your feedback or ask questions in the comments section. Or contact us through our support forum, support portal, or feedback portal. We are happy to assist you!

Related blogs

• How to Draw 2D Graphics in .NET MAUI’s GraphicsView
• Keyboard Shortcuts in .NET MAUI Scheduler
• 4 Impressive Features of .NET MAUI in .NET 7
• Syncfusion Mobile and Desktop Controls Are Now Compatible with .NET 7

View Details

As we all know, Microsoft SharePoint is one of the most popular and widely used applications for storing files in the cloud. In this blog, we will see how to implement SharePoint authentication, access PDF files, and view them easily in a Xamarin application using our Syncfusion Xamarin PDF Viewer.

Let’s get started!

Configuring the Xamarin application using the Azure Portal

To start with, you need to register your Xamarin application in Azure AD. Sign into the Azure Portal, search for and select Azure Active Directory, then go to the App registrations tab and select New registration.

Step 1: In the Register an application page:

1. Enter a Name for your app registration.
2. Select the type of accounts you want to grant access to your app.
3. Select Register.

Step 2: After the app registration is created, take note of the Application (client) ID for later use. You can find it in the Overview tab of the application registration we just created.

Step 3: Then, go to the Authentication tab, click Add a platform, and add both iOS and Android. Just for Android, we need to generate and provide a signature hash.

Creating and configuring a Xamarin application

Now, integrate the Microsoft SharePoint authentication into our Xamarin application to access the PDF documents and view them using our Syncfusion Xamarin PDF Viewer.

Step 1: Create a new Xamarin.Forms project.

Step 2: Install the following NuGet packages in the PCL and all platform projects:

• PnP.Framework—To authenticate and retrieve data from SharePoint.
• Syncfusion.Xamarin.SfPdfViewer—To view the PDF documents.
• Syncfusion.Xamarin.SfTreeView —To visualize the retrieved SharePoint documents like in a file explorer.
• Syncfusion.Xamarin.SfProgressBar—To indicate the progress of a task.

Additionally, in iOS, to launch the application with Syncfusion controls, you need to call the SfPdfDocumentViewRenderer.Init(),SfTreeViewRenderer.Init(), and SfLinearProgressBarRenderer.Init() methods in the FinishedLaunching overridden method of the AppDelegate class after the Xamarin.Forms framework has been initialized and before the LoadApplication is called. Refer to the following code sample.

public override bool FinishedLaunching(UIApplication app, NSDictionary options){ global::Xamarin.Forms.Forms.Init(); Syncfusion.SfPdfViewer.XForms.iOS.SfPdfDocumentViewRenderer.Init(); Syncfusion.XForms.iOS.TreeView.SfTreeViewRenderer.Init(); Syncfusion.XForms.iOS.ProgressBar.SfLinearProgressBarRenderer.Init(); LoadApplication(new App()); App.ParentWindow = null; return base.FinishedLaunching(app, options);}

Note: Here, the SfTreeView and SfProgressBar have just been used to improve the usability of the application. You can replace these with the controls of your choice.

Step 3: Create model classes named FileManager and PDFFile to hold the data of the SharePoint documents and the PDF document, respectively. Refer to the following code example.

FileManager.cs

using System.ComponentModel;using Xamarin.Forms;using Microsoft.SharePoint.Client;namespace SharePoint{ public class FileManager : INotifyPropertyChanged { private string itemName; private bool hasChildNodes; private Folder folder; private File file; private ImageSource imageIcon; public FileManager() { } public string ItemName { get { return itemName; } set { itemName = value; RaisedOnPropertyChanged("ItemName"); } } public bool HasChildNodes { get { return hasChildNodes; } set { hasChildNodes = value; RaisedOnPropertyChanged("HasChildNodes"); } } public Folder Folder { get { return folder; } set { folder = value; RaisedOnPropertyChanged("Folder"); } } public File File { get { return file; } set { file = value; RaisedOnPropertyChanged("File"); } } public ImageSource ImageIcon { get { return imageIcon; } set { imageIcon = value; RaisedOnPropertyChanged("ImageIcon"); } } public event PropertyChangedEventHandler PropertyChanged; public void RaisedOnPropertyChanged(string \_PropertyName) { if (PropertyChanged != null) { PropertyChanged(this, new PropertyChangedEventArgs(\_PropertyName)); } } }}

PDFFile.cs

using System.IO;namespace SharePoint{ public class PdfFile { public Stream DocumentStream { get; set; } public string Name { get; set; } public PdfFile(Stream pdfStream,string pdfName) { DocumentStream = pdfStream; Name = pdfName; } }}

Step 4: Create a ViewModel class named SharePointViewModel.cs. Implement the logic to authenticate and retrieve the SharePoint documents and return the document stream of the selected PDF file in the File Manager. Refer to the following code example.

SharePointViewModel.cs

using Microsoft.Identity.Client;using Microsoft.SharePoint.Client;using PnP.Framework;using Syncfusion.TreeView.Engine;using System;using System.Collections.ObjectModel;using System.IO;using System.Reflection;using System.Threading.Tasks;using System.Windows.Input;using Xamarin.Essentials;using Xamarin.Forms;namespace SharePoint{ internal class SharePointViewModel { // Replace with your SharePoint tenant name. private const string Tenant = "{YOUR TENANT NAME}"; // Replace with your targeted SharePoint site name. private const string SiteName = "{YOUR SITE NAME}"; // Replace with your Azure AD Application's Client ID. private const string ClientId = "{YOUR CLIENT ID}"; // Replace with your Azure AD Application's Package Name or Bundle ID. private const string AppId = "{YOUR APP ID}"; // For Android, replace with your Authentication Signature Hash. private const string SignatureHash = "{YOUR SIGNATURE HASH}"; public ObservableCollection<FileManager> Documents { get; set; } public ClientContext Context { get; set; } public ICommand DocumentsViewOnDemandCommand { get; set; } public SharePointViewModel() { DocumentsViewOnDemandCommand = new Command(ExecuteOnDemandLoading, CanExecuteOnDemandLoading); } private bool CanExecuteOnDemandLoading(object sender) { var hasChildNodes = ((sender as TreeViewNode).Content as FileManager).HasChildNodes; if (hasChildNodes) return true; else return false; } private void ExecuteOnDemandLoading(object obj) { var node = obj as TreeViewNode; // Skip the repeated population of child items when every time the node expands. if (node.ChildNodes.Count > 0) { node.IsExpanded = true; return; } //Animation starts for expander to show progress of load on demand. node.ShowExpanderAnimation = true; Microsoft.SharePoint.Client.Folder root = (node.Content as FileManager).Folder; var documents = GetDocuments(root); node.PopulateChildNodes(documents); if (documents.Count > 0) { //Expand the node after child items are added. node.IsExpanded = true; } //Stop the animation after load on demand is executed. If animation not stopped, it remains still after execution of load on demand. node.ShowExpanderAnimation = false; } /// <summary> /// Perform SharePoint authentication and return the documents of the target site. /// </summary> /// <returns>Documents of the target site</returns> internal async Task AuthenticateAndAcquireDocuments() { string redirectURI = DeviceInfo.Platform == DevicePlatform.Android ? $"msauth://{AppId}/{SignatureHash}" : $"msauth.{AppId}://auth"; IPublicClientApplication PublicClientApp = PublicClientApplicationBuilder.Create(ClientId) .WithIosKeychainSecurityGroup(AppId) .WithRedirectUri(redirectURI) .WithAuthority("https://login.microsoftonline.com/common") .Build(); var \_scopes = new String[] { $"https://{Tenant}.sharepoint.com/AllSites.Read" }; //Replace with your own permissions. try { AuthenticationResult authResult = await PublicClientApp.AcquireTokenInteractive(\_scopes) .WithParentActivityOrWindow(App.ParentWindow) .WithUseEmbeddedWebView(true) .ExecuteAsync(); var authManager = new AuthenticationManager().GetAccessTokenContext( $"https://{Tenant}.sharepoint.com/sites/{SiteName}", authResult.AccessToken); Context = authManager.GetSiteCollectionContext(); var web = Context.Web;//Gets target site web details. var docs = web.Lists.GetByTitle("Documents");//Gets site's documents list. Var root = docs.RootFolder; //Root folder. Documents = GetDocuments(root); } catch (Exception e) { } } /// <summary> /// Returns the documents present in the passed root or parent folder. /// </summary> /// <param name="root">Root folder</param> /// <returns>Documents of the root or parent folder</returns> internal ObservableCollection<FileManager> GetDocuments(Microsoft.SharePoint.Client.Folder root) { ObservableCollection<FileManager> documents = new ObservableCollection<FileManager>(); Assembly assembly = typeof(DocumentsPage).GetTypeInfo().Assembly; Context.Load(root, f => f.ItemCount, f => f.Folders); Context.Load(root, f => f.ItemCount, f => f.Files); Context.ExecuteQuery(); foreach (Microsoft.SharePoint.Client.Folder folder in root.Folders) { bool hasChildNodes = folder.ItemCount > 0 ? true : false; var folderItem = new FileManager() { ItemName = folder.Name, Folder = folder, HasChildNodes = hasChildNodes, ImageIcon = ImageSource.FromResource("SharePoint.Icons.treeview\_folder.png", assembly) }; documents.Add(folderItem); } foreach (Microsoft.SharePoint.Client.File file in root.Files) { if (file.Name.EndsWith(".pdf")) { var fileItem = new FileManager() { ItemName = file.Name, File = file, ImageIcon = ImageSource.FromResource("SharePoint.Icons.treeview\_pdf.png", assembly) }; documents.Add(fileItem); } } return documents; } /// <summary> /// Returns the chosen PDF document details. /// </summary> /// <param name="file">PDF file chosen from the File Explorer</param> /// <returns>PDF document details</returns> internal PdfFile GetPdfDocumentDetails(Microsoft.SharePoint.Client.File file) { MemoryStream PdfDocumentStream = new MemoryStream(); var fileStream = file.OpenBinaryStream(); Context.Load(file); Context.ExecuteQuery(); fileStream.Value.CopyTo(PdfDocumentStream); PdfDocumentStream.Position = 0; return new PdfFile(PdfDocumentStream, file.Name); } }}

Make sure to replace the following things in the previous code example:

• Tenant—SharePoint tenant name.
• SiteName—SharePoint site name.
• ClientId—Application’s Client ID noted from the Azure AD.
• AppId—Application’s package name [Android] or bundle ID [iOS] given during Azure AD authentication.
• SignatureHash—Signature hash noted from Android’s authentication.

Step 5: Create a view named PdfViewerPage to view the selected PDF file from the SharePoint documents. Refer to the following code example.

PdfViewerPage.xaml

<?xml version="1.0" encoding="utf-8" ?><ContentPage xmlns="http://xamarin.com/schemas/2014/forms" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" xmlns:syncfusion="clr-namespace:Syncfusion.SfPdfViewer.XForms;assembly=Syncfusion.SfPdfViewer.XForms" x:Class="SharePoint.PdfViewerPage"> <ContentPage.Content> <syncfusion:SfPdfViewer x:Name="PdfViewer"/> </ContentPage.Content></ContentPage>

PdfViewerPage.xaml.cs

using Xamarin.Forms;using Xamarin.Forms.Xaml;namespace SharePoint{ [XamlCompilation(XamlCompilationOptions.Compile)] public partial class PdfViewerPage : ContentPage { public PdfViewerPage(PdfFile pdfFile) { InitializeComponent(); this.Title = pdfFile.Name; pdfFile.DocumentStream.Position = 0; PdfViewer.LoadDocument(pdfFile.DocumentStream); } protected override void OnDisappearing() { PdfViewer.Dispose(); base.OnDisappearing(); } }}

Step 6: Create another view named DocumentsPage to login and display the SharePoint documents of the given site name in the File Explorer-like Treeview. Also, in the TreeView’s ItemTapped handler method, implement the logic to retrieve the selected PDF document details and navigate to the PdfViewerPage to view them.

Note: In this example, we have used TreeView’s ItemTemplate Selector to customize the appearance of each item with different templates to create the file explorer view.

Refer to the following code example.

DocumentsPage.xaml

<?xml version="1.0" encoding="utf-8" ?><ContentPage xmlns="http://xamarin.com/schemas/2014/forms" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" xmlns:treeView="clr-namespace:Syncfusion.XForms.TreeView;assembly=Syncfusion.SfTreeView.XForms" xmlns:progressBar="clr-namespace:Syncfusion.XForms.ProgressBar;assembly=Syncfusion.SfProgressBar.XForms" xmlns:local="clr-namespace:SharePoint" NavigationPage.HasNavigationBar="False" x:Class="SharePoint.DocumentsPage"> <ContentPage.BindingContext> <local:SharePointViewModel/> </ContentPage.BindingContext> <ContentPage.Resources> <ResourceDictionary> <local:ItemTemplateSelector x:Key="ItemTemplateSelector" /> </ResourceDictionary> </ContentPage.Resources> <ContentPage.Content> <Grid> <Grid.RowDefinitions> <RowDefinition Height="auto"/> <RowDefinition Height="*"/> </Grid.RowDefinitions> <progressBar:SfLinearProgressBar x:Name="ProgressBar" Grid.Row="0" HeightRequest="5" IsIndeterminate="True" IsVisible="false" ProgressColor="#038387"/> <StackLayout Grid.Row="1" Orientation="Vertical" VerticalOptions="Center"> <Image x:Name="SharepointImage" HeightRequest="175" WidthRequest="175" VerticalOptions="Center"></Image> <Button Text="SHAREPOINT LOGIN" x:Name="LoginButton" WidthRequest="250" HorizontalOptions="Center" Font="18" Clicked="LoginButton\_Clicked"/> <Label x:Name="DocumentsTitleLabel" HeightRequest="50" IsVisible="false" Text="Documents" HorizontalTextAlignment="Center" VerticalTextAlignment="Center" FontSize="20" TextColor="White" BackgroundColor="#038387"/> <treeView:SfTreeView x:Name="DocumentsView" ItemHeight="40" IsVisible="false" ChildPropertyName="SubFiles" LoadOnDemandCommand="{Binding DocumentsViewOnDemandCommand}" ItemTemplateContextType="Node" ItemTapped="DocumentsView\_ItemTapped" SelectionBackgroundColor="#038387" SelectionForegroundColor="White" Indentation="20" ExpanderWidth="40" ItemTemplate="{StaticResource ItemTemplateSelector}"> </treeView:SfTreeView> </StackLayout> </Grid> </ContentPage.Content></ContentPage>

DocumentsPage.xaml.cs

using System;using System.Reflection;using Xamarin.Forms;using Xamarin.Forms.Xaml;namespace SharePoint{ [XamlCompilation(XamlCompilationOptions.Compile)] public partial class DocumentsPage : ContentPage { public DocumentsPage() { InitializeComponent(); SharepointImage.Source = ImageSource.FromResource("SharePoint.Icons.sharepoint.png", typeof(DocumentsPage).GetTypeInfo().Assembly); } private async void LoginButton\_Clicked(object sender, EventArgs e) { ProgressBar.IsVisible = true; LoginButton.IsVisible = false; await (BindingContext as SharePointViewModel).AuthenticateAndAcquireDocuments(); SharepointImage.IsVisible = false; DocumentsTitleLabel.IsVisible = true; DocumentsView.IsVisible = true; DocumentsView.ItemsSource = (BindingContext as SharePointViewModel).Documents; ProgressBar.IsVisible = false; } private void DocumentsView\_ItemTapped(object sender, Syncfusion.XForms.TreeView.ItemTappedEventArgs e) { Microsoft.SharePoint.Client.File file = (e.Node.Content as FileManager).File; if (file != null) { Navigation.PushAsync(new PdfViewerPage((BindingContext as SharePointViewModel) .GetPdfDocumentDetails(file))); } } }}

In this example, you can navigate back to the Documents page from PDF Viewer page to choose or load another PDF document by clicking the back icon in the navigation bar. Refer to the following image.

Step 7: Before running the application, there are some configurations that need to be done in both Android and iOS platforms to make the SharePoint authentication successful and to continue with our application.

iOS

In iOS, to reopen our application after the authentication flow is completed, override the OpenUrl method in the AppDelegate class. Refer to the following code example.

public override bool OpenUrl(UIApplication app, NSUrl url, NSDictionary options){ AuthenticationContinuationHelper.SetAuthenticationContinuationEventArgs(url); return true;}

Next, open the Entitlements.plist file and check the Enable Keychain option. This will add an entry for our app to the keychain, which is where iOS securely stores our credentials.

To allow the application to use the keychain, set the Custom Entitlements setting to point to the Entitlements.plist file. This setting option can be found in the Properties -> iOS Bundle Signing -> Additional Resources.

Finally, configure the iOS application to respond to the callback URL by defining a URL type in the Info.plist file. Add or update the Identifier, URL Schemes, and Role properties in the URL type. Refer to the following screenshot.

Android

In Android, to reopen our application after the authentication is completed, override the OnActivityResult method in the MainActivity class. Refer to the following code example.

protected override void OnActivityResult(int requestCode, Result resultCode, Intent data){ base.OnActivityResult(requestCode, resultCode, data); AuthenticationContinuationHelper.SetAuthenticationContinuationEventArgs(requestCode, resultCode, data);}

Next, configure the Android application to respond to the callback URL by providing an activity and an intent-filter in the AndroidManifest.xml file. Refer to the following code example.

AndroidManifest.xml

<?xml version="1.0" encoding="utf-8"?><manifest xmlns:android="http://schemas.android.com/apk/res/android" android:versionCode="1" android:versionName="1.0" package="com.companyname.SharePoint" android:installLocation="preferExternal"> <uses-sdk android:minSdkVersion="21" android:targetSdkVersion="30" /> <uses-permission android:name="android.permission.INTERNET" /> <uses-permission android:name="android.permission.ACCESS\_NETWORK\_STATE" /> <uses-permission android:name="android.permission.WRITE\_EXTERNAL\_STORAGE" /> <application android:label="SharePoint.Android"> <activity android:name="microsoft.identity.client.BrowserTabActivity"> <intent-filter> <action android:name="android.intent.action.VIEW" /> <category android:name="android.intent.category.DEFAULT" /> <category android:name="android.intent.category.BROWSABLE" /> <data android:scheme="msauth" android:host="com.syncfusion.sharepointauth" android:path="{YOUR\_SIGNATURE\_HASH}" /> </intent-filter> </activity> </application></manifest>

Note: Please make sure to replace the text {YOUR\_SIGNATURE\_HASH} with your application’s signature hash in the AndroidManifest.xml file.

Step 8: Finally, you can deploy the application. The output of this example application will look as follows.

Resource

For more details, check out the complete code example on GitHub.

Conclusion

Thanks for reading! We have seen in this blog how to access PDF files from SharePoint and load them using Syncfusion’s Xamarin.Forms PDF Viewer control. Try this in your application and share your feedback in the comment section below!

If you aren’t a customer, you can try our 30-day free trial to check out these features. Also, try our other Xamarin examples from this GitHub location.

If you have any questions, you can contact us through our support forum, support portal, or feedback portal. We are always happy to assist you!

Related blogs

• Easily Lock and Unlock Annotations Using Xamarin.Forms PDF Viewer
• Migrating Syncfusion Xamarin.Forms Controls to .NET MAUI
• View PDF Annotations as a List and Navigate Using Xamarin.Forms PDF Viewer
• Lazy Load JSON Data in Xamarin.Forms ListView: An Overview

View Details

We are excited to announce that the Syncfusion .NET MAUI control demos are now available in the app stores. Syncfusion offers a wide range of .NET MAUI controls and document processing libraries, providing everything you need to build modern mobile and desktop applications for platforms such as Android, iOS, Mac Catalyst, and Windows.

To start off 2023, we have published our sample browser, which contains demos of our .NET MAUI controls, in the app stores for your convenience. With these demos, you can easily explore the capabilities of our controls and see how they can enhance your apps’ development. Whether you are building a new app or looking to upgrade your current app, Syncfusion’s .NET MAUI controls are the perfect solution.

Syncfusion .NET MAUI controls

Syncfusion offers the following 35+ .NET MAUI controls and file-format libraries:

Syncfusion’s .NET MAUI sample browser demos

Syncfusion’s .NET MAUI sample browser is a comprehensive app that showcases the capabilities of our .NET MAUI controls. You can deploy this app on various devices, including Android, iOS, macOS, and Windows. It can adapt to different screen sizes to provide an optimal user experience on mobile and desktop devices. The app also includes a settings page and code viewer navigator to help you customize and explore the demos.

This is a valuable resource for anyone looking to incorporate Syncfusion controls into their .NET MAUI apps. It features a wide range of demos that showcase real-world use cases, making it easy to see how these controls can be used in your projects. The controls are user-friendly and highly customizable, making them an excellent choice for developers who want to add rich, feature-packed functionalities to their apps. Whether you’re looking to build a mobile or desktop app, the Syncfusion .NET MAUI sample browser is an essential tool for anyone looking to take advantage of these robust controls.

How to get and install the .NET MAUI sample browser app

The Syncfusion .NET MAUI sample browser app is available on the Android, iOS, macOS, and Windows stores.

.NET MAUI demos for Android

Download the Syncfusion .NET MAUI demos for Android devices from the Google Play Store or scan the following QR code.

.NET MAUI demos for Windows

Install the .NET MAUI demos for Windows from the Microsoft Store or scan the following QR code.

.NET MAUI demos for iOS

According to Apple’s App Store Review Guidelines (section 2.2 on beta testing), we cannot upload our Syncfusion .NET MAUI sample browser app to the App Store. We understand and respect the guidelines set forth by Apple.

However, you can still experience the app in an iOS device. You can install our .NET MAUI demos for iOS using the TestFlight app on your device. Or you can scan the following QR code to get them.

.NET MAUI demos for macOS

Install the .NET MAUI demos for macOS from the App Center or scan the following QR code to download them.

View demo code on GitHub

You can also find the complete code examples for Syncfusion .NET MAUI controls on the GitHub repository.

Conclusion

Thanks for reading! In this blog, we have seen the availability of Syncfusion .NET MAUI control demos in the app stores for Android, iOS, macOS, and Windows platforms. These demonstrations go through the capabilities and features of our controls in detail and help you build elegant, high-performance, and cross-platform apps. Try them out and leave your feedback in the comments section below!

For questions, you can contact us through our support forum, support portal, or feedback portal. We are always happy to assist you!

I hope the demos are helpful and informative and you will consider using the Syncfusion .NET MAUI controls for your next project. Happy coding!

Related blogs

• Replicating a Cruise Travel App UI in .NET MAUI
• Building an Audio Recorder and Player App in .NET MAUI
• Introducing the New .NET MAUI Pyramid Charts
• Introducing the New .NET MAUI Text Input Layout

View Details

Syncfusion is excited to announce the availability of another valuable control, PDF Viewer, for the .NET MAUI platform in the 2022 Volume 4 release.

The new .NET MAUI PDF Viewer control allows you to easily add PDF viewing capabilities within your applications. It is supported in Windows, macOS, iOS, and Android platforms.

In this blog, we’ll explore the features of the .NET MAUI PDF Viewer and the steps to get started with it.

Key features

The key features of the new .NET MAUI PDF Viewer are:

• Virtual scrolling: Easily scroll through the pages in a PDF document with a fluent experience. The pages are rendered on demand in order to enhance the loading and scrolling performance.
• Magnification: The content of a PDF document can be efficiently zoomed in and out by pinching or changing the zoom factor programmatically.
• Page navigation: Navigate to the desired pages instantly using the programmatic page navigation or by dragging the scroll box in the UI.
• Opening password-protected PDFs: Load and view password-protected PDFs in a hassle-free way. Also, you can design a custom password request view and integrate the functionality easily with built-in options.

Getting started with .NET MAUI PDF Viewer

Let’s see how to integrate the Syncfusion .NET MAUI PDF Viewer control in your application and use its basic features.

Creating a .NET MAUI application with the PDF Viewer

Step 1: First, create a new .NET MAUI application in Visual Studio.

Step 2: Then, add the Syncfusion.Maui.PdfViewer NuGet package reference to your project from the NuGet Gallery.

Step 3: Then, register the handler for the Syncfusion core package in the MauiProgram.cs file. Refer to the following code.

using Syncfusion.Maui.Core.Hosting;namespace PdfViewerExample{ public static class MauiProgram { public static MauiApp CreateMauiApp() {var builder = MauiApp.CreateBuilder();builder .UseMauiApp<App>() .ConfigureFonts(fonts => { fonts.AddFont("OpenSans-Regular.ttf", "OpenSansRegular"); fonts.AddFont("OpenSans-Semibold.ttf", "OpenSansSemibold"); }); builder.ConfigureSyncfusionCore(); return builder.Build(); } }}

Step 4: Add a new folder to the project named Assets and add the PDF document you want to view (such as PDF\_Succinctly.pdf) using the PDF Viewer.

Note: You can also load PDF files from local storage or a URL.

Step 5: We are going to use the MVVM binding technique. So, create a new view model class named PdfViewerViewModel.cs and add the following code to it.

using System.ComponentModel;using System.Reflection;namespace PdfViewerExample{ internal class PdfViewerViewModel: INotifyPropertyChanged { private Stream? m\_pdfDocumentStream; /// <summary> /// An event to detect the change in the value of a property. /// </summary> public event PropertyChangedEventHandler? PropertyChanged; /// <summary> /// The PDF document stream that is loaded into the instance of the PDF viewer. /// </summary> public Stream PdfDocumentStream { get { return m\_pdfDocumentStream; } set { m\_pdfDocumentStream = value; OnPropertyChanged("PdfDocumentStream"); } } /// <summary> /// Constructor of the view model class. /// </summary> public PdfViewerViewModel() { //Accessing the PDF document that is added as an embedded resource as a stream. m\_pdfDocumentStream = typeof(App).GetTypeInfo().Assembly.GetManifestResourceStream("PdfViewerExample.Assets.PDF\_Succinctly.pdf"); } public void OnPropertyChanged(string name) { PropertyChanged?.Invoke(this, new PropertyChangedEventArgs(name)); } }}

Step 6: In the MainPage.xaml page, import the control namespace Syncfusion.Maui.PdfViewer, initialize the SfPdfViewer control, and bind the created PdfDocumentStream to the SfPdfViewer.DocumentSourceproperty. Refer to the following code example.

Note: The DocumentSource property accepts both stream and byte[] instances.

<?xml version="1.0" encoding="utf-8" ?><ContentPage xmlns="http://schemas.microsoft.com/dotnet/2021/maui" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" xmlns:syncfusion="clr-namespace:Syncfusion.Maui.PdfViewer;assembly=Syncfusion.Maui.PdfViewer" xmlns:local="clr-namespace:PdfViewerExample" x:Class="PdfViewerExample.MainPage"> <ContentPage.BindingContext> <local:PdfViewerViewModel x:Name="viewModel" /> </ContentPage.BindingContext> <ContentPage.Content> <syncfusion:SfPdfViewer x:Name="PdfViewer" DocumentSource="{Binding PdfDocumentStream}"> </syncfusion:SfPdfViewer> </ContentPage.Content></ContentPage>

Note: If you are using multiple pages in your app, then make sure to unload the document from the SfPdfViewer class while leaving the page that has it to release the memory and resources consumed by the loaded PDF document. You can unload documents by calling the UnloadDocument method. Also, while changing or opening different documents on the same page, the previously loaded document will be unloaded automatically by the SfPdfViewer.

Step 7: Finally, run the app. Refer to the following output image.

Note: For more details, refer to the .NET MAUI PDF Viewer GitHub demo.

Creating a custom toolbar

Currently, we do not support a built-in toolbar in the .NET MAUI PDF Viewer. However, we have provided APIs for performing magnification and page navigation programmatically.

Therefore, you can design a simple custom toolbar and invoke the operations using the following APIs.

Load document API

Page navigation APIs

Zoom APIs

Note: For more details, refer to the .NET MAUI PDF Viewer with a custom toolbar demo on GitHub.

Opening a password-protected PDF

To open a password-protected or encrypted PDF document, you can use the LoadDocument() method by providing the password along with the document stream.

Refer to the following code example.

string password = "PASSWORD";pdfViewer.LoadDocument(pdfDocumentStream, password);

Using the following APIs, you can determine whether a PDF document is password protected.

Note: For more details, refer to the opening a password-protected PDF using the .NET MAUI PDF Viewer demo on GitHub.

Reference

Refer to the .NET MAUI PDF Viewer documentation to learn about its other features.

Coming soon

We have planned and are working to support the following major features in the .NET MAUI PDF Viewer control in upcoming releases:

• Built-in toolbar.
• Text search.
• Text selection and copy.
• Bookmark, TOC, and hyperlink navigation.
• Localization.
• Accessibility.
• RTL text.
• The ability to add, edit, save, and remove annotations.
• Form filling with edit and save functions.
• Single-page layout mode.
• Thumbnails.
• Themes.

Conclusion

Thanks for reading! I hope you enjoyed learning about the new Syncfusion .NET MAUI PDF Viewer introduced in 2022 Volume 4. You can download and check out our MAUI demo app from Google Play and the Microsoft Store.

Also, check out our Release Notes and the What’s New pages to see the other updates in this release.

For current customers, the new version is available for download from the License and Downloads page. If you are not yet a Syncfusion customer, you can try our 30-day free trial to check out our newest features.

You can share your feedback and questions through the comments section below or contact us through our support forums, support portal, or feedback portal. We are always happy to assist you!

Related blogs

• Introducing the New .NET MAUI Rating Control
• Introducing the Sixth Set of .NET MAUI Controls
• Authenticate the .NET MAUI App with Azure AD
• Agenda View in .NET MAUI Scheduler: A Perfect Tool for Modern-Day Office Management

View Details

I’ve been banging my head against a wall trying to run XUnit tests on my Mac, for my Xamarin Forms app.

View Details

The .NET MAUI Backdrop included in our 2022 Volume 4 release is a specialized content page. It provides a full-screen interface for displaying and interacting with a single piece of content. This page comprises two surfaces, a back layer and a front layer, stacked one over the other. The back layer displays actions and context, while the rest of the page is covered by the front layer.

Integrating the Backdrop with built-in .NET MAUI pages such as NavigationPage and FlyoutPage allow you to utilize features such as title, icon, page navigation, and toolbar item customization.

The back layer holds options such as navigation, filtration, and more, which updates the front layer content on performing specific actions. When concealed, the back layer can provide contextual information about the front layer. When revealed, the back layer displays contextual controls that relate to the front layer.

Front layer

The front layer is always visible in front of the back layer. It is displayed at full width and holds primary content.

You can customize the corner of the front layer of the .NET MAUI Backdrop to be curve or flat. You can customize one or both corners of the front layer with these shapes. It is also possible to change the default radius of the custom shapes.

Back layer

The back layer appears at the lowest elevation in the app, filling the entire background. It holds actionable content that is relevant to the front layer.

When the back layer is revealed, use the auto adjustment option to adjust its height based on its content, or expand it fully until only the front layer’s header is visible.

Reveal and conceal the back layer

The Backdrop provides options to reveal and conceal the back layer.

• Programmatically: Reveals the back layer by setting the IsBackLayerRevealed property to true. By default, it is set to false.
• Touch interaction: Reveals the back layer by tapping the toolbar icon at the top-right corner of the navigation bar header. The hamburger icon reveals the back layer, while the close icon conceals it. When adding the Backdrop as a child of the FlyoutPage, the hamburger, and close icons will be replaced by expand (or down arrow) and collapse (or up arrow) icons, respectively.

  

• Swipe or flick action: Reveals the back layer when swiping or flicking the front layer header. Swipe downward to reveal, and swipe upward to conceal the back layer. The swipe or flick action will be handled only on the top of the front layer (header).

  

Add the .NET MAUI Backdrop to your application

We have seen the key features of the .NET MAUI Backdrop control. Let’s see how to create a simple .NET MAUI app with the Backdrop to demonstrate its primary usage.

Step 1: Create a .NET MAUI app.

First, create a new .NET MAUI app in Visual Studio.

Step 2: Install the NuGet packages.

Syncfusion .NET MAUI controls are available in the NuGet Gallery. To add the SfBackdropPage control to your project, open the NuGet package manager in Visual Studio, and search for Syncfusion.Maui.Backdrop, and then install it.

Step 3: Handler registration.

The Syncfusion.Maui.Core NuGet package is a dependent package for all Syncfusion .NET MAUI controls. In the MauiProgram.cs file, register the handler for the Syncfusion core package using the ConfigureSyncfusionCore() method.

Refer to the following code.

public static class MauiProgram{ public static MauiApp CreateMauiApp() { var builder = MauiApp.CreateBuilder(); builder.UseMauiApp<App>().ConfigureSyncfusionCore().ConfigureFonts(fonts =>{ fonts.AddFont("OpenSans-Regular.ttf", "OpenSansRegular"); fonts.AddFont("OpenSans-Semibold.ttf", "OpenSansSemibold");}); return builder.Build(); }}

Step 4: Initializing Backdrop

Create a page and import the SfBackdropPage XAML namespace. Refer to the following code.

<backdrop:SfBackdropPage xmlns="http://schemas.microsoft.com/dotnet/2021/maui" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" x:Class= “BackdropGettingStarted.BackdropSamplePage” Title= “Menu” xmlns:backdrop= “clr-namespace:Syncfusion.Maui.Backdrop;assembly=Syncfusion.Maui.Backdrop” IsBackLayerRevealed= “True”>

Note: The Title and ToolBarItems properties of the Page can be used to customize the appearance of the navigation bar header.

Step 5: Configure the header

The page navigation bar header for the Backdrop appears only when adding Backdrop as a child of the NavigationPage. To learn more about it, refer to the header configuration.

Step 6: Add back layer content

The back layer holds actionable content (navigation or filtration) relevant to the front layer. The back layer will either fill the entire background or occupy the background based on the content height. Add a back layer using the BackLayer property as shown in the code below.

<backdrop:SfBackdropPage.BackLayer> <backdrop:BackdropBackLayer> <Grid> <Grid.RowDefinitions> <RowDefinition Height= “Auto”/> </Grid.RowDefinitions> <ListView> <ListView.ItemsSource> <x:Array Type="{x:Type x:String}"> <x:String>Appetizers</x:String> <x:String>Soups</x:String> <x:String>Desserts</x:String> <x:String>Salads</x:String> </x:Array> </ListView.ItemsSource> </ListView> </Grid> </backdrop:BackdropBackLayer></backdrop:SfBackdropPage.BackLayer>

Step 7: Add front layer content

The front layer always appears in front of the back layer and holds primary content. Add the front layer using the FrontLayer property as shown in the code below.

<backdrop:SfBackdropPage.FrontLayer> <backdrop:BackdropFrontLayer> <Grid BackgroundColor= “WhiteSmoke”/> </backdrop:BackdropFrontLayer></backdrop:SfBackdropPage.FrontLayer>

GitHub reference

For more information, refer to the .NET MAUI Backdrop Control Getting Started demo on GitHub.

Conclusion

Thanks for reading! In this blog, we walked you through the new Syncfusion .NET MAUI Backdrop control and its features. For more information, refer to its user guide.

Leave your feedback in the comments section below.

Refer to our Release Notes and What’s New pages to check out the other updates in this release. Also, you can contact us through our support forums, support portal, or feedback portal. We are always happy to assist you!

Related blogs

• Syncfusion .NET MAUI 2023 Roadmap
• Introducing the New .NET MAUI Rating Control
• Introducing the Sixth Set of .NET MAUI Controls
• Authenticate the .NET MAUI App With Azure AD
• Agenda View in .NET MAUI Scheduler: A Perfect Tool for Modern-Day Office Management

View Details

.NET MAUI is a cross-platform framework that allows developers to create desktop and mobile applications from a single codebase with C#. In this article, we develop a simple .NET MAUI OCR scanner to scan images and convert them to PDF with searchable text using the Syncfusion OCR library.

The Syncfusion .NET Optical Character Recognition (OCR) library extracts text from scanned PDFs and images. It uses the Tesseract OCR engine. The Syncfusion OCR library does not work on mobile platforms with the Tesseract engine, so starting from version 20.3.0.47, we added support to use any external OCR service, such as Azure Cognitive Services OCR, with our existing OCR library to process OCR in mobile platforms.

Steps to build an OCR scanner application in .NET MAUI

In the following steps, we will create a .NET MAUI app, install different dependencies, and use the Syncfusion OCR library to convert an image into a readable PDF.

Step 1: Create a .NET MAUI project

Create a simple .NET MAUI project by referring to the documentation build your first .NET MAUI app.

Step 2: Install the dependencies

Install the following NuGet packages:

• Syncfusion.PDF.OCR.NET: The Syncfusion .NET OCR library.
• Microsoft.Azure.CognitiveServices.Vision.ComputerVision: This client library provides access to the Microsoft Cognitive Services ComputerVision APIs.

Step 3: Add UI elements

In this application, we get images from the user in the following ways:

• Open the camera and capture images such as receipts, notes, documents, photos, and business cards.
• Select images from the device’s photo gallery.

Open camera and capture image

Add a button in the UI to open the camera.

<Button x:Name=”CameraBtn” Text=”Open Camera” Clicked=”OnCameraClicked” HorizontalOptions=”Center” />

Use the MAUI MediaPicker API to open and capture images using the camera. The MediaPicker API needs permission to access the camera and internal storage. Refer to the get started section of the API documentation to set the permissions.

Call the CapturePhotoAsync method to open the camera and capture the image. Refer to the complete code below.

private void OnCameraClicked(object sender, EventArgs e){ TakePhoto();}//Open camera and take photopublic async void TakePhoto(){ if (MediaPicker.Default.IsCaptureSupported) { FileResult photo = await MediaPicker.Default.CapturePhotoAsync(); if (photo != null) { // Save the file into local storage. string localFilePath = Path.Combine(FileSystem.CacheDirectory, photo.FileName); //Reduce the size of the image. using Stream sourceStream = await photo.OpenReadAsync(); using SKBitmap sourceBitmap=SKBitmap.Decode(sourceStream); int height = Math.Min(794, sourceBitmap.Height); int width = Math.Min(794, sourceBitmap.Width); using SKBitmap scaledBitmap = sourceBitmap.Resize(new SKImageInfo(width, height),SKFilterQuality.Medium); using SKImage scaledImage = SKImage.FromBitmap(scaledBitmap); using (SKData data = scaledImage.Encode()) { File.WriteAllBytes(localFilePath, data.ToArray()); } //Create model and add to the collection ImageModel model = new ImageModel() { ImagePath = localFilePath, Title = "sample", Description = "Cool" }; viewModel.Items.Add(model); } }}

Select an image from the gallery

Add a button in the UI to select an image.

<Buttonx:Name="CounterBtn"Text="Select Image"Clicked="OnCounterClicked"HorizontalOptions="Center" />

Use the MAUI MediaPicker API to select images from the device’s photo gallery. Use the PickPhotoAsync method to select images from the gallery. Refer to the following code snippet.

private void OnCounterClicked(object sender, EventArgs e){ PickPhoto();}//Select images from gallery.public async void PickPhoto(){ if (MediaPicker.Default.IsCaptureSupported) { FileResult photo = await MediaPicker.Default.PickPhotoAsync(); if (photo != null) { // Save the file into local storage. string localFilePath = Path.Combine(FileSystem.CacheDirectory, photo.FileName); using Stream sourceStream = await photo.OpenReadAsync(); using FileStream localFileStream = File.OpenWrite(localFilePath); await sourceStream.CopyToAsync(localFileStream); ImageModel model = new ImageModel() { ImagePath = localFilePath, Title = "sample", Description = "Cool" }; viewModel.Items.Add(model); } }}

Once we receive the images, present those images in the UI using the CollectionView. Refer to the MAUI data templates documentation to bind the image data into the CollectionView.

Finally, convert the image to PDF with OCR, so our simple UI looks like the following picture.

Refer to the MainPage.xaml file on GitHub for the complete UI.

Step 4: Convert images to PDF with OCR text

Here, we use the Syncfusion OCR library with the external Azure OCR engine to convert images to PDF.

Please refer to this article to configure and use the Azure Computer Vision OCR services. We have already created a class named AzureOcrEngine.cs to process images. You can use this class as it is in your project without any changes. You just need to add your subscription key and endpoint in the code.

The AzureOCREngine implements the interface IOcrEngine. The IOcrEngine has a method named PerformOCR that takes an image stream as an argument. Now, call the external OCR service with the input image and it returns OCRLayoutResult as the result.

Assign AzureOCREngine as an external OCR engine using the API ExternalEngine available in the OCRProcessor class from the Syncfusion PDF OCR library.

Refer to the following code example.

public void ConvertToPDF(){ Task.Run(async () => { PdfDocument finalDcoument = new PdfDocument(); if (viewModel.Items.Count == 0) return; using (OCRProcessor processor = new OCRProcessor()) { processor.ExternalEngine = new AzureOcrEngine(); foreach (var item in viewModel.Items) { FileStream imageStream = new FileStream(item.ImagePath,FileMode.Open); PdfDocument document = processor.PerformOCR(imageStream); MemoryStream saveStream = new MemoryStream(); document.Save(saveStream); document.Close(true); PdfDocument.Merge(finalDcoument,saveStream); } } MemoryStream fileSave = new MemoryStream(); finalDcoument.Save(fileSave); fileSave.Position = 0; finalDcoument.Close(true); Dispatcher.Dispatch(() => { popup.Close(); SaveService service = new SaveService(); service.SaveAndView("Output.pdf", "application/pdf", fileSave); }); });}

After executing the above code, you will get the following output.

Note: To save the PDF document to external storage, add the platform-specific service classes. Refer to the respective classes in the following links:

• Android
• Windows
• iOS
• Mac Catalyst

GitHub sample

For more details about this project, refer to the complete .NET MAUI OCR scanner application on GitHub.

Conclusion

In this blog post, we created a simple .NET MAUI OCR scanner application to process existing images and new images captured using the camera into PDFs with machine-readable text.

Take a moment to explore the documentation, where you will find other options and features of the Syncfusion OCR library, all with accompanying code samples.

If you have any questions or comments, you can contact us through our support forums, support portal, or feedback portal. We are always happy to assist you!

Related blogs

If you liked this article, we think you would also like the following articles about our PDF Library:

• Generate Dynamic PDF Reports from an HTML Template Using C#
• Digitally Sign and Verify Signatures in PDF Files Using C#
• How to Find Corrupted PDF Files in C# Easily
• How to Convert an Image to PDF in ASP.NET Core
• Easy Ways to Redact PDFs Using C#
• 7 Ways to Compress PDF Files in C#, VB.NET

View Details

View Details

When use an Image Control… Have you ever been confused between the different values ​​of the Aspect property? You are in the right place , in this article you will learn the difference of each one!

Let’s start!

Exploring the Aspect Property

The Image control has an Aspect property  which allow us to indicate how an image will fit into the display area (scaling). This property offers different values ​​which allows us to play with the visualization.

Let’s look at each one of them:

AspectFit: Allow the entire image to fit in the display area (If necessary letterboxes the image), it takes care of adding spaces at the top and bottom or on the sides (depending on the dimensions of the image). 

AspectFill: Clips the image to fill the display area without altering the aspect ratio.

Fill: It’s responsible for stretching the image to completely fill the display area.

This stretching can distort the image.

Center: It’s responsible for centralizing the image in the display area without altering the aspect ratio.

And done!!  From now on, you are ready to play with the Image Aspect property in .NET MAUI I hope you like it!

<Label Text=”Thanks for ready! ” />

 

Spanish article:  https://es.askxammy.com/escalado-de-imagenes-en-net-maui/

View Details

View Details

Howdy! In this blog, we’ll replicate a cruise travel application UI in .NET MAUI. It is a design created by Ilham Maulana that they shared on Dribbble.

Let’s start designing the UI by dividing it into the following block structure. 

Skills that you’ll develop

In addition to strengthening your XAML skills, you will learn to implement the following .NET MAUI features in this article:

Easily build cross-platform mobile and desktop apps with the flexible and feature-rich controls of the Syncfusion .NET MAUI platform.

Explore Now

• Appearance modes: Manage the appearance of visual elements based on your UI design for both light and dark modes.
• Labels:
  • Handle different styles on the same label.
  • Add line breaks in the Text property.
• Overlapping visual elements:
  • Implement the overlay effect on visual elements based on your UI design.
• Exploration controls: Use the Syncfusion .NET MAUI ListView control to present lists of data vertically or horizontally with different layouts.

General settings for the project

Page creation

Here, we are going to design two different pages. So, I recommend creating a Views folder and, inside it creating the following pages:

• CruisePage.xaml: We will add the list of all the ships available in the app to this page.
• CruiseDetailsPage.xaml: We will add the details about a specific cruise to this page.

Appearance mode

Before you begin, note the following point about the behavior of the appearance modes: It’s not mandatory to add colors to your UI to adapt to the different appearance modes if a visual element does not have a specific value assigned in a property that receives a color. The visual element will take the default values ​​for the appearance mode in which the device is configured (i.e. light or dark).

Let’s understand this better with a use case!

Consider that if you don’t add the BackgroundColor property to your page and your device is set to dark mode, then your page’s background color will be black.

If your device is in light mode, your app will take the white background color. If you want to use a different color, then you should add the BackgroundColor property with the desired value.

Keeping this information in mind, since the CruisePage will have a different BackgroundColor for light mode, we have to add the following line of code in the ContentPage tags:

BackgroundColor="{AppThemeBinding Light=#efefef,Dark=Black}"

Step 1: Header

Every property of the Syncfusion .NET MAUI controls is completely documented to make it easy to get started.

Read Now

Main layout

Let’s start building the CruisePage.xaml page. First, add the main layout that will contain all the content from blocks one through three.

Refer to the following code example.

<ScrollView Margin="0,0,0,-30" VerticalScrollBarVisibility="Never"> <Grid ColumnDefinitions="*,Auto" RowDefinitions="Auto,Auto,Auto,Auto,Auto,Auto,Auto" Padding="25,30,0,0"> <!-- Add all the information corresponding to block 1 -- > <!-- Add all the information corresponding to block 2 -- > <!-- Add all the information corresponding to block 3 -- > </Grid></ScrollView>

We have added everything inside a ScrollView to make the page content scrollable. Additionally, we added a Grid with two columns and seven rows to organize all the page elements.

Header elements

The header is composed of the following four elements:

• Greetings
• Bell icon
• Main title
• Search bar

Let’s design them!

Syncfusion’s .NET MAUI controls suite is the expert’s choice for building modern mobile apps.

Explore Now

Greetings and a bell icon

Refer to the following code example to render the greetings and bell icon.

<!-- Greetings and bell icon--> <Label Grid.Column="0" Grid.Row="0" Text="Hi, Shalima!" FontSize="17"/> <Image Grid.Column="1" Grid.Row="0" Source="bell" HeightRequest="30" WidthRequest="30" Margin="0,0,20,0"/><!-- Add here all the information explained in the next code block -- >

Main title

Here, we are going to use the FormattedString, that allows us to add different styles to the same Label. You can see our UI title (Choose a Cruise Ship to Explore the World) has purple text in bold and also black text without bold formatting.

We will also add line breaks using the string &#10; that you can see in some text properties.

The AppThemeBinding markup extension helps us adapt to the visual characteristics for both light and dark modes. In this case, we will use it to change the text color depending on the configured appearance mode.

Note: For more details, refer to the respond to system theme changes documentation page.

<!-- Main title--> <Label Grid.Column="0" Grid.Row="1" Grid.ColumnSpan="2" FontSize="25" Margin="0,20"> <Label.FormattedText> <FormattedString> <Span Text="Choose a " TextColor="{ AppThemeBinding Light=#383838, Dark=White}"/> <Span Text="Cruise Ship&#10;" TextColor="#625ba5" FontAttributes="Bold" /> <Span Text="to " TextColor="{ AppThemeBinding Light=#383838, Dark=White}"/> <Span Text="Explore The World" TextColor="#625ba5" FontAttributes="Bold" /> </FormattedString> </Label.FormattedText> </Label><!-- Add here all the information explained in the next code block -- >

Search bar

The search bar has small gray borders by default which we don’t need for this UI. So, let’s define the borders and negative padding as shown in the following code example to remove them.

<!—Search bar--><Border Grid.Column="0" Grid.Row="2" Grid.ColumnSpan="2" Stroke="Transparent" Padding="0,-20,0,0"> <SearchBar Placeholder="Search to find a cruise ship" BackgroundColor="{ AppThemeBinding Light=#fafafa, Dark=Transparent}" PlaceholderColor="Silver" Margin="0,10,20,0"/></Border><!-- Add here all the information explained in the next code block -- >

Step 2: American ships

To design the list of American Cruise Ships, first, add the labels that contain the ship descriptions. Then, to render the list, let’s use the Syncfusion .NET MAUI ListView control by following these steps:

Note: Before starting, please refer to the .NET MAUI ListView getting started guide.

1. Add the Syncfusion.Maui.ListView NuGet package.
   

   

2. Go to the MauiProgram.cs file and register the handler for the Syncfusion .NET MAUI ListView. To do this, navigate to the CreateMauiApp method and then just before the line return builder.Build();, add the builder.ConfigureSyncfusionListView(); method. 
3. Then, add the Syncfusion.Maui.ListView namespace in your XAML file.

   xmlns:syncfusion="clr-namespace:Syncfusion.Maui.ListView;assembly=Syncfusion.Maui.ListView"

4. Now, add the following code to your XAML page.

   <!-- American Cruise Ship Descriptions--><Label Grid.Column="0" Grid.Row="3" Text="American Cruise Ships" FontSize="17" /><Label Grid.Column="1" Grid.Row="3" Text="See All" Padding="0,0,30,0" TextColor="#625ba5" HorizontalTextAlignment="End"/><!--American Cruise Ship List--><syncfusion:SfListView Grid.Column="0" Grid.Row="4" Grid.ColumnSpan="2" Margin="0,10,0,0" ItemsSource="{Binding Cruise}" ItemSize="190" ItemSpacing="5" ScrollBarVisibility="Never" HeightRequest="280" HorizontalOptions="Start" Orientation="Horizontal"> <syncfusion:SfListView.ItemTemplate> <DataTemplate> <Frame CornerRadius="10" BorderColor="Transparent" Padding="10,0,0,0" IsClippedToBounds="True" HorizontalOptions="Start" BackgroundColor="{ AppThemeBinding Light=White, Dark=#1c1c1f}"> <Grid RowDefinitions="Auto,Auto,Auto,Auto,Auto,Auto" Grid.ColumnDefinitions="Auto,*" RowSpacing="10"> <!-- Main picture--> <Image Grid.Column="0" Margin="-10,0" Grid.Row="0" Grid.ColumnSpan="2" Source="{Binding Picture}" WidthRequest="200" Aspect="AspectFill" HeightRequest="100"/> <!-- Cruise's name--> <Label Grid.Column="0" Grid.Row="1" Grid.ColumnSpan="2" Text="{Binding Name}" FontAttributes="Bold"/> <!-- Rating--> <Image Grid.Column="0" Grid.Row="2" Source="star" HeightRequest="20" WidthRequest="20" /> <Label Grid.Column="1" Grid.Row="2" Text="{Binding Rate}" Padding="5,0,0,0" TextColor="#B9B9B4"/> <!-- Location--> <Image Grid.Column="0" Grid.Row="3" Source="location" HeightRequest="20" WidthRequest="20" Aspect="AspectFill"/> <Label Grid.Column="1" Grid.Row="3" Text="{Binding Location}" Padding="5,0,0,0" TextColor="#B9B9B4"/> <!-- Starting From --> <Label Grid.Column="0" Grid.Row="4" Grid.ColumnSpan="2" Text="Starting from" FontSize="13" TextColor="#B9B9B4"/> <Label Grid.Column="0" Grid.Row="5" Grid.ColumnSpan="2" Text="{Binding StartingFrom}" FontSize="18" FontAttributes="Bold" TextColor="#7c77b4"/> </Grid> </Frame> </DataTemplate> </syncfusion:SfListView.ItemTemplate></syncfusion:SfListView><!-- Add here all the information explained in the next code block -- >

Syncfusion .NET MAUI controls are well-documented, which helps to quickly get started and migrate your Xamarin apps.

Read Now

Step 3: European Ships

To design the list of European cruise ships, we are going to use the same visual elements and steps used in the previous block.

Refer to the following code example.

<!-- European Cruise Ship Descriptions--> <Label Grid.Column="0" Grid.Row="5" Text="Europe Cruise Ship" FontSize="17"/> <Label Grid.Column="1" Grid.Row="5" Text="See All" Padding="0,0,30,0" TextColor="#625ba5" HorizontalTextAlignment="End"/> <!--European Cruise Ship List--><syncfusion:SfListView Grid.Column="0" Grid.Row="6" Grid.ColumnSpan="2" Margin="0,10,0,0" ItemsSource="{Binding EuropeCruise}" ItemSize="190" ItemSpacing="5" ScrollBarVisibility="Never" HeightRequest="280" HorizontalOptions="Start" Orientation="Horizontal"> <syncfusion:SfListView.ItemTemplate> <DataTemplate> <Frame CornerRadius="10" BorderColor="Transparent" Padding="10,0,0,0" IsClippedToBounds="True" HorizontalOptions="Start" BackgroundColor="{ AppThemeBinding Light=White, Dark=#1c1c1f}"> <Grid RowDefinitions="Auto,Auto,Auto,Auto,Auto,Auto" Grid.ColumnDefinitions="Auto,*" RowSpacing="10"> <!-- Main picture--> <Image Grid.Column="0" Margin="-10,0" Grid.Row="0" Grid.ColumnSpan="2" Source="{Binding Picture}" Aspect="AspectFill" HeightRequest="100" WidthRequest="200"/> <!-- Cruise's name--> <Label Grid.Column="0" Grid.Row="1" Grid.ColumnSpan="2" Text="{Binding Name}" FontAttributes="Bold"/> <!-- Rating--> <Image Grid.Column="0" Grid.Row="2" Source="star" HeightRequest="20" WidthRequest="20" /> <Label Grid.Column="1" Grid.Row="2" Text="{Binding Rate}" Padding="5,0,0,0" TextColor="#B9B9B4"/> <!-- Location--> <Image Grid.Column="0" Grid.Row="3" Source="location" HeightRequest="20" WidthRequest="20" Aspect="AspectFill"/> <Label Grid.Column="1" Grid.Row="3" Text="{Binding Location}" Padding="5,0,0,0" TextColor="#B9B9B4"/> <!-- Starting From --> <Label Grid.Column="0" Grid.Row="4" Grid.ColumnSpan="2" Text="Starting from" FontSize="13" TextColor="#B9B9B4"/> <Label Grid.Column="0" Grid.Row="5" Grid.ColumnSpan="2" Text="{Binding StartingFrom}" FontSize="18" FontAttributes="Bold" TextColor="#7c77b4"/> </Grid> </Frame> </DataTemplate> </syncfusion:SfListView.ItemTemplate></syncfusion:SfListView>

Step 4: Cruise’s picture

In this block, we will design the second page, the CruiseDetailsPage.xaml page, to display the details of a specific ship.

As in the first block, before starting with the code to add the image, let’s define the main layout.

Main layout

Here, we are going to define a Grid with two rows, one for the main image, and the other for the frame which contains all the remaining information of the page.

<Grid RowDefinitions="Auto,*"> <!-- Add all the information corresponding to block 4 -- > <!-- Add all the information corresponding to blocks 5 and 6 -- ></Grid>

Cruise picture

Now, add the main picture and place it in row number 0.

<Image Grid.Row="0" Source="cruise" Aspect="AspectFill" HeightRequest="350" Margin="0,-50,0,0"/><!-- Add here all the information explained in the next code block -- >

Step 5: Cruise’s description

We are going to design the cruise’s description and price blocks inside a Frame.

First, let’s see how to render the cruise’s description.

Frame and overlapping

Add a Frame and place it in row number 1. Then, add a negative margin to design the rounded edges of the Frame and overlap it on the top of the image of the previous block.

In addition, inside the Frame, add a Grid to organize the additional information. Refer to the following code example.

<Frame Grid.Row="1" CornerRadius="30" Margin="0,-30,0,0" VerticalOptions="FillAndExpand" BorderColor="Transparent"> <Grid ColumnDefinitions="*,Auto" RowDefinitions="Auto,Auto,*,Auto,Auto,Auto,Auto" Margin="0,20" RowSpacing="10" Padding="15,0"> <!-- Add all the information corresponding to blocks 5 and 6 -- > </Grid></Frame>

Cruise description

We are going to modify this block a bit from the original design by rendering the following components:

• Name
• Location
• Description

Refer to the following code example.

<!--Name--><Label Grid.Column="0" Grid.Row="0" Text="Harmony of the Seas" FontAttributes="Bold" FontSize="18" TextColor="{AppThemeBinding Light=#303030, Dark=White}"/><!-- Location--><Label Grid.Column="0" Grid.Row="1" Text="Los Angeles, USA" TextColor="#aeaeb2"/><!-- Description--><Label Grid.Column="0" Grid.Row="2" Grid.ColumnSpan="2" TextColor="#565659" LineHeight="1.5" Padding="0,0,0,20" Text="Harmony of the Seas is an Oasis-class cruise ship built by STX France at the Chantiers de l'Atlanthique shipyard in Saint-Nazaire, France. [citation needed] for Royal Caribbean International. With a gross tonnage of 226,963 GT, She is the second largest passenger ship in the world, surpassing her older sisters Oasis of the Seas."/> <!-- Add here all the information explained in the next code block -- >

Step 6: Cruise’s price

Finally, let’s develop the price block with the following elements:

• Price list
• Separator
• Book Now button

To make it easy for developers to include Syncfusion .NET MAUI controls in their projects, we have shared some working ones.

Explore Now

Price list

Refer to the following code example to design the title and description of the Cruise Ship, Price American Trip, and See All labels.

<!-- Price American Trip Description--><Label Grid.Column="0" Grid.Row="3" Text="Price American Trip" FontSize="17"/><Label Grid.Column="1" Grid.Row="3" Text="See All" TextColor="#625ba5" HorizontalTextAlignment="End"/><!-- Add here all the information explained in the next code block -- >

Now, let’s design the following components:

• Checkboxes for the options to select.
• Checkbox descriptions.
• The price and a label of other text descriptions with different formats. To design this, we’ll use FormattedText.

All of this is wrapped in the Syncfusion .NET MAUI ListView control.

<syncfusion:SfListView Grid.Column="0" Grid.Row="4" Grid.ColumnSpan="2" ItemsSource="{Binding Plan}" ScrollBarVisibility="Never" HeightRequest="85" HorizontalOptions="Start"> <syncfusion:SfListView.ItemTemplate> <DataTemplate> <Grid ColumnDefinitions="Auto,Auto,*"> <CheckBox Grid.Column="0" Color="#5b50b2" HeightRequest="20" WidthRequest="20" HorizontalOptions="Start"/> <Label Grid.Column="1" Text="{Binding Name}" VerticalTextAlignment="Center" /> <Label Grid.Column="2" HorizontalTextAlignment="End" VerticalTextAlignment="Center"> <Label.FormattedText> <FormattedString> <Span Text="{Binding Price}" TextColor="#5b50b2" FontAttributes="Bold" FontSize="25"/> <Span Text=" per trip" TextColor="#a9a9a9"/> </FormattedString> </Label.FormattedText> </Label> </Grid> </DataTemplate> </syncfusion:SfListView.ItemTemplate></syncfusion:SfListView><!-- Add here all the information explained in the next code block -- >

Separator and button

To design the separator line, we will use a BoxView, and for the booking option, we are going to add a button.

Refer to the following code example.

<!--Separator and Button--><BoxView Grid.Column="0" Grid.Row="5" Grid.ColumnSpan="2" HorizontalOptions="FillAndExpand" HeightRequest="1" Color="#d8d5d5" Margin="-35,10"/><Button Grid.Column="0" Grid.Row="6" Grid.ColumnSpan="2" BackgroundColor="#594ad5" TextColor="White" Text="Book Now" FontAttributes="Bold" HeightRequest="60" FontSize="16" CornerRadius="13"/>

That’s all! We have now finished developing our cruise travel app UI!

GitHub reference

To see the complete code structure, refer to our Cruise Travel App UI in .NET MAUI demo on GitHub.

Syncfusion .NET MAUI controls allow you to build powerful line-of-business applications.

Explore Now

Conclusion

Thanks for reading! In this blog, we saw how to replicate a cruise travel app UI using the Syncfusion .NET MAUI controls. Try out the steps in this blog post and leave your feedback in the comments section below!

Syncfusion .NET MAUI controls were built from scratch using .NET MAUI, so they feel like framework controls. They are fine-tuned to work with a huge volume of data. Use them to build elite cross-platform mobile and desktop apps!

Also, if you have any questions, you can contact us through our support forum, support portal, or feedback portal. We are always happy to assist you!

See you next time!

Related blogs

• Achieve Outlook-Like Swiping Using .NET MAUI ListView
• Replicating an Invoice Page UI in .NET MAUI
• How to Draw 2D Graphics in .NET MAUI’s GraphicsView
• 4 Impressive Features of .NET MAUI in .NET 7

View Details

In this blog, you will learn how to develop an audio recorder and player in .NET MAUI. The audio player will record and play audio files.

This application can be deployed and used on both Android and iOS.

Let’s get started!

Prerequisites

Tool: Visual Studio 2022

Supported Platform: Android and iOS

Supported OS: Android (7.0 and above) and iOS (v12 and above)

Developing audio recorder and player app

Step 1: Add required permissions in both platforms.

To record audio and save it in a device, the application will have to access the device’s audio input and storage. For that, we need to grant the following permissions:

• RECORD\_AUDIO,
• READ\_EXTERNAL\_STORAGE
• WRITE\_EXTERNAL\_STORAGE

Note: In iOS, you can’t add storage permissions. It will always return Granted when checked and requested.

In Android, add the following code to the AndroidManifest.xml file.

<uses-permission android:name="android.permission.READ\_EXTERNAL\_STORAGE" /><uses-permission android:name="android.permission.WRITE\_EXTERNAL\_STORAGE" /><uses-permission android:name="android.permission.RECORD\_AUDIO" />

In iOS, add the following code to the Info.plist file.

<key>NSMicrophoneUsageDescription</key> <string>The audio recorder app wants to use your microphone to record audio.</string>

Easily build cross-platform mobile and desktop apps with the flexible and feature-rich controls of the Syncfusion .NET MAUI platform.

Explore Now

Step 2: Create a service for recording and playing the audio.

There is no direct support for recording audio and playing it in .NET MAUI. So, we must create a service in the native platform for recording and playing the audio files.

Before creating a service class, create an interface for invoking the native methods.

Refer to the following code.

public interface IAudioPlayer{ void PlayAudio(string filePath); void Pause(); void Stop(); string GetCurrentPlayTime(); bool CheckFinishedPlayingAudio();}public interface IRecordAudio{ void StartRecord(); string StopRecord(); void PauseRecord(); void ResetRecord();}

Then, create the service to record and play audio on both platforms.

Audio recorder service for Android

Reference the following methods and properties to create an audio recorder service for Android:

• Create an instance of MediaRecorder class, which will be used to record the audio.
• SetAudioSource(): Specify which hardware device to use to capture the audio input.
• SetOutputFile(): Specify the name of the output audio file.
• Prepare(): Initialize the audio recorder.
• Start(): Start recording the audio.
• Reset(): Discard the recorded audio and resets the recorder.
• Pause(): Pause the recording in the current running position.
• Resume(): Resume recording from the paused position.
• Stop(): Stop the audio recording.

Refer to the following code.

public class RecordAudio : IRecordAudio{ #region Fields private MediaRecorder mediaRecorder; private string storagePath; private bool isRecordStarted = false; #endregion #region Methods public void StartRecord() { if (mediaRecorder == null) { SetAudioFilePath(); mediaRecorder = new MediaRecorder(); mediaRecorder.Reset(); mediaRecorder.SetAudioSource(AudioSource.Mic); mediaRecorder.SetOutputFormat(OutputFormat.AacAdts); mediaRecorder.SetAudioEncoder(AudioEncoder.Aac); mediaRecorder.SetOutputFile(storagePath); mediaRecorder.Prepare(); mediaRecorder.Start(); } else { mediaRecorder.Resume(); } isRecordStarted = true; } public void PauseRecord() { if (mediaRecorder == null) { return; } mediaRecorder.Pause(); isRecordStarted = false; } public void ResetRecord() { if (mediaRecorder != null) { mediaRecorder.Resume(); mediaRecorder.Reset(); } mediaRecorder = null; isRecordStarted = false; } public string StopRecord() { if (mediaRecorder == null) { return string.Empty; } mediaRecorder.Resume(); mediaRecorder.Stop(); mediaRecorder = null; isRecordStarted = false; return storagePath; } private void SetAudioFilePath() { string fileName = "/Record\_" + DateTime.UtcNow.ToString("ddMMM\_hhmmss") + ".mp3"; var path = Environment.GetFolderPath(System.Environment.SpecialFolder.MyDocuments); storagePath = path + fileName; Directory.CreateDirectory(path); } #endregion}

Audio recorder service for iOS

Now, we create the audio recorder service for the iOS platform using AVAudioRecorder:

• Initialize the audio session before trying to record.
• Specify the recording format and location in which to save the recording. The recording format is specified as an entry from NSDictionary with two NSObject arrays containing the keys and values of the format.
• Call the Record method when ready to initiate recording the audio.
• When finished recording, call the Stop() method on the recorder.

Refer to the following code.

public class RecordAudio : IRecordAudio{ AVAudioRecorder recorder; NSUrl url; NSError error; NSDictionary settings; string audioFilePath; public RecordAudio() { InitializeAudioSession(); } private bool InitializeAudioSession() { var audioSession = AVAudioSession.SharedInstance(); var err = audioSession.SetCategory(AVAudioSessionCategory.PlayAndRecord); if (err != null) { Console.WriteLine("audioSession: {0}", err); return false; } err = audioSession.SetActive(true); if (err != null) { Console.WriteLine("audioSession: {0}", err); return false; } return false; } public void PauseRecord() { recorder.Pause(); } public void ResetRecord() { recorder.Dispose(); recorder = null; } public void StartRecord() { if (recorder == null) { string fileName = "/Record\_" + DateTime.UtcNow.ToString("ddMMM\_hhmmss") + ".wav"; var docuFolder = Environment.GetFolderPath(Environment.SpecialFolder.MyDocuments); audioFilePath = docuFolder + fileName; url = NSUrl.FromFilename(audioFilePath); NSObject[] values = new NSObject[] { NSNumber.FromFloat(44100.0f), NSNumber.FromInt32((int)AudioToolbox.AudioFormatType.LinearPCM), NSNumber.FromInt32(2), NSNumber.FromInt32(16), NSNumber.FromBoolean(false), NSNumber.FromBoolean(false) }; NSObject[] key = new NSObject[] { AVAudioSettings.AVSampleRateKey, AVAudioSettings.AVFormatIDKey, AVAudioSettings.AVNumberOfChannelsKey, AVAudioSettings.AVLinearPCMBitDepthKey, AVAudioSettings.AVLinearPCMIsBigEndianKey, AVAudioSettings.AVLinearPCMIsFloatKey }; settings = NSDictionary.FromObjectsAndKeys(values, key); recorder = AVAudioRecorder.Create(url, new AudioSettings(settings), out error); recorder.PrepareToRecord(); recorder.Record(); } else { recorder.Record(); } } public string StopRecord() { if (recorder == null) { return string.Empty; } recorder.Stop(); recorder = null; return audioFilePath; }}

Now, let’s implement an audio player service for playing the recorded audio on both platforms.

Syncfusion’s .NET MAUI controls suite is the expert’s choice for building modern mobile apps.

Explore Now

Audio player service for Android

Follow these steps to create an audio-playing service for Android:

1. Create an instance of the MediaPlayer class to play the audio file.
2. Provide the file path of the audio file to the MediaPlayer instance through the SetDataSource method.
3. After setting the data source, prepare the media player by calling the Prepare method.
4. Once the media player is prepared, start playing the audio using the Start method.

Refer to the following code.

public class AudioPlayer : IAudioPlayer{ #region Fields private MediaPlayer \_mediaPlayer; private int currentPositionLength = 0; private bool isPrepared; private bool isCompleted; #endregion #region Methods public void PlayAudio(string filePath) { if (\_mediaPlayer != null && !\_mediaPlayer.IsPlaying) { \_mediaPlayer.SeekTo(currentPositionLength); currentPositionLength = 0; \_mediaPlayer.Start(); } else if (\_mediaPlayer == null || !\_mediaPlayer.IsPlaying) { try { isCompleted = false; \_mediaPlayer = new MediaPlayer(); \_mediaPlayer.SetDataSource(filePath); \_mediaPlayer.SetAudioStreamType(Stream.Music); \_mediaPlayer.PrepareAsync(); \_mediaPlayer.Prepared += (sender, args) => { isPrepared = true; \_mediaPlayer.Start(); }; \_mediaPlayer.Completion += (sender, args) => { isCompleted = true; }; } catch (Exception e) { \_mediaPlayer = null; } } } public void Pause() { if (\_mediaPlayer != null && \_mediaPlayer.IsPlaying) { \_mediaPlayer.Pause(); currentPositionLength = \_mediaPlayer.CurrentPosition; } } public void Stop() { if (\_mediaPlayer != null) { if (isPrepared) { \_mediaPlayer.Stop(); \_mediaPlayer.Release(); isPrepared = false; } isCompleted = false; \_mediaPlayer = null; } } public string GetCurrentPlayTime() { if (\_mediaPlayer != null) { var positionTimeSeconds = double.Parse(\_mediaPlayer.CurrentPosition.ToString()); positionTimeSeconds = positionTimeSeconds / 1000; TimeSpan currentTime = TimeSpan.FromSeconds(positionTimeSeconds); string currentPlayTime = string.Format("{0:mm\\:ss}", currentTime); return currentPlayTime; } return null; } public bool CheckFinishedPlayingAudio() { return isCompleted; } #endregion}

Audio player service for iOS

Create an audio playing service in iOS using the AVPlayer class:

1. Configure the audio file to play through the AVPlayerItem built-in class.
2. Call the Play method to start the audio playing.

Refer to the following code.

public class AudioPlayer : IAudioPlayer{ AVPlayer \_player; NSObject notificationHandle; NSUrl url; private bool isFinishedPlaying; private bool isPlaying; public bool IsPlaying { get { return isPlaying; } set { if (\_player.Rate == 1 && \_player.Error == null) isPlaying = true; else isPlaying = false; } } public AudioPlayer() { RegisterNotification(); } ~AudioPlayer() { UnregisterNotification(); } public void PlayAudio(string filePath) { isFinishedPlaying = false; if (\_player == null) { url = NSUrl.FromString(filePath); AVPlayerItem avPlayerItem = new AVPlayerItem(URL); \_player = new AVPlayer(avPlayerItem); \_player.AutomaticallyWaitsToMinimizeStalling = false; \_player.Volume = 1; \_player.Play(); IsPlaying = true; isFinishedPlaying = false; } else if (\_player != null && !IsPlaying) { \_player.Play(); IsPlaying = true; isFinishedPlaying = false; } } public void Pause() { if (\_player != null && IsPlaying) { \_player.Pause(); IsPlaying = false; } } public void Stop() { if (\_player != null) { \_player.Dispose(); IsPlaying = false; \_player = null; } } public string GetCurrentPlayTime() { if (\_player != null) { var positionTimeSeconds = \_player.CurrentTime.Seconds; TimeSpan currentTime = TimeSpan.FromSeconds(positionTimeSeconds); string currentPlayTime = string.Format("{0:mm\\:ss}", currentTime); return currentPlayTime; } return null; } public bool CheckFinishedPlayingAudio() { return isFinishedPlaying; } private void RegisterNotification() { notificationHandle = NSNotificationCenter.DefaultCenter.AddObserver(AVPlayerItem.DidPlayToEndTimeNotification, HandleNotification); } private void UnregisterNotification() { NSNotificationCenter.DefaultCenter.RemoveObserver(notificationHandle); } private void HandleNotification(NSNotification notification) { isFinishedPlaying = true; Stop(); }}

Syncfusion .NET MAUI controls are well-documented, which helps to quickly get started and migrate your Xamarin apps.

Read Now

Step 3: Creating a model.

Create a model class to show the recorded audio files in a list. Refer to the following code.

public class Audio : INotifyPropertyChanged{ #region Private private bool isPlayVisible; private bool isPauseVisible; private string currentAudioPostion; #endregion #region Constructor public Audio() { IsPlayVisible = true; } #endregion #region Properties public string AudioName { get; set; } public string AudioURL { get; set; } public string Caption { get; set; } public bool IsPlayVisible { get { return isPlayVisible; } set { isPlayVisible = value; OnPropertyChanged(); IsPauseVisble = !value; } } public bool IsPauseVisble { get { return isPauseVisible; } set { isPauseVisible = value; OnPropertyChanged(); } } public string CurrentAudioPosition { get { return currentAudioPostion; } set { if (string.IsNullOrEmpty(currentAudioPostion)) { currentAudioPostion = string.Format("{0:mm\\:ss}", new TimeSpan()); } else { currentAudioPostion = value; } OnPropertyChanged(); } } #endregion}

In the code, the CurrentAudioPosition property helps us to display the playing audio time.

Step 4: Creating the UI.

We are going to create a simple UI for showing recorded audio files and for recording audio. For this, we will be using Syncfusion’s ListView for .NET MAUI. Install the .NET MAUI ListView NuGet package, and then include it in the application.

The following XAML code will display the recorded audio in Syncfusion’s .NET MAUI ListView control.

<syncfusion:SfListView x:Name="AudioList" Grid.Row="0" Grid.ColumnSpan="2" Margin="0,8" IsVisible="true" ItemsSource="{Binding Audios}" SelectionMode="None"> <syncfusion:SfListView.ItemTemplate> <DataTemplate> <ViewCell> <Grid x:Name="PlayAudioGrid" Margin="0,4,0,12" BackgroundColor="Transparent" HeightRequest="60"> <Grid.ColumnDefinitions> <ColumnDefinition Width="50" /> <ColumnDefinition Width="*" /> <ColumnDefinition Width="50" /> <ColumnDefinition Width="80" /> </Grid.ColumnDefinitions> <Button Grid.Column="0" Padding="0" BackgroundColor="Transparent" Command="{Binding Path=BindingContext.PlayAudioCommand, Source={x:Reference mainPage}}" CommandParameter="{Binding .}" FontFamily="AudioIconFonts" FontSize="22" IsVisible="{Binding IsPlayVisible}" Text="&#xea15;" TextColor="Black" /> <Button Grid.Column="0" Padding="0" BackgroundColor="Transparent" BorderColor="LightGray" Command="{Binding Path=BindingContext.PauseAudioCommand, Source={x:Reference mainPage}}" CommandParameter="{Binding .}" FontFamily="AudioIconFonts" FontSize="22" IsVisible="{Binding IsPauseVisble}" Text="&#xea16;" TextColor="Black" /> <Label Grid.Column="1" FontSize="14" Text="{Binding AudioName}" TextColor="Black" VerticalTextAlignment="Center" /> <Label Grid.Column="2" Margin="0,0,12,0" FontSize="14" IsVisible="{Binding IsPauseVisble}" Text="{Binding CurrentAudioPosition}" TextColor="Black" VerticalTextAlignment="Center" /> <Button Grid.Column="3" BackgroundColor="Transparent" Command="{Binding Path=BindingContext.DeleteCommand, Source={x:Reference mainPage}}" CommandParameter="{Binding}" FontFamily="AudioIconFonts" FontSize="20" Text="&#xe9ac" TextColor="Red" /> </Grid> </ViewCell> </DataTemplate> </syncfusion:SfListView.ItemTemplate></syncfusion:SfListView>

Every property of the Syncfusion .NET MAUI controls is completely documented to make it easy to get started.

Read Now

The following XAML code is used to design the UI for recording audio.

<!-- Timer Label --><StackLayout Grid.Row="2" Grid.ColumnSpan="2" Margin="0,0,0,32" VerticalOptions="End"> <Label FontSize="14" HorizontalTextAlignment="Center" IsVisible="{Binding IsRecordingAudio}" Text="Recording…" TextColor="#7D898F" /> <Label FontSize="60" HorizontalTextAlignment="Center" IsVisible="{Binding IsRecordingAudio}" Text="{Binding TimerLabel}" TextColor="Black" /></StackLayout> <!-- Button Setup --><Grid Grid.Row="3" Grid.ColumnSpan="2" ColumnSpacing="60"> <Grid.ColumnDefinitions> <ColumnDefinition Width="*" /> <ColumnDefinition Width="*" /> <ColumnDefinition Width="*" /> </Grid.ColumnDefinitions> <!-- Retry --> <Grid Grid.Column="0" RowDefinitions="auto,auto"> <Button Grid.Row="0" BackgroundColor="LightGray" BorderColor="#5F49FF" BorderWidth="1" Command="{Binding ResetCommand}" CornerRadius="25" FontFamily="AudioIconFonts" FontSize="22" HeightRequest="50" IsEnabled="{Binding IsRecordingAudio}" Text="&#xe900;" TextColor="#5F49FF" WidthRequest="50"> <Button.Triggers> <DataTrigger Binding="{Binding IsRecordingAudio}" TargetType="Button" Value="False"> <Setter Property="TextColor" Value="Gray" /> <Setter Property="BorderColor" Value="Gray" /> </DataTrigger> </Button.Triggers> </Button> <Label Grid.Row="1" HorizontalOptions="Center" Text="Retry" /> </Grid> <!-- Play --> <Grid Grid.Column="1" HorizontalOptions="CenterAndExpand" RowDefinitions="auto,auto"> <!-- Record Button --> <Button Grid.Row="0" BackgroundColor="Red" BorderColor="Red" BorderWidth="1" Command="{Binding RecordCommand}" CornerRadius="25" FontFamily="AudioIconFonts" FontSize="22" HeightRequest="50" IsVisible="{Binding IsRecordButtonVisible}" Text="&#xe91e;" TextColor="White" WidthRequest="50" /> <Label Grid.Row="1" HorizontalOptions="Center" IsVisible="{Binding IsRecordButtonVisible}" Text="Record" /> <!-- Pause Button --> <Button Grid.Row="0" BackgroundColor="Green" BorderColor="Green" BorderWidth="1" Command="{Binding PauseCommand}" CornerRadius="25" FontFamily="AudioIconFonts" FontSize="22" HeightRequest="50" IsVisible="{Binding IsPauseButtonVisible}" Text="&#xea1d;" TextColor="White" WidthRequest="50" /> <Label Grid.Row="1" HorizontalOptions="Center" IsVisible="{Binding IsPauseButtonVisible}" Text="Pause" /> <!-- Resume Button --> <Button Grid.Row="0" BackgroundColor="Red" BorderColor="Red" BorderWidth="1" Command="{Binding RecordCommand}" CornerRadius="25" FontFamily="AudioIconFonts" FontSize="22" HeightRequest="50" IsVisible="{Binding IsResumeButtonVisible}" Text="&#xea1c;" TextColor="White" WidthRequest="50" /> <Label Grid.Row="1" HorizontalOptions="Center" IsVisible="{Binding IsResumeButtonVisible}" Text="Resume" /> </Grid> <!-- Stop --> <Grid Grid.Column="2" RowDefinitions="auto,auto"> <Button Grid.Row="0" BackgroundColor="LightGray" BorderColor="#5F49FF" BorderWidth="1" Command="{Binding StopCommand}" CornerRadius="25" FontFamily="AudioIconFonts" FontSize="22" HeightRequest="50" IsEnabled="{Binding IsRecordingAudio}" Text="&#xea1e;" TextColor="#5F49FF" WidthRequest="50"> <Button.Triggers> <DataTrigger Binding="{Binding IsRecordingAudio}" TargetType="Button" Value="False"> <Setter Property="TextColor" Value="Gray" /> <Setter Property="BorderColor" Value="Gray" /> </DataTrigger> </Button.Triggers> </Button> <Label Grid.Row="1" HorizontalOptions="Center" Text="Stop" /> </Grid></Grid>

Step 5: Register dependency injection to access the objects in the constructor.

Dependency injection is a way in which an object (client) receives other objects (services) that depend on it. To learn more about using dependency injection in .NET MAUI, refer to the blog Learn How to Use Dependency Injection in .NET MAUI.

Refer to the following code to register the dependency injection services. First, we must add the necessary services. Then, we can directly access the objects in the desired class constructors. Therefore, we can access the AudioPlayerService and RecordAudioService objects in the ViewModel.

public static MauiApp CreateMauiApp(){ var builder = MauiApp.CreateBuilder(); builder .UseMauiApp<App>() .ConfigureFonts(fonts => { fonts.AddFont("OpenSans-Regular.ttf", "OpenSansRegular"); fonts.AddFont("OpenSans-Semibold.ttf", "OpenSansSemibold"); fonts.AddFont("AudioIconFonts.ttf", "AudioIconFonts"); }); #if ANDROID || IOS builder.Services.AddTransient<IAudioPlayerService, AudioPlayerService>(); builder.Services.AddTransient<IRecordAudioService, RecordAudioService>(); #endif builder.Services.AddTransient<MainPage>(); builder.Services.AddTransient<AppShell>(); builder.ConfigureSyncfusionListView(); return builder.Build();}

To make it easy for developers to include Syncfusion .NET MAUI controls in their projects, we have shared some working ones.

Explore Now

Step 6: Creating a ViewModel.

We have followed the MVVM (model-view-viewmodel) structure to develop this application. So, we need to create a ViewModel (MainPageViewModel.cs) file for recording and playing audio. In the ViewModel, we generate an audio collection to bind the data for recorded audio.

Properties in ViewModel class

• recordTime, playTimer: The timer properties used in the UI when we play or record an audio.
• IsRecordingAudio: Controls the visibility of the reset and stop options.
• IsPauseButtonVisible: Controls the visibility of the Pause button in the UI.
• IsRecordButtonVisible: Controls the visibility of the Record button.
• IsResumeButtonVisible: Controls the visibility of the Resume button.
• audios: The collection of all the recorded audio files to be displayed in a list view.
• recordAudioService, audioPlayerService: These interface properties invoke the native platform-specific code.

The following code examples demonstrate the audio recorder.

Use the following code to initiate the recorder. We must invoke the dependency service method recordAudio.StartRecord() to start the recorder.

Note: Only if the permissions are granted can we start the recorder.

private async void StartRecording(){ if (!IsRecordingAudio) { var permissionStatus = await RequestandCheckPermission(); if (permissionStatus == PermissionStatus.Granted) { IsRecordingAudio = true; IsPauseButtonVisible = true; recordAudio.StartRecord(); IsRecordButtonVisible = false; isRecord = true; timerValue = new TimeSpan(0, 0, -1); recordTimer.Start(); } else { IsRecordingAudio = false; IsPauseButtonVisible = false; } } else { ResumeRecording(); }}

Pause the recorder using the recordAudio.PauseRecord() platform-specific method.

private void PauseRecording(){ isRecord = false; IsPauseButtonVisible = false; IsResumeButtonVisible = true; recordAudio.PauseRecord();}

The following method is used to continue the recording from a paused position.

private void ResumeRecording(){ recordAudio.StartRecord(); IsResumeButtonVisible = false; IsPauseButtonVisible = true; isRecord = true;}

Use the following code to reset the recorder and start it from the initial position. Use the platform-specific code recordAudio.ResetRecord() to reset the recorder.

private void ResetRecording(){ recordAudio.ResetRecord(); timerValue = new TimeSpan(); TimerLabel = string.Format("{0:mm\\:ss}", timerValue); IsRecordingAudio = false; IsPauseButtonVisible = false; IsResumeButtonVisible = false; StartRecording();}

To stop the recorder, use the platform-specific code recordAudio.StopRecord().

private async void StopRecording(){ IsPauseButtonVisible = false; IsResumeButtonVisible = false; IsRecordingAudio = false; IsRecordButtonVisible = true; timerValue = new TimeSpan(); recordTimer.Stop(); RecentAudioFilePath = recordAudio.StopRecord(); await App.Current.MainPage.DisplayAlert("Alert", "Audio has been recorded", "Ok"); TimerLabel = string.Format("{0:mm\\:ss}", timerValue); SendRecording();}private void SendRecording(){ Audio recordedFile = new Audio() { AudioURL = RecentAudioFilePath }; if (recordedFile != null) { recordedFile.AudioName = Path.GetFileName(RecentAudioFilePath); Audios.Insert(0, recordedFile); }}

The following code is used to get permission to record

public async Task<PermissionStatus> RequestandCheckPermission(){ PermissionStatus status = await Permissions.CheckStatusAsync<Permissions.StorageWrite>(); if (status != PermissionStatus.Granted) await Permissions.RequestAsync<Permissions.StorageWrite>(); status = await Permissions.CheckStatusAsync<Permissions.Microphone>(); if (status != PermissionStatus.Granted) await Permissions.RequestAsync<Permissions.Microphone>(); PermissionStatus storagePermission = await Permissions.CheckStatusAsync<Permissions.StorageWrite>(); PermissionStatus microPhonePermission = await Permissions.CheckStatusAsync<Permissions.Microphone>(); if (storagePermission == PermissionStatus.Granted && microPhonePermission == PermissionStatus.Granted) { return PermissionStatus.Granted; } return PermissionStatus.Denied;}

The following code examples demonstrate the audio player.

We invoke the platform-specific method audioPlayer.PlayAudio(audioFilePath) to play the audio.

private void StartPlayingAudio(object obj){ if (audioFile != null && audioFile != (Audio)obj) { AudioFile.IsPlayVisible = true; StopAudio(); } if (obj is Audio) { audioFile = (Audio)obj; audioFile.IsPlayVisible = false; string audioFilePath = AudioFile.AudioURL; audioPlayer.PlayAudio(audioFilePath); SetCurrentAudioPosition(); }}

Use the following method to pause the audio using the platform-specific method audioPlayer.Pause().

private void PauseAudio(object obj){ if (obj is Audio) { var audiophile = (Audio)obj; audioFile.IsPlayVisible = true; audioPlayer.Pause(); }}

Using the method audioPlayer.Stop() to stop the audio in the following code.

public void StopAudio(){ if (AudioFile != null) { audioPlayer.Stop(); playTimer.Stop(); }}

Syncfusion .NET MAUI controls allow you to build powerful line-of-business applications.

Explore Now

Use the following code to get the current position of the audio and display it in the UI.

private void SetCurrentAudioPosition(){ playTimer.Interval = new TimeSpan(0, 0, 0, 0, 250); playTimer.Tick += (s, e) => { if (AudioFile != null) { AudioFile.CurrentAudioPosition = audioPlayer.GetCurrentPlayTime(); bool isAudioCompleted = audioPlayer.CheckFinishedPlayingAudio(); if (isAudioCompleted) { AudioFile.IsPlayVisible = true; playTimer.Stop(); } } }; playTimer.Start();}

Output

The following is a screenshot of the application.

Resources

For more details, refer to the GitHub project .NET MAUI Audio Recorder and Player.

Conclusion

I hope you now have a clear idea of how to develop a .NET MAUI application to record and play audio files in your Android and iOS phones. Try the project sample and share your feedback in the comments section below.

Syncfusion’s .NET MAUI controls were built from scratch using .NET MAUI, so they feel like framework controls. They are fine-tuned to work with a huge volume of data. Use them to build better cross-platform mobile and desktop apps!

For current customers, the new Essential Studio version is available for download from the License and Downloads page. If you are not yet a Syncfusion customer, you can always download our free evaluation to see all our controls in action.

For questions, you can contact us through our support forum, support portal, or feedback portal. We are always happy to assist you!

Reference

1. Android:
   • Android Audio
2. iOS:
   • AVAudioPlayer Class
   • AVAudioRecorder Class

Related blogs

• Syncfusion .NET MAUI 2023 Roadmap
• Authenticate the .NET MAUI App with Azure AD
• Introducing the Sixth Set of .NET MAUI Controls
• Create Project Planning and Resource Management Calendar in .NET MAUI

View Details

In Essential Studio 2022 Volume 4, we have added one more data visualization tool to the Syncfusion .NET MAUI suite, the Pyramid Charts.

The new .NET MAUI Pyramid Charts is a powerful data visualization tool. It allows developers to concisely show hierarchical relationships among data. It is an excellent choice for displaying data hierarchies, such as showing the division of a total into its parts or visualizing the composition of a population.

In this blog, we will explore the features of the new .NET MAUI Pyramid Charts and the steps to get started with it.

Features of .NET MAUI Pyramid Charts

Data labels

You can display data labels with various placement options in the Pyramid Charts. Place the data labels inside or outside of the pyramid segments. This makes it easy to focus on the significant information and quickly identify the breakdown.

In space-constrained scenarios, the data labels smartly align themselves based on the available space, thus improving the user experience and readability.

Tooltip

Use the tooltip feature to display more information about data points while hovering over them. By default, the tooltip displays the value (y–value) of each segment of the pyramid.

With the help of the TooltipTemplate support, we can customize tooltips to show different information using any .NET MAUI view control. 

Legend

Render a legend next to your Pyramid Charts. By default, the legend items will appear with the names of the pyramid segments. You can customize the legend with any .NET MAUI view control using the ItemTemplate support.

Note: Refer to the .NET MAUI Pyramid Charts documentation to know its other available features.

Getting started with .NET MAUI Pyramid Charts

This section explains the steps to getting started with the new .NET MAUI Pyramid Charts and populating it with data.

Step #1: First, create a simple .NET MAUI project.

Step #2: The Syncfusion .NET MAUI controls are available on the NuGet Gallery. To add the SfPyramidChart to your project, open the NuGet package manager in Visual Studio. Search for Syncfusion.Maui.Charts and then install it.

Step #3: Then, register the handler for Syncfusion core in the MauiProgram.cs file. Refer to the following code.

public static class MauiProgram{ public static MauiApp CreateMauiApp() { var builder = MauiApp.CreateBuilder(); builder .UseMauiApp<App>() .ConfigureSyncfusionCore() .ConfigureFonts(fonts => { fonts.AddFont("OpenSans-Regular.ttf", "OpenSansRegular"); fonts.AddFont("OpenSans-Semibold.ttf", "OpenSansSemibold"); }); builder.ConfigureSampleBrowserBase(); return builder.Build(); }}

Step #4: Next, import the Syncfusion.Maui.Charts namespace on your XAML page.

xmlns:chart= “clr-namespace:Syncfusion.Maui.Charts;assembly=Syncfusion.Maui.Charts”

Step #5: Initialize an empty Pyramid Charts control like in the following code.

<chart:SfPyramidChart/>

Step #6: Create a business model to populate items in the Pyramid Charts. This includes the creation of the example ChartDataModel class and ChartViewModel with the list of data objects.

public class ChartDataModel{ public string ProgressName { get; set; } public double Value { get; set; } }public class ChartViewModel{ public ObservableCollection<ChartDataModel> Data { get; set; } public ChartViewModel() { Data = new ObservableCollection<ChartDataModel> { new ChartDataModel("Retail",14), new ChartDataModel("Manufacturing",14.25), new ChartDataModel("Marketing",17.82), new ChartDataModel("Shipping",22.51), new ChartDataModel("R&D",28.71) }; }}

Step #7: Finally, set the BindingContext to the ChartViewModel. Bind the data to the Pyramid Charts’ ItemsSource property. Then, bind the ProgressName and Value properties with the XBindingPath, and YBindingPath properties, respectively.

Refer to the following code example.

<chart:SfPyramidChart ItemsSource="{Binding Data}" XBindingPath="ProgressName" YBindingPath="Value"> <chart:SfPyramidChart.BindingContext> <local:ChartViewModel/> </chart:SfPyramidChart.BindingContext></chart:SfPyramidChart>

After executing these code samples, we will get output like the following image.

Conclusion

Thanks for reading! In this blog, we have seen the features of the new .NET MAUI Pyramid Charts, rolled out in the 2022 Volume 4 release.  Try out this stunning data visualization control and leave your feedback in the comment section below!

Check out our Release Notes and the What’s New pages to see the other updates in this release.

For questions, you can reach us through our support forums, support portal, or feedback portal. We are always happy to assist you!

Related blogs

• Syncfusion Essential Studio 2022 Volume 4 Is Here!
• Introducing the Sixth Set of .NET MAUI Controls
• Introducing the New .NET MAUI Rating Control
• Syncfusion .NET MAUI 2023 Roadmap

View Details

View Details

In the world of app development, it’s important to stay on top of the latest tools and technologies available. One of these is .NET MAUI (Multi-platform App UI), a cross-platform desktop and mobile application framework native to C# and XAML that enables developers to build apps for iOS, Android, macOS, and Windows from C# code shared.

If you are a beginner and interested in learning .NET MAUI in this new year 2023, you are at the right place. In this article, we will present you with a complete guide to learn .NET MAUI from scratch. From available learning options to required background knowledge and online resources, we’ll give you everything you need to get started with .NET MAUI and build your first apps.

So without further ado, let’s get started!

Learn .NET MAUI the best way

What is .NET MAUI

.NET MAUI (Multi-platform App UI) is a cross-platform desktop and mobile application framework native to C# and XAML that enables developers to build apps for iOS, Android, macOS, and Windows from shared C# code. If you are a beginner and interested in learning .NET MAUI in this new year of 2023, it is important to have a clear understanding of what it is and how it works.

.NET MAUI was announced at the .NET Conf 2020 event as the next generation of Xamarin.Forms, and that it is available from the beginning of 2022. Although it is only a year in the making, there are already many resources online that will help you to get ready.

Learning options

There are several options available to learn .NET MAUI in this new year 2023. One of them is the .NET Beginners series offered on Learn TV. In this series, you’ll get a thorough introduction to building apps with .NET MAUI. The episodes are broadcast live and are presented by experts, so it’s a great opportunity to learn something new and do it alongside others.

Another option is to visit the .NET MAUI Learn page on the Microsoft website. On this page, you’ll find an introductory video that will give you an overview of what .NET MAUI is and how it works. In addition, there are several guides and tutorials available to help you get started with .NET MAUI and build your first applications.

Finally, you can also follow the tutorials provided by Microsoft on their learning website. One of these tutorials shows you how to run your first .NET MAUI app on Windows. The tutorial includes detailed instructions and screenshots that walk you through the process step by step.

Necessary previous knowledge

Before you start learning .NET MAUI, it’s important to have some background knowledge. This includes a basic understanding of programming and programming languages, such as C# or XAML. If you don’t have previous programming experience, it’s a good idea to take a basic programming course or tutorial before starting to work with .NET MAUI.

In addition to programming, it’s also helpful to have a basic understanding of user interface (UI) design and experience working with graphic design tools, such as Adobe Photoshop or Illustrator. This will help you design and build apps that are visually appealing and easy to use.

Online Resources and Tutorials

.NET MAUI is now available, and there are many resources and tutorials online to help you prepare for its release. Some of these resources include:

• The .NET MAUI Learn page on the Microsoft website, which includes tutorials, guides, and documentation on working with .NET MAUI.
• The online .NET community, which offers forums and discussion groups where you can interact with other developers and get help and support.
• YouTube’s channels and developer blogs, which offer video tutorials and guides on working with .NET MAUI.
• .NET MAUI e-books and print books, which provide detailed information and step-by-step tutorials on working with the framework.

Here are some links that might be of interest:

1. The .NET MAUI learn page on the Microsoft website:
   https://dotnet.microsoft.com/en-us/learn/maui
2. The .NET MAUI documentation on the Microsoft developer page:
   https://docs.microsoft.com/en-us/dotnet/maui/
3. The Microsoft Visual Studio YouTube channel, which includes tutorials and videos on .NET MAUI:
   https://www.youtube.com/user/VisualStudio
4. The .NET Developer’s Blog, including posts and tutorials on .NET MAUI:
   https://devblogs.microsoft.com/dotnet/
5. The .NET online community, which offers forums and discussion groups where you can interact with other developers and get help and support:
   https://community.dot.net/

Practice and patience

As with any new skill, learning .NET MAUI will take time and practice. Don’t expect to master the framework right away, and don’t be discouraged if you run into obstacles or get frustrated at any point. Patience and persistence are key to success.

In addition to practice, it’s important to keep up to date with the latest trends and developments in the world of .NET MAUI. This includes reading technology blogs and magazines, attending conferences and workshops, and joining online developer communities. This will help you keep abreast of the latest developments and keep you motivated to continue learning.

Resume

In summary, learning .NET MAUI in this new year 2023 is a great opportunity to develop your skills as a programmer and create amazing applications for multiple platforms. With a combination of learning options, background knowledge, online resources, and practice, you can be on your way to success in the world of .NET MAUI.

I hope this article has helped you understand how to learn .NET MAUI and how to make the most of this framework to build cross-platform applications. Feel free to put what you’ve learned into practice and share your achievements with us in the .NET community!

Good luck learning .NET MAUI!

The post Learn .NET MAUI: Beginner’s Guide appeared first on Luis Matos.

View Details

En el mundo del desarrollo de aplicaciones, es importante estar al tanto de las últimas herramientas y tecnologías disponibles. Una de ellas es .NET MAUI (Multi-platform App UI), un marco de aplicaciones móviles y de escritorio multiplataforma nativas con C# y XAML que permite a los desarrolladores crear aplicaciones para iOS, Android, macOS y Windows a partir de un código C# compartido.

Si eres un principiante y estás interesado en aprender .NET MAUI en este nuevo año 2023, estás en el lugar correcto. En este artículo, te presentaremos una guía completa para aprender .NET MAUI desde cero. Desde las opciones de aprendizaje disponibles hasta los conocimientos previos necesarios y los recursos en línea, te daremos todo lo que necesitas para empezar a trabajar con .NET MAUI y crear tus primeras aplicaciones. ¡Así que sin más preámbulos, vamos a comenzar!

Aprende .NET MAUI de la mejor manera

Qué es .NET MAUI

.NET MAUI (Multi-platform App UI) es un marco de aplicaciones móviles y de escritorio multiplataforma nativas con C# y XAML que permite a los desarrolladores crear aplicaciones para iOS, Android, macOS y Windows a partir de un código C# compartido. Si eres un principiante y estás interesado en aprender .NET MAUI en este nuevo año 2023, es importante tener una comprensión clara de lo que es y cómo funciona.

.NET MAUI fue anunciado en el evento .NET Conf 2020 como la próxima generación de Xamarin.Forms, y que está disponible desde principios de 2022. Aunque solo tiene un año en curso, ya se pueden encontrar muchos recursos en línea que te ayudarán a prepararte.

Opciones de aprendizaje

Hay varias opciones disponibles para aprender .NET MAUI en este nuevo año 2023. Una de ellas es la serie de principiantes de .NET que se ofrece en Learn TV. En esta serie, obtendrás una introducción completa a la compilación de aplicaciones con .NET MAUI. Los capítulos se transmiten en vivo y están presentados por expertos, por lo que es una oportunidad excelente para aprender algo nuevo y hacerlo junto a otros.

Otra opción es visitar la página de aprendizaje de .NET MAUI en el sitio web de Microsoft. En esta página, encontrarás un vídeo introductorio que te dará una idea general de lo que es .NET MAUI y cómo funciona. Además, hay varias guías y tutoriales disponibles que te ayudarán a empezar a trabajar con .NET MAUI y a crear tus primeras aplicaciones.

Finalmente, también puedes seguir los tutoriales proporcionados por Microsoft en su sitio web de aprendizaje. Uno de estos tutoriales te muestra cómo ejecutar tu primera aplicación .NET MAUI en Windows. El tutorial incluye instrucciones detalladas y capturas de pantalla que te guían a través del proceso paso a paso.

Conocimientos previos necesarios

Antes de comenzar a aprender .NET MAUI, es importante tener ciertos conocimientos previos. Esto incluye una comprensión básica de programación y lenguajes de programación, como C# o XAML. Si no tienes experiencia previa en programación, es recomendable tomar un curso o tutorial básico de programación antes de comenzar a trabajar con .NET MAUI.

Además de la programación, también es útil tener conocimientos básicos de diseño de interfaz de usuario (UI) y experiencia trabajando con herramientas de diseño gráfico, como Adobe Photoshop o Illustrator. Esto te ayudará a diseñar y crear aplicaciones visualmente atractivas y fáciles de usar.

Recursos y tutoriales en línea

.NET MAUI ya está disponible, y hay muchos recursos y tutoriales en línea que te ayudarán a prepararte para su lanzamiento. Algunos de estos recursos incluyen:

• La página de aprendizaje de .NET MAUI en el sitio web de Microsoft, que incluye tutoriales, guías y documentación sobre cómo trabajar con .NET MAUI.
• La comunidad en línea de .NET, que ofrece foros y grupos de discusión donde puedes interactuar con otros desarrolladores y obtener ayuda y soporte.
• Los canales de YouTube y los blogs de desarrolladores, que ofrecen tutoriales y guías en video sobre cómo trabajar con .NET MAUI.
• Los libros electrónicos y los libros impresos sobre .NET MAUI, que ofrecen información detallada y tutoriales paso a paso sobre cómo trabajar con el marco.

Aquí hay algunos enlaces que podrían ser de interés:

1. La página de aprendizaje de .NET MAUI en el sitio web de Microsoft: https://dotnet.microsoft.com/en-us/learn/maui
2. La documentación de .NET MAUI en la página de desarrolladores de Microsoft: https://docs.microsoft.com/en-us/dotnet/maui/
3. El canal de YouTube de Microsoft Visual Studio, que incluye tutoriales y videos sobre .NET MAUI: https://www.youtube.com/user/VisualStudio
4. El blog de desarrolladores de .NET, que incluye publicaciones y tutoriales sobre .NET MAUI: https://devblogs.microsoft.com/dotnet/
5. La comunidad en línea de .NET, que ofrece foros y grupos de discusión donde puedes interactuar con otros desarrolladores y obtener ayuda y soporte: https://community.dot.net/

Práctica y paciencia

Como con cualquier habilidad nueva, aprender .NET MAUI llevará tiempo y práctica. No esperes dominar el marco de inmediato, y no te desanimes si encuentras obstáculos o te sientes frustrado en algún momento. La paciencia y la persistencia son clave para el éxito.

Además de la práctica, es importante mantenerse actualizado con las últimas tendencias y desarrollos en el mundo de .NET MAUI. Esto incluye leer blogs y revistas de tecnología, asistir a conferencias y talleres, y unirse a comunidades en línea de desarrolladores. Esto te ayudará a mantenerte al tanto de las últimas novedades y te mantendrá motivado a seguir aprendiendo.

Resumen

En resumen, aprender .NET MAUI en este nuevo año 2023 es una gran oportunidad para desarrollar tus habilidades como programador y crear aplicaciones increíbles para múltiples plataformas. Con una combinación de opciones de aprendizaje, conocimientos previos, recursos en línea y práctica, puedes estar en el camino hacia el éxito en el mundo de .NET MAUI.

Espero que este artículo te haya ayudado a entender cómo aprender .NET MAUI y cómo aprovechar al máximo este marco para crear aplicaciones multiplataforma. ¡No dudes en poner en práctica lo que has aprendido y compartir tus logros con nosotros en la comunidad de .NET!

¡Buena suerte en tu aprendizaje con .NET MAUI!

The post Aprende .NET MAUI: Guía para principiantes appeared first on Luis Matos.

View Details

A text input layout control was one of the most-requested controls by our mobile app developers. We understand the requirement for this essential control and have now delivered the .NET MAUI Text Input Layout control in our 2022 Volume 4 release.

This control can be used to build UIs that require user input. It allows users to add floating labels, password toggle icons, leading and trailing icons, and assistive labels such as error messages and help text on top of the input controls. These features help improve the interface’s usability and make it easier for users to enter and submit information.

In this article, we will see the key features of the new .NET MAUI Text Input Layout and the steps to get started with it.

Key features

The .NET MAUI Text Input Layout supports numerous user-friendly features. Some of them are listed here.

• Supported input controls
• Container types
• Supported states
• Toggling password visibility
• Floating labels and hints
• Helper text
• Error text
• Leading and trailing icons

Supported input controls

The .NET MAUI Text Input Layout control can enhance the appearance and functionality of the Syncfusion Autocomplete or ComboBox controls, and the Microsoft Entry and Editor controls in the .NET MAUI framework.

By wrapping these input views with the Text Input Layout, you can easily add assistive labels and icons to improve your app’s usability and visual appeal.

Container types

The .NET MAUI Text Input Layout supports the following container types:

• Filled: The background of the input view will fill with the container color, and the baseline stroke and thickness will change based on the state of the input view.
• Outlined: The container will be framed with a rounded border.
• None: The container will have an empty background and space around it.

Supported states

The .NET MAUI Text Input Layout supports the focused, unfocused, error, and disabled visual states.

Toggling password visibility

You can enable the password toggle icon to show or hide a password interactively.

Floating labels and hints

Use the hint text feature to add placeholder text to the input view. This hint text will be displayed in the middle of the input view and will move to the top to become a floating label when the input field becomes active. This can help save space and avoid the need for additional titles.

Helper text

In addition to the hint text, the Text Input Layout control also provides a helper text feature. It allows you to display additional information about the text that is expected to be entered. This can be useful for giving instructions or examples to help users understand how to correctly enter details in the input field.

Error text

Use the error text feature to display error messages that assist users in solving validation errors. This can improve the usability of your app by providing clear feedback to users when there are problems with their input.

Leading and trailing icons

You can use leading icons to indicate the expected input type, such as a birth date, phone number, or password. These can help users understand the purpose of the input field and easily enter the appropriate information.

Trailing icons, on the other hand, can be used for various purposes, such as adding a clear button, error icon, voice input icon, or drop-down icon. These can improve the functionality of the input view and make it easier for users to interact with it.

Note: For more details, refer to the .NET MAUI Text Input Layout documentation.

Getting started with the .NET MAUI Text Input Layout control

We have seen the key features of the .NET MAUI Text Input Layout (SfTextInputLayout). Let’s see how to configure it with a floating label.

Step 1: First, create a .NET MAUI application.

Step 2: The Syncfusion .NET MAUI controls are available on NuGet Gallery. To add the .NET MAUI Text Input Layout control to your project, open the NuGet package manager in Visual Studio. Search for Syncfusion.Maui.Core and then install it.

Step 3: Now, register the handler for the Syncfusion core in the MauiProgram.cs file.

using Microsoft.Maui;using Microsoft.Maui.Hosting;using Microsoft.Maui.Controls.Compatibility;using Microsoft.Maui.Controls.Hosting;using Microsoft.Maui.Controls.Xaml;using Syncfusion.Maui.Core.Hosting;namespace TextInputLayoutSample{ public static class MauiProgram {public static MauiApp CreateMauiApp(){var builder = MauiApp.CreateBuilder();builder.UseMauiApp<App>().ConfigureSyncfusionCore().ConfigureFonts(fonts =>{ fonts.AddFont("OpenSans-Regular.ttf", "OpenSansRegular");});return builder.Build(); } }}

Step 3: Add Syncfusion.Maui.Core namespace in your XAML page.

xmlns:inputLayout="clr-namespace:Syncfusion.Maui.Core;assembly=Syncfusion.Maui.Core"

Step 4:Then, add any input view control such as Entry, Editor, Autocomplete, or ComboBox to the Text Input Layout.

<inputLayout:SfTextInputLayout> <Entry /></inputLayout:SfTextInputLayout>

Step 5: Now, we can add the floating label for the Text Input Layout by setting the Hint property with the text you want to display as the label. You can also control the visibility of the hint by setting the ShowHint property as true or false. By default, it’s set to true to display the floating label.

Refer to the following code example.

<inputLayout:SfTextInputLayout Hint=”First Name”> <Entry Text = “Selva Ganapathy Kathiresan”/></inputLayout:SfTextInputLayout>

Conclusion

Thanks for reading! In this blog, we’ve seen the features of the new .NET MAUI Text Input Layout control rolled out in the 2022 Volume 4 release. Information about our other new controls and features is available in our Release Notes and What’s New pages. Try them out and leave your feedback in the comments section below!

Download Essential Studio for .NET MAUI to start evaluating them immediately.

If you have any questions or need further assistance, please don’t hesitate to contact us through our support forum, support portal, or feedback portal. We are always happy to help you!

Related blogs

• Authenticate a .NET MAUI App with Azure AD
• Agenda View in .NET MAUI Scheduler: A Perfect Tool For Modern-Day Office Management
• Achieve Outlook-like Swiping Using .NET MAUI Listview
• Replicating an Invoice Page UI in .NET MAUI
• How to Draw 2D Graphics in .NET MAUI’s GraphicsView

View Details

When developing your desktop applications in .NET MAUI, you can control both the size and position of your application windows. In this article you will learn how to do it very quickly!

Let’s start!

Preparing the stage

First of all, you have to override the CreateWindows Method which allow you to handle the Window’s settings. Go to your App.xam.cs and add it! To overwrite it faster, apply the following steps:

Type “override Create” and press Enter or Tab button twice.

This will complete the base structure of the method.

Next, let’s access the window information using a variable, as shown in the following code:

Sizing your Windows

You already have the stage prepared, now you only have to add the properties. To modify the size of your window, you only have to access the Width and Height properties, as I show you below:

We also have properties that help us control the minimum or maximum values ​​of the width or height of the screen which are the following:

MaximumHeight and MaximumWidth: Sets the maximum value that the screen can reach in width or height respectively. (Receives a double as value)

MinimumHeight and MinimumWidth: Sets the minimum value that the screen can reach in width or height respectively. (Receives a double as value)

Positioning your Windows

Finally, to position your Windows you can access the X and Y properties as follows:

Limitations

Mac Catalyst does not support resizing or repositioning windows using the above.

And done!!  From now on, you are ready to play with the size and position of your application windows in .NET MAUI! I hope you liked it!

<Label Text=”Thanks for ready! ” />

.

Spanish article:  https://es.askxammy.com/manejo-de-tamano-y-posicion-de-ventanas-en-net-maui/

View Details

A project planning calendar for resource scheduling is an effective project management tool. It makes it easier to plan, track, update, and collaborate on project tasks with your team. The Syncfusion .NET MAUI Scheduler control allows you to create a real-time project planning and resource management calendar by using the resource view feature in timeline views.

In this blog, I’ll explain how to create a calendar for planning employees’ tasks using the Scheduler’s timeline month view.

Note: If you are new to using our .NET MAUI Scheduler control, please read the Getting Started with .NET MAUI Scheduler documentation before proceeding further.

Designing the calendar for each resource

Create a calendar for each employee to schedule and manage their tasks in one place. The Scheduler resources feature can be used to manage tasks that the project team is planning to work on in the timeline day, timeline week, timeline workweek, and timeline month views.

Refer to the following code to initialize the scheduler timeline month view.

xmlns:schedule="clr-namespace:Syncfusion.Maui.Scheduler;assembly=Syncfusion.Maui.Scheduler" <schedule:SfScheduler x:Name="Scheduler" View="TimelineMonth"/>

Create an employee model

It’s very simple to add a resource view to the Scheduler control. You can create any kind of object and bind it in the Resources property of SchedulerResourceView class.