Search
Page 2 of 183. Showing 1,824 results (0.026 seconds)
Adding Custom Plugins
to the interface. A plugin must supply a type, name, and context. 'name' is the display name of the plugin 'context' determines under which tabs this [tab] plugin…Adding Custom Plugins
(QbUIPlugin): """ UserUIPlugin - user created plugins for Qube UI to add functinality to the interface. A plugin must supply a type, name, and context. 'name…Adding Custom Plugins
to the interface. A plugin must supply a type, name, and context. 'name' is the display name of the plugin 'context' determines under which tabs this [tab] plugin…Adding Custom Plugins
, and context. 'name' is the display name of the plugin 'context' determines under which tabs this [tab] plugin will be displayed. Current available contexts are job…Adding Custom Plugins
to the interface. A plugin must supply a type, name, and context. 'name' is the display name of the plugin 'context' determines under which tabs this [tab] plugin…Events
Breaking down the event specification syntax, is generalized into these 4 parts: --- Some simple example callback triggers are: complete-job-self: called when this job is complete done-job-self: called when this job is complete…Triggers
occurring prior to a job's submission. Syntax The syntax for specifying an event consists of: name-type-context-extra Operators Triggers can be logically AND'd or OR'd…Triggers
occurring prior to a job's submission. Syntax The syntax for specifying an event consists of: name-type-context-extra Refer to Trigger Event Syntax for more details. Operators…Triggers
occurring prior to a job's submission. Syntax The syntax for specifying an event consists of: name-type-context-extra Refer to Trigger Event Syntax for more details. Operators…Triggers
occurring prior to a job's submission. Syntax The syntax for specifying an event consists of: name-type-context-extra Refer to Trigger Event Syntax for more details. Operators…