In the MVVM (Model, View, ViewModel) pattern in xaml based applications (Windows Phone 7, Silverlight and WPF) there are two different ways a view model will notify the view of changes. If you’re unaware of the differences you can end up wondering why your changes aren’t being reflected in your view.
The eventing mechanisms in .NET are great for being notified when certain things occur, but often you don’t care about every occurrence just the next one, really what you’re wanting is a callback. The most common scenario I’ve encountered for this during my development on the Windows Phone 7 is wanting to execute code after an animation is complete and by extension when an animation part of a visual state is complete.
For a limited time I’ve dropped the price of To Do Today for Windows Phone 7 to $0.99 as part of a pricing experiment.
One of the controls I felt was missing out of the box for the Windows Phone 7 was a Notification control similar to how Toast notifications are displayed. As part of an application I’m working on I need a control like this with some of the animation effects the toast has.
An avid reader of startup blogs I’ve always enjoyed reading about the companies that are completely transparent about their numbers, how the company is going and the history for those numbers. There are some great lessons that can be learned from other companies when they do this. So I thought I’d do the same for the first three months of my first app To Do Today.