Now it become a lot of Google translate And i get the point its your view that all should look like the skin i use and for built in system plugins thats very important

But for any free third-party plugin like MediPortal and simular plugins not part of any OS the GUI is as important as the functions of the plugin.

But we can drop it, i get it and it was just a question from the beginning if its possible to easy use some custom fonts along with some custom itemHeights

and the answer i simple. No

And my second question was. Is it possible for the developers to maybe add this functions to the eListbox

and the answer is No

So if you two can speak for the whole developer Team then we can go and have a coffy break boys

and in the end thanks for taking time and debate this with me

Best Regards Seagen

No problem we have Google translate even if not perfect i get your opinions

And for full image skins i must say that DreamOS is cutting edge. The new way of setting up the skin like you explained in an earlier post is just amazing.

And i look at plugins like apps for Android. When you create a plugin you should also have the freedom to design the look of the plugin

not be limeted to allways have to use the same look as skin default.

All custom skins are not as well done as yours so therfor a plugin might look really bad and also be hard to understand.

The GUI of a plugin is very important to how a user will understand the functions and also of cause the use of the plugin.

And it should be no secret that i am used to skin for OE 2.0 so all this is new for me, The python coding for OE 2.5/2.6 is pretty stright forward

and are easy to adapt to. Its the skinning, some parts of the skinning is incredible nice and easy to work with but they all favor full image skinning

I can set any custom font i want for a label but not for a eListbox.

So my first opininon was how hard can it be to just add that to the eListbox and at the same time keep the eListbox alternatives.

Then we get the freedom to do both

Image skinners can take advantage of the <listboxcontent> but at the same time if needed add an custom font to one or more eListboxes to make skinning more diverce and vivid

Thanks so much Zombi for your reply

And I really do appreciate all answers i get but the mode from all except Zombi is so hostile

I now that the solution i come up with is not correct and does not suit my purpuse since it hi-jack all config listboxes and give them wrong font.

I also get that DreamOS dont give the freedom to assign any custom fonts to a plugin in its present state.

But if you @gutemine have an example where you can show me how to assign a custom font and itemHight to an config listbox that dont effect all config listboxes i really would appreciate that

And again why would a plugin want or need their own custom fonts and itemHights.

Well in my opinion many plugins today are so stand alone and would even be confusing if they all look like skin default

And its also a way of branding your plugins so people easy can recognize them no matter of what image or skin they use.

I have been looking in to Mediaportal plugin and found some hints on how to get around this problem for me.

And i think i might found a solution but my God its a lot of work and a lot of coding just to get a simple font="Customfont; 32" to work for 1 config listbox

I dont now what the bottom of your post is gutemine if its just a footer note or directed to me???

But i can tell you that this plugin we working on got the attention of DreamMultimedia and they accully

sponsored me with an Dreambox One UltraHD so I could develope and convert this plugin for OE2.5/2.6

This is very interesting and thanks for taking time with an old dog like me

My plugin is simple But any way look is allways important but if its not possible to have custom fonts without "misuse of some applet code ;)"

Then i am of the oposite opionion. It wold be in the devs interest to put a stop to this.

I see two simple ways.

1. do what i asked for first just add setFont in to the enigma

2. Give any applet code the ability to be unloaded on exit so the whole global configs get hi-jacked

Or accully a third solution.. Maybe there is a way to use applet code so it only affects the ongoing instance?

I have try this but does not even work

self["config"].instance.setDescriptionFont(gFont("customfont", 33))

self["config"].instance.setValueFont(gFont("customfont", 30))

self["config"].instance.setItemHeight(56)

Okey that makes some sence But as i wrote a couple of post up

You can set custom fonts but then you have to use applet code like this

<widget name="config" position="519,309" size="1372,672" foregroundColor="#ffffff" backgroundColor="#232323" foregroundColorSelected="#ffffff" backgroundColorSelected="#0e6382" itemHeight="56" scrollbarMode="showOnDemand" transparent="1" zPosition="2" />

<applet type="onLayoutFinish">

from enigma import eListboxPythonConfigContent, gFont

self["config"].l.setDescriptionFont(gFont("customfont", 33))

self["config"].l.setValueFont(gFont("customfont", 30))

self["config"].l.setItemHeight(56)

</applet>

And this gives the plugin custom font. Why would i want that you ask

Well Plugin has its own design and look and the font is a important part of that so therefore would i like to use my custom font

And now you thinking this 55 year old Swede must be totaly stupid since he has a solution for his problem

And i do but with this code all settings screens get my custom code??? Every Default-FHD settings screen gets the font

and thats my point it must be a bugg somewhere in the DreamOS core code when some simple applet code

hi-jacks the whole DreamOS skin and not just the plugins skin

And therefor was my first question would it not be nice if the DreamOS developers did add setFont to eListbox so we can set font the good old way

I trying to figure that out bit its in German and my German is as good as google translate

To me his solution looks like a full skin solution while i just look for a simple embedded plugin skin solution

And all works just as i want except that i cant use any custom font in the plugin skin when using standard widgets like eListbox

All my plugin needs is a screen title, some labels and an config listbox that act as my settings page

I want to use my font not the default font thats it and for me who are new to DreamOS this gets very complicated for something that should just look like this

<screen name="Settings" position="0,0" size="1920,1080" backgroundColor="#232323" flags="wfNoBorder">

widget name="config" position="519,309" size="1372,672" foregroundColor="#ffffff" backgroundColor="#232323"

foregroundColorSelected="#ffffff" backgroundColorSelected="#0e6382" itemHeight="56" font="customfontname;32" scrollbarMode="showOnDemand" transparent="1" zPosition="2" />

</screen>

But please just forget it if am so stupid and you all have forgot that you all started from scratch...

Or maybe some one can take it in English??

Well i dont really get you answer gutemine???

Yes there is no problem to get about any plugin to run in DreamOS but i am very new to skinning for DreamOS.

And if i want to use lets say my custom font in the plugin skin how is that possible if i cant set my fonts in my skin files?

They are sett in the python code with no errors or problem and debug shows they get loaded

And for all custom widgets i can of causle also set my fonts. But when calling a regular <widget name="config" then it all goes south.

A friend of mine is a really good coder and skinner and he has built a very good plugin where we have manage to get this working

with applet code.

from enigma import eListboxPythonConfigContent, gFont

self["config"].l.setDescriptionFont(gFont("customfont", 33))

self["config"].l.setValueFont(gFont("customfont", 30))

self["config"].l.setItemHeight(56)

</applet>

But now everything gets really strange

After leaving the plugins setting screen that have this code all settings screens in DreamOS has this font until i reboot Enigma2

If this is not a bug in DreamOS what is then?

And to DreamOS developers would it be to much to ask to add setFont in to the enigma2?? would make life easier for everone

And give us better tools to build vivid nice plugins for this platform

Took some time to translate

But what i understand if a simple skin for a small plugin i can jsu skipp the setFont or in the skin code

i dont need font="Regular;28" as example since plugin can use the default skin settings?

Hi

Lots of reading but German is not my language so read alot with Google Translate

I am and old DMM user who have been gone for many years to the other side

but back again and now try and rapp my head around the new DreamOS OE 2.6

Its alot diffrent since the outdated OE 2.0 and really nice also.

But when it comes to skinning you really have made this complicated for small plugins.

Like when i want to add a simple eListbox widget, i cant set my font???

AttributeError: 'eListbox' object has no attribute 'setFont'

Plugin usally only need a small simple skin but with this OS all gets really complicated

Would it not be nice if you added this small but very important possibillity to the enigma2.py??

Best Regards Seagen