a
    ©ˆc  ã                   @   s$   d Z ddlmZ G dd„ deƒZdS )z! The plugin activator interface. é    )Ú	Interfacec                   @   s    e Zd ZdZdd„ Zdd„ ZdS )ÚIPluginActivatora6   The plugin activator interface.

    A plugin activator is really just a collection of two strategies - one
    to start the plugin and one to stop it.

    We use an activator so that the framework can implement default start and
    stop strategies without forcing the plugin writer to call 'super' if they
    override the 'start' and 'stop' methods on 'IPlugin'.

    I'm not sure that having to call 'super' is such a burden, but some people
    seem to like it this way, and it does mean one less thing for a plugin
    writer to have to remember to do!

    c                 C   s   dS )z& Start the specified plugin.

        N© ©ÚselfZpluginr   r   ú^/home/yuhw/wc/wire-cell-python/wcpy/lib/python3.9/site-packages/envisage/i_plugin_activator.pyÚstart_plugin!   s    zIPluginActivator.start_pluginc                 C   s   dS )z% Stop the specified plugin.

        Nr   r   r   r   r   Ústop_plugin&   s    zIPluginActivator.stop_pluginN)Ú__name__Ú
__module__Ú__qualname__Ú__doc__r   r	   r   r   r   r   r      s   r   N)r   Z
traits.apir   r   r   r   r   r   Ú<module>
   s   