An extended table to integration with some of the most widely used CSS frameworks. (Supports Bootstrap, Semantic UI, Bulma, Material Design, Foundation, Vue.js)
-
Updated
Mar 17, 2022 - JavaScript
{{ message }}
An extended table to integration with some of the most widely used CSS frameworks. (Supports Bootstrap, Semantic UI, Bulma, Material Design, Foundation, Vue.js)
Transmits AM radio on computers without radio transmitting hardware.
Turn checkboxes and radio buttons in toggle switches.
Add the ability to display the grid that blocks snap to in GRC. This should be toggleable and saved using a preference and have a menu item in the dropdown menu to enable/disable.
low (just an idea)
Thanks to @skoslowski for outlining the steps to implement the drawing of the grid:
To implement it, you'll want to start here
Professional Radio Station App for iOS!
A self-hosted web radio management suite, including turnkey installer tools for the full radio software stack and a modern, easy-to-use web app to manage your stations.
A Curated list of IoT Security Resources
Custom firmware for the HackRF+PortaPack H1/H2
Spectrum analyzer for multiple SDR platforms (PyQtGraph based GUI for soapy_power, hackrf_sweep, rtl_power, rx_power and other backends)
A cross platform Python frequency scanning GUI for the OsmoSDR rtl-sdr library
It would be nice to be able to select which entries in the playout history are included when the list is exported. The checkout boxes are already there, but need plumbing into the export buttons.
Messaging patterns for Backbone applications.
radio browser app that uses www.radio-browser.info on android
library for turning a RTL2832 based DVB dongle into a Software DefinedReceiver; mirror from https://gitea.osmocom.org/sdr/rtl-sdr
Add a description, image, and links to the radio topic page so that developers can more easily learn about it.
To associate your repository with the radio topic, visit your repo's landing page and select "manage topics."
A common protocol structure is to have a header containing a
lengthfield, followed by data oflengthbytes, followed by additional protocol fields such as a CRC. If the length field is variable, the position of subsequent URH-specified protocol fields defined by fixed position will not be in the correct location.I do not know the best way to address this, but quick and easy way to support