Opened at 2009-10-16T19:43:11Z
Last modified at 2011-11-19T01:45:51Z
#340 accepted planned
Identify required query and enumeration operations
| Reported by: | Ichthyostega | Owned by: | Ichthyostega |
|---|---|---|---|
| Priority: | lesser | Milestone: | 0integration |
| Component: | lumieraSteam | Keywords: | interfaces design |
| Sub Tickets: | #319, #341, #342, #343 | Parent Tickets: | #150, #401 |
Description (last modified by )
the Query operations of individual Placements are already on the API of PlacementIndex. Need to identify the more generic query operations, allowing the PlacementIndex to provide a system of nested scopes
Change history (9)
comment:1 by , at 2009-11-26T21:21:00Z
| blockedby: | 319 → 319, 341 |
|---|
comment:2 by , at 2009-11-26T21:21:15Z
| blockedby: | 319, 341 → 319, 341, 342 |
|---|
comment:3 by , at 2009-11-26T21:21:28Z
| blockedby: | 319, 341, 342 → 319, 341, 342, 343 |
|---|
comment:4 by , at 2009-12-28T02:43:39Z
| blocking: | 303 → 391 |
|---|---|
| Description: | modified (diff) |
| Status: | new → accepted |
comment:5 by , at 2010-01-19T10:33:09Z
| blocking: | 391 → 150, 401 |
|---|---|
| Keywords: | session removed |
| Priority: | normal → lesser |
now this is basically design/documentation work, detached from the implementation level
comment:6 by , at 2011-11-19T01:27:30Z
| Type: | todo → planned |
|---|
future -- currently focussing on engine and playback
comment:7 by , at 2011-11-19T01:45:51Z
| blocking: | 150 → 150, 401 |
|---|
comment:8 by , at 2011-11-19T01:50:10Z
| blocking: | 150, 401 → 150 |
|---|
comment:9 by , at 2025-12-25T00:00:00Z
| blockedby: | 319, 341, 342, 343 |
|---|---|
| blocking: | 150, 401 |
| Parent Tickets: | → 150, 401 |
| Sub Tickets: | → 319, 341, 342, 343 |
Migration MasterTickets ⟼ Subtickets-plugin
Note:
See TracTickets
for help on using tickets.
This task has been shifted over from the PlacementIndex to ContentsQuery, while the index is now a rather low-level implementation facility. As far as I can see, the more generic query operations are coded up; but there should be a conclusive list what will be required by the public session API