"kbenson" wrote:
That's interesting. I think I'll actually be doing some work on the Roku in the near future, so I'll try to take a look and see what's happening and try to fix it.
That said, if Roku now provides a native JSON serialization method, that's likely much better than the one implemented in librokudev, which is somewhat hacky.
If anyone has any requests, comments or suggestions for librokudev, please let me know.
"TheEndless" wrote:
Hey kbenson! Long time, no rearing of your head!
"TheEndless" wrote:
Unless I'm mistaken, I believe the librokudev JSON implementation was actually based on our collaborative Roku forum efforts several years ago (read: my appallingly bad regex, and your refinements), so I have decided to take offense to your "somewhat hacky" comment, even if it is accurate! 😉
We’re upgrading Roku Community to bring you a faster, more mobile-friendly experience. You may notice limited functionality or read-only access during this time. You will not be able to log in or post new comments or kudos during this time. Read more here.
Planned Downtime:
Community will be unavailable for up to 24–48 hours during the upgrade window during the week of May 12 and you may notice reduced functionality.
In the meantime, for additional assistance, visit our Support Site.
Thanks for your patience — we’re excited to share what’s next!