Change Details

Currently, Time.tcl provide an onLoad procedure to initialize first the broker, then the notifications: ```name=Wearg/Time.tcl,lang=tcl utimer 90 onload proc onload {} { ::broker::init ::notifications::init } ``` If the first fails, the procedure will stop without initializing notifications engine. Afterwards, we'll fix broker connectivity but forgot about that one, so proposal is to move ::notifications::init to a callback for a broker initialized event AND DOCUMENT HOW TO FIX THIS MESS (or provide a high-level .broker command to restore broker connectivity and fire ::notifications::init if needed)

Currently, Time.tcl provide an onLoad procedure to initialize first the broker, then the notifications: ```name=Wearg/Time.tcl,lang=tcl utimer 90 onload proc onload {} { ::broker::init ::notifications::init } ``` If `::broker::init` fails, the procedure will stop without initializing notifications engine. Afterwards, we'll fix broker connectivity but forgot about that one, so proposal is to move `::notifications::init` to a callback for a new `onBrokerInitialized` event. We should also document how to fix any broker connection issue, perhaps a .broker high-level command to restore connectivity and call the needed init methods could be nice. Careful to not blindly call `::notifications::init`: we don't want to call twice (or 3 times, 4 times, etc.) each callback function.

Currently, Time.tcl provide an onLoad procedure to initialize first the broker, then the notifications: ```name=Wearg/Time.tcl,lang=tcl utimer 90 onload proc onload {} { ::broker::init ::notifications::init } ``` If the firstIf `::broker::init` fails, the procedure will stop without initializing notifications engine. Afterwards, we'll fix broker connectivity but forgot about that one, so proposal is to move `::notifications::init` to a callback for a bnew `onBroker iInitialized` event. AND DOCUMENT HOW TO FIX THIS MESS (or provide a high-level .broker command to restore broker connectivity and fire ::notifications::init if needed)We should also document how to fix any broker connection issue, perhaps a .broker high-level command to restore connectivity and call the needed init methods could be nice. Careful to not blindly call `::notifications::init`: we don't want to call twice (or 3 times, 4 times, etc.) each callback function.