Ticket #340 (accepted planned)

Opened 2 years ago

Last modified 3 months ago

Identify required query and enumeration operations

Reported by: ichthyo Owned by: ichthyo
Priority: lesser Milestone: 0integration
Component: lumieraProc Keywords: interfaces design
Cc: Blocked By: #319, #341, #342, #343
Blocking: #150, #401

Description (last modified by ichthyo) (diff)

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

comment:1 Changed 2 years ago by ichthyo

  • Blocked By 341 added

comment:2 Changed 2 years ago by ichthyo

  • Blocked By 342 added

comment:3 Changed 2 years ago by ichthyo

  • Blocked By 343 added

comment:4 Changed 2 years ago by ichthyo

  • Status changed from new to accepted
  • Blocking 391 added; 303 removed
  • Description modified (diff)

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

comment:5 Changed 2 years ago by ichthyo

  • Keywords session removed
  • Priority changed from normal to lesser
  • Blocking 150, 401 added; 391 removed

now this is basically design/documentation work, detached from the implementation level

comment:6 Changed 3 months ago by ichthyo

  • Type changed from todo to planned

future -- currently focussing on engine and playback

comment:7 Changed 3 months ago by ichthyo

  • Blocking 401 added

comment:8 Changed 3 months ago by ichthyo

  • Blocking 401 removed
Note: See TracTickets for help on using tickets.