In the 2.8 ECP document, it specifies a new “query/icons” command. It appears that it should be “query/icon” (singular), though.
Good catch.
–Kevin
Yes, good catch. “icons” was not working for me and now I know why.
Anyone able to get the search command to work in netflix?
The search command doesn’t work yet in Netflix… The docs got a bit ahead of our release schedule in this regard.
–Kevin
Good to know.
I have question about the /query/icon command
should it be the same as the /query/apps command
GET /query/apps HTTP/1.1CRLFCRLF
GET /query/icon HTTP/1.1CRLFCRLF
or am i missing something painfully obvious?
“tdurrant420” wrote:
Good to know.I have question about the /query/icon command
should it be the same as the /query/apps command
GET /query/apps HTTP/1.1CRLFCRLF
GET /query/icon HTTP/1.1CRLFCRLFor am i missing something painfully obvious?
It should be “/query/icon/appid” and returns the HD channel icon for the specified app.
What kind of controller are you workin on Endless? I am doing control for Crestron Control Processors.
“tdurrant420” wrote:
What kind of controller are you workin on Endless? I am doing control for Crestron Control Processors.
I’m not.. I’m just curious..
I still haven’t figured out what the new touchdown, touchdrag, and touchup commands do, though. I thought it might allow for a swiping interface in the grid screen, but I couldn’t get it to do anything.
when you get a response from /query/icon is it mostly unprintable characters?
“tdurrant420” wrote:
when you get a response from /query/icon is it mostly unprintable characters?
It should a PNG or JPG. If you’re trying to view that as a string instead of as an image, it will look like mostly unprintable characters.
Ahh i get it.
So it only returns the actual picture of the app, not the dynamic link of the app pic.(rokuip.apppic.png) I wonder if they plan to do the same command at every level?
If you check the Content-Type: in the returned header it tells you the type for the data returned (eg: image/png.
What exactly do the touch commands do?
The best thing I can think of is that you send coordinates, and it simulates keypresses to that item, like in a grid interface
“brandon15811” wrote:
What exactly do the touch commands do?
The best thing I can think of is that you send coordinates, and it simulates keypresses to that item, like in a grid interface
I’d like to know this too. I assumed it would require an application to explicitly code in support for the touch commands (catching the events and handling them). If so, an example app would be great (along with accompanying example remote code).
Yes, it would be very nice 
The touch commands are not useful yet. Although the box will receive the commands, current firmware versions do not do anything useful with them.
–Kevin
“RokuKevin” wrote:
The touch commands are not useful yet. Although the box will receive the commands, current firmware versions do not do anything useful with them.–Kevin
Since the roku isn’t a touch device, as far as I know, could you tell us what they would actually do?
“RokuKevin” wrote:
The touch commands are not useful yet. Although the box will receive the commands, current firmware versions do not do anything useful with them.–KevinYou tease! :p. But seriously, thanks for the answer. Looking forward to whatever’s cooking
“brandon15811” wrote:
“RokuKevin” wrote:
The touch commands are not useful yet. Although the box will receive the commands, current firmware versions do not do anything useful with them.
Since the roku isn’t a touch device, as far as I know, could you tell us what they would actually do?
They are for the upcoming phone version of the Roku, of course! 
Hmm, Roku tablet. That’s got promise…
