Git Product home page Git Product logo

Comments (7)

nicollasricas avatar nicollasricas commented on June 18, 2024

Hi,

Could you share more info about what are you trying to achieve? The plugin on the stream deck side have a websocket server and accept each vscode instance as a connection.

Each connection has its ID, and that's how I can filter to which vscode instance (websocket clients) should send the messages (whenever the user press a key).

from vscode-deck.

theS1LV3R avatar theS1LV3R commented on June 18, 2024

I'm basically trying to recreate the StreamDeck plugin, but for companion instead of the Elgato StreamDeck program. There are no docs anywhere i could find that documents the communication between VSCode and the StreamDeck plugin over WSS, so it's really hard to recreate.

from vscode-deck.

nicollasricas avatar nicollasricas commented on June 18, 2024

The project were divided into two repositories (which I find very annoying, but when the idea started I built one at the time and i'm lazy to put them together).

The communication it's quite simple, so just take a look at the two repositories and you will be fine.

If you need any assistant send me a ping and I will try to help you.

vscode extension - https://github.com/nicollasricas/vscode-streamdeck
stream deck plugin - https://github.com/nicollasricas/streamdeckvsc

from vscode-deck.

nicollasricas avatar nicollasricas commented on June 18, 2024

Maybe I misunderstood it, do you wish to integrate my plugin with your companion app?

If that's the case, I don't see how this could work. Unless, if there's a way to send data from a client to another client.

from vscode-deck.

theS1LV3R avatar theS1LV3R commented on June 18, 2024

I was mainly thinking of docs that document the communication between the VSCode plugin and the Stream Deck plugin, like what messages are sent, what params, types, etc.

from vscode-deck.

nicollasricas avatar nicollasricas commented on June 18, 2024

Then just looking at both repositories you will be able to implement it.

Since each side sends/receives messages, they don't know anything about the other side execution.

Each message is just a simple class converted to a string JSON.

from vscode-deck.

nicollasricas avatar nicollasricas commented on June 18, 2024

Eg.::

from vscode-deck.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.