Milestone 4 Tasking (for 4/4/03)

UI Group:

All completion dates are by 4/4/2003 unless otherwise noted

1. Renderer (TJ and Kijana )
   1. Able to see full mall with stores being added as clients log on
   2. Get double buffering working so the flicker is gone
   3. Make animation smoother
      
2. Remove the code that uses remoting lib and implement networking hub (Brian and Jeff )
   
3. Debug some nasty exceptions (Brian and Jeff )
   1. Weird GDI exception
   2. Out of memory exception
      
4. Mock up GUI for pocket pc! (Jeff and Kijana )
   
5. Get mall adapter from model group to further populate rest of tabs (Kijana and Jeff )
   
6. Implement Code Review suggestions (all )
   
7. Work with model group to get factories ready for next milestone (all )
   
8. Work with AR group to get pocket pc web services ready for next milestone (all )

Model Group:

• Clean up code as per suggestions from review.  Remove old code and rename everything to remove “MS3…” names.
  
• Figure out how factories will work – look into reporting lists of builders available, and clean them up to a point where they are ready to integrate with the UI in the next milestone.
  
• Implement the new networking model – give the existing level of functionality while using the new framework.
  
• Start building actual attributes and behaviors.  (Design behaviors that will be used in our final code – make people do interesting things)
  
• Build a Mall adapter that gives the UI the functionality it needs (in the same way that we have space adapters currently)
  

Ryan – Factories and code clean-up.
Bryan – Mall Adapter.
Jim – Networking
Ali, Gilbert – Attributes/Behaviors

AR Group:

Justin & Robby:

•  Look through MS.NET remoting documentation for all possible
     exceptions and catch them where possible in the NetHub
  
•  Reorganize current NetHub exceptions into a heirarchical structure
  
•  Create new, specific exceptions where necessary and throw them when
     appropriate in the NetHub code to signal a specific problem
  
•  Determine final feasibility of "closing" remoting connections and
     services; deprecate if determined to be impossible.
  

Will & Theo:

•  Analyze Model/UI code and develop a strategy for making the necessary
     information available to PocketPC clients -- keeping in mind that
     remoting is not supported on the compact framework, meaning that all
     data will probably need to be polled through a WebMethod hosted on
     Exciton or another server.
  
•  Make recommendations to the Model/UI groups on what abstractions or
     separations of code are required for the above.
  
•  Make sure that all resources necessary for implementing WebMethods are
     installed and available on Exciton.