You get a lot of quality with the command pattern (though it can come at the cost of some code that looks like it should be wizard-generated). This provides you with the common architecture you need to create a command (see #2). There needs to be a common, clearly-defined coupling between your visual state and your application state. What is important is that your software recognizes the difference between its current state and the displayed state, and decouples appropriately. The first key isn't so much the religious or pattern-zealot implementation of your high-level architecture. There are a few fundamental patterns that you'll want to take advantage of: Trying to add it to an existing project can be very expensive if it wasn't designed with this capability in mind. The important thing is that you start designing it in early in the project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |