60 replies to this topic

[Taapat]

Before that we were discussing about changes in ServiceName in merge requests for PLI's git, but I think that there's not the right place for this question.
When changed ServiceName I am glad that now I will be able to use it in my skin, and will not need to use additional components.
Unfortunately, today littlesat changed Orbital position to satname: http://sourceforge.n...6ff14f966eb43f/
Perhaps it is more appropriate to the human reading, but now I can not use it in my skin because the line is too long.

 screenshot2.jpg   88.93KB   10 downloads
I know that in the PL-HD is not the problem. For myself I can revert it, but maybe someone else have a problem with it, and we can change it back?

[littlesat]

Strange it should give position and satname...

[Taapat]

As I wrote before. It comes from the sat name in satellites.xml. I am using this file from http://www.satellites-xml.eu/ and therefore for me name is a little different than on openpli feed (name="Astra 4A/SES 5 (4.9E)").

But in any case for me it is too long.

If it does not interfere with anyone else, ok, leave as is. For myself, I will use the previous version, where is just orbital pozition.

Edited by Taapat, 15 March 2015 - 21:47.

[blzr]

+1

imho, sat name provides little added value.

I really don't care if the satelite name is hotbird or astra whatever number

(moreover there are similar names on different positions, so I find it rather confusing than helpful...)

[littlesat]

Or better let's make a choise via a skin attribute or so...

[Taapat]

Maybe it would be better, but I'm not sure that therefore should add a lot of complex code.
But maybe that really ServiceName can change such as ServiceName2: https://github.com/O...ServiceName2.py (this is old and not optimized version, just a example)

where you can specify exactly what to display with the parameters + display providers.

[ims]

 

I am using this file from http://www.satellites-xml.eu/ and therefore for me name is a little different than on openpli feed (name="Astra 4A/SES 5 (4.9E)").

 

But why do you not using pli feed ?

[Taapat]

1. Because I do not have mipsel receiver.
2. It seems to me (maybe I am mistaken) that in http://www.satellites-xml.eu/ is always up to date information.

Edited by Taapat, 16 March 2015 - 09:36.

[Erik Slagter]

The OpenPLi version has been out of date for some time, but should be ok now.

[ims]

1. Because I do not have mipsel receiver.
 

but then you can use own patch for it, when you building own image... why make it as basic in PLi ?

 

 

 

BTW - when I made it for using in "All" screen, I had worry, that somebody will make from it "intergalactic" info... Several weeks and it is here... Golden good orbital position which was here ...

[littlesat]

But maybe that really ServiceName can change such as ServiceName2: https://github.com/O...ServiceName2.py (this is old and not optimized version, just a example)

 

This is exactly what I do not like... having ServiceName2, 3, 4 etc..... This is something that was invented by our colleagues of OE-A.

 

As this has nothing to do with service name it s even better to move it completely out there and make a new one... TransponderInfo.py or something like that... But than again... skins should be adapted.... But in fact this is the only optimal way this should be done....

 

in addition going from degrees like 235 to readable data could be done in a one liner to 23.5E... including the degrees character...

Edited by littlesat, 16 March 2015 - 11:04.

[blzr]

BTW - when I made it for using in "All" screen, I had worry, that somebody will make from it "intergalactic" info... Several weeks and it is here... Golden good orbital position which was here ...

hear, hear!

actually, displaying complete transponder data in channelselection screen are unneeded bells and whistles IMHO
the (short) sat position is the one info that might be considered really usefull, since you could have same service from different sats in the list, but the rest? meh...

but of course, opinions vary...

[littlesat]

I thought adding the satellite name was a nice addition.... But it seems more people - different meanings....

[Rob van der Does]

the (short) sat position is the one info that might be considered really usefull, since you could have same service from different sats in the list, but the rest?

I agree with that, if it is also clear if the service is on DVB-C/S/T, as it happens quite often that the same satellite service is also on cable or terrestrial.

[littlesat]

I'm planning to revise this whole transponder info stuff.... and the skin can decide to give more or less issue then.... but there will be a new converter added as I go for the structural way...

Edited by littlesat, 16 March 2015 - 12:22.

[Taapat]

I agree that this has nothing to do with service name, and create a new converter with transponder info would be an optimal way.
And yes, maybe in ConvertToHumanReadable correctly would be get orbital pozition from degrees instead of return name from satellites.xml.

[tension]

I agree that this has nothing to do with service name, and create a new converter with transponder info would be an optimal way.
And yes, maybe in ConvertToHumanReadable correctly would be get orbital pozition from degrees instead of return name from satellites.xml.

 

Agree, i posted something similar : http://forums.openpl...e-2#entry452536

Taapat, i use your metropolis skin.... thank you.

Attached Files

•  tpinfo.jpg   109.35KB   2 downloads

[Erik Slagter]

 

BTW - when I made it for using in "All" screen, I had worry, that somebody will make from it "intergalactic" info... Several weeks and it is here... Golden good orbital position which was here ...

hear, hear!

actually, displaying complete transponder data in channelselection screen are unneeded bells and whistles IMHO
the (short) sat position is the one info that might be considered really usefull, since you could have same service from different sats in the list, but the rest? meh...

but of course, opinions vary...

Yes agree, the other data can be found on the second info bar.

[Taapat]

@littlesat thanks for a separate converter TransponderInfo.

Only I do not understand why you used a global variable self.transponderdata rather than simply transponderdata, if he is not used anywhere else? http://sourceforge.n...nderInfo.py#l39

[littlesat]

Thanks.... good point.... I missed that one... originally when all those functions were called this was mandatory

Pushed....

Edited by littlesat, 20 March 2015 - 15:34.