Media Browser Integration

[mvallevand]

To me... mutli-channel would equate to the users Channel Group(s).....

I don't disagree, but that is how reven uses it after sub added it to the xml http://forums.nextpvr.com/showthread.php...post459690 Remember too it is possible to have client side Channel groups.

I figure NEWA should be a superset. The only use case I can think of for one channel is to provide updates during a long live tv session.

Martin

[UncleJohnsBand]

I don't disagree, but that is how reven uses it after sub added it to the xml http://forums.nextpvr.com/showthread.php...post459690 Remember too it is possible to have client side Channel groups.

I figure NEWA should be a superset. The only use case I can think of for one channel is to provide updates during a long live tv session.

Martin

I could see where depending UI (i.e. mobile view) you may only want to access a channel at a time so you would want the ability to just get a guide for one channel at a time.

I could update to parse a delimitated list like the xml return sub has if that is really what is needed.

I always struggle with doing something specific to one UI need.... vs. the client taking the data and managing it within their environment. If you are managing objects on the client like the server does... it really shouldn't be an issue.

[lukemb3]

One channel is what I wanted. A channel OID based filter would be more ideal though.

UJB - I agree and that's one of the principles of Rest that I like the most. I would never ask for you for an individualistic feature because at that point it would turn into Rpc. So a filter is just a filter. Your api doesn't have to care what the client needs it for. But you're right though, it's for mobile.

[lukemb3]

Seeing this on the latest build with SortedFilteredList

{
"ManageResults": {
"EPGEvents": [
{},
{},
{},
{
"epgEventJSONObject": {
"epgEvent": {
"OID": 1051353,

[mvallevand]

Seeing this on the latest build with SortedFilteredList

I'm using your database with my patch and not seeing that. What filter parameters are you passing?

@UJB I woke up this morning realizing that my patch still would have problems when there are no epg_events and no recurring oid and I've confirmed that this will still dumps all the recurr records when they aren't being requested.

Martin

[lukemb3]

I'm using your database with my patch and not seeing that. What filter parameters are you passing?

@UJB I woke up this morning realizing that my patch still would have problems when there are no epg_events and no recurring oid and I've confirmed that this will still dumps all the recurr records when they aren't being requested.

Martin

var filterOptions = new
{
resultLimit = -1,
All = false,
None = false,
Pending = false,
InProgress = true,
Completed = true,
Failed = true,
Conflict = false,
Recurring = false,
Deleted = false
};

[mvallevand]

var filterOptions = new

No it works fine here, even with the Chrome addon UJB suggested. What C# parser are you using? My test is with Newtonsoft.

Martin

[UncleJohnsBand]

One channel is what I wanted. A channel OID based filter would be more ideal though.

UJB - I agree and that's one of the principles of Rest that I like the most. I would never ask for you for an individualistic feature because at that point it would turn into Rpc. So a filter is just a filter. Your api doesn't have to care what the client needs it for. But you're right though, it's for mobile.

20131218-1 on server now uses channelId qyerstrng to take in the OID of the channel

[UncleJohnsBand]

I'm using your database with my patch and not seeing that. What filter parameters are you passing?

@UJB I woke up this morning realizing that my patch still would have problems when there are no epg_events and no recurring oid and I've confirmed that this will still dumps all the recurr records when they aren't being requested.

Martin

I'll step through the code and see what happens... to confirm

In manageservice when not request recurring you are still getting recurring?
For a manual recording one-off you do not get anything because there is no EPG and no recurring?

[UncleJohnsBand]

var filterOptions = new
{
resultLimit = -1,
All = false,
None = false,
Pending = false,
InProgress = true,
Completed = true,
Failed = true,
Conflict = false,
Recurring = false,
Deleted = false
};

The class you are posting isn't a complete class.... I pulled a default sortedFilterList object from /public/ManageService/Get/RecordingsSortFilterObj and set your settings and it parses through. The partial class is coming in as null.....

{
"resultLimit": -1,
"datetimeSortSeq": 0,
"channelSortSeq": 0,
"titleSortSeq": 0,
"statusSortSeq": 0,
"datetimeDecending": false,
"channelDecending": false,
"titleDecending": false,
"statusDecending": false,
"All": false,
"None": false,
"Pending": false,
"InProgress": true,
"Completed": true,
"Failed": true,
"Conflict": false,
"Recurring": false,
"Deleted": false,
"FilterByName": false,
"NameFilter": null,
"NameFilterCaseSensative": false
}