I just stepping into this world of apps and must say I am lost already! I am sure in due time I will get my bearings rolling here. I have been looking for reference and so far have not found anything on this, has anyone created an app connecting to OData.org type feeds? I have a service that display real time data and currently display the data through a desktop app. I would like to do the same for mobile devices, really looking forward to diving in here.

Hello @DBS, Welcome to buzztouch! I thought I remember somebody trying the OData.org stuff, but I can't recall for sure. I bet they'll pipe up if they have, because I think it was one of the more active members. Don't hesitate to post any questions you might have! Mark

Thanks Mark!

oData.org is a protocol, a standard, a method of representing info. It's for sure a perfect way to consume meaningful information in a mobile format. The 64-million-dollar-questions will be... a) What type of data are you displaying b) How much data are you interested in "downloading" and saving locally on the device c) How "real time" is it. All devies are very capable of making simply HTTP requests for data. Lots of the buzztouch plugins already do this so you can easily glean some insights on "how" the do it by reviewing the code for a given screen after downloading your project. I'm interested in learning more about what you're attempting and will do what I can to point you in the right direction. In the meantime...some homework.... a) Try to figure out how the JSON items in the config.txt data are represented in the app. Have a look at the BT_item.m file (assuming iOS here) to see what a simple "object" looks like. b) Imagine what your "custom object" may look like so you can create it when the time comes. I'm guessing you'll be working with some sort of object that represents each "thing" your displaying. c) Have a look at one of the plugins...say the BT_screen_menuButtons.m file and browse the "loadData" method. You'll see how the JSON data is parsed (looped through) and each item in the JSON is "converted" into a BT_item. In your case, you'll be parsing the JSON from oData.org and transforming it into your custom object. When you get a list of objects (holding the JSON for each thing) you'll be able to do custom, neat things with the data - like turn it into meaningful information. Following this post...

Thanks David, I will check out your advice. Not familiar with JSON so that will be a learning curve too. Plan for iOS, Android, Win8 and other devices. The data has unique identifiers for each timing event. There has been as much 1500 data streams in an event period of 72 hours.