The binding conventions in Caliburn.Micro can be extended to do almost anything you want. The method ConventionManager.AddElementConvention<T> returns a ElementConvention which can be further customised. In this post I’ll show what things we can do with this by modifying the ElementConvention.ApplyBinding action.
Really proud to say that I’ll be speaking in August at NDC Sydney on Techniques in creating great cross platform apps.. This talk will be a spiritual successor to last years talk where I’ll cover some of the newer code sharing options in Visual Studio 2017 and expanding on the ideas of the view model composition that Caliburn.Micro supports.
Previously I’ve talked about Supporting Xamarin.Forms Tabbed Page in Caliburn.Micro using conductors and Caliburns excellent view location features. I’d like to now show how we can do the same with the MasterDetailPage.
In the last couple of days I’ve put together and published a roadmap for Caliburn.Micro, there’s a couple of reasons for this. The first is help me plan what I want to do and what will be needed, the second to let people know what to expect in the future (although I deliberately didn’t attach dates to anything).
One of the best features of Caliburn.Micro in my opinion is get away from “one view model per screen” and starting to compose view models together to form the screen.