alpha
/
Kaleidoscope
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
370 Commits
34 Branches
19 Tags
23 MiB
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'aa9c30fa5a'
${ noResults }
Commit Graph

18 Commits (aa9c30fa5ae501d796e8694a311d3ed865768692)

Author SHA1 Message Date
Jesse Vincent 59fbee7591 Beginning to implement the ATTiny based firmwaare
9 years ago
Jesse Vincent 3c223d4b3d better implementation/general separation for keyswitch matrix
9 years ago
Jesse Vincent 0be763e1d0 We're not using WS2812 in the new implementation
9 years ago
Jesse Vincent b96c06338f At least for now, use Scott Torborg's http://web.mit.edu/storborg/Public/hsvtorgb.c
9 years ago
Jesse Vincent a95308cc47 Move the HARDWARE_IMPLEMENTATION macro into the implementation defintion
9 years ago
Jesse Vincent 2876509076 Selectable implementations that appear to work.
9 years ago
Jesse Vincent 70d892f2c7 wip implementation select
9 years ago
Jesse Vincent 608cdb0273 We don't need to declare that object here
9 years ago
Jesse Vincent 01aae54a80 Move header includes into header file
9 years ago
Jesse Vincent c59a6a80d6 Remove an unused API
9 years ago
Jesse Vincent 2d071e7109 Don't need that layer of indirection
9 years ago
Jesse Vincent 38de84caa5 rebuild the implementation class for the new model01
9 years ago
Jesse Vincent 3ccfb27fc5 Move more data into the class definition
9 years ago
Jesse Vincent 7cd1286810 simplify the 'setup' API for the hardware
9 years ago
Jesse Vincent 9bb0e64f4a move "scan_matrix" into the implementation specific class, since it looks like it'll be very different between beta and production
9 years ago
Jesse Vincent e1c7069c80 A first, very hacky way to plug backend hardware implementations that shows off just how little I know about C++
9 years ago
Jesse Vincent 0400670487 Rename the beta implementation to be Model01Beta
9 years ago
Jesse Vincent 0f92dc4943 first steps to pluggable implementations
9 years ago