[WIP] New Confluence Skin for XNEWA

[pkscout]

I've made some changes to get the images into the detail screens (the size is arbitrary, so I just made the dialogs bigger). If you add images to the lists, there is clearly space for them now, and I can add them.

t haven't had a chance to look at the right click issue, and I'm leaving for a trip in a few hours. I'll look at that when I get back next weekend. I'll post an update after I see if I can fix that.

P.S. I didn't see the updated XNEWA_Connect.py.

[smajor]

Wow. Looking forward to this. I'm just a sucker for a unified appearance. The XNEWA is what makes NPVR/XBMC work. Still too many unconnected pieces on the XMBC side for a true PVR experience IMHO. Fantastic work graphically and programmatically, both of you.

[mvallevand]

Let me know when you get back pkscout. I made a few more changes to support changing priority of recurring recordings, and made a few other small changes. I added a couple of string too for this but I put them in starting at 32001 to avoid getting in your way.

Martin

[pkscout]

OK, I'm back. Unless I missed some strings, I'm done with the localization, so you should be able to slot the strings in where ever you want. I'm attaching beta4 of what I've got.

Updates:
- added images to detail screen
- fix in confluence skin so that right clicking consistently initiates BACK action
- fix in conflicts.py so BACK action is properly recognized
- additional logic in search.py so that passing an empty search string aborts search

The last two are little bugs I found. conflicts.py didn't have quite the same logic as the other scripts for detecting the BACK action, so you could use the ESC key to get out of that screen, but not the DELETE key (which I think initiates the BACK action). search.py would accept an empty string as a search term (e.g. if you just hit DONE on the virtual keyboard without typing in any text), and that caused things to get stuck at WORKING (I suspect it would have returned results eventually). Anyway, now an empty string behaves the same as if you canceled out of the virtual keyboard.

[pkscout]

Quick question/request. I noticed that the Recurring Recordings list doesn't appear to be sorted. I see in the code that it is sorted by priority, but all the priorities are 0, and I don't see anyway in any of the interfaces (NextPVR client, XNEWA or NEWA) to set a priority. It would be nice to either have it sorted by title or have an option to sort by title, channel, or priority (sort of like the sort options for All Recordings. I changed mine to sort by title, but adding sort options looked like a bit more than I wanted to bite off without at least floating the idea here on the forum.

[mvallevand]

Quick question/request. I noticed that the Recurring Recordings list doesn't appear to be sorted. I see in the code that it is sorted by priority, but all the priorities are 0, and I don't see anyway in any of the interfaces (NextPVR client, XNEWA or NEWA) to set a priority.

Right it is not supported in NEWA right now, it slipped by UJB and I in 3.2.9. You can get them showing with a quick change to the NEWA source. In loadRecurringInfo() in webServiceEPGEvent,cs add this

recur.Priority = recurr.Priority;

the restart the recording service. Even with that you cannot set priority but UJB has added it for his next release, PM him for details on his ftp server if you are interested. For me his beta breaks All Recordings.

It would be nice to either have it sorted by title or have an option to sort by title, channel, or priority (sort of like the sort options for All Recordings. I changed mine to sort by title, but adding sort options looked like a bit more than I wanted to bite off without at least floating the idea here on the forum.

No problem with a sort consistency is good I implemented priority raise/lower on the recurring screen itself so the outer sort shouldn't matter.

Attached is my update to your beta4. I included a patch file if you are running from a local git.

Martin

[pkscout]

OK, here's a beta5. It includes all the stuff you sent me plus the option to sort the recurring recording list by title (default), channel, or priority. I used the same control number as the sort for all recordings and error trapped it so that if the control doesn't exist (as it doesn't in the Default skin) everything will still work.

[mvallevand]

Thanks. Did you contact UJB? I have a solution to the changed SOAP call causing the problem.

Martin

[pkscout]

I didn't. I only have one Windows machine on which to run NextPVR, and it's the production machine. I try and stay away from beta stuff on there, as my wife will kill me if we miss recordings. '-)

If the long term plan is to ask NPVR to send the lists sorted a certain way, then we can just consider the post sorting I did an interim fix.

[mvallevand]

I didn't. I only have one Windows machine on which to run NextPVR, and it's the production machine. I try and stay away from beta stuff on there, as my wife will kill me if we miss recordings. '-)

Understood hopefully 2.13 will get released as production soon enough. I will have to figure out how to move some SOAP to JSON and still allow you to keep working.

If the long term plan is to ask NPVR to send the lists sorted a certain way, then we can just consider the post sorting I did an interim fix.

The speed of loading recurring lists isn't too much of a conern to me even on an RPi.

Martin