delagroov

Thanks

Some tweaks
https://github.com/d...leases/tag/vs58

What worries even more is that i proposed to make you contributors in my MQB fork, so you can add your own Pli stuff and do a pull request yourself, but apparently pli is not interested in getting MQB workin.

Appearently not..

Specific fix has been done on request of Littlesat..but Pli does not use it.

Keep in mind  MQB version in feed is not usable for 8 months..and I think users are important

What worries even more is that i porposed to make you contrubutors in my MQB fok, so you can add your own Pli stuff, but appearently pli is not interst in getting MQB workin.

Hmm..you are sure about that, letting plnick do all the work then.

LOL

 

One was complaining long time ago about not commiting back, and pointing out by littesat one is only usin original MQB from e2openplugins
And ther is no point to have it in feeds for Vu+..AFAIK it should also work on others.
http://openpli.org/f...e-2#entry317724

 

 

Posted 3 December 2012 - 21:04

Is dit dan ook als commit request doorgestuurd naar de eigenlijke bron e2openplugin? Alleen zo komt die mqb in openpli... Want wij maken gebruik van de originele e2openplugins

Edited by littlesat, 3 December 2012 - 21:11.

 

Posted 4 December 2012 - 09:20

Ik kan daar op e2openplugins niets doen... maar iemand zou daar wel een commit op kunnen pushen...

Ik begrijp ook niet waarom de oe allince de e2openplugins forkt ipv er voor zorgt dat er maar ook iets terug komt...???

MQB e2openplugins is van plnick en dient als basis..net zoals ander plugins geforked zijn om aan specifiek image aan te passen.
Plnick van Vti heeft in MQB voor Vti ook meer opties, aangepast voor Vti menu en die commit dat naturrlijk ook niet naar e2openplugins MQB

Dus ik denk dat iemand MQB kan forken en dan aan passen voor Pli specifieke buttons en die gebruiken.

Edited by delagroov, 4 December 2012 - 09:24.

No wonder one gets an other MQB version 2.4 from feed, which is older and as the packagename suggests.

 

It appears that MQB 2.7.13+ is not used from Github at all,

In this case HbbTv for redbutton is useless, as the E2openplugin/MQB is not used in Pli

 

 

Package: enigma2-plugin-extensions-multiquickbutton
Version: 2.7
Description: Multi Quickbutton editor/wizard/code interpreter for keyboard and RC
Section: extra
Priority: optional
Maintainer: emanuel
Architecture: mipsel
OE: enigma2-plugin-extensions-multiquickbutton-2.7
Homepage: http://www.i-have-a-dreambox.com/wbb2/thread.php?threadid=111878
Depends: libgcc1 (>= 4.1.1), libc6 (>= 2.3.5+cvs20051107), libstdc++6 (>= 4.1.1)
Source: ftp://www.unknown.com/emanuel/enigma2-plugin-extensions-multiquickbutton-2.7.tar.gz
 

 

 

Seems there is only an old MQB vs 2.4 in the feed, when I tried it on solo2 with no HbbTv support for red button
 

if Plnick wants to merge Pullrequest the needed HbbTv button wil be in it for E2Openplugins/MQB-vu version 2.7

 

https://github.com/E...vu/pull/2/files

Hi Stigarta,
I already tested it with yellowsoft , but i was not convinced to use that color also for evennames and epg in left screen

Ok, i can understand your decision.
I think yellow is a little bit to bright, because i like colours, that are not so bright
Give it an yellow between yellow and yellowsoft?
Or is it possible to use white?

THX for your answer and your very good work

Yes ...it is possible and I agree that the yellow is to bright.

So i changed yellow and it has less saturation now, so its same color only less bright

Try this one

Hi Stigarta,

I already tested it with yellowsoft , but i was not convinced to use that color also for evennames and epg in left screen

So for the moment i kept the color in yellow and only use yellowsoft for description in channellist.

made some new changes today and increased videosize picture..

if one can not wait for the next update you can use attached skin.xml

Zoals bij veel zaken speelt smaak een grote rol. Zoveel hoofden zoveel zinnen.
In eerste instantie was ik persoonlijk 'minder gecharmeerd' van de kleur van de achtergrond. Op dit moment vind ik het na enige gewenning toch een prima skin met een lekker rustig beeld.
Mooi zo laten zou ik willen zeggen en vooral doorgaan!!!

Dat is precies mijn insteek .
S' avonds is het rustig aan de ogen en toch scherp.
Dat het op verschillende TV anders uitwerkt is een variable factor/afhankelijk van de instellingen of mogelijkheden van je TV

Mijin samsung is erg goed in zwart tinten, dus is het hier goed. En neutraal gecalibreert zonder te extreme waarden of beeldverslechteraars

Bij een ander is het misschien te grijs...

Can gave an exapmle how that would work to call

Now i see a problem to give the specific config screen a title

I suggest to use specific names in the plugins for calling configs

class EPGImportConfig(ConfigListScreen,Screen):

class AutobackupConfig(ConfigListScreen,Screen):

This way it does not confict when using it in skins....

But why using a new title in choicebox?

I have deleted the directory fonts from github and the lettertype is DejaVu Sans vs 2.3

The are free for commercial use, so this would be okay then.

Okay now i took yours

https://github.com/d...Li-HD-Night.git