Design Approach to the Interfaces
In following the XP methodology for keeping the design simple, there are several approaches to take; however, I wonder how many of those are really worth it. For instance, I could implement a CAB solution, but the learning curve, along with the time frame to create the application, wouldn't seem to be a worthy approach, or one that is the simplest design, no matter how functional it may be. I could create an extensive object model; I will be creating some objects, but I refrain from that when possible, because of the complexity and sheer volume of work involved.
With that said, the environment that I am working in handles some of those features. For instance, the list view handles sorting, which implements one of my features for me, although I do have sorting implemented in my collection and tested. But the key is what to weigh as important, and what not to undertake, especially to work in your iterative time periods.
But you have to wonder about the delicate balance between complexity and ease of development. For intance, and object model is more complicated, but may be easier to work with in the long run. Is it work an iteration cycle? Surely, a future refactoring cycle or release could add this, but at what cost to the application, and would it be worth it then? I often have these "philosophical" questions running through my head.
I'm going to use simple designs, as well as avoid a complex object model for now, building on it as I go. I'm going to try to keep it the simplest way possible, but that is usually inevitable, as being 10,000 ways to do things, you're bound to find a way simpler. The goal I hope to achieve is to keep it less complicated than it needs to be, to increase readability and achieve simplicity, which I hope I can do. You'll be able to tell me as I go.