MCelliotG

Very valid point, but not all skins have to be PIG. It was a choice I made long ago. Now, if there was an option with an additional screen on ChannelSelection to display MiniTV, I would do it with no second thought. Otherwise it's all choices and preferences!

BTW, this week I'm testing the new installation layout (I separated the pythons from the skin files). Once testing is ready, I believe the new colors will be ready for launch!

Guys, thank you for testing my skin.

I'm currently testing the colored skins now, and I have encountered a little problem with the ipk standalone installers I make.

The skins use the same Converters/Renderers (as they should). Since the ipks should be working as standalone installers, file clashes are inevitable, when one skin tries to install when another is already installed.

On OpenATV I solved this problem easily with the Replaces flag in the control file. This will overwrite and replace only the common files, so if the user wants a second Glamour skin, everything should be fine. Additionally, I wrote a postrm skin that will prevent removing the Converters/Renderers if another Glamour skin is still in use.

On OpenPLI however the Replaces flag does not work as I expected. The new skin will completely uninstall the other first. As a dirty workaround I wrote an additional postinst script that initially copies the converters to /tmp and then overwrites the installed ones, but I don't like this way.

Should I leave it this way, or this will cause troubles in building from Github or even updating from it?

Why the Replaces flag in the control file works differently between OpenPLI and OpenATV?

That's quite strange, there was no lag on channel change even on an "old" VuDuo2 I had tested it on! Maybe something else hinders the zap, or you use an older version of my skin?

Thank you! I already uploaded the other skins privately on my Github, testing the install scripts atm for file clashes.