isomer.events.system module¶
Module: Events¶
Major Isomer event declarations
-
class
anonymous_event
(action, data, client, *args)[source]¶ Bases:
isomer.events.system.isomer_ui_event
Base class for events for logged in users.
Bases:
isomer.events.system.isomer_ui_event
Base class for events for logged in users.
Initializes an Isomer authorized user interface event.
Parameters: - user – User object from :py:class:isomer.web.clientmanager.User
- action –
- data –
- client –
- args –
Returns:
Return real name of an object class
Return real name of an object class
-
class
componentupdaterequest
(force=False, install=False, *args)[source]¶ Bases:
isomer.events.system.frontendbuildrequest
Check for updated components
-
class
debugrequest
(*args)[source]¶ Bases:
isomer.events.system.authorized_event
Debugging event
-
class
frontendbuildrequest
(force=False, install=False, *args)[source]¶ Bases:
circuits.core.events.Event
Rebuild and/or install the frontend
-
__init__
(force=False, install=False, *args)[source]¶ An event is a message send to one or more channels. It is eventually dispatched to all components that have handlers for one of the channels and the event type.
All normal arguments and keyword arguments passed to the constructor of an event are passed on to the handler. When declaring a handler, its argument list must therefore match the arguments used for creating the event.
Every event has a
name
attribute that is used for matching the event with the handlers.Variables: - channels –
an optional attribute that may be set before firing the event. If defined (usually as a class variable), the attribute specifies the channels that the event should be delivered to as a tuple. This overrides the default behavior of sending the event to the firing component’s channel.
When an event is fired, the value in this attribute is replaced for the instance with the channels that the event is actually sent to. This information may be used e.g. when the event is passed as a parameter to a handler.
- value – this is a
circuits.core.values.Value
object that holds the results returned by the handlers invoked for the event. - success – if this optional attribute is set to
True
, an associated eventsuccess
(original name with “_success” appended) will automatically be fired when all handlers for the event have been invoked successfully. - success_channels – the success event is, by default, delivered to same channels as the successfully dispatched event itself. This may be overridden by specifying an alternative list of destinations using this attribute.
- complete – if this optional attribute is set to
True
, an associated eventcomplete
(original name with “_complete” appended) will automatically be fired when all handlers for the event and all events fired by these handlers (recursively) have been invoked successfully. - complete_channels – the complete event is, by default, delivered to same channels as the initially dispatched event itself. This may be overridden by specifying an alternative list of destinations using this attribute.
- channels –
-
-
class
isomer_basic_event
(*args, **kwargs)[source]¶ Bases:
circuits.core.events.Event
Basic Isomer event class
-
class
isomer_event
(*args, **kwargs)[source]¶ Bases:
isomer.events.system.isomer_basic_event
Isomer internal event class
-
class
isomer_ui_event
(*args, **kwargs)[source]¶ Bases:
isomer.events.system.isomer_basic_event
Isomer user interface event class
-
class
logtailrequest
(user, action, data, client, *args)[source]¶ Bases:
isomer.events.system.authorized_event
Request the logger’s latest output
-
class
profilerequest
(*args)[source]¶ Bases:
isomer.events.system.authorized_event
A user has changed his profile
-
class
reload_configuration
(target, *args, **kwargs)[source]¶ Bases:
isomer.events.system.isomer_ui_event
Instructs a component to reload its configuration
-
class
system_stop
(*args, **kwargs)[source]¶ Bases:
isomer.events.system.isomer_event
Stop everything, save persistent state and cease operations