btsimonh

One way I considered doing this was to store the template on the device, but construct it in the webapp. In this way, the webapp can be quite sophisticated in...

Hi Luis, a good place to start would be to populate the Wiki here. I really hate the TAS docs build process, but we could always migrate the pages &...

note the GPIO numbers most likely will not match - I would guess. Let us know how you get on with cloudcutter....

I also have units with IR on them - at least RX. Would love to get an IR blaster too, as have many ceiling lights which are IR controlled.... But.....

We've been discussing. We have a couple of issues, c++ support being one, and the other being a high res timer. Of course the C++ thing is just getting the...

For those following this topic, it's almost ready :).

hi blakadder, welcome to the party :). My initial thoughts on this were very similar to @iprak 's implementation. I imagined the device database being served off a site like...

@blakadder - I guess what I'm saying is as you are the god of TAS config pages, we'd take your lead on where to store the json, how it would...

> vendor, name, serial I like that, 'cos then it can be hierarchical if required. Maybe vendor, name, serial plus a pure descriptive which can by default be built from...

> One thing I couldn't figure out was how to configure the custom WebApp location. Using a local website would always result in [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) error which might be because my...