New TAP to manage the PVR using HTML/CSS/JavaScript.

[Sirius]

My SRP-2100 has the newest firmware with UTF8 support.

Maybe jkIT has a non-UTF8 Firmware on his SRP-2410? (I don't know)

[DeltaMikeCharlie]

Here is the latest version of TMA1 to play with (A-011).

• This week I have added the ability for the JavaScript code to store and retrieve settings with the PVR. I have implemented a very simple "Config" screen to demonstrate this feature where you can adjust the number of channels listed across the screen in the "Channels" menu option.
• The "Config" screen also represents my first attempt to modularise TMA1. This is an external HTML file with an external JS file as well. Index.hml loads these independently. Eventually, I plan to have the ability to have all of the features constructed from add-in modules so that if you don't like one module (timers for example) you can write your own and install it without damaging any of the other modules. The TMA1-Setup TAP will be able to set which modules are loaded and in which position on the menu they appear.
• I think I have fixed the caching problem, again. I hope I'm right this time.
• I have also implemented a test fixed for jkIT's idea about JSON.parse rather than eval. For the timers only, I have fixed the comma problem and changed index.html to use JSON.parse for the timers data. All other areas, including apitest.html, still use eval for now. The point is that both JSON.parse and eval now work for timers, proving the concept.

On the issue of character encoding, I'm either going to have to find a way to determine if the PVR is UTF8 compliant or have a configuration setting to force the encoding method.

Also, all along, there has been an emergency stop key for the TAP. If you press "Sleep", the TAP should stop.

As always, please be careful and power-cycle your PVR after testing.

[DeltaMikeCharlie]

Today's additions (A-012):

• The recorded programmes list can now navigate down into subdirectories and commence playback of files in those subdirectories. To get back up to /DataFiles, press the menu button again.
• I have fixed the trailing comma problem with all of the lists so that JSON.parse SHOULD work, but I have not tested that yet.
• The "config" API call has a new element returned called "utftoppy". This calls FireBird's isUTFToppy() and returns that value. The apitest.html page has been modified to show this value.
  (jkIT and Sirius, can you please load apitest.html and let me know the value of the "utftoppy" field in the "PVR Configuration" section?)
• The "Alive" heartbeat output to the telnet console now includes a timestamp.

[Mucki]

Hallo DeltaMikeCharlie,

my Channellist is now empty !

If I select Apitest.html all Channels are shown.

[Isarwolf]

TMA-012
Many thanks for the new features.

1. My channellist is empty
2. Recording programs, i can open the subdirectories and start programs.
Best regards

[jkIT]

wow, 2 versions while germany is sleeping (and beating the Austrians in soccer)

I may reverse the UTF8 coding in the web page, but leave it in the JSON data.

no, leave it as it is
because:

My SRP-2100 has the newest firmware with UTF8 support.
Maybe jkIT has a non-UTF8 Firmware on his SRP-2410? (I don't know)

Yes, i have a non UTF8 Firmware, so i hope, you can encode the strings like servicename, filename, etc, when you put them into the json structure. Maybe firebird can help with code tables, or what else is required.

Today's additions (A-012):
I have fixed the trailing comma problem with all of the lists so that JSON.parse SHOULD work, but I have not tested that yet.

It works for all, except files and settings. Firebug says "SyntaxError: JSON.parse: expected double-quoted property name"
I think, thats another trailing comma problem

Code: Alles auswählen

/api?function=setting&action=set!key=apitest01&value=test%20value&
{
  "timestamp":"2013/09/07 10:21:58", 
  "content":"setting-set", 
  "status":1, 
  "setting_key":"apitest01", 
  "setting_value":"test value"[color=red][b],[/b][/color] 
}

The "config" API call has a new element returned called "utftoppy". This calls FireBird's isUTFToppy() and returns that value. The apitest.html page has been modified to show this value.
(jkIT and Sirius, can you please load apitest.html and let me know the value of the "utftoppy" field in the "PVR Configuration" section?)

my result:

Code: Alles auswählen

{
  "content":"config", 
  "sysid":22121, 
  "device":"SRP-2410", 
  "apptype":"", 
  "remotetype":1, 
  "maxrecstreams":4, 
  "version":263, 
  "recextension":".rec", 
  "language_code":"de", 
  "utftoppy" :[ b]0[/b], 
  "utcoffset":120, 
  "dst":3, 
  "timestamp":"2013/09/07 10:21:57"
}

[jkIT]

Hallo DeltaMikeCharlie,

my Channellist is now empty !

If I select Apitest.html all Channels are shown.

DMC just forgot to remove a test entry in the code.
Edit index.html and move the // from line 245 to 246

Code: Alles auswählen

    chRequest.open( "GET", "api?function=channels&action=get!", false );
   [b] //[/b]chRequest.open( "GET", "channels.txt", false );

[Mucki]

Danke dir !

[Sirius]

Thank you for the new versions!

Code: Alles auswählen

Object	Value
content	config
sysid	22010
device	SRP-2100 (TMS)
apptype	
remotetype	1
maxrecstreams	2
version	277
recextension	.rec
language_code	de
[b]utftoppy	1[/b]
utcoffset	120
dst	3
timestamp	2013/09/07 10:55:49

The playback of a file in a subdirectory works here also.

I get now also no list of Channels. (see Edit 2)

Edit: die Lösung ist ja schon in Sicht... werde es gleich testen ...
Edit 2: Now the channel list is there. Thank you jkIT!
.
.

[Isarwolf]

@jkIT
Thanks!

[Mucki]

DMC just forgot to remove a test entry in the code.
Edit index.html and move the // from line 245 to 246

Code: Alles auswählen

    chRequest.open( "GET", "api?function=channels&action=get!", false );
   [b] //[/b]chRequest.open( "GET", "channels.txt", false );

Bei mir leider ohne Erfolg !

[Sirius]

@Mucki - I made this and it works now:
- stop the TAP
- edit the index.html like jkIT wrote and copy to PVR
- start the tma TAP again

[DeltaMikeCharlie]

I apologise for the problem with the channels. As jkIT kindly pointed out, I had left some debug code active. (Thanks jkIT)

I have uploaded a new version that should be OK now.

I will look into the trailing comma problem (again) tomorrow.

Has anybody tested the new "Config" menu and tried to change the width of the channel listing? I'd like to hear if that works OK.

@Sirius - It is not normally necessary to stop the TAP when one of the files is changed. Sometimes, you need to "reload" the file in the browser so that it is not loaded from cache. Also, if you stop/start the TAP too many time, the TAP will become unresponsive.

[Isarwolf]

[quote="DeltaMikeCharlie"]
Has anybody tested the new "Config" menu and tried to change the width of the channel listing? I'd like to hear if that works OK.
[/quote]

It works well.

best regards

[DeltaMikeCharlie]

[quote="Isarwolf"]It works well.[/quote]
Thanks

[FireBird]

[quote="jkIT"]Yes, i have a non UTF8 Firmware, so i hope, you can encode the strings like servicename, filename, etc, when you put them into the json structure.[/quote]
It's not the firmware, it is up to the provider who defines the encoding. The German channels in our region usually use ISO8859-9 (Latin 5).

[DeltaMikeCharlie]

It works for all, except files and settings.

Code: Alles auswählen

/api?function=setting&action=set!key=apitest01&value=test%20value&
{
  "timestamp":"2013/09/07 10:21:58", 
  "content":"setting-set", 
  "status":1, 
  "setting_key":"apitest01", 
  "setting_value":"test value"[color=red][b],[/b][/color] 
}

I have uploaded A-013 with what I hope is the final fix for the trailing comma problem. It is very untested, so I have also included a copy of A-012 as a fallback just in case.

[DeltaMikeCharlie]

[quote="FireBird"]It's not the firmware, it is up to the provider who defines the encoding. The German channels in our region usually use ISO8859-9 (Latin 5).[/quote]

Before UTF8, I was using ISO-8859-1, now I have to think about ISO8859-9. This is all getting very complicated.

The spec for JSON states that it should use UTF8. Perhaps I need to look at the PVR language code and select the best ISO-8859-? For that language and then convert that to UTF8.

Perhaps there needs to be a manual configuration setting to select the best code for the region that the user lives in?

[macfan]

Here is the latest version of TMA1 to play with (A-011).

Everything works, thanks!

This week I have added the ability for the JavaScript code to store and retrieve settings with the PVR. I have implemented a very simple "Config" screen to demonstrate this feature where you can adjust the number of channels listed across the screen in the "Channels" menu option.
The "Config" screen also represents my first attempt to modularise TMA1. This is an external HTML file with an external JS file as well. Index.hml loads these independently.

And this is great! The only "number of channels listed across the screen" that is useful for me is the 10, because I sorted the channels using multiples of 10. But you gave the option for 2 to 7, not for 10. One little change in "config.html", and now I have the view I wanted to have.

Gruß, Horst

[FireBird]

I'm sorry but I didn't invent all the different tables. Check out EN300468 Annex A.2 for some samples. Of course, Unicode is the best method because every character has its well defined location. But the 8-bit tables are still widely used.