eaadf8743b
We now have a global OctoPrintClient, which is the class from which
all clients are derived, and a global OctoPrint, which is a single
instance already setup and ready to use in case we only need one.
It would be cleaner to have clients create that singular instance
themselves, but we need to maintain backward compatibility for now
with how we established the client to work with the 1.3.0 release.
New clients can be create with
client = new OctoPrintClient({ /* options */ });
Alternatively the options can be left out and set at a later point:
client = new OctoPrintClient();
/* ... */
client.options = { /* options */ };
Individual client components register themselves with OctoPrintClient
via OctoPrintClient.registerComponent(name, component) from the
component JS files. Just like before their instances are then
available in the individual client instances under "<client>.<name>",
e.g. "OctoPrint.files".
Plugin components register themselves with OctoPrintClient via
OctoPrintClient.registerPluginComponent(name, component) from the
component JS files. Just like before their instances are then
available in the individual client instances under "<client>.plugins
.<name>", e.g. "OctoPrint.plugins.softwareupdate".
This should make it possible to create dashboard pages utilizing the
JS client that monitor the status of multiple OctoPrint instances,
without workarounds such as having to swap out the options globally
before each request.
See #1681 for the corresponding discussion.
49 lines
1.8 KiB
ReStructuredText
49 lines
1.8 KiB
ReStructuredText
.. _sec-jsclientlib-connection:
|
|
|
|
:mod:`OctoPrintClient.connection`
|
|
---------------------------------
|
|
|
|
.. js:function:: OctoPrintClient.connection.getSettings(opts)
|
|
|
|
Retrieves the available connection options for connection to a printer.
|
|
|
|
See :ref:`Get connection settings <sec-api-connection-current>` for the response format.
|
|
|
|
:param object opts: Additional options for the request
|
|
:returns Promise: A `jQuery Promise <http://api.jquery.com/Types/#Promise>`_ for the request's response
|
|
|
|
.. js:function:: OctoPrintClient.connection.connect(data, opts)
|
|
|
|
Connects to the printer, optionally using the provided connection ``data`` as parameters.
|
|
|
|
If ``data`` is provided it's expected to be an object specifying one or more of
|
|
|
|
* ``port``
|
|
* ``baudrate``
|
|
* ``printerProfile``
|
|
* ``save``
|
|
* ``autoconnect``
|
|
|
|
See :ref:`Issue a connection command <sec-api-connection-command>` for more details.
|
|
|
|
:param object data: Connection data to use
|
|
:param object opts: Additional options for the request
|
|
:returns Promise: A `jQuery Promise <http://api.jquery.com/Types/#Promise>`_ for the request's response
|
|
|
|
.. js:function:: OctoPrintClient.connection.disconnect(opts)
|
|
|
|
Disconnects from the printer.
|
|
|
|
See :ref:`Issue a connection command <sec-api-connection-command>` for more details.
|
|
|
|
:param object opts: Additional options for the request
|
|
:returns Promise: A `jQuery Promise <http://api.jquery.com/Types/#Promise>`_ for the request's response
|
|
|
|
.. js:function:: OctoPrintClient.connection.fakeAck(opts)
|
|
|
|
Triggers a fake acknowledgement (``ok``) on the printer.
|
|
|
|
See :ref:`Issue a connection command <sec-api-connection-command>` for more details.
|
|
|
|
:param object opts: Additional options for the request
|
|
:returns Promise: A `jQuery Promise <http://api.jquery.com/Types/#Promise>`_ for the request's response
|