214 replies to this topic

[ims]

or create my own .bb for it  (for my github plugin) and put it into enigma2-plugins recipes

Edited by ims, 24 February 2015 - 10:00.

[Erik Slagter]

It can't go into enigma2-plugins, because all these plugins share a single recipe (which is a bit complex, which is why you can't 1:1 copy a plugin in there).

 

But I can add your recipe to the openpli-recipes no problem. There is one drawback though:

 

- github and sf tend to be unreachable quite often

- when the recipe is set to autoupdate (${AUTOREV}), the build process will contact the git provider on every build

- if the git provider isn't reachable, the complete build will stop

 

That's why we prefer to "pin" packages to a certain commit. If this commit has already been fetched on a previous build, it doesn't need to be fetched again, much less risk for fetch errors.

 

So your recipe would also be "pinned" and you'd need to notify us every time you want another commit as HEAD for the package.

 

The enigma2-plugins are not pinned because they give a lot of plugins for a relative small risk of mis-fetch.

 

You get to decide

Edited by Erik Slagter, 24 February 2015 - 11:47.

[ims]

github and sf tend to be unreachable quite often

- when the recipe is set to autoupdate (${AUTOREV}), the build process will contact the git provider on every build

- if the git provider isn't reachable, the complete build will stop

 

 but all this is same for e2plugins and skin.

[Erik Slagter]

Yes, but every recipe with ${AUTOREV} increases the risk of a fetch error happening. We're trying to find a solution, but in the meantime, as little recipes with ${AUTOREV} as possible.

[ims]

1.08 - Added almost all basic used colors in skin.

Make "Recreate" as first step after install (=> will be created new .xml with all new params for editing) !

Attached Files

•  enigma2-plugin-extensions-modifyplifullhd_1.08_all.ipk   5.06KB   42 downloads

[Ad]

Is er ergens een handleiding voor deze plugin .Ik heb hem al wel op mijn Solo2 maar kan er nog niets mee

 

Alvast bedankt

[ims]

Run (if you use old version, make Recreate), change some color ( input in decimal) , pres green and after restart you will see.

 

See on picture:

 

1 - Top color

2 - Bottom color

3 - Selector color

6 - TransponderInfo color

4 - SelectedFG color

7 - Yellow color

5 - SecondFG color

 

Fallback color - color of items in services list available via Fallback receiver only

Notavailable color - color of unavailable item in service list ( bussy tuner etc )

Red color - used for display recorded event in list, moving item in list, edit bouquet

 

Attached Files

•  Plugin1.png   311.47KB   8 downloads

[Ad]

Thankyou very much i will try to night

[Ad]

enigma2-plugin-extensions-modifyplifullhd_1.08_all.ipk   Komt deze ook in feet??

[ims]

Old version (1.02). I cannot tell how 1.08... I made patch for auto compiling and adding plugin in feed...

Edited by ims, 25 February 2015 - 19:53.

[littlesat]

Als het stabiel is kan ik ze wel in de feeds zetten

Ik vind het alleen nog heel,erg sjips dat een full hd skin niet goed samenwerkt met de hbbtv plugin...

Edited by littlesat, 25 February 2015 - 20:55.

[ims]

I sent yesterday to Erik patch for oe...

[cobus]

ik gebruik al een skin_user.xml voor het display maar deze plugins maken ook een skin_user.xml en dan heb je dus een probleem in mijn geval is er een manier om dat te veranderen want de plugin zit wel goed in elkaar en werkt verder goed.

[ims]

??? this making nothing with skin_user.xml

 

Do you think, that you had something in skin_user_pli-fullhd.xml before using this plugin ? But I wrote - in this case make backup of it, run plugin, recreate and then put your parts from backup on end of this .xml file.

[cobus]

Ok thanks

[littlesat]

I just uploaded it to the buildserver... so from the next builds it should be in the feeds...

 

@ims... isn't it better to put this plugin somewhere on github?

[Erik Slagter]

ik gebruik al een skin_user.xml voor het display maar deze plugins maken ook een skin_user.xml en dan heb je dus een probleem in mijn geval is er een manier om dat te veranderen want de plugin zit wel goed in elkaar en werkt verder goed.

I notice the same. Enigma either uses your own skin_display.xml or the skin-specific one, but never both.

 

So what I do is, I use the plugin once, copy the settings to my own skin_display.xml and the remove the one that the plugin made.

 

A patch for inclusion is in my inbox.

[ims]

PLi's enigma using 2 users xml: one is common for ALL skins and it is skin_user.xml.  Second is specific skin_user_nameofskin.xml.

 

skin_user_nameofskin.xml has priority and when is presented feg. for PLi-FullHD skin, then skin_user.xml is not used for this skin, but is used for all others skins.

[cobus]

No it doesnt he only use the skin user skinname xml

[ims]

No it doesnt he only use the skin user skinname xml

but it I wrote ... when is presented skin_user_skinname.xml, then skin_user.xml is not used. It is feature, not bug. Then you can use for each skin own user setting.

Where is your problem ?