214 replies to this topic

[Erik Slagter]

OK, thanks.

[ims]

ver. 1.02:

- restart gui after changes in current skin (yes/no)

- added LiberationSans-Italic, Bold, BoldItalic

Attached Files

•  enigma2-plugin-extensions-modifyplifullhd_1.02_all.ipk   3.66KB   10 downloads

[littlesat]

Why this ipk?

[ims]

user can very easy changing colors of Top and Bottom as he want and change Regular fonts in skin.

Edited by ims, 8 February 2015 - 10:37.

[Erik Slagter]

Yes and as it controls a skin (which is not part of enigma) the code should not be in enigma itself.

 

Maybe we could make a dep on it? But then it may not be working on other images.

[Erik Slagter]

I have updated it in the feeds.

[ims]

thx.

[Pedro_Newbie]

SInds vandaag is mij opgevallen dat bij de progressbar bij het afspelen van een opname er zwarte vlakken zichtbaar zijn, lijkt mij iets met de transparantie

Skin: Pli-FullHD

 

[ims]

I forgot set back transparent background, when I made correction in coordinates and for better setting I temporary set background to black. Today was fixed

[Pedro_Newbie]

OK thanks, I will update tomorrow

[Erik Slagter]

Thx, here same.

[ims]

Modify 1.03:

 

- added color for selector !

- added color for added transponderinfo

 

- added button for recreate = remove .xml and create new.

 

Who using version before - please - remove and create new .xml ( can be made from plugin with blue button ). If you have added some own changes in, make backup before, recreate and then manualy add into new file own changes.

Attached Files

•  enigma2-plugin-extensions-modifyplifullhd_1.03_all.ipk   4.43KB   3 downloads

[ims]

v. 1.04

- fixed problem with close

- .bak before recreate

Attached Files

•  enigma2-plugin-extensions-modifyplifullhd_1.04_all.ipk   4.44KB   4 downloads

[Erik Slagter]

Can't you prepare a version ready to be included in plugins-enigma2 or e2plugins?

[ims]

I thought about it, but it is very specific (and little "ugly" made in hurry) plugin used for this 2 skins and for PLi only -due it is not suitable to add it to e2plugins (it is not problem add it for me). And in plugins-enigma2 it will be for you same work as change it in feed, imho. In future I would to find a way, how change this parameters online in memory, not with user-skin. But is not time and idea now...

 

There will not be so much changes more. I added new 2 menu items - I hope, I will must not change blue progressbar to grey progressbar

[Erik Slagter]

Still I'd like to have it in plugins-enigma2.

 

Actually appling a patch to plugins-enigma2 is quite a bit less work than adding a 3rd party plugin to the feed. Also we're planning to remove the 3rd party feed at some time altogether, because it gives all sorts of problems.

[ims]

And when I will add it into my own github ? It would be possible ? I want not add it to e2plugins, when it is PLi specific...

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

[Erik Slagter]

Yes that is possible, but I'd prefer to have it in plugins-enigma2. If you fork it, you can work on it yourself an send a pull request when it's ready. I find pulling easier to deal with than applying patches.

[ims]

but in github it is without assistence and more operative for author ...

[Erik Slagter]

You only need github to push your stuff to. The web interface is awful, I try to avoid it as much as possible.

 

Here is how I would do it, it sounds complex but it really isn't.

 

- git clone plugins-enigma2 to directory on your harddisk

- create your own github repo with the same name (this is the only point where you have to deal with the awful github webif)

- set your cloned repo to have the github repo as parent ("origin", "upstream")

- push once to populate the github repo

- work on your local repo, make commits, and push if it's finished

- tell us once the url of the github repo and we'll add it as upstream to our local repo's

- tell me when it's finished, I'll do a pull (from) you and a push (to the pli repo)

 

If you're going to work on several things, in the same repo, at the same time either:

 

- only commit/push one change and wait until it's pushed by us OR

- make a branch for each project and tell which branch to pull (preferred) OR

- tell us which commit to cherry-pick (if it's only one)