26 replies to this topic

[Taapat]

Simple and clean multi resolution skin for OpenPLi or on OpenPLi based enigma2 images.

 

Skins use automatic scaling, thefore it is available in all, SD, HD and FHD resolutions.

Skins use svg images, so their quality does not change at all resolutions.

 

Will work on OpenPLi images starting from version 8.1 because the older images does not support scaling and svg.

 

Repository: https://github.com/T...skin-SimpleGray

 

Download: https://github.com/T...leGray/releases

 

Skin is also be available on the develop image feed.

 

 

 SGInfobar.jpg   98.86KB   21 downloads  SGSecondInfobar.jpg   163.04KB   18 downloads  SGChannelSelection.jpg   141.86KB   19 downloads  SGSingleEPG.jpg   134.07KB   13 downloads  SGGMEPG.jpg   133.96KB   13 downloads  SGSetup.jpg   171.44KB   16 downloads

Edited by Taapat, 14 November 2021 - 16:32.

[WanWizard]

Looks good. Merged.

 

Would be great if there would be a version where all screens are full screen (either with or without transparency, I don't like the overlays).

[Taapat]

Thanks!

 

But I personally don't like PIG screens, that's why i create such.

Everyone has their own perferences  .

[WanWizard]

I am not to bothered with a PIG as well, but I don't like the TV image "leaking" around all sides in a sort of "fake" window look...

[Taapat]

Ok. I have noticed that transparency does not work on my hisilicon receivers.

Therefore, I agree with the "fake" window look on large screens.

I assume that small screens, such as a message box, do not interfere.

But I don't know if a few seconds, while you're looking at the message box, means something, and instead you can use a screen that will fill the screen.

Edited by Taapat, 14 November 2021 - 17:08.

[Taapat]

Please merge also this: https://github.com/O...-core/pull/1085

[WanWizard]

Done.

 

I assume that small screens, such as a message box, do not interfere.

 

Sure, that is something completely different.  

[pgmpli]

Installed and approved, looks good, works well, nice job.

[athoik]

Great job @tapat!

 

Nice to see my initial work improved and used! Kudos to you!

[Taapat]

Thanks athoik for starting svg support and showing the way to go.

Also thanks to Huevos who started seriously introduce scalling support in enigma.

[Pr2]

The translator about screen is too small not all text is displayed. But personally I prefer skin with PiG otherwise this is a nice skin.

[Huevos]

 1.jpg   95KB   6 downloads

 

For me something is weird at SD resolution. Many screens seem distorted. HD and FHD look good.

 

BTW, I have forked this. I want to get it working for OpenViX. I hope that is OK.

[Taapat]

For me something is weird at SD resolution. Many screens seem distorted. HD and FHD look good.

Honestly, I haven't tested SD skins very much.  

BTW, I have forked this. I want to get it working for OpenViX. I hope that is OK.

No problem

[Taapat]

The translator about screen is too small not all text is displayed. But personally I prefer skin with PiG otherwise this is a nice skin.

 

Maybe I'll miss something, but it's usually just one sentence.

[Huevos]

@Taapat, can I suggest to you using a setup panel that can be used in a lot of screens. In my skin I have similar and it replaces 86 screens. Something like this:

<screen name="SetupPanel">
	<widget name="introduction" objectTypes="introduction,Button,Label" ... />
	<widget name="introduction" source="introduction" render="Label" objectTypes="introduction,StaticText" ... />
	<!-- "config" and "list" widget positioned identically -->
	<widget name="config" conditional="config" scrollbarMode="showOnDemand" ... />
	<widget name="list" conditional="list" scrollbarMode="showOnDemand" ... />
	<widget name="description" objectTypes="description,Button,Label" ... />
	<widget source="description" render="Label" objectTypes="description,StaticText" ... />
	<widget name="footnote" objectTypes="footnote,Button,Label" ... />
	<widget source="footnote" render="Label" objectTypes="footnote,StaticText" ... />
	<widget name="HelpWindow" conditional="HelpWindow" pixmap="icons/vkey_icon.png" ... />
	<widget source="VKeyIcon" conditional="VKeyIcon" render="Pixmap" pixmap="buttons/key_text.png" ... >
		<convert type="ConditionalShowHide"/>
	</widget>
	<panel name="DynamicButtonsTemplate"/>
</screen>

And it doesn't matter what elements are present in the actual screen because the whole thing is conditional, so no error messages.

 

In my case "VKeyIcon" is part of my dynamic button bar.

 

https://github.com/O...s.xml#L232-L241

Edited by Huevos, 1 December 2021 - 09:42.

[Taapat]

Thanks! I find this a very good suggestion.

I use panels for screens with the same content.

You've gone a step further by creating a universal panel with conditional that allows to use it in screens with widgets with different names.

[littlesat]

I use panels for screens with the same content.

 

Even better in the python code to change the class or arrange that such basic screen is used at least as fallback... (to keep compatibility with 'old school skins'....) actually the conditional and panels were designed to make skinning easier...

 

The same with plugins... best strive to use existing screens and when it does not exist try to add a missing feature to an existing screen and at last only add a custom screen when it is really really really really required... this will keep the code and skinning short and clean and the result is also a common look in the ui.

Edited by littlesat, 1 December 2021 - 16:22.

[Huevos]

 

I use panels for screens with the same content.

 

Even better in the python code to change the class or arrange that such basic screen is used at least as fallback... (to keep compatibility with 'old school skins'....) actually the conditional and panels were designed to make skinning easier...

 

The same with plugins... best strive to use existing screens and when it does not exist try to add a missing feature to an existing screen and at last only add a custom screen when it is really really really really required... this will keep the code and skinning short and clean and the result is also a common look in the ui.

 

Yes, you can do that once you have a decent universal screen in all your skins. And you also need to automate all the buttons like has been done in OpenViX, not just the colour buttons. At least HELP, TEXT, INFO, MENU and NEXT/PREV should be added to the automatic button bar.

[Pr2]

The translator about screen is too small not all text is displayed. But personally I prefer skin with PiG otherwise this is a nice skin.

Maybe I'll miss something, but it's usually just one sentence.

No there are many sentence check it in the French translation. :-)

[Taapat]

As stated in the comment at TRANSLATOR_INFO, the information is provided for up to 6 lines: https://github.com/O.../po/fr.po#L8720

In the French translation is 9 and therefore does not fit in the screen.

Of course I can increase the screen size, but maybe it would be correct to display the information as it is stated in the comment for this translation.

It may not be fully displayed in another skin, which also relies on what is specified in the translation file.

Edited by Taapat, 2 December 2021 - 08:14.