Core data structure in the Zeitgeist framework. It is an optimized and convenient representation of an event.
This class is designed so that you can pass it directly over DBus using the Python DBus bindings. It will automagically be marshalled with the signature a(asaasay). See also the section on the event serialization format.
This class does integer based lookups everywhere and can wrap any conformant data structure without the need for marshalling back and forth between DBus wire format. These two properties makes it highly efficient and is recommended for use everywhere.
Read/write property defining the application or entity responsible for emitting the event. For applications, the format of this field is the base filename of the corresponding .desktop file with an application:// URI scheme. For example, /usr/share/applications/firefox.desktop is encoded as application://firefox.desktop
Append a new empty Subject and return a reference to it
Read only property containing the the event id if the event has one
Read/write property defining the interpretation type of the event
Read/write property defining the manifestation type of the event
Interpret self as the template an match event against it. This method is the dual method of matches_template().
Return True if this event matches event_template. The matching is done where unset fields in the template is interpreted as wild cards. Interpretations and manifestations are also matched if they are children of the types specified in event_template. If the template has more than one subject, this event matches if at least one of the subjects on this event matches any single one of the subjects on the template.
Basically this method mimics the matching behaviour found in the FindEventIds() method on the Zeitgeist engine.
Create a new Event setting event_data as the backing array behind the event metadata. The contents of the array must contain the event metadata at the positions defined by the Event.Fields enumeration.
Returns a new Event instance or None if struct is a NULL_EVENT
Create a new Event instance from a collection of keyword arguments.
| Parameters: |
|
|---|
Instead of setting the subjects argument one may use a more convenient approach for events that have exactly one Subject. Namely by using the subject_* keys - mapping directly to their counterparts in Subject.new_for_values():
| Parameters: |
|
|---|
Read/write property defining the origin where the event was emitted.
Free form attachment for the event. Transfered over DBus as an array of bytes
Read/write property with the event timestamp defined as milliseconds since the Epoch. By default it is set to the moment of instance creation
Represents a subject of an Event. This class is both used to represent actual subjects, but also create subject templates to match other subjects against.
Applications should normally use the method new_for_values() to create new subjects.
Read/write property with the current URI of the subject encoded as a string
Read/write property defining the interpretation type of the subject
Read/write property defining the manifestation type of the subject
Return True if this Subject matches subject_template. Empty fields in the template are treated as wildcards. Interpretations and manifestations are also matched if they are children of the types specified in subject_template.
See also Event.matches_template()
Read/write property containing the mimetype of the subject (encoded as a string) if applicable
Create a new Subject instance and set its properties according to the keyword arguments passed to this method.
| Parameters: |
|
|---|
Read/write property with the URI of the location where the subject can be found. For files this is the parent directory, or for downloaded files it would be the URL of the page where you clicked the download link
Read/write property with a string id of the storage medium where the subject is stored. Fx. the UUID of the disk partition or just the string ‘net’ for items requiring network interface to be available
Read/write property with a free form textual annotation of the subject
Read/write property with the URI of the subject encoded as a string
A collection of Symbol objects which represents the interpretations defined by the zeitgeist ontology. For more information see Interpretations.
A collection of Symbol objects which represents the manifestations defined by the zeitgeist ontology. For more information see Manifestations.
A class that represents a time range with a beginning and an end. The timestamps used are integers representing milliseconds since the Epoch.
By design this class will be automatically transformed to the DBus type (xx).
The begining timestamp of this time range
The end timestamp of this time range
Return a TimeRange ranging from “sec” seconds before the instant of invocation to the same.
Return a TimeRange ranging from the given timestamp until the end of time.
The given timestamp is expected to be expressed in miliseconds.
Return a new TimeRange that is the intersection of the two time range intervals. If the intersection is empty this method returns None.
Returns True if this time range goes from timestamp 0 (January 1, 1970) -or lower- to the most distant future.
An enumeration class used to define how query results should be returned from the Zeitgeist engine.
Enumeration class defining the possible values for the storage state of an event subject.
The StorageState enumeration can be used to control whether or not matched events must have their subjects available to the user. Fx. not including deleted files, files on unplugged USB drives, files available only when a network is available etc.
Optimized and convenient data structure representing a datasource.
This class is designed so that you can pass it directly over DBus using the Python DBus bindings. It will automagically be marshalled with the signature a(asaasay). See also the section on the event serialization format.
This class does integer based lookups everywhere and can wrap any conformant data structure without the need for marshalling back and forth between DBus wire format. These two properties makes it highly efficient and is recommended for use everywhere.
This is part of the org.gnome.zeitgeist.DataSourceRegistry extension.