RefactoringIncrementIIIStory

Meeting minutes

• To ensure that the projects stays active its time to attract more developers.
• The demo-server must be updated more frequently
• The last two increments are combined in one final increment
• As soon as the refactorings are complete a first release is to be made.
• To make a first install simpler we are going to create a way to define the majority of the application settings through the web browser -> FirstRunStory

Refactoring after increment III

• Hibernate
  • OpenSessionInViewFilter is to be avoided as much as possible we are going to use manual session/transaction handling.
  • Relations in the model classes are to be handled through the managers so that we're never working with stale data.
  • After this refactoring the adding and editing of events should be a breeze.
• Timezones must be handled consistently throughout the application
• The javadoc should be made usefull. Because the panels are changed often only the domain is re-javadoced.

• Views
  • The event list shows null when the description is not filled out
  • the time format does not match the users locale
  • after adding/editing an event the panel returns to the wrong view
  • Ajax should be turned on by default unless the user does not support it
  • There is no way to remove an event as off yet
  • The use of Panels for small components seems unnecessary, we should make more use of fragments
  • The weekview and monthview have a double entry for the summary, this should be a summary and the start time.

• There is a lack of null-checks throughout some of the code. For example Event.isValidForDateRange().
• Event contains logic specific to iCalendar. This should be made available through a manager call
• The recurrence is incomplete, RDate is not taken into account.

-- IvoVanDongen - 16 Dec 2006