Ticket #319 (accepted planned)

Opened 2 years ago

Last modified 3 months ago

define generic and specific query API

Reported by: ichthyo Owned by: ichthyo
Priority: urgent Milestone: 0integration
Component: lumieraProc Keywords: interfaces design session
Cc: Blocked By: #182, #500, #539, #639
Blocking: #306, #318, #340, #412, #676

Description (last modified by ichthyo) (diff)

  • decide what kind of operations goes on which part of the API
  • care for adding them to the relevant classes consistently

Change History

comment:1 Changed 2 years ago by ichthyo

  • Blocking 318 added

comment:2 Changed 2 years ago by ichthyo

  • Blocking 339 added

comment:3 Changed 2 years ago by ichthyo

  • Blocking 340 added

comment:4 Changed 2 years ago by ichthyo

  • Blocking 339 removed

(In #339) as a sideeffect of working out the QueryResolver API, this got almost completely solved. Indeed the meaning is changed, as now there isn't any active "registration" necessary anymore.

comment:5 Changed 2 years ago by ichthyo

  • Blocking 412 added

(In #412) 90% of the implementation is in place now, so this boils down to defining a sensible API

comment:6 Changed 2 years ago by ichthyo

  • Keywords session added; sesion removed

comment:7 Changed 2 years ago by ichthyo

  • Blocked By 500 added

comment:8 Changed 2 years ago by ichthyo

  • Blocked By 539 added

comment:9 Changed 2 years ago by ichthyo

  • Blocking 546 added

comment:10 Changed 22 months ago by ichthyo

  • Status changed from new to accepted
  • Blocking 546 removed
  • Description modified (diff)

Considering the basic spec as done now. Still have to code up all the individual API functions

comment:11 Changed 20 months ago by ichthyo

  • Blocked By 639 added

comment:12 Changed 16 months ago by ichthyo

  • Blocking 676 added

comment:13 Changed 3 months ago by ichthyo

  • Type changed from todo to planned

future -- currently focussing on engine and playback

Note: See TracTickets for help on using tickets.