Search Results for "connect"

Bot Framework Emulator is a desktop application that allows bot developers to test and debug bots, either locally or remotely. Using the Emulator, you can chat with your bot and inspect the messages that your bot sends and receives. The Emulator displays messages as they would appear in a web chat UI and logs JSON requests and responses as you exchange messages with your bot. Before you deploy your bot to the cloud, run it locally and test it using the Emulator. You can test your bot using...

Electronic circuit simulator. Simple environment to run and debug firmware for AVR 8-bit microprocessors. Able to run arduino firmware. Internally this program uses the open source Simavr AVR Processor Simulator (https://github.com/buserror/simavr) and wraps all its functions in a GUI shell. Setups for firmware debugging scenarios can be created dynamically. Able to run 16MHz MCU with decent set of external parts in real time. In particular this can be used for development of CNC firmware...

...You can use it to debug code running locally in Firefox or running remotely, for example on an Android device running Firefox for Android. See remote debugging to learn how to connect the debugger to a remote target. You probably want to pause the execution of your code, in order to see what is going on at various points. There are multiple ways to tell the Debugger how and when to pause. You probably want to see the value of variables or expressions, either during execution or when it is paused.

...Powered by node.js and socket.io. Install Vorlon.JS and add a single line of JavaScript to your web app. Run your server and start the Vorlon.JS dashboard. Remotely connect up to 50 devices simultaneously. Run your code on each or all of them with a single click. Debug JavaScript on nearly any platform with a web environment. Plugins allow you to add new features and resources. You could also download the desktop version of Vorlon. It is a standalone executable working on Windows and MacOS. By default Vorlon.JS application logs with debug level and files are stored in the installation folder.

gtracer traces gsignal's `connect', `emit', `disconnect' and `callback invocations' in gtk application, and about `connect', `emit' and `disconnect', backtracing of function calls is also provided.

The original intent was to make a pretty simple "connect and send" http client, it has since grown to include as much http 1.0 client capabilitlies (as defined in RFC 1945) as possible.