3460:4/521 Introduction to Object-Oriented Programming Fall 2009

To keep track of changes to Apprise, the best way is to view the Timeline, which gives a quick summary. Unfortunately, it doesn't show when comments were added to tickets.

I had Chuck turn on the email notifications. If you create a ticket, you will get an email notification of it. If you would like to be notified when a ticket changes, put your account name in the "Cc:" field. If there are other names, put a comma between your names and the others. Whenever the ticket is modified or commented on, you will receive an email notification.

If it is a major issue, feel free to put my uanetid (collard) in the Cc: field. I will probably notice the issue faster. In the worst case, I can remove my email from the ticket.

By default, the email will be sent to uanetid@zips.uakron.edu. If you need to change this (like I did), then there is an email that you can specify in trac on the Preferences page.

In general, the use of path names in the filename for an include file is not a good idea:

#include "/home/collard/MyClass.hpp" - Evil, won't build on other people's machine

#include "C:/collard/MyClass.hpp" - Also evil

#include "../ProjectBase/MyClass.hpp" - Not evil

#include "MyClass.hpp" - Good, let build/compiler specify directory

Since some people are having a build issue, we will accept "Not evil". In other words, relative paths are permissible.

In general, we have a pretty open system here in terms of contributions and changes, etc. But there are some situations that which need some oversight to avoid any potential problems.

In general, do not create tickets for removal of .hpp or .cpp files. Email me, and I will consider it and create a ticket. You can then add to the comments for it. We may wait until there is some discussion before it is ready to go. If there is an open ticket for removal of .hpp or .cpp files where I make the decision to go forward, then be careful in what you remove.

The class-wide directory where Project 5 code will go is at:

https://dev.cs.uakron.edu/svn/cs421/Apprise

Check out a working copy of this. We had some issues with commits being marked as "anonymous". You may have to login now to commit. Let me know if there is a problem.

Project 5 is due on Friday, Nov 20.

You will be taking the knowledge that you gained from implementing Features from Qt in the last Project, and adding this knowledge to the implementation of Apprise. The goal is to get enough implementation done so that Scenario 1 is accomplished. This scenario has one class with only the class name listed:

The classes that have been identified are to be created. Enough of the interface needs to be in place so that other parts of the project can use them.

The basic process will be:

• Create a ticket for the class/method that needs to be created
• Assign the ticket to yourself
• Create the class
• Provide enough implementation as necessary for the display of the first scenario
• Create tickets for other tasks that need to be done. These may be implemented by other members of the class

The pages in the wiki about the classes must be kept up to date.

Guidelines:

• There will never be enough time for coding. Work smart
• Do your work in the Apprise directory of your working copy
• Update frequently
• Commit frequently
• Focus more on interface and simple, direct implementation.
• Stub implementation is acceptable, e.g., hardcode data in UMLClassModel
• If you need something from another class, then create a ticket with that request
• If there is a stubbed method that needs to be implemented, then create a ticket for it.
• Assign tickets to the Scenario that it is needed for.
• The code is owned collectively. You can make changes to any part of the code. Try to coordinate using tickets.
• You can implement code then what is required for Scenario 1. Just make sure that what you code doesn't break Scenario 1.

The role of the Benevolent Dictator Project Lead:

• Will not make code changes
• Will assist in debugging
• Will create tickets for any necessary code changes
• May make build changes