Your Digital Media Has Never Looked So Good

 
belltown
Posts: 1445
Joined: Thu Dec 09, 2010 1:43 pm
Contact:

Re: SDK documentation: links to fix, missing/broken/etc

Wed Nov 30, 2016 12:15 am

In the Fields section of the Scene Graph Audio component in the Scene Graph XML Reference, errorMessage should say errorMsg.

(PS. rNB: fixed)
https://github.com/belltown/
 
EnTerr
** Valued Community Member **
Topic Author
Posts: 3834
Joined: Sun Jan 02, 2011 2:41 am

Re: SDK documentation: links to fix, missing/broken/etc

Thu Dec 08, 2016 3:22 pm

Needs to document somewhere that NUL (U+0000) characters are not supported in String and roString - i.e. cannot be embedded, internalized or externalized. In particular importing external entity with embedded \0 (by means of reading text file, parsing JSON, URL transfer or byte array) in all likelihood will result in the text ended prematurely at the first \0 occurrence.

See viewtopic.php?f=34&t=97717 thread for discussion.
 
EnTerr
** Valued Community Member **
Topic Author
Posts: 3834
Joined: Sun Jan 02, 2011 2:41 am

Re: SDK documentation: links to fix, missing/broken/etc

Sat Jan 07, 2017 11:17 am

fixed.
roBitmap doc and examples need updating to show that "PHY:/" prefix is now required,
see https://forums.roku.com/viewtopic.php?f=34&t=98497 for discussion
 
User avatar
destruk
Posts: 2504
Joined: Sat Dec 18, 2010 4:58 pm

Re: SDK documentation: links to fix, missing/broken/etc

Tue Mar 07, 2017 12:12 pm

The FastVideoStart.zip sample file has some files in it saved as "Read Only" -
just an FYI - if we're trying to learn from this and edit the sample files they should not be saved as read-only as a courtesy to those trying to learn.
The manifest is fine but it appears everything else needs the read-only flag toggled to edit.

https://sdkdocs.roku.com/download/attac ... 813&api=v2
 
User avatar
destruk
Posts: 2504
Joined: Sat Dec 18, 2010 4:58 pm

Re: SDK documentation: links to fix, missing/broken/etc

Tue Mar 07, 2017 12:59 pm

In Simple_Grid_with_Details_and_Video.zip and also in Simple_Grid_with_Video.zip
In components/screens/loadingindicator.brs -

Function getParentWidth() As Float
If m.top.getParent()<>invalid And m.top.getParent().width<>invalid
Return m.top.getParent().width
Else
Return 1270
End If
End Function

Shouldn't that return 1280 instead of 1270 if the parent is invalid?
 
User avatar
destruk
Posts: 2504
Joined: Sat Dec 18, 2010 4:58 pm

Re: SDK documentation: links to fix, missing/broken/etc

Tue Mar 28, 2017 3:40 am

For Roku Global Search, the non-TMS feed validator xsd needs to be updated to match the SDK documentation --
https://sdkdocs.roku.com/download/attac ... 356&api=v2

Specifically - the License values -
"The type of license terms for the video content item. Must be one of the following (can either be initial capitalization or all lowercase):
free
Free
rental
Rental
purchase
Purchase
subscription
Subscription"

The xsd only allows for all lowercase.


Also on the metadata charts -
https://sdkdocs.roku.com/display/sdkdoc/Roku+Search

series/originalAirDate --- Optional --- Optional but very important. We recommend that you provide this.
episode/airDate --- Optional --- Optional but recommended. This is helpful for matching and such.

It would be nice to have a sample value for these in the chart like we see for the birthday/deathday of an actor or cast member.  The xsd says it will accept either YYYY/MM/DD or MM/DD/YYYY
 
User avatar
destruk
Posts: 2504
Joined: Sat Dec 18, 2010 4:58 pm

Re: SDK documentation: links to fix, missing/broken/etc

Tue Mar 28, 2017 12:59 pm

Along the same lines, it mentions short-form content will not be indexed, but it doesn't define what short-form content is.  Roku support says any content less than 15 minutes long.  Can that be noted?
 
User avatar
destruk
Posts: 2504
Joined: Sat Dec 18, 2010 4:58 pm

Re: SDK documentation: links to fix, missing/broken/etc

Tue Apr 04, 2017 9:09 am

GetPartialUserData

This would be better if it was more consistent.
GetPartialUserData("email") returns email - that is ok
GetPartialUserData("firstname") returns firstname - that is ok
GetPartialUserData("lastname") returns lastname - that is ok
GetPartialUserData("city") returns city - that is ok
GetPartialUserData("state") returns state - that is ok
GetPartialUserData("country") returns country - that is ok

GetPartialUserData("zipcode") returns zip -- WHY not zipcode?
GetPartialUserData("phonenumber") returns phone -- WHY not phonenumber?
GetPartialUserData("street")  returns street1 and street2 -- suggest you add a request value of GetPartialUserData("street1,street2") for consistency.

It's like prior history where some screens use "SetPort" while others use "SetMessagePort", and no screen supported both methods, and then you tried fixing it in newer firmware but didn't release the firmware update for all devices IIRC.
 
User avatar
destruk
Posts: 2504
Joined: Sat Dec 18, 2010 4:58 pm

Re: SDK documentation: links to fix, missing/broken/etc

Tue Apr 04, 2017 9:23 am

The online SDK Wiki appears to have removed SetPort from all pages except ifSocketAddress -- however, RokuMarkN stated -
"You can use SetPort on non-legacy devices. You don't need to test for legacy and call SetMessagePort."

It's probably another reason you want to erase all the older components - just I hope you are more careful with coding in the future.  If routines are buried away in the firmware where none of us can modify them - like roChannelStore, or your array sorting, and you screw them up without proper QA testing and push them into the wild, like the few remaining gridscreen bugs you aren't going to ever fix, then it hurts everybody.  Why does it take 7+ seconds to do a purchase with the Roku Billing system anyway?  If any delay in our channel code we submit for certification of 3 seconds requires a 'Busy" dialog or animation, then the roChannelStore component should require the same simply for consistency.
 
tim_beynart
Posts: 171
Joined: Wed Jul 15, 2015 8:30 am

Re: SDK documentation: links to fix, missing/broken/etc

Wed Apr 12, 2017 10:05 am

RAF documentation for the Ad Structure is not consistent with the example in ServerStitchedAdSDK1Sample.
IN https://sdkdocs.roku.com/display/sdkdoc/Integrating+the+Roku+Advertising+Framework#IntegratingtheRokuAdvertisingFramework-AdStructure, the pods element does not document a tracking array. However, in the example code the pods contain an empty tracking array.
This is confusing. Will RAF honor this undocumented array? BTW I'm implementing RAF for server side ad insertion.

From the sample code, in a file called MixedSttitchedAds.json
[
  {
    "ads": [...],
    "duration": 90,
    "rendersequence": "preroll",
    "rendertime": 0,
    "tracking": [],
    "viewed": false
  },


From the wiki:

adPods : [
   viewed : Boolean,
   renderSequence : "preroll" | "midroll" | "postroll",
   duration : Float (in s),
   renderTime : Float (in s),
   backfilled : Boolean,
   ads:[...]
   ]

(edit)
Furthermore, the "required" adserver parameter for the ad object is missing from the example JSON:
      {
        "companionads": [...],
        "duration": 30,
        "streamformat": "brightline",
        "streams": [
          {
            "mimetype": "application/json",
            "url": "https://a.brightline.tv/?id=ROKU_RAF_1&ver=%%SDK_VER%%&cb=%%CACHEBUSTER%%&mblist=2450X,2500X"
          }
        ],
        "tracking": [...]
      }
 
joetesta
Posts: 589
Joined: Wed Apr 20, 2011 11:48 am

Re: SDK documentation: links to fix, missing/broken/etc

Wed Jun 14, 2017 5:14 pm

On https://blog.roku.com/developer/2016/03 ... -tutorial/
under Sthree resources, the link is broken to 
aspiring
 
tim_beynart
Posts: 171
Joined: Wed Jul 15, 2015 8:30 am

Re: SDK documentation: links to fix, missing/broken/etc

Tue Jun 20, 2017 7:04 am

BifDisplay node is mentioned in Video fields, but is not fully documented. No examples provided.
 
joetesta
Posts: 589
Joined: Wed Apr 20, 2011 11:48 am

Re: SDK documentation: links to fix, missing/broken/etc

Wed Jul 12, 2017 12:25 pm

On this page https://sdkdocs.roku.com/display/sdkdoc/Button
are incorrect default values for iconUri, focusedIconUri

ref: https://forums.roku.com/viewtopic.php?f ... 80#p564280
aspiring
 
joetesta
Posts: 589
Joined: Wed Apr 20, 2011 11:48 am

Re: SDK documentation: links to fix, missing/broken/etc

Wed Jul 12, 2017 12:29 pm

Additionally, for Button if using an image with a size larger than maxwidth, if  minWidth is not set, seems it's defaulting to the width of the image and therefore minwidth must be set to decrease the size. (what I would expect maxwidth to do)
if I set maxwidth only (and no minwidth), the button is much wider than the maxwidth value.  if set minwidth only (and no maxwidth), the button is the width of minwidth.  seems something's mixed up here, or is it just me?
thanks
Last edited by joetesta on Thu Jul 13, 2017 1:02 pm, edited 1 time in total.
aspiring
 
joetesta
Posts: 589
Joined: Wed Apr 20, 2011 11:48 am

Re: SDK documentation: links to fix, missing/broken/etc

Thu Jul 13, 2017 1:00 pm

https://sdkdocs.roku.com/display/sdkdoc ... terpolator
Seems to me the description (Use) for fieldToInterp is wrong, says should be separated by colon but that doesn't work (for me on Roku 3, targetting opacity), needs to be separated by a dot;

separated by a colon. For example, "title:width"  <---- what's there now

separated by a dot. For example, "title.width"    <---- what it should probably be

(PS. rNB: fixed)
aspiring

Who is online

Users browsing this forum: No registered users and 5 guests