2041 replies to this topic

[DimitarCC]

Thanks. I cant test cablescan... Maybe can use the layout of sat scan....

[DimitarCC]

My latest observations summed….
On the hotkey screens I miss the pager dots. The last item in the list is also not completely shown.
In the movie list Instill miss the waiting widget.

Also here the last
Option in the list is not fully shown.
In network mount support the middle two options are not skinned
It would be helpfull when flashing image where you select the image get a larger screen so also all buttons text fit.
In info, channel info the pid information does not have a pager and also the last option is shown half.
There is no pager on menu>applications (plugin browser)
The multiboot selection screen could also be bigger at least to allow the color button text have more space.
The autobackup screen makes the whole screen back while the border still could show tv picture

 

 

So Waiting widget in MovieList - Added

The cuttng of the last item in MovieList - onHold (see my previous posts)

PluginBrowser requires extension that was reverted some time ago due to some complains. Without that extension a pager can not be added there.

 

......

 

Strill investigate the others....

[littlesat]

When you point me to the GitHub and give me rights I can help. E.g with finetuning stuff.

Edited by littlesat, 7 December 2023 - 08:44.

[littlesat]

When moving services with option 6 in the channel list sometimes the number before the service you move is not shown (I'm afraid this is cpp stuff that needs to be adapted).

Edited by littlesat, 7 December 2023 - 13:54.

[DimitarCC]

I cant reproduce that....Maybe is PLi specific...

[littlesat]

It seems to happen when we have to of the same serviceref in one bouquet.... This is something e2 in general cannot handle... so do not worry about it. I was messing up today with my channel settings... I'm busy with a merge/update downloaded services package and pin bouquets feature in a 'deep solo-brainstormy' phase at this moment...

Edited by littlesat, 7 December 2023 - 14:45.

[littlesat]

I just discovered that there is python code in the skin as a convert py file. At least I saw CardInfo2.py. This is something we should prevent.... then better adapt a converter/renderer in the standard skin. In addition why is PLiExtrainfo not sufficient or why can't we adapt it... (I know the name of that module is also bad... but that is history )
Maybe I can help to add an add advanced to it so you can show it at once via pliExtraninfo without the colored crypto letters.
In the tuner letters the standaard skin show always the first tuner of a fbc or combo in gray. Now we only see the used letters

Edited by littlesat, 8 December 2023 - 17:19.

[DimitarCC]

I use cardinfo2.py only for displaying currently active caid in infobar.
This currently is not in pliExtrainfo.
But yes can be extended.
Also there are several converters and renderer that comes with the skin.
It will be nice if they are included into the base code as well...

[Huevos]

I've made a PR for fixes to listboxeservice required after recent commits.

 

https://github.com/O...igma2/pull/3864

[littlesat]

Trustful merged

[littlesat]

And indeed better extend it in pli extra info… better not to have own renderers…./ I always hated that… eg skins with the same name in code can kill eachother. Or search for existing alternatives or add what you need. Sometimes something that exists and looks slightly different is also good

Edited by littlesat, 8 December 2023 - 21:08.

[DimitarCC]

So regarding the caid info you suggest extend PLiExtraInfo? What about othe rconverters and renderers? Should they also be in the image.

OE-A have one of them built in (AudioIcon/Renderer and Converter/) and other one is BoxLogo. Should that be added to core enigma files?

[littlesat]

Actually it is a bad idea to put renderers in the skin. They belong to the enigma core. And maybe also some things are only there for pomp the x-mass tree style. Eg having vu+ icons or so is not really needed. Maybe just show openpli or vix logo there. For boxlogo you need to have a boxlogo inside and as far I know the way it is doing now put all of them in. So this belongs to the build environment (bsp) then no special renderer is needed. This is difficult but python code in skins is actually not a good idea. Then better have it in the image…. Where I’m afraid the box specific images are the most complicated challenge. For this you do not need a renderer at all. The correct picture should simply be there via the bsp.
The caid info may indeed be better to extended in pli extra info.

Edited by littlesat, 9 December 2023 - 09:58.

[littlesat]

I have until now no idea what exactly the audio renderer/converter does… but such stuff is always helpfull to other skins…

[littlesat]

The box specific icons. Maybe we need to create packages with a name and put them box specific in the 3rd party stream. And put a dependancy in the skin. So when you download the skin you get the right pictures right away. And when that package does not exist you get the standard icon. So for vu+ by example we just add a ipk package….
I hope you understand what I mean..

Edited by littlesat, 9 December 2023 - 10:03.

[DimitarCC]

I have until now no idea what exactly the audio renderer/converter does… but such stuff is always helpfull to other skins…

 

The AudioIcon converter/renderer is for displaying the audio codec icon for the current service. Currently in my skin is used in the MoviePlayer infobar.

[DimitarCC]

The box specific icons. Maybe we need to create packages with a name and put them box specific in the 3rd party stream. And put a dependancy in the skin. So when you download the skin you get the right pictures right away. And when that package does not exist you get the standard icon. So for vu+ by example we just add a ipk package….
I hope you understand what I mean..

 

I understand what you mean. Also i think would be the best is the brand and model logos comes with base code (or dependency package) specific for the box that image is installed on.

That will greatly simply the things. However i see 2 issues with that currently if that is added to the BSP or dependency package:

1. All images that skin runs on have to adopt that and make similar handling. So that to be standardized.

2.What images and what sizes will be put in the BSP/dependency package? They have to be SVGs in this case so to fit on all possible resolutions used in skins.

 

That will be difficult to be handled i think.

 

Also removing the model logo (that is in main menu) is too subjective. Some people like it, some people not. That also can be provided in enigma core as svg and to be box specific. So to be available for the one that want it.

For people that prefer clean look it can be added options to show that or not in the skins (i know you dont like options but sometimes that is needed so to satisfy users).

 

So a decision have to be made here. And all teams have to decide that i think. Till then at least the box logo stuff have to be left like it is since i require the skin to be compatible with all images that use it or have it in the feed officially (currently OpenViX, OpenBH, OpenPLi).

[DimitarCC]

The caid info may indeed be better to extended in pli extra info.

 

Then i will make a pull for that to include it in PLiExtraInfo

[littlesat]

For the box icons you can make a renderer that checks if a box specific picture is available and then show this one instead of the standard one…. And then make a ipk that makes them downloadable.
Then they can be added in the bsp or an ipk could be added in a box specific 3rd party feed. Or we just build them and but the right ones in there during the build process.

Edited by littlesat, 9 December 2023 - 11:37.

[DimitarCC]

So here is converters and renderers that have general use and extended PliExtraInfo.

 

https://github.com/O...igma2/pull/3866