buttplugio / vue-buttplug-material-component Goto Github PK

View Code? Open in Web Editor NEW

3.0 3.0 3.0 3.91 MB

DEPRECATED - Vue.js Buttplug Client Management Component using vue-material

License: Other

TypeScript 37.79% Vue 27.05% JavaScript 29.88% HTML 5.28%

vue-buttplug-material-component's People

Contributors

Stargazers

Watchers

Forkers

mftrips blackspherefollower cualquiercosa327

vue-buttplug-material-component's Issues

Add npm package publishing to CI steps

Devices don't stop if deselected in device list

If a device is deselected in the device list, it should send StopDeviceCmd to the server. This doesn't seem to be happening currently.

Export example as github page

Have the CI build the example and export it to gh-pages.

ButtplugPanel doesn't emit connected on WebSocket connect

When the ButtplugPanel connects its ButtplugClient using either the webbluetooth or the simulator , the panel emits connected. This doesn't happen when connecting via websocket to the Windows Server GUI.

Devices do not disconnect properly when using Websocket server

Devices that disconnect from the websocket server are not removed from the panel.

Warn user when websocket address is not (ws|wss)://

Just had a report of issues on discord, where the user was trying to connect to the websocket server using https instead of wss. We should warn and not connect in that case, as the error is pretty opaque.

Show what devices we support connecting to when using in-browser connect

@qdot commented on Mon Aug 28 2017

Add CI building

Write some tests

Bought a book on vue.js testing, might as well actually use it.

Already connected devices don't show up on list

If we connect to a websocket server that already has connections, the devices don't show up on connect or scan..

Show warning dialog on lack of proper bluetooth radio

@qdot commented on Sun Aug 27 2017

If a user doesn't have a radio that will work for Syncydink, they should be warned after hitting the "start scanning" button. This warning should ideally emit from buttplug-js.

"Stop Scanning" button should go back to "Start Scanning" on ScanningFinished message

@qdot commented on Mon Aug 28 2017

Websocket does not register disconnect on server shutdown

If the embedded buttplug client is connected to a server using websockets, and the server quits, the connection dialog does not update accordingly.

Component clears device list if websocket connection returns late

If a websocket connection returns a failure after another connection succeeded, the device list gets cleared.

Add autoconnect capabilities

When opening the component, it should just start trying to connect automatically, and we should have a waiting icon/message to denote this. That way people can tweak intiface desktop and start/stop services while it tries.

Disconnect button always disabled when connected to Websocket server

Disconnect button does not work when connected to websocket server. Works when connected to local server.

Export built version of component for CDN usage

I /think/ we should be able to export a CDN version of the component, so developers can load it via CDN. Might make app bringup or tutorials on glitch easier?

Load device configuration file from CDN when possible

The device configuration file should be loaded from CDN when possible, as it means we won't have to constantly update the app for new devices.