39 replies to this topic

[Rob van der Does]

It seems you're missing the point.

You stated that Pli already supports a 1080-resolution skin. I tried to show you that supporting 1080-framebuffer, although a prerequisite, is not nearly enough to really and fully support a full-HD skin. And it looks like I finally managed to convince you

 

Whether or not a skinner is prepared to create a full-HD skin for PLi is something I cannot tell you. But I could understand that any enthusiasm from a skinner should be supported by PLi making the required changes to the images. And that's a lot of work as you have seen now.... 

 

 

But to answer your question: apart from staying up-to-date with the master branch (all the identical commits to both branches) all commits in there are purely done for supporting OSD in full HD. Most of them were done at the early days of that branch.

 

 

Not sure what 'Hotkey' has to do with this thread, so I'll let the compliment pass.

Edited by SatKiekerd, 31 October 2014 - 15:38.

[littlesat]

What is your added value here?

Openpli supports even auto adjusting skins for a few years... But no skinner did really use these features yet...

So please stop telling false rumors here... With telling false rumors you driving me nuts.

And hotkey is on topic here... Simply because of you.

And for 1089hd skins no modifications in enigma2 are really required.... I explained it already several times here... And I'm still waiting for the really required commits on the vix sources regards this topic....

Edited by littlesat, 31 October 2014 - 16:14.

[Rob van der Does]

OK, then I'm pretty anxious to see the first full-HD skin arrive for PLi without any adjustments to the image being required.
If indeed nothing will have to be changed it will be peanuts for any skinner to provide a 1920x1080 skin. One could even wonder why this hasn't happened yet?
 
I will be very curiously following any skinners attempt to do only what you suggested
 

It might be the skin needs some (slightly) changes as it is build on the based on OpenPLi OE-A "ViX" image....
 
E.g. it needs a adaption of the about screen because they make it about-oe screen or so... It is a non-PIG skin, so I suggest the adaptions for plugins and features etc. should be reduced...

to get a full blown HD skin.....
That would be really added value for PLi-images.

I really hope you're right.

The 'auto scale' skin was a never finished, but much promising project,

Edited by SatKiekerd, 31 October 2014 - 16:16.

[littlesat]

The 'auto scale' skin was a never finished, but much promising project, 

 

Skinners need to understand and use it.... And note even I did in fact only use the panel and position="full" option...

It is currently difficult to use and test this specific skin on openpli... because skin related stuff is replaced to /usr/share/enigma2/skin_default.... 
 

Edited by littlesat, 31 October 2014 - 17:20.

[littlesat]

Ik heb het hele zaakje nog eens bekeken... Feitelijk is het complete onzin om een compleet nieuwe branch te maken voor een 1080HD skin... Dat is echt nergens voor nodig...

Edited by littlesat, 31 October 2014 - 17:44.

[Rob van der Does]

Again: I'm anxiously awaiting the first full-HD skin.....

But apparently you're sure any skin(ner) will overcome in Python and C++ hardcoded lay-out elements (mainly in lists). We'll see....

[littlesat]

Where are the commits to modify the listst????? 

 

E.g. https://github.com/O...c51d0ac416a56b6

 

And yep also for lists it is possible to set fontsizes, itemheights etc within the skin xml.... nor patch in cpp required at all when it can be done in the xml....

 

And when something is really required you should add that something to make everything backwards compatible and not simply change some "default" values....

Edited by littlesat, 31 October 2014 - 18:18.

[Rob van der Does]

Re-reading your posts: I hope you're not suggesting to scale a/any skin from 1280x720 to 1920x1080 (positions and graphics)?
As that would indeed be really pointless. The whole purpose of a full HD skin is to get high reolution graphics; which looks indeed fabulous!

[WanWizard]

Can we stop this discussion please, this is not getting anywhere.

 

The facts:

1. An OpenPLi image supports 1080 skins

2. We are not in the business of creating skins

3. We are not responsible for making sure plugins adapt to different resolutions

 

Everything else is blah. Case closed. For the sake the TS, make sure a moderator doesn't have to close this topic.

[Rob van der Does]

When I get a chance I'll convert OP's skin a bit, so it runs on PLi. Will take a couple of days though, so if anyone beats me I'll be grateful.

After all the proof is in the pudding, not in denial.

 

And I can't see any reason to close a topic; we never went off-topic, only discussed (possible) issues around using a high resolution skin.

[littlesat]

And possibly I can demonstrate that you do not need to create a saperate brench for a full hd skin.

It might be you needed some changes to add features to change fonts and/or item heights or some positions that are currently fixed with help from a skin parameter. A saperate brench is not needed at all.

If you want to make it I'm happy to see it!

Edited by littlesat, 1 November 2014 - 07:08.

[Rob van der Does]

And possibly I can demonstrate that you do not need to create a saperate brench for a full hd skin.

It might be you needed some changes to add features to change fonts and/or item heights or some positions that are currently fixed with help from a skin parameter. A saperate brench is not needed at all.

I really hope so. After all that's the way it should be.

And I will get this skin to run on PLi (at least basically, as proof of concept; not sure if I have the opportunity to adapt all image-specific screens). But I'm really short in time atm, so it might take a couple of days to complete.

 

In the meantime: can you tell me if the PLi skin-engine supports

1- multiple 'includes' as used in this skin?

2- smart png-location look up (i.e. if pixmap="icons/xxx.png" the engine first looks in the icon-folder of the active skin and if not present it will look in the icon-folder of the skin_default)?

 

If both the above items are supported porting the skin to PLi (and after that maintaining it) would be much more easy.

[rossi2000]

if you want have a play

this "should" work on pli.

 

but fair abit will need to be adapted becuase of different converters/renderers etc.   widgets etc.

Attached Files

•  PLiView.rar   2.15MB   63 downloads

Edited by rossi2000, 2 November 2014 - 19:03.

[jpuigs]

Yes, it works on my ET8000.

[Matrix10]

HQ 1920 x 1080 example : MX BlackSpeed HQ

 

 

Coding PIG skins is many hours of work.

But this is surely the future of skins and graphics.

 

More about this:

http://www.vuplus-co...44/#post-148575

Attached Files

•  shot3.jpg   74.16KB   7 downloads
•  shot1HQ.jpg   55.01KB   9 downloads

Edited by Matrix10, 3 November 2014 - 11:10.

[Rob van der Does]

Well, I gave it a try, but I'm sorry to say: it's far to much work to get the basics running under PLi.
First of all PLi indeed doesn't support more than 2 'includes', but even when that has overcome by including the text of the files in the skin.xml, there are loads of screens falling back on the default skin. Far too much to be able to say anything about issues around hard-coded screen elements.

I know I promised to get it to work as proof of concept, but it is really too much work. I'm sorry about that.

Anyway a basic remark can be made, related to the topic of OP: at least the skin default will have to be adapted for a full HD resolution.

[littlesat]

Openpli supports multiple skin includes, without any limitation.
And the screen default needs no adaptions at all... The hd skin should taken over all these screens when you want to adjust those...

Edited by littlesat, 4 November 2014 - 14:54.

[Rob van der Does]

Yes, but apparently only two times, see:
 

[SKIN] loading include: /usr/share/enigma2/PLiView/skin_YouViX_Templates.xml
[SKIN] loading include: /usr/share/enigma2/PLiView/skin_YouViX.xml

The other two includes were never loaded.

[littlesat]

And this is pli's fault?

[Rob van der Does]

Before I started I asked:

In the meantime: can you tell me if the PLi skin-engine supports
1- multiple 'includes' as used in this skin?
2- smart png-location look up (i.e. if pixmap="icons/xxx.png" the engine first looks in the icon-folder of the active skin and if not present it will look in the icon-folder of the skin_default)?
 
If both the above items are supported porting the skin to PLi (and after that maintaining it) would be much more easy.

I never even got a reply.

Now that I'm giving it a try, it turns out that the answer to
1- is partial YES, and to
2- is NO, as that will count for the multiple fall back on skin default.

Edited by SatKiekerd, 4 November 2014 - 15:04.