#530 new planned

external model interface

Reported by: Ichthyostega Owned by:
Priority: normal Milestone: 1alpha
Component: lumiera Keywords: design interfaces cleanup
Sub Tickets: #44, #531, #578, #637, #1234 Parent Tickets: #18, #444, #887

Description (last modified by Ichthyostega)

factor out a export interface of the high-level model, cleanly separated from the implementation.

Ideally, it should be usable without linking against liblumierasteam.so

Change history (10)

comment:1 by Ichthyostega, at 2010-01-18T07:29:05Z

blockedby: 4444, 531

comment:2 by Ichthyostega, at 2010-03-21T00:48:43Z

blockedby: 44, 53144, 531, 578

comment:3 by Ichthyostega, at 2010-06-13T23:27:52Z

blockedby: 44, 531, 57844, 531, 578, 637

comment:4 by Ichthyostega, at 2011-05-13T23:30:20Z

blockedby: 44, 531, 578, 637531, 578, 637

(in #44) Meanwhile, I'm understanding the situation much better.

  • I was able to remove all dependencies from lib. This essentially breaks the cycle between the libraries.
  • but the common (application core) will always necessarily depend on both steam and vault. The reason are the data types used on the Session and Engine interfaces.
  • if we want to avoid the latter, we'd need to do some magic dance with an transparent proxy layer and export interfaces using only placeholder data types.

I don't see any reason why to put any effort into the latter right now. Thus closing as wontfix

Last edited at 2022-10-21T23:00:50Z by Ichthyostega (previous) (diff)

comment:7 by Ichthyostega, at 2011-05-13T23:53:05Z

blockedby: 531, 578, 63744, 531, 578, 637

comment:8 by Ichthyostega, at 2012-03-24T20:50:39Z

blocking: 444444, 887

comment:9 by Ichthyostega, at 2022-10-21T21:12:01Z

Description: modified (diff)

comment:10 by Ichthyostega, at 2023-07-03T23:20:10Z

blocking: 444, 88718, 444, 887

comment:11 by Ichthyostega, at 2023-09-13T17:15:00Z

blockedby: 44, 531, 578, 63744, 531, 578, 637, 1234

comment:10 by Undercover Agent, at 2025-12-25T00:00:00Z

blockedby: 44, 531, 578, 637, 1234
blocking: 18, 444, 887
Parent Tickets: 18, 444, 887
Sub Tickets: 44, 531, 578, 637, 1234

Migration MasterTickets ⟼ Subtickets-plugin

Note: See TracTickets for help on using tickets.