events in cpia

conversation with John, Donn and Jed

• good cpia events: high level events that have semantic meaning in Chandler
  • action requests: new, commit repository, etc. (the event is consumed by one handler)
  • notifications: selection changed, etc. (multiple consumers may react to event)

• shouldn't be cpia events: low level events, mouse clicks, enter pressed, etc.
  • wxWidget event should be handled and translated into a higher level semantic cpia event
  • enterPressed ==> urlChanged, for example

• would be cool to set up an event log
  • perhaps a 1/2 day task to investigate (probably more work to actually iron out all of the snags)
  • log all events in post, with enough information to recreate them
  • write bit of code to run the log, posting all the events, see what happens
  • referrng to uuids may cause snags, even if you use a known repository, create new uuids for newly generated items
  • could perhaps use as unit tests, etc.

• in parcel xml, would be nice to standardize on namespace of the current parcel file
  • self, this?

• when you make up a new event, run it by folks on dev list (hard to do in a vacuum)
  • alternatively, in code reviews

• create noop event for menus, etc. that don't have code yet -- will be disabled (Donn)

• Morgen's dialog could hook into attribute renderers

• depricate block demo at some point, get rid of enter pressed

• read only attributes in the detail view -- how to model this

-- KatieCappsParlante - 26 Jul 2004