{"id":38181,"date":"2018-10-18T15:06:38","date_gmt":"2018-10-18T19:06:38","guid":{"rendered":"https:\/\/blog.xamarin.com\/?p=38181"},"modified":"2019-03-25T13:58:36","modified_gmt":"2019-03-25T21:58:36","slug":"xamarin-forms-3-3-0-little-things-huge-difference","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/xamarin\/xamarin-forms-3-3-0-little-things-huge-difference\/","title":{"rendered":"Xamarin.Forms 3.3.0: Little Things, Huge Difference"},"content":{"rendered":"

The Xamarin.Forms team has been working closely with our open-source community to help fill in the \u201clittle things\u201d. Things you\u2019ve told us are important to building your mobile apps and being supremely productive in the process. Since Xamarin.Forms 3.0 shipped at Build 2018, we have been collaborating with you to deliver over 20 new features and fixes. With many more on the roadmap<\/a>!<\/p>\n

The three most often used controls in mobile applications are buttons, images, and labels. They are just about everywhere! It\u2019s no wonder we shipped the Android Fast Renderers<\/a> for those back in 2.4.0 with the main focus being on improved layout performance. Which is why that Label continues to get a lot of focus in this Xamarin.Forms 3 series of \u201clittle things\u201d enhancements. In this post, we\u2019ll highlight those updates, give you a taste of what\u2019s happening for Android image performance, and show you how to update your WebView \u202ffor optimal performance on iOS.<\/p>\n

More Label Love<\/h2>\n

In the past few releases of Xamarin.Forms, Labels have been getting some serious upgrades thanks to community contributions that added bindings and gestures to spans. Now, thanks to Alan Grgic\u2019s<\/a> contribution, you can easily add text decorations such as underline and strike-through. Combine everything together, and you\u2019ve got the coveted inline hyperlink!<\/p>\n

<Label>\r\n    <Label.FormattedText>\r\n        <FormattedString>\r\n            <FormattedString.Spans>\r\n                <Span Text=\"This app is written in C#, XAML, and native APIs using the\" \/>\r\n                <Span Text=\" \" \/>\r\n                <Span Text=\"Xamarin Platform\" FontAttributes=\"Bold\" TextColor=\"Blue\" TextDecorations=\"Underline\">\r\n                    <Span.GestureRecognizers>\r\n                       <TapGestureRecognizer \r\n                            Command=\"{Binding TapCommand, Mode=OneWay}\"\r\n                            CommandParameter=\"https:\/\/docs.microsoft.com\/en-us\/xamarin\/xamarin-forms\/\"\/>\r\n                     <\/Span.GestureRecognizers>\r\n                <\/Span>\r\n                <Span Text=\".\" \/>\r\n            <\/FormattedString.Spans>\r\n        <\/FormattedString>\r\n    <\/Label.FormattedText>\r\n<\/Label><\/pre>\n
\"\"<\/a><\/p>\n
That\u2019s not all. Gerald Versluis<\/a> has contributed the ability to set the maximum number of lines you wish a label to render. This is super useful for doing things such as displaying a few lines and adding a \u201cread more\u201d to expand the full text.<\/p>\n
<Label x:Name=\"TruncatedLabel\" \r\n    MaxLines=\"4\" \r\n    LineBreakMode=\"TailTruncation\" \r\n    Text=\"You should see 4 lines of text and truncation at the end. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Etiam mattis quam non enim pellentesque, ut placerat purus finibus. Nulla quis tincidunt ante. Ut mauris lectus, aliquam a sagittis vitae, consequat eget elit. Interdum et malesuada fames ac ante ipsum primis in faucibus. Pellentesque convallis nunc nisi, a imperdiet elit efficitur et. Duis in lectus mollis, interdum ipsum et, tincidunt orci. Fusce ipsum metus, imperdiet non lacus vitae, facilisis feugiat magna. Nulla volutpat nisl tortor, a consectetur felis consectetur non. Curabitur in enim vulputate sem volutpat bibendum id nec lorem. Mauris laoreet lacus ac volutpat tempus.\"\/>\r\n<Button x:Name=\"ReadButton\" \r\n    Text=\"[read more]\" \r\n    Clicked=\"Button_Clicked\" \/><\/pre>\n
\"\"<\/a><\/span><\/span><\/p>\n
 <\/p>\n
Android Image Performance and Memory Boost<\/h2>\n
To better support future efforts of image handling, we have introduced the new IImageViewHandler<\/span>\u00a0. You can combine this new interface with the Android Glide library made available as GlideX for Xamarin.Forms<\/a> by our own Jonathan Peppers. And we have the performance benchmarks to tell the real story!<\/p>\n
Below you can check the memory allocation results between a default Xamarin.Forms app and a Xamarin.Forms app that leverages the GlideX library.<\/p>\n
\n\n\n\n\n\n\n\n\n\n\n\n
\n
Page<\/b><\/span><\/span><\/div>\n<\/td>\n
\n
Loaded by<\/b><\/span><\/span><\/div>\n<\/td>\n
\n
Peak Memory Usage (bytes)<\/b><\/span><\/span><\/div>\n<\/td>\n<\/tr>\n
\n
GridPage<\/span><\/div>\n<\/td>\n
\n
Xamarin.Forms<\/span><\/div>\n<\/td>\n
\n
268,387,112<\/span><\/div>\n<\/td>\n<\/tr>\n
\n
GridPage<\/span><\/div>\n<\/td>\n
\n
glidex.forms<\/span><\/div>\n<\/td>\n
\n
16,484,584<\/span><\/div>\n<\/td>\n<\/tr>\n
\n
ViewCellPage<\/span><\/div>\n<\/td>\n
\n
Xamarin.Forms<\/span><\/div>\n<\/td>\n
\n
94,412,136<\/span><\/div>\n<\/td>\n<\/tr>\n
\n
ViewCellPage<\/span><\/div>\n<\/td>\n
\n
glidex.forms<\/span><\/div>\n<\/td>\n
\n
12,698,112<\/span><\/div>\n<\/td>\n<\/tr>\n
\n
ImageCellPage<\/span><\/div>\n<\/td>\n
\n
Xamarin.Forms<\/span><\/div>\n<\/td>\n
\n
24,413,600<\/span><\/div>\n<\/td>\n<\/tr>\n
\n
ImageCellPage<\/span><\/div>\n<\/td>\n
\n
glidex.forms<\/span><\/div>\n<\/td>\n
\n
9,977,272<\/span><\/div>\n<\/td>\n<\/tr>\n
\n
HugeImagePage<\/span><\/div>\n<\/td>\n
\n
Xamarin.Forms<\/span><\/div>\n<\/td>\n
\n
267,309,792<\/span><\/div>\n<\/td>\n<\/tr>\n
\n
HugeImagePage<\/span><\/div>\n<\/td>\n
\n
glidex.forms<\/span><\/div>\n<\/td>\n
\n
9,943,184<\/span><\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
We look forward to bringing additional performance improvements to images in Xamarin.Forms. The Team is actively investigating more tightly integrating GlideX so you can get the best performance experience by default.<\/p>\n
WebView Updated for iOS<\/h2>\n
iOS has used the UIWebView<\/span>\u00a0for displaying a web browser control since iOS 2, and it provides Xamarin.Forms with the best backward compatibility when you use the WebView control. With iOS 8.0, Apple introduced WKWebView<\/span>, and this is now available as an option for you when using in Xamarin.Forms 3.3.0. WKWebView<\/span>\u00a0 runs Safari in a separate process and provides better performance, especially when you need to execute JavaScript.<\/p>\n
To use the WKWebView<\/span>\u00a0 instead of the UIWebView<\/span>\u00a0 you have to add this directive to your AssemblyInfo.cs:<\/p>\n
[assembly: ExportRenderer(typeof(WebView), typeof(WKWebViewRenderer))]<\/pre>\n
Get Started Today!<\/h2>\n
Check the full release notes<\/a> for all the details, and we would encourage you to explore the documentation. Xamarin.Forms 3.3.0 includes more than 30 bug fixes and ships just 30 days after 3.2.0 meaning you don\u2019t have to wait long to benefit from all those quality improvements.<\/p>\n
This update is now available on NuGet and via your Visual Studio package manager:<\/p>\n