Redeveloping my Word Tutor spelling application using .Net Core 3.0.
Redeveloping my Word Tutor spelling application using .Net Core 3.0.
Saturday, March 02 2019
wordtutor-redux
csharp
Let’s try an experiment - taking many of the things I’ve been blogging about over the past few years and applying them to the design and build of an actual application, with the source code published step by step.
Saturday, March 09 2019
wordtutor-redux
csharp
To begin our little project, we need to create our initial project structure. Once that’s in place, we can create the first class from our application model - VocabularyWord.
Saturday, March 16 2019
wordtutor-redux
csharp
After creating VocabularyWord last time, our next step is to create VocabularySet, a container for many words.
Saturday, March 23 2019
wordtutor-redux
csharp
Now that we have both VocabularyWord and ‘VocabularySet`, we can turn our attention to defining application model itself, allowing us to capture the overall state of the entire application.
Saturday, March 30 2019
wordtutor-redux
csharp
Before we get much further in this project, we should set up command line builds while things are still simple. It’s easier to enhance the builds step by step as required than to configure a complex build system in one go.
Saturday, April 06 2019
wordtutor-redux
csharp
At the core of the Redux design pattern is the store, a central place for storing the current state of the application. There’s only ever one store for the entire application. Changes in state are made by dispatching messages to the store that are processed by a reducer.
Saturday, April 13 2019
wordtutor-redux
csharp
I’ve long been a fan of static analysis tools. They can act as a co-pilot, keeping an eye on things while you work, helping you to catch common types of problems. Let’s add (and tune!) some tools.
Saturday, April 20 2019
wordtutor-redux
csharp
Before we can start adding screens to our application, we need to set up some infrastructure for our WPF specific classes. In order to keep the WordTutor.Core technology independent, we’ll do this by creating a new project.
Saturday, May 04 2019
wordtutor-redux
csharp
Let’s look at the first of the screens we need to build for our application - the Add Word screen, used (surprisingly enough) to add a new word to the list of words we’re currently viewing.
Saturday, May 11 2019
wordtutor-redux
csharp
With the add vocabulary word screen that we defined last time, we can now look at the implementation of the related view model.
Saturday, May 25 2019
wordtutor-redux
csharp
Leveraging the add vocabulary word view model from last time, we now turn our attention to creating the associated view. Once we have that, we can wire everything up into a working WPF application.
Saturday, June 08 2019
wordtutor-redux
csharp
First light is the term used for the first time that an observation is made through a new telescope (or other astronomical instrument). Lets get our application up and running.
Saturday, June 15 2019
wordtutor-redux
csharp
When I went to write the code for our next view model (VocabularyBrowserViewModel), I ran into some problems with our original ViewModelBase. Let’s visit those problems and look at how they can be resolved.
Saturday, June 29 2019
wordtutor-redux
csharp
For our second screen, we’ll create a browser to show all of the words in a single vocabulary list. Let’s start with a small bit of design, so we know what we’re aiming to build.
Saturday, July 13 2019
wordtutor-redux
csharp
When I got to this point of the series, I expected to be writing about some interaction testing - checking that our messages triggered the right transitions between screens.
Saturday, July 20 2019
wordtutor-redux
csharp
testing
In addition to the unit tests we’re already writing for each of our core classes, we should also write some integration tests to ensure our types interact properly.
Saturday, July 27 2019
wordtutor-redux
csharp
To this point, we’ve been able to run each of our screens by hand-coding the necessary object initialization. We could continue this as we move forward, but the complexity would grow with each additional screen we complete. Instead, let’s take the time to configure a dependency injection framework that will take care of the complexity for us.
Saturday, August 10 2019
wordtutor-redux
csharp
Based on the foundation from last time, we can now turn our attention to our view-models. How can we use our dependency injection framework to construct each view model on demand?
Saturday, August 17 2019
wordtutor-redux
csharp
We saw last time that setting up dependency injection for our viewmodels involved a small number of moving parts. The same applies when applying dependency injection to our views, but with a few additional complexities.
Sunday, August 25 2019
wordtutor-redux
csharp
One of the problems we currently have is caused by lack of updates - our application model can change without our view-models being notified that the change has happened, leaving our user interface showing stale information. To solve this, we’ll extend our Redux store with subscriptions, to allow each view-models to be proactively notified when things change.
Saturday, August 31 2019
wordtutor-redux
csharp
Now that our Redux store supports subscriptions, we can register to update our existing view models, allowing them to automatically stay current as our application state changes. The changes to each will be similar, but with a few variations on the common theme.
Saturday, September 14 2019
wordtutor-redux
csharp
With subscriptions wired up to keep our view models updated, we can run our application and start clicking around. When we select a word, we can trace through the flow of messages to see how everything updates. But, it’s easy to crash. Let’s debug that crash and work out how to make the application more robust.
Saturday, September 21 2019
wordtutor-redux
csharp
Up until this point, we’ve relied exclusively on data-binding for the link between our view-models and our views. While data-binding handles a lot of scenarios well, it doesn’t support buttons, menu items and so on.
Saturday, September 28 2019
wordtutor-redux
csharp
It’s been a big week of releases in the world of .NET with the release of both .NET Core 3.0 and C# 8. Let’s upgrade the Wordtutor projects to all the latest versions and see what we learn.
Saturday, October 12 2019
wordtutor-redux
csharp
Continuing our the upgrade process from last time, in this post we’ll explore the changes required to our WordTutor.Desktop project.
Saturday, October 19 2019
wordtutor-redux
csharp
Continuing on the theme from our past two posts, we’ll address the remaining issues related to nullable types, as well as taming the rest of our current storm of compiler warnings.
Saturday, October 26 2019
wordtutor-redux
csharp
Here’s an odd warning that came up when I was working on last weeks Code Gardening post:
Saturday, November 09 2019
wordtutor-redux
csharp
The existing model class ModifyVocabularyWordScreen only handles the creation of a new word. We need to modify it to support the modification of an existing word as well.
Saturday, November 16 2019
wordtutor-redux
csharp
If you’ve tried out our application as it stood after last week’s post, you may have noticed that the user experience for modifying a word is a bit suboptimal. After selecting a word, you have to separately press the Modify button. Can we do better?
Saturday, November 30 2019
wordtutor-redux
csharp
testing
The Redux architecture we’re using for our application state relies on all our state objects being properly immutable. So far, we’ve relied on nothing more than self-discipline to ensure no mistakes are made. By adding some convention testing to our project, we can enlist some help in avoiding common errors.
Saturday, December 14 2019
wordtutor-redux
csharp
testing
Following on from our previous post on convention testing we can extend the conventions by considering the standards we want to follow when we write methods on our immutable types.