My guess is they had a closed beta for a few developers that they sent dev units to a few weeks ago so they could test it out and make sure there were no problems. I know for a fact that was the case with the Roku 2. I have no idea what the selection criteria entails, so it could be somewhat random....

Hey kbenson! Long time, no rearing of your head! Yeah, I lurk every few months with a few specific searches to see if I've been called out or anyone's mentioned any of my pet projects, but generally that doesn't happen often. ...but Roku contacted me recently re: RAF, and the numbers look interesti...

That's interesting. I think I'll actually be doing some work on the Roku in the near future, so I'll try to take a look and see what's happening and try to fix it. That said, if Roku now provides a native JSON serialization method, that's likely much better than the one implemented in librokudev, wh...

As commentary, some of the corollaries will be: ⋅ Never loop over big roList with index access (for i=1 to a.count(): ... a[i] ... ) ⋅ In fact, don't use roList, except in a rare event that calls for it; e.g. queue (RemoveHead/AddTail) or dequeue ⋅ Don't use shift/unsh...

Yeah, we implement a TAP library for testing, and used it for some of the other tools. For example: see https://github.com/rokudev/librokudev/blob/master/source/librokudev/source/tests/test_rdTAP.brs which is rdTAP testing itself, and https://github.com/rokudev/librokudev/blob/master/source/librokud...

TheEndless wrote:

Even if you did have the time, you wouldn't be able to do it. The motion controls aren't exposed to Brightscript (yet?).

Huh. I should really be more surprised about that than I am.

from the Forum Rules: ... In general, if a thread is more than six months old, it will be best for our moderators if you generate a new thread, to prevent confusion. With all due respect, I don't think that should apply to channel specific threads, created by the developer, like this one. Indeed. I...

Efficient dissemination of changes/fixes/features in new firmware releases has always been a problem. At least they have a wiki now, so maybe they can make some use of it to help this.

If you have to calculate the line length yourself, you may find hints and/or suitable pseudo-code here: viewtopic.php?f=34&t=35607&start=0&hilit=wrap

Since 4.5 or so firmware, you can rotate to any angle. Hmm, then I guess I have some work to do, don't I? ;) I was actually testing this out the other day.. don't get your hopes up too high... ;) Also, still limited to 90 degree rotations on the Roku 1. Actually, I just checked some old email, and ...

RokuJoel wrote:

Since 4.5 or so firmware, you can rotate to any angle.

Hmm, then I guess I have some work to do, don't I? ;)

It's worth noting (just in case you are using it) that rotation in roScreen is not equivalent to rotation in roImageCanvas. Last time I checked, roScreen could only rotate by 90 degree increments. P.S. We would *happily* write a compatibility library so you could use roScreen like roImageCanvas if r...

Somewhat off topic: ⋅  I'm getting warm fuzzies about all this. It's awesome that rdPNG has been of use since we put it out. ⋅  As requested originally (years ago), shift and xor operators/functions from Roku would help a lot. ⋅  The optimizations found are really inter...

You're welcome to add my code to librokudev, and make any changes to it that you see fit. Let me know if there's anything I need to do to make that happen. Since rdJSONParser has a different interface from my code and is faster for smaller inputs, even though it doesn't handle all JSON data, you mi...

I ran some tests on my Roku 1 to compare execution times for the different parsers using the Twitter API, changing the value of rpp to return different numbers of results: http://search.twitter.com/search.json?q=roku&rpp=1&include_entities=true&result_type=mixed rpp=1 => 2,304 bytes. JS...