Adding platform specific magic to cross-platform Xamarin Forms apps
Download as PPTX, PDF0 likes57 views
The document appears to be technical in nature, discussing the implementation of a custom entry renderer in Xamarin.Forms. It references a user or contributor associated with a series of links and documentation related to Xamarin.Forms. The focus seems to be on using attributes to customize rendering behavior for a specific entry component.
![@JimBobBennett aka.ms/
[assembly: ExportRenderer(typeof(Entry),
typeof(MyEntryRenderer))
]](https://image.slidesharecdn.com/xamarinplatformspecifics-181004102609/85/Adding-platform-specific-magic-to-cross-platform-Xamarin-Forms-apps-18-320.jpg)
![@JimBobBennett aka.ms/
[assembly: ExportRenderer(typeof(Entry),
typeof(MyEntryRenderer))
]
public class MyEntryRenderer : EntryRenderer
{
…
}](https://image.slidesharecdn.com/xamarinplatformspecifics-181004102609/85/Adding-platform-specific-magic-to-cross-platform-Xamarin-Forms-apps-19-320.jpg)
Adding platform specific magic to cross-platform Xamarin Forms apps
- 19. @JimBobBennett aka.ms/ [assembly: ExportRenderer(typeof(Entry), typeof(MyEntryRenderer)) ] public class MyEntryRenderer : EntryRenderer { … }
Editor's Notes
- #3: Write once, run everywhere - iOS, Android, UWP, WPF, macOS, Linux, Tizen, Native UI To most Forms IS Xamarin Fast to market - EROAD Inspect
- #8: To make Forms work on all platforms means it’s a lowest common denominator model Only features that work on all platforms are available Simplicity was key as well, so only the basics were ported
- #9: Beautiful design - part of it is good typography. Designers love fonts and want different weights all over the place Not easy in Forms
- #11: Problem - designer wants light fonts. How can we do this?
- #12: Look at two ways to do it - effects, custom renderers Only going to cover iOS and Android, but principles apply to all platforms
- #13: Effects - lightweight ways to manipulate underlying controls Attach to a control to allow you to tweak the underlying control
- #14: Forms - wraps native controls in Forms controls Put an entry on the screen, on iOS you get a UITextField, Android gives an EditText Effects attach to these controls Effects are NOT control specific - can attach to any control
- #15: Demo on for iOS and Android Effect for font
- #16: Two parts - platform effect for the platform, routing effect in core project Effects have an Id with a two part key - resolution group name and effect name Platform specific - resolution group name registered in assembly as first part of key Effect exported by name Allows multiple effect NuGets with same effect name to not clash. Effects can be read off control to evaluate properties
- #17: All forms controls use renderers to convert from Forms to Native These renderers are open, so you can tweak to suit, or write your own
- #18: All forms controls use renderers to convert from Forms to Native These renderers are open, so you can tweak to suit, or write your own
- #19: ExportRenderer tells Xamarin Forms which renderer to use for a control
- #20: You can export your own renderers to ‘override’ the default from Xamarin Forms Own renderers derived from the Xamarin ones with customizations
- #21: Demo on for iOS and Android Renderer Renderer has control and element - native control and Forms element
- #22: Effects when you want to tweak certain controls only, and want to add effects to multiple types Renderers for tweaking all controls of one type