2022 replies to this topic

[littlesat]

Any idea how we can learn the pager this… as it seems (I’m not 100% sure) the standard slider seems to know.

[Huevos]

Any idea how we can learn the pager this… as it seems (I’m not 100% sure) the standard slider seems to know.

The scrollbar is built in.

[DimitarCC]

Any idea how we can learn the pager this… as it seems (I’m not 100% sure) the standard slider seems to know.

I have, but it needs cpp modifications...

[littlesat]

[littlesat]

The pagers look so nice…. But they are complicated… also the hiding stuff is made complicated.

Edited by littlesat, 11 December 2023 - 23:48.

[DimitarCC]

OK. Pager should be fixed with that

 

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

[littlesat]

I thought that would be more complicated

[DimitarCC]

[Huevos]

I thought that would be more complicated

I sure he could make it a lot more complicated if you want.

[littlesat]

[Huevos]

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..

Just put a logo on the box, e.g. in /usr/share/enigma2/skin_default/logo.png. No need for dependencies. And every distro can decide how to put that image there. And by the way don't forget there is a difference in box names between PLi and other distros. So add a logo in your build and other distros can do similar, as long as the logo is at the same file system location on all distros, all that needs to happen in any skin is link to that logo. And if the logo is missing it won't show.

[littlesat]

You are talking so easy with telling just put it on the box as it starts fist with an agreement where it might land and also only appears when it is needed thinking about the kitchen sink. Yes it works to put it somewhere but please think about doing it properly.

[Huevos]

You are talking so easy with telling just put it on the box as it starts fist with an agreement where it might land and also only appears when it is needed thinking about the kitchen sink. Yes it works to put it somewhere but please think about doing it properly.

It is just the same as the rc.png images. My point was once a location is agreed each distro should do it themselves. You don't even need a location. Just agree a filename and the SCOPE lookup will do the rest. Anyway, a project like this shouldn't be the responsibility of the skinner.

[littlesat]

It is the skin that shows it so there should be a dependency in the skin that installs them… I hope you understand this point. Indeed the structure of the image does define it. The pictures should only be there when they are needed. At least for more stuff in the image. Sorry this is about the everything but the kitchen sink.

Edited by littlesat, 12 December 2023 - 21:47.

[Huevos]

It is the skin also that displays the rc.png image, so should that also be the responsibility of the skin?

[DimitarCC]

Well we are speaking for 2 images. If they are vector type it will take few kb....
I dont think there are many options. Have them in the skin (but have them all). Or have only 2 images for the specific box (provided with the image). Thats it....
I can easily strip the images from the skin and make it like @Huevos suggested. But then on PLi it will leave empty places or default skin images for every box since PLi will not provide the correct images... I think it is a matter of decision...

Edited by DimitarCC, 12 December 2023 - 22:02.

[littlesat]

I think it does not have any added value to get into this kind of discussion again.
I only strive to get this as best as possible….
The manufacturer’s image is new. Install all the manufacturer images is actually not done. Even when it are a few KBs as this is a bad argument. To get the picture on a location when you install an images that needs it because it used it is what should be done here. I also need eg wanwizard or so as hel to get this done and I’m also sure Huevos or so really understand what I mean here and is also able to implement it….

Edited by littlesat, 12 December 2023 - 23:11.

[DimitarCC]

OK. Then i need a strait answer about that.

 

Are this going to be implemented in the right way (built in in the image) or not?

 

If not i will keep it like it is at the moment.

 

In the worst/best case the skin will show only E2 DarkOS logo. I have no plans to remove the logos completly.

 

In which way will go depends which distros will integrate the logos into the image and which not.

[Abu Baniaz]

Can the path/location of the logo be looked up from boxinfo or systeminfo, if not present return a default logo from the default/backup skin?

[littlesat]

This is the first image we have that show this type of logo in a skin, while enigma2 should be enigma2 for all boxes. Now the skin should have all the logo’s for all the boxes and when the skin does not have the logo it shows its skins own logo. When you do this each skin that should contain these logos should have the logos on its own again. This is not a structured way to do it. Better have a location for box logos and put them at a defined location and arrange that they will get there via the build process…. So we need to agree a location and then how it is done in the build is upto the images.