Or probably in addition to. When loading a subpanel we can just ignore any missing events (make sure at least EITHER the generic one or the stop event gets stored). When stopping a subpanel we can throw both the boolean quit event and the generic event with "stop". This would preserve backwards compatibility while allowing for a simpler experience.
Defined events:
Stop (boolean)
Refresh (string)
Save (boolean) (make sure all data is cached)
Reload (boolean) (I see this as being a stronger form of refresh. while refresh assumes it has been running the whole time and can be used for minor changes to the local data this event says "something external changed without telling you, make sure nothing bad happened")
RESPONSE_Valid? (tell editor my state changed from valid to invalid)
Or probably in addition to. When loading a subpanel we can just ignore any missing events (make sure at least EITHER the generic one or the stop event gets stored). When stopping a subpanel we can throw both the boolean quit event and the generic event with "stop". This would preserve backwards compatibility while allowing for a simpler experience.
Defined events: Stop (boolean) Refresh (string) Save (boolean) (make sure all data is cached) Reload (boolean) (I see this as being a stronger form of refresh. while refresh assumes it has been running the whole time and can be used for minor changes to the local data this event says "something external changed without telling you, make sure nothing bad happened") RESPONSE_Valid? (tell editor my state changed from valid to invalid)