260 replies to this topic

[BuGless]

The creative commons license is a lot more restrictive to end-users than GPL. If you don't know what to pick, select GPLv2 because that is what all the rest of OpenPLi is using.

There's a matrix of Creative Commons licenses; I think I picked the one closest resembling GPL. But if this is undesirable, I'll happily change it to GPL.

[MiLo]

Please change it to GPL. Easier for everyone.

[BuGless]

Please change it to GPL. Easier for everyone.

Ok, changed the license to GPLv2+.

I'm still battling the bitbake dependencies though, I figured out why it briefly worked. The place where the enigma2-plugin-skins-pli-scale-hd are mentioned in the dependencies (now) is not enough to get it built. Adding it to "recommended" sort of fixes it.
It should, of course, be mentioned elsewhere, the question is where.

[pieterg]

well, the fact that your changes to the license file broke last night's build, proofs that the skin is really included in the build

But note that you have to bitbake openpli-enigma2-feed (instead of openpli-enigma2-image).

[littlesat]

And also this morning no images

[BuGless]

well, the fact that your changes to the license file broke last night's build, proofs that the skin is really included in the build

Ok, then there must have been some issues last week causing this to fail a few days in a row?
I'll provide a patch today, to update the .bb file.

But note that you have to bitbake openpli-enigma2-feed (instead of openpli-enigma2-image).

Well, I figured this out eventually. This is kind of non-obvious, if I may say so. A small README or something in the root would have helped.

[Rob van der Does]

If you don't mind me asking: why use a separate GiT and not the existing open plugins GiT?

[pieterg]

well, the fact that your changes to the license file broke last night's build, proofs that the skin is really included in the build

Ok, then there must have been some issues last week causing this to fail a few days in a row?

no, we didn't get the issue till I fixed AUTOREV a few days ago.

But note that you have to bitbake openpli-enigma2-feed (instead of openpli-enigma2-image).

Well, I figured this out eventually. This is kind of non-obvious, if I may say so. A small README or something in the root would have helped.

I've now mentioned this in the wrapper makefile.

[ims]

And also this morning no images

there can be some problem in availability sources - timeout ? When I rem line for this plugin, I still cannot build image in most than 90%...
It finishing on parsing on 95-98% with error.

[littlesat]

Is it possible to "kick" the buildserver now then?

[ims]

What do you think ?

[BuGless]

If you don't mind me asking: why use a separate GiT and not the existing open plugins GiT?

Simplicity, mostly. The project is largely standalone, so contaminating the git repository with other projects needlessly complicates matters (for one, the change-history gets a lot larger).

I've now mentioned this in the wrapper makefile.

Many thanks.

[Rob van der Does]

A minor cosmetic: the green button in the about screen has no label.

[BuGless]

A minor cosmetic: the green button in the about screen has no label.

While checking this, I was wondering, what is supposed to be displayed when you press it anyway?

[Rob van der Does]

A minor cosmetic: the green button in the about screen has no label.

While checking this, I was wondering, what is supposed to be displayed when you press it anyway?

Translation info (see screenie). Tha actual contents depends on what has been added by the respective translator(team).
 Translation info.jpg   80.59KB   76 downloads

[BuGless]

Translation info (see screenie). Tha actual contents depends on what has been added by the respective translator(team).
 Translation info.jpg   80.59KB   76 downloads

Ah ok, that's why it's empty on my system.

I'm curious though, why do your screenshots always have the current time in the upper-right-hand corner as well? I know the skin doesn't do it. Is that a plugin which displays the time even when menu-screens are being displayed?

[Rob van der Does]

I'm curious though, why do your screenshots always have the current time in the upper-right-hand corner as well? I know the skin doesn't do it. Is that a plugin which displays the time even when menu-screens are being displayed?

Ahm yes, 'Permanent Clock'. Sorry about that.
I normally give the screen of that plugin a low zposition, so that it won't overlaye on menu's. Not done yet (this is only a test box).

You might consider adding that screen to your skin to prevent others from experiencing the same (I think this is a much used plugin).

<screen name="PermanentClockScreen" position="0,0" size="120,30" zPosition="-1" backgroundColor="transparent" title="%s" flags="wfNoBorder">
        <widget source="global.CurrentTime" render="Label" position="1,1" size="120,30" backgroundColor="transparent" transparent="1" zPosition="0" foregroundColor="grey" borderWidth="2" font="Regular;26" borderColor="black" valign="center" halign="center">
            <convert type="ClockToText">Default</convert>
        </widget>
    </screen>

[BuGless]

Ahm yes, 'Permanent Clock'. Sorry about that.
You might consider adding that screen to your skin to prevent others from experiencing the same (I think this is a much used plugin).

Ok, will do so shortly.

Which brings me to a possibly related question... I've never completely understood the zPosition specs. Putting it at -1, does that mean that if a screen/menu of mine would happen to put something transparent in that corner, the time would still show through?
And again related to that, what would it take to make the teletext subtitles stay visible even though the InfoBar or SecondInfoBar screens are shown?

[Rob van der Does]

Think of it as layers: the highest zposition of a stack of layers will be visible.
But layer-level and pellucidly might interfere?

LOL: you located the infobar at the top of the screen, so subtitles will always be visible......

Edited by SatKiekerd, 21 February 2013 - 17:49.

[BuGless]

Think of it as layers: the highest zposition of a stack of layers will be visible.
But layer-level and pellucidly might interfere?

Yes, well, this still leaves some questions unanswered; you paint at level 1 and you paint something else at level 2:
q. But not at the same spots where you painted at level 1.
b. At the same spot, but with the transparent="1" parameter turned on.
c. At the same spot, but with transparent="0" using a #ff000000 foreground color.
d. At the same spot, but with transparent="0" using a #ff000000 background color.

When does it show the things painted at level 1? When does it not show the things painted at level 1, but the videoscreen instead?
Is there a special meaning for zPositions <0 or zPosition = 0?

LOL: you located the infobar at the top of the screen, so subtitles will always be visible......

Yes, that was the idea, but in practice the teletext subtitles are being suppressed while the InfoBars are visible.

Edited by BuGless, 21 February 2013 - 20:50.