Ticket #2 (new task)
Replace mixins with other mechanisms
| Reported by: | whitelynx | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 3.0 |
| Component: | Core | Version: | |
| Keywords: | Cc: |
Description
Get rid of the entire mixin mechanism except when they actually add functionality to e.g. a Client object. Instead, let each little class that handles some function listen to AddClient? events, and when that happens register event handlers for that new client object (using the mechanism above). Some base class can be written to do the AddClient/RemoveClient? event listening.
Attachments
Change History
Note: See
TracTickets for help on using
tickets.
