2057 replies to this topic

[DimitarCC]

Sure OK.

However for boxes that have different models like h9.s the current solution can pick only h9 as logo without to specify it exactly...But if a separation can be done runtime thats ok...

[WanWizard]

Your recipe was OE-A specific, we don't have things like MACHINE_BRAND available at the bitbake level, and our MACHINE value is not compatible with OE-A.

 

As long as you follow the exact naming conventions, based on the MACHINE and MACHINE_BRAND values used in OE-A, for the brand and box images in your repo, I'll do the mapping to boxlogo.svg and brandlogo.svg in the recipe.

 

So, as an example, for the "h9.s", just include zgemmah9s.svg. I'll take care of the rest.

[DimitarCC]

Well i have just built it with latest PLi OE core and it works just fine for duo4kse. It included correct logos in build time.
And you have MACHINE_BRAND in PLi env.

This is just for reference... I will wait for your fixes

Edited by DimitarCC, 2 January 2024 - 17:18.

[littlesat]

There are boxes we build 1 image for and then at runtime it adapts to the model depending on the tuner attached... where oe-a images builds multiple different images for them. The duo4kse is not one of these boxes... .... Wanwizard knows the trick how to handle with this. We had the same 'issue' with the engima.info file.

Edited by littlesat, 2 January 2024 - 17:33.

[WanWizard]

Implemented boxlogos in OpenPLi. Will be available after the next develop build.

[littlesat]

[Huevos]

Implemented boxlogos in OpenPLi. Will be available after the next develop build.

https://github.com/o...990eae4a94e7de2

 

That change was requested by @Littlesat but your recipe does not appear to include it.

[littlesat]

It was indeed the idea to put them in a subdir. Like the remote control files are also in a subdir. It was indeed discussed.

Edited by littlesat, 2 January 2024 - 21:08.

[DimitarCC]

Yes the recipe have to be updated so to match the renderer code

[WanWizard]

https://github.com/o...990eae4a94e7de2

 

That change was requested by @Littlesat but your recipe does not appear to include it.

 

Missed that, I started work before that change, will update it today.

[WanWizard]

Done.

[Pr2]

I check the DimitarCC repo and find out that the zgemmah10 is not yet foreseen in it.

 

Do you need some information about this box?  If so let me know which command to execute on it.

[Pr2]

About the skin itself, the screen to enter the PIN code for a protected service seems quite big to me, especially if we compared it with the other skin screens.

[Pr2]

Other remarks, where can I see the CAID:IDENT used for descrambling in you skin.

Seems that long OK that we had in the OpenPLi second infoscreen is not working in this skin to enable it.

[Huevos]

Other remarks, where can I see the CAID:IDENT used for descrambling in you skin.

Seems that long OK that we had in the OpenPLi second infoscreen is not working in this skin to enable it.

Those 2 screens are currently identical.

 

https://github.com/D...n.xml#L354-L356

[littlesat]

The box icons are back... After an update I did uninstall the skin and reinstall it back to get the dependency in...

[mrvica]

just like SimpleChannelSelection

https://github.com/D...n.xml#L592-L594

I still can´t get the clue what this one is good for, last time I remembered the key sequence how to envoke it again

in simple EPG (or long yellow on PLi) than Ch+/Ch-

[littlesat]

The simple second infobar still needs to be designed... it is intended this one only shows EPG and not technical information.

 

In the normal infobar itself I know a lot of people are used to see the emu data in one row. It is configurable via a setting to enable/disable it. But this skin does not have the widget available and I also have no idea where to locate it when enabled. Maybe consider just to show it right aligned white with black borders above the background for those who like to enable it... even when it might look ugly...

 

Also I discovered that the REC button can be shown over the channelnumber|channelname|providername combi widget when this widget becomes long.... 

 

Long Long time ago I had the idea only to show enabled icons.... like it is done now with the combination widget with the dots in between... So everything that is after the crypto indication (e.g. FTA when there is no crypto) could be shown kind of compressed.... the icons with only black background are not shown... Maybe the REC button and also the FTA could be added to this combi thing. I know they are not shown on exactly the same locations, but with the combination with the channelnumber|channelname|providername it might give more 'space' and maybe a more quit look. (I hope you understand what I mean). I understand this is a complicated change and believe my I never made it because I had no idea to do it.

 

Also in some screens e.g. the plugins/application screen I miss the < > and 0 icons that indicate that you can move and hide plugins shown there.

Edited by littlesat, 4 January 2024 - 18:30.

[littlesat]

Simple channel selection can be found under the blue button for example in the channel EPG. It is a channel selector just to select channels without context menu etc...

[WanWizard]

The subtitle page still doesn't fit as well.