outputrouting.go RawHistoryFolder

1package app
2
3import "github.com/bnema/neferwl/internal/ports"
4
5// outputChannels is the shared app-to-backend wiring. The backend loop remains
6// the sole owner of outputSet and outputApply. Security producers use bounded
7// lossless FIFO forwarders; contents are not routed here: each output is
8// attached to wayland's content feed (contentAttacher).
9// heads, configured and replies are fed from the outputApply outbox.
10type outputChannels struct {
11	security        ports.SessionSecurity
12	securityChanges <-chan ports.SecurityState
13	securityEvents  chan<- ports.SecurityBackendEvent
14	leaseRequests   <-chan ports.LeaseMessage
15	leaseEvents     chan<- ports.LeaseMessage
16	events          chan<- ports.OutputEvent
17	scenes          <-chan []ports.Scene
18	content         contentAttacher
19	cursorChanges   <-chan ports.CursorChange
20	presented       ports.PresentationSink
21	frames          chan<- ports.OutputFrame
22	captures        <-chan ports.CaptureRequest
23	captured        chan<- ports.CaptureDone
24	formats         chan<- ports.OutputFormats
25	heads           chan<- ports.OutputHeads
26	// reloads carries file configuration; configured carries the effective
27	// configuration, overrides included, to core.
28	reloads    <-chan ports.ConfigChanged
29	configured chan<- ports.ConfigChanged
30	requests   <-chan ports.OutputApply
31	replies    chan<- ports.OutputApplied
32}
33
34// routes are the inputs the output router feeds the outputs from.
35func (ch outputChannels) routes() outputRoutes {
36	return outputRoutes{scenes: ch.scenes, cursor: ch.cursorChanges, captures: ch.captures}
37}