FAQ - This post is taken from a list of the most frequently asked questions during the pre-release of the WDK
The documentation I have describes a tv object which supplies OEM (tv.system.oem) among other things. Seems that the object tv is undefined in the emulator, though, so I can't access any of the values described in the documentation (v0.93 p258). Is this something that is not yet implemented but will be available in the next release?
What I need is a way of getting the OEM and the device model number.
Also, I would very much appreciate a way to get a unique identifier, preferrably the device's mac address. I know there is something in the docs describing an identifier---tv.system.devideId---but I'm not quite sure what that's supposed to represent. Is it the mac, a serial or some other identifier?
Last, I've been tinkering with starting and stopping widgets from other widgets. What I want to do is to have a button in WidgetX that closes WidgetX and opens WidgetY when I press it. Is this possible, and if so---how? The docs describe something on pages 223-226, but again the version I have doesn't really say anything at all about how and where to use that functionality. Have you got any take on this?
1. How do I identify a device OEM and model?
2. How can I get the device's mac?
3. How can I open one widget from another widget?
The tv.system.oem object is not fully available yet. In the future, you will be able to access the specific gallery, UI and any other unique conditions.
The unique identifier is offered in our deviceID API's but Samsung is currently not taking advantage of it but other OEMs are considering it. Currently no one is offering unique IDs or MAC addresses. If you really need to identify a unique device you can issue your own cookie when the user does a simple registration. You can have JS generate and store a GUID since JS has random number generators. If it's not required for security purposes that should work fine for a unique ID. Please let me know what you are trying to use this function for and I can help direct you.
Inter widget communication is currently not supported in the engine. It is high on our roadmap to address this year, but you should plan this first phase to include a way to communicate with another widget (e.g., launch another widget, send events or messages to other widgets etc.)
