Ticket #29 (new task)

Opened 2 years ago

Last modified 10 months ago

Expand the Observer Pattern to identify starts and stops

Reported by: sthiel Assigned to: sthiel
Priority: minor Milestone: discarded
Component: Implementation Version:
Keywords: Cc:
Super-ticket: Reviewer:
Minutes Spent:

Description

If we identify starts/stops and manual time changes using this, I think it'll be better. We can also maybe directly associate GUI components as Observers instead of passing through the controller. We can also probably pass some information? Nah, the observer should probably know about the subscriber in the first place (in fact, that's a good guideline... whoever sees the subscriber should probably be an observer; not always, but often).

Change History

04/27/07 18:27:59 changed by sthiel

  • minutes_worked changed.
  • milestone changed from milestone2 to milestone3.

-Gotta move it to milestone3, I'm running too far behind.

03/07/08 09:44:46 changed by sthiel

  • priority changed from major to minor.
  • reviewer changed.
  • super_ticket changed.
  • milestone changed from milestone3 to milestone6.

perhaps obsolete?

03/08/08 11:29:29 changed by sthiel

  • milestone changed from milestone6 to discarded.

Well, we're addressing the need here... this sort of design decision should wait till we do a full redesign of the architecture. Proof of concept is in place, best to clean it up one of these days :(