| Summary: | [activity] define data model for task activity records | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Steffen Pingel <steffen.pingel> |
| Component: | Mylyn | Assignee: | Steffen Pingel <steffen.pingel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | 3.9 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 376233 | ||
I have implemented a first iteration of the data model and pushed that into the o.e.m.tasks.activity.core bundle. The basic idea is that IActivtyStream provides access to a collection of ActivityEvents. An event is a build, new code review, patch set etc. that is provided by concrete providers (e.g. bug 378097, bug 378101). I'll mark this as resolved for now. We can open new bugs to extend the data model, e.g. to add support for notifications. a bug for the notification support (commits) is already opened: bug 380847 Okay, I have checked out the code. Now I will merge my model code with yours. |
The task activity viewer aggregates activity information from various sources. The activity should be stored in a data model that can be cached and indexed. Proposal for the ActivityRecord data model: ActivityRecord { // time the event happened, e.g. a change set was committed Data date; List<IIdentity> people; List<IResource> resources; // unique handle identifier, uri? String handle; // identifies the source of the contribution String kind; // related task ITask task; } We'll also need a notification mechanism but that maybe more suitable on the provider level.