Open jamesadevine opened 3 years ago
We released yesterday that ability to run a simulator from vscode.
Upgrade mic and use "mic serve" + jacdac dev tools
Maybe that helps
yeah, we could use a little tool support here, but essentially the pattern is:
you can do mkc add jacdac-joystick
already
can we have more details about this?
the role === makecode client name, which is shown in the dashboard device. but that does not seem to be obvious
Where to put the details?
Add to this bug
you can do
mkc add jacdac-joystick
alreadycan we have more details about this?
Right, that's fine if you know joystick maps to "jacdac-joystick" in pxt-jacdac. The issue is, for someone who isn't us and is using mkc + visual studio, how do they work out what packages to specify in the mkc add
command
It would be cool for the mkc command to auto detect modules, but i understand there are dragons with usb via node...
sample output?
mkc jdls
-> rotary -> jacdac-rotary
-> button -> jacdac-button
-> joystick -> jacdac-joystick
Auto install? [y/n]
the mkc command prompt currently does not do USB;
we should extend search to also return jacdac sub-repoes. the cloud search does not support mono-repoes
@pelikhan - does this need to be documented somewhere?
it should go here https://microsoft.github.io/jacdac-docs/clients/makecode/code/
It's unclear how devices in the device tree map to service clients in pxt-jacdac. This is problematic if you are using mkc and visual studio code to write programs for makecode + jacdac.