Task #1219 (new)
Opened 16 years ago
Last modified 15 years ago
Decide on proper Filter.limit handling in ITimeline
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | General | Version: | 3.0-M1 |
| Keywords: | n.a. | Cc: | atarkowska |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Current limit is 50, which is obviously non-optimal.
Change History (4)
comment:1 Changed 16 years ago by atarkowska
- Priority changed from minor to major
comment:2 Changed 16 years ago by jmoore
- Milestone changed from OMERO-Beta4 to OMERO-Beta4.1
comment:3 Changed 15 years ago by jmoore
- Milestone changed from OMERO-Beta4.1 to OMERO-Beta4.2
comment:4 Changed 15 years ago by jmoore
- Milestone changed from OMERO-Beta4.2 to Unscheduled
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
The purpose of getEventsByPeriod is to present how many events happens on the system in particular period. Maybe we need to have countEventsByPeriod what returns {"Image": number, "Dataset": number, "Project":number, and another types...} with no limits.
The particular day needs the data:
self.cal_days.append({'day':self.cal_weeks[week][day], 'counter': {'imgCounter':imgCounter, 'rdCounter':rdCounter, 'dsCounter':dsCounter, 'prCounter':prCounter }})WARNING: event types currently supported: INSERT/UPDATE