"RokuMarkn" wrote:
There is an undocumented global function which does what you want:
FormatJSON(aa as Object) as String
I'm not sure why this isn't documented, probably an oversight.
--Mark
"TheEndless" wrote:"RokuMarkn" wrote:
There is an undocumented global function which does what you want:
FormatJSON(aa as Object) as String
I'm not sure why this isn't documented, probably an oversight.
--Mark
Wow.. that should definitely be documented! I've written and refined three different versions of the same functionality so far in BS.. 😛
Any chance it's also available in the 3.1 firmware?
"TheEndless" wrote:"RokuMarkn" wrote:
There is an undocumented global function which does what you want:
FormatJSON(aa as Object) as String
I'm not sure why this isn't documented, probably an oversight.
--Mark
Wow.. that should definitely be documented! I've written and refined three different versions of the same functionality so far in BS.. 😛
Any chance it's also available in the 3.1 firmware?
"malloys" wrote:
Bump.
Roku support...
Any answer on the 3.1 question?
Also, it appears the FormatJSON global function is still not in the online docs. - Can we get the docs updated?
BTW... it's hard to be 100% sure the docs haven't been updated, since the developer wiki's dashboard functionality that listed recent changes went missing sometime in the last month or two - any chance we can get that reinstated? That was a very useful feature.
"EnTerr" wrote:"malloys" wrote:
Bump.
Roku support...
Any answer on the 3.1 question?
Also, it appears the FormatJSON global function is still not in the online docs. - Can we get the docs updated?
BTW... it's hard to be 100% sure the docs haven't been updated, since the developer wiki's dashboard functionality that listed recent changes went missing sometime in the last month or two - any chance we can get that reinstated? That was a very useful feature.
Useful it is indeed, though in a corner hard to find: http://sdkdocs.roku.com/pages/recentlyu ... key=sdkdoc
"RokuJoel" wrote:You could tag such features as *experimental* or similar in the documentation(with a formal statement that they're subject to change/removal) and then receive potentially useful feedback on them like bugs, enhancement requests, and discussion of the feature documentation, all prior to having to officially support it. The way I see it, if it's going to be discussed in the forum anyway, it might as well be properly organized. There's a lot of precedent for documenting not-yet-released features in, just for instance, web browsers and web technologies.
Before functions like FormatJSON are published in the documentation, they need to go through an API review process. Anything that hasn't, is potentially subject to change, so basing a public channel on an upublished function is somewhat risky.
- Joel