If you are an active member of the Red community, you will have likely been keeping track of Red’s progress through our Gitter rooms and Github repositories, but we wanted to officially bring everyone up to speed with a shiny new blog post. The team has been busy since January on many fronts, multiplexing its efforts on many different branches of development. Here is an overview of what we have been cooking and what is coming.
We are preparing to release v0.4.0 of the RED Wallet which will feature:
- Bitcoin support with both Legacy and SegWit addresses!
- Updated support for ERC-20 tokens for Ledger Nano keys (after Ledger externalized such token management to the wallet software earlier this year).
- Support for the latest firmware of the Trezor key.
- Some bug fixes.
The new wallet is currently under heavy testing, we plan to release it publicly in about a week.
The first public alpha of the C3/System compiler is coming this summer. It is still under heavy development though. C3/High has made little progress as it needs real-world use-cases from the smart contract ecosystem for modelling the DSL(s). That ecosystem has not spread around much, probably due to the so-called “crypto-winter”. As new big players are now entering the space, we are looking forward to the possibilities for providing new backends for the C3/System, like for the Libra
We will be soon releasing our ETH connector for Red. The final part missing is the integration of hardware and software key support for signing transactions on real online networks (we use private networks during development). The code for hardware key support is already there in our wallet, so we just need to integrate it inside the connector. For software keys, we have developed specific support
for them, but it relies on third-party libraries, which are currently not a good match for our single binary distribution model.
Red should offer soon a pretty good GUI backend for Linux, thanks to the community effort led by R cqls
. The last PR
for red/GTK branch weighs in at about 400 commits and covers most of View features.
The main remaining features to cover are:
- Camera widget support (already available in an experimental branch)
- Rich-text and Draw improvements
- Shape dialect support
- Some stability fixes
Here are some examples of scripts and apps using the GTK backend:
GTK theming is also supported:
The ARM backend got many improvements:
- Largely improved ARMhf (hard-float) support.
- Fixes on regressions for ARMsf (soft-float).
- Various libraries loading fixes, now all unit tests are passing again.
- New ARMhf target added to our Travis CI backend.
A few low-level features were added
, that would make it easier to write device drivers or operating systems directly in Red/System:
- Ability to save/reload all CPU registers on stack using intrinsics.
- Ability to read/write CPU I/O ports using new intrinsics.
- Ability to inline machine-code pretty much anywhere in R/S source code.
- Replacing hard native support for modulo operation on floats by the soft fmod() import.
- Smarter code completion
- Realtime syntax checking
- Goto definition support
Other WIP features
JSON format is now supported
by Red’s codec system. So it can be used in load/as
to convert JSON data back and forth to Red values. More info about its usage in the Red 0.6.5 release notes.
Shadows in Draw
Some simple shadow effects in Draw have been implemented
. They have the capabilities of the box-shadow
model of CSS.
GPIO library for Raspberry Pi
Red has supported Raspberry Pi as a compilation target for many years, but we were still lacking a proper GPIO library, which is now under development. It will be implemented as a gpio://
port for now in the port-type
branch. A dedicated library or dialect should be added also as a higher abstraction layer in order to simplify GPIO programming even further. Hobbyists and seasoned programmers will be able soon to build IoT projects on RPi easily using Red with GTK for the GUI support.
Next Red releases
0.6.5: Splitting the console and compiler
This is an important change that will be the new way to use Red and, hopefully, provide an even better experience, especially for newcomers. Not much coding is involved but we still need a prototype before giving the final go-ahead then proceeding with the code and infrastructure changes. We plan to finish those tasks during this summer (no precise ETA for now).
0.7.0: Full async I/O
Work started on this release many months ago but with a low-priority, as we have many other features to release first. The current state on the main features is:
- port! type is almost completed and already usable (e.g. the eth:// port)
- the native ports TCP, UDP, DNS should be implemented this summer.
- the async API still needs design work before being implemented.
We are setting up the last steps for the RED tokens retro-distribution (past contributions) and the first monthly distribution for new contributors. We will publish the first article in July that will provide all the rules that we have established for that process. Then shortly after, we will publish the list of the contributors who were selected according to those rules, with the reward amounts and proceed with the distribution (using the batch transactions feature of the RED Wallet).
For example, as part of our tokens rewarding program for contributors, R cqls should receive a good amount of them in the next distribution,
The road ahead…
The most notable next planned milestones are:
- RED Wallet 0.4.0 in July.
- C3/System alpha release in August!
- Red/Android beta release in September!
- Red/Pro for New year!
- Red 64-bit will be split into two phases:
- cross-compiled from 32-bit platform: end of the year
- toolchain ported to 64-bit: 2020
We plan to give more information about each of those big new additions to the Red family this summer.
As several development tracks are coming to fruition in the next couple of months, new articles should come up more frequently.
Go Red Go!