added notice
This commit is contained in:
@@ -2,6 +2,12 @@
|
|||||||
|
|
||||||
[![][cq img]][cq] [![][license img]][license]
|
[![][cq img]][cq] [![][license img]][license]
|
||||||
|
|
||||||
|
# DEPRECATED
|
||||||
|
|
||||||
|
This project is no longer maintained and has been superseded by LedD.Go.
|
||||||
|
|
||||||
|
## General
|
||||||
|
|
||||||
LedD is a multipurpose daemon for interfacing LED(s) written in python. It provides an abstract interface for effects to control any kind of LED through an backend, although its original purpose was interfacing a PCA9685 chip via i2c. Since there are multiple ways to control leds we made the decision to write LedD as open as possible to other ways of controlling leds. As a result of this decision we split LedD in a server part (this repository) and multiple clients, which can be written in any kind of language and can use a custom way to control its LEDs, as long as they implement LedD's protobuf protocol they can be controled with LedD.
|
LedD is a multipurpose daemon for interfacing LED(s) written in python. It provides an abstract interface for effects to control any kind of LED through an backend, although its original purpose was interfacing a PCA9685 chip via i2c. Since there are multiple ways to control leds we made the decision to write LedD as open as possible to other ways of controlling leds. As a result of this decision we split LedD in a server part (this repository) and multiple clients, which can be written in any kind of language and can use a custom way to control its LEDs, as long as they implement LedD's protobuf protocol they can be controled with LedD.
|
||||||
|
|
||||||
As for frontends there is only an Android app available at this time, there will be more some time in the future. (You are encouraged to write your own!)
|
As for frontends there is only an Android app available at this time, there will be more some time in the future. (You are encouraged to write your own!)
|
||||||
|
Reference in New Issue
Block a user