Snack Pack | The New Xamarin Android Device Manager
Play Extending Xamarin.Forms with Behaviors with Matthew Soucoup
Description
This week, James is joined yet again by friend of the show Matthew Soucoup, who shows us how to extend the built-in capabilities of any View in Xamarin.Forms with little gems of awesomeness known as Behaviors. Matt demonstrates what a Behavior is, and how these reusable classes can expand the Xamarin.Forms controls functionality without having to subclass controls or modify the code-behind files.
Show Links:
- Code used in show
- Documentation: Xamarin.Forms Behaviors
- Reusable Command to Action Behavior
- Find James on: Twitter, GitHub, Blog, and his weekly development podcast Merge Conflict.
- Follow @JamesMontemagno
- Never Miss an Episode: Follow @TheXamarinShow
- Find Matt on Twitter, GitHub, and his Blog
Download
More episodes in this series
Custom Vision – Machine Learning Made Easy with Jim Bennett
Related episodes
XAML Hot Reload for Xamarin.Forms In-Depth | The Xamarin Show
XAML Hot Reload for Xamarin.Forms Preview
Pretty XAML With XAML Styler | The Xamarin Show
Xamarin.Forms 101: Dynamic Resources
Xamarin.Forms 101: Application Resources
Xamarin.Forms 101: Control Reference Binding (View-to-View)
Xamarin.Forms 101: Command Parameters
FlexLayout for Xamarin.Forms Explained
Xamarin.Forms 3.1 & Platform Specifics for Tuning the UI
Using Lottie for Beautiful Animations with Matt Soucoup
The Discussion
-
Me Ask You You beard makes you look like Yusuf Islam. No pun intended.
-
CodeGrue How do Behaviors differ from Effects? They seem very similar.
-
MattSoucoup @CodeGrue:They are very similar, both used to add additional features!
You generally use an Effect for a small styling/UI change to a control. And the change you want to make has to be done in a platform specific way.
Behaviors on the other hand are extending the functionality of the control - like adding validation. And the functionality that you're adding does not need to tap into anything platform specific.
Quick way to keep them straight ... Effects=UI ... Behaviors=Functionality.