- what objects will you have, what they will do (their methods), what data they will contain (their properties) and how they will interact with other objects or be used in the grand scheme of things
- usually helps to think of how you can break down the problem into objects first… before going into their methods and properties… just think about what this object’s main purpose is
- an object should be good at doing one thing… dealing with taht type of object… you dont’ want an object that just does everything
- you want to have everything that method does “encapsulated” in the object, meaning that only it knows how to do things best… everything else that uses it is only concerned with “hey, i want this done, go do it” and it will do it and no one else has to care how it’s doing it
- if you can, it’s good to think about the different layers of the app… you’ve got the GUI side, then you have the Data side, then you’ll need somethign that controls everything…. this is the typical way of doing apps — it’s called the MVC pattern (model view controller)
- MVC
This entry was posted
on Tuesday, October 2nd, 2007 at 12:00 pm and is filed under Uncategorized.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.