Opened at 2017-08-10T19:16:31Z

Closed at 2017-08-10T19:30:56Z

#1103 closed todo (done)

basic concept for binding and handling sesssion commands in the UI

Reported by: Ichthyostega Owned by: Ichthyostega
Priority: grave Milestone: 0integration
Component: lumieraGui Keywords: gui architecture lifecycle design
Sub Tickets: #975, #1064, #1088 Parent Tickets: #978, #1032, #1044, #1048, #1070, #1085

Description

  • the concrete way to define them
  • how to address commands in the simplest case
  • how and where argument binding is done
  • how to send them over the UI-Bus
  • how to implement invocation in the Session thread


Change history (4)

comment:1 by Ichthyostega, at 2017-08-10T19:18:18Z

blockedby: 1064, 978 → 1064
blocking: 1070, 1032, 1044, 1048, 1085 → 978, 1032, 1044, 1048, 1070, 1085

comment:2 by Ichthyostega, at 2017-08-10T19:26:08Z

blockedby: 1064 → 1064, 1088, 975

comment:3 by Ichthyostega, at 2017-08-10T19:30:56Z

blockedby: 1064, 1088, 975 → 975, 1064, 1088
Resolution: → done
Status: new → closed

consider this basic part of UI/Proc integration as settled by now

  • there is a mechanism in place to define the commands
  • we have a convention how to organise the corresponding source files
  • we're able to bind and invoke commands by ID via the UI-Bus

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

blockedby: 975, 1064, 1088
blocking: 978, 1032, 1044, 1048, 1070, 1085
Parent Tickets: → 978, 1032, 1044, 1048, 1070, 1085
Sub Tickets: → 975, 1064, 1088

Migration MasterTickets ⟼ Subtickets-plugin

Note: See TracTickets for help on using tickets.