Insignia Infocast 8" Touchscreen $99

@damage,

I tried out your chumby app, but I can't get it to do anything other than have it sit on the black screen where it says configuring. I have put in the address of my configuration file: http://10.0.1.4:8081/chumby/chumby.xml I know this is right because I can access it from other machines on my network. You also mentioned needing a crossdomain.xml file. What is this and what do I do with it?

Thanks for the app and any help.
 
this should help you out http://kb2.adobe.com/cps/142/tn_14213.html http://forum.chumby.com/viewtopic.php?pid=11020#p11020
 
Thanks. I have put a crossdomain.xml file in the root of my server: http://10.0.1.4:8081/crossdomain.xml:

Code:
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">

<cross-domain-policy>
  <allow-access-from domain="*" />
</cross-domain-policy>

Still the same results with that. I also tried to put it in the same directory as the configuration xml with the same results. Is that what the crossdomain.xml should look like?

for referrence, how long can i expect to see the configuring screen before it loads?
 
Thanks. I have put a crossdomain.xml file in the root of my server: http://10.0.1.4:8081/crossdomain.xml:

Code:
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">

<cross-domain-policy>
  <allow-access-from domain="*" />
</cross-domain-policy>

Still the same results with that. I also tried to put it in the same directory as the configuration xml with the same results. Is that what the crossdomain.xml should look like?

for referrence, how long can i expect to see the configuring screen before it loads?

your crossdomain.xml file looks fine to me. it shouldn't take more than a second or two. depends on how large the xml file is. have you tried using my sample xml file on your server? it could be there's something wrong w/ the syntax/structure of your xml file. the app was slapped together so it has no error checking.
 
Yes, I am using the sample xml file. Does the address of the file need to be externally accessible? Maybe using a non standard port is a problem?
 
i uploaded a new version to print out the URL next to the configuring message so you can see if it got the correct URL. one thing i forgot to ask, is the crossdomain.xml file in the root directory of your webserver? also, if you go back to the chumby site, manage the channel & customize panel builder again, put http://www.doghouselabs.com/chumby.xml which is the default address and see if the test panel comes up. it should since the app preview on chumby.com shows the test panel.
 
So it looks like the problem was was my webserver. I am using a pretty non-standard one that is embedded in another HA app. I installed XAMMP and hosted the config file there and it works. Thanks again for the app and all the help.
 
I had an idea for your Panel Builder app. Add the ability to put set a button's action to be a different configuration xml file. Then when the button is pressed it would render that screen. This way you could have multiple screens with more control and navigate between them easily.
 
I had an idea for your Panel Builder app. Add the ability to put set a button's action to be a different configuration xml file. Then when the button is pressed it would render that screen. This way you could have multiple screens with more control and navigate between them easily.

i actually have this working in a private app but haven't had the chance to migrate it. at the bottom is the thumbnail from my private chumby app for a lighting panel i'm debugging. the picture's really small but that's all i have access to here @ work. the app has a row of buttons at the bottom that select a different room via loading a different xml file (it actually just passes a different request string to a php script and the script generates the xml file on the fly - so it's really just 1 php script that creates multiple xml files). the problem is the infocast cpu is slow parsing the xml, it takes a couple seconds for the new screen to show up (similar to what happens when panel builder starts up). i spent several hours trying to optimize the parsing & the xml file structure but it's not much better so it's on the backburner for now.
 

Attachments

  • 6268F0E6-2E8E-11E0-88EC-0021288E6F90.jpg
    6268F0E6-2E8E-11E0-88EC-0021288E6F90.jpg
    1.9 KB · Views: 34
optimized the XML parsing a little better, but there's still a lag between screens: http://goo.gl/yfi3n
unfortunately, i don't think it's going to get much better. added support for a new button type called "menu":

Code:
    <button type="menu">
      <btncolor>0x555555</btncolor> 
      <btnborder>0xffffff</btnborder> 
      <labelsize>17</labelsize> 
      <btnwidth>60</btnwidth> 
      <btnheight>30</btnheight> 
      <btnx>250</btnx> 
      <btny>35</btny> 
      <label>NewXML</label> 
      <labelx>125</labelx> 
      <labely>30</labely> 
      <labeloffsetx>0</labeloffsetx>
      <labeloffsety>0</labeloffsety>
      <action>http://192.168.1.2/test2.xml</action> 
    </button>

action specified is the URL to the new XML file & screen. no limit on the number of menu buttons you can have.
 
Back
Top