Update 2022-12-20-draft.md
This commit is contained in:
parent
402c4e7234
commit
ed130a7024
1 changed files with 22 additions and 18 deletions
|
|
@ -296,45 +296,49 @@ What is the team up to this week? Let’s check in!
|
|||
|
||||
**Dan**
|
||||
|
||||
[](url)
|
||||
|
||||
text - [site](url).
|
||||
I've been researching and fixing a variety of issues for the CircuitPython 8.0.0 release. Some issues were fixed easily, some were not reproducible, and some I moved forward, past 8.0.0. We have about a dozen issues open: the number goes up and down, but the trend is down!
|
||||
|
||||
**Kattni**
|
||||
|
||||
[](url)
|
||||
This week I collaborated with Liz to publish the [EYESPI Breakout Board](https://learn.adafruit.com/adafruit-eyespi-breakout-board) guide. It has everything you need to get started with your EYESPI breakout. If you picked one of these up and need more info or a little help getting started, check out this guide!
|
||||
|
||||
text - [site](url).
|
||||
The next guide is a scrolling countdown timer using three quad alphanumeric STEMMA QT display backpacks, and a QT Py ESP32-S2. You can customise it for any event you would like to count down to, and it scrolls the time left until that event, as well as displaying any message you choose when the event starts.
|
||||
|
||||
**Melissa**
|
||||
|
||||
[](url)
|
||||
|
||||
text - [site](url).
|
||||
I've been out most of the past week due to the death of a close friend. Prior to that I was working on updating code.circuitpython.org and rewriting the USB workflow to make use of the File System Access api. The initial pull request was merged in and I have been working on polishing the changes up to make the USB workflow even more usable.
|
||||
|
||||
**Tim**
|
||||
|
||||
[](url)
|
||||
|
||||
text - [site](url).
|
||||
I have been working on helper functions that generate lists of colors representing a gradient between two or more given input colors. I've implemented 3 different types of increasing complexity: linear, polylinear, and bezier gradients. I have experimented with visualizing with displayio and vectorio. I'm hoping to use the gradients with neopixels and led_animation ultimately as well.
|
||||
|
||||
**Jeff**
|
||||
|
||||
[](url)
|
||||
The `settings.toml` change I mentioned in the last newsletter has finally been merged, and will be in *beta.6* and newer! Aside from that, I worked on some hidden problems with building CircuitPython that was a pre-existing problem that was exposed when a new version of isort was released.
|
||||
|
||||
text - [site](url).
|
||||
Here's a quick tutorial on `settings.toml`:
|
||||
* Just like the removed `.env` support, these values are used e.g., to set up the web workflow, or can be retrieved with a call to `os.getenv()`
|
||||
* CircuitPython supports a subset of the full toml syntax.
|
||||
* It supports simple string and integer values
|
||||
* It supports comments which start with "#"
|
||||
* Each line should be of the form "NAME=value".
|
||||
* String values have to be enclosed in double quotes (`NAME="string value"`). You can directly use non-ASCII characters like œ or 🎉 as long as you save in UTF-8 format. Or, you can use non-ascii characters with a `\uxxxx` 4-digit code.
|
||||
* Integers must *not* be quoted. They may be in decimal or hexadecimal format only. (`NAME=42`)
|
||||
* A non-supported value type *that is written on a single line* will not cause a compatibility problem. However, trying to retrieve the value will generally result in an exception
|
||||
* A non-supported value *that is written on multiple lines* (like triple quoted strings) can cause a problem if one of the contained lines looks like a supported `NAME=value` line.
|
||||
* Parsing ends at a line that starts with `[`.
|
||||
|
||||
We'll be updating our guides and sample code that referred to `.env` to reflect the new `settings.toml` way of doing things shortly after the release of beta.6.
|
||||
|
||||
**Scott**
|
||||
|
||||
[](url)
|
||||
|
||||
text - [site](url).
|
||||
This week I've continued working on the coprocessor/ULP support for the ESP32-S2 and S3. I've been testing a ULP program that reads a pin input and then wakes up the main core when the pin goes low. It now works during pretend deep sleep but not full deep sleep. Once I get that working, I hope to send out the pull request.
|
||||
|
||||
**Liz**
|
||||
|
||||
[](url)
|
||||
I worked on the [EYESPI breakout board guide](https://learn.adafruit.com/adafruit-eyespi-breakout-board) with Kattni. It gives a basic overview on how to use the EYESPI breakout and EYESPI connector port on the newer SPI displays in the shop. I'd always avoided SPI displays in the past because of the wiring but this breakout with the FPC cable makes everything a lot simpler. I think folks will especially find this standard to be especially useful for cyberdecks.
|
||||
|
||||
text - [site](url).
|
||||
I also worked on the [MOSFET Driver Learn Guide](https://learn.adafruit.com/adafruit-mosfet-driver). This breakout has the MOSFET diode circuit that is needed for driving things like high power LED's, motors and solenoids. The terminal block onboard is very fancy and provides a sturdy connection.
|
||||
|
||||
## Upcoming events!
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue