support of jsonp about pebblejs

[Meiguro]

According to their docs, it looks like by not specifying ?callback=<identifier>, OpenRemote will respond with plain JSON. They just decided to show JSONP as their primary use case.

It's possible that some of their endpoints only support JSONP. You're not out of luck. You can specify, for example, a function "receivePanels" such as var receivePanels = function (x) { console.log(x); }. Then in your ajax call, you would eval their response. This is evil, but that is how JSONP works, and why I don't recommend using JSONP. The example ajax:

ajax(
  {
    url: 'http://localhost:8080/controller/rest/panels?callback=receivePanels'
  },
  function success(data, status) {
    eval(data);
  },
  function failure(error, status) {
    console.log('Error: ' + status + ' ' + error); 
  }
)

If CloudPebble does not let you use eval, you may use the new Function(source)() trick. For the function trick, if your callback function is locally scoped, you will need to pass it.

Alternatively, if their JSON in the JSONP response is well formed, you may simply regex match their JSON out of the response data. This is also nasty, but not as evil. For example /\w+\s*&&\s*\w+\((.*)\)/. With the first match group, you can then call JSON.parse on it.

Let me know if any of these solutions work for you. I may decide to add JSONP support, but I hope that JSON APIs replace them.

[gwijsman]

Hi Meiguro,
Thanks for your answer that really helped me!
I tested the evil solution (for me the easy way...)
Removing the callback is not helping me because OpenRemote supplies XML (Talking about evil...)
The suggested recievePanels function gets the nicely parsed object as parameter. Evil or not it works for me!
It must be possible to configure this way a set of switches in OpenRemote and give your pebble watch a dynamic interface to control your domotica.
Thanks for developing and maintaining pebble.js! great initiative!