Main Page | Namespace List | Class Hierarchy | Compound List | File List | Namespace Members | Compound Members | File Members | Related Pages

Todo List

Member CComponent::set_absolute_pos (const CPoint &pos)
This method should only be called by a parent on its child! This should really be a protected member, but it won't work when a derived class calls a protected member on a different object of the same base class.

Member CComponent::set_parent (CComponent *n_parent)
See if we can make this protected? Has the same problem as the CComponent::set_absolute_pos() method.

Member CDebug::log_error (const char *err_msg, int fatal=0)
Make this method throw an exception someday.

Member Testing::CFPSGraphicalObserver::do_handle_event (CEvent &event)
Very bad smell here. Even if we made the activation key a parameter, what if we wanted to toggle the visibility every time the user clicked the mouse? This is very good motivation for decoupling the view and controller parts of CComponent.

Member CGame::do_draw (CSurface &surface, CRect &rect)
Remove this method eventually; if the client wants a background color, they can just add a screen-sized CColoredPanel to the back of the CGame panel.

Member CGame::get_font_large ()
This doesn't belong here. Implement a flyweight-pool based singleton as a resource manager or something.

Member CGame::tickables
Encapsulate this as a private member...?

Class CIterator< T >
The STL already defines iterators that are more robust and convenient than this interface; I've implemented them here for the sake of the final project, but if I continue to work on this framework outside of class, I should remove this class and just use the STL iterators.

Member CPanel::~CPanel ()
Currently, this destructor does nothing. Should we destroy our children here?

Namespace TempGameConstants
Remove this namespace eventually.

Generated on Wed Aug 27 11:59:27 2003 for GFW by doxygen 1.3.3