Focused And Slim
SCENE XXIII
The home on the internets of one J. Sedlak.
Enter John “Quiet Before Focused” Sedlak.
John. One piece of functionality I consistently find myself writing and rewriting is the implementation of the INotifyPropertyChanged interface. This class, located in the main FGF library, makes that rewriting unnecessary by implementing it in an open way.
Share the goods.
John. As you no doubt saw in the writing of the Application class, FGF implements its own version of the XNA Framework’s component classes. The first major reason for doing so is that the builtin component classes require you to pass in a (Framework) Game object through the constructor. […] The second major reason for my implementation is that by controlling the interfaces and base classes, I can easily support more advanced situations such as the separation between initialization and content loading/unloading.
Introduce the modules.
Move on and Collect with events.
John. For most purposes, the builtin collection classes supplied by the .NET Framework are terrific. They are simple and straight forward implementations that do exactly as you expect. But for our purposes, a collection class that fires events when the collection is changed is simply better and in some cases, necessary.
Explain the code.
Exit.
SCENE XXIV
A well-known space of venting.
Enter Promit “Slim And Tuned” Roy.
Promit. I’ve been doing some work on SlimTune quietly, and now it’s to the point that I have to decide what the next phase of things should be. There are essentially three major groups of work to tackle: UI improvements, memory profiling, and instrumentation.
Explain the UI improvements.
Promit. I’m hoping that with the next release branch, 0.2.x, users will enjoy a much better overall experience.
Exeunt.
