Thanks dhwz for nice answer and i can see your point when its so good explained.

I was just concern that we might start to fallback because of this, But you have calme down

Thanks

Thanks for your answer Reichi

The last first.. Is there a timeline for this release???

And to my statement about people choosing Box A or Box B depending of python version.

If popular plugin developers move from python 2.7 to python 3 you as a developer now that it would be some trouble with missing dependency files.

Anyway this does not matter i bend my neck for you and moves on back under my rock...

Yes i know that lots of plugin are py3 ready... I am involved in some of the development my self .

I also got my Dreamboxes sponsored by DP but i am not here to brag about my self or any project i am involved in.

I asked about the python version and when or if python3 is to be implemented, the answer at the moment is

We are running on python 2.7 and until there is a whole new OE we will run on python 2.7

The reason i guess that one of the Developers or Admins can answer better then you and me bitching about this

Now you are threding needles my friend

OE-Allince builds are common now as OE 2.0 images among regular users, And DreamOS are OE 2.5/2.6 by the same users

Then of cuase you are totaly correct but you get my point about the python question i assume

Well lets call "them" for what they are then.. OpenSorce (OE 2.0) images built on the OE-Alliance are using Python 3 now

Its over 1 year since it was announced that python 2.7 was to be cancel Januari 2020.

Its good news that DP and others are working on DreamOS to also move to Python 3 i did read that in your post

But as i said before see no reason why "them" can adapt who use an old outdated Enigma version when "we" are on the newest.

I just wonder why dhwz is claiming that we need a whole new OE for this??

Well others have converted allredy so thinking about it does not solve the fact as you self state. Thirdparty developers are moving over to python 3

And if others who use OE 2.0 can do it i see no reason why "we" cant do it also.. And with we i mean us who are Dreambox/DreamOS users.

I am also pretty sure that Dream Property want to be at the tipp of the sword and not in the other end

And just so we dont have to be stuck in this whats best and not.

I love my Dreamboxes.. They work super.. And my involment with thirparty plugin for DreamOs is also very fun.

Maybe thats the reason why only 10% is sold world wide

You gave me a good with your jokes...

I am from Sweden (Scandinavia) and here Dreambox was the number 1 choice but as the year progress other brands have taken over

Brands that ususal are referd to as running on an old outdated Enigma2. But they are moving on to Python 3 since the old python we are using

was stopped early this year. Also plugin creators are moving over to python 3. since the most Global users have turned away from Dreamboxes.

And that we still are stuck with an outdated python version is as bad as an outdated enigma2 when the future are forward

Sorry if i sound a littl bit grumpy now

But why is it that This forum publish everything in German?? The most common language for Global users are English

All coding is done in English and so on

Or is Dreambox only for Germans??

Thanks for the link to Python 3 Joe99

Amazing

Python 2.7 have been shutdown and are no longer updated i was surten that latest OE 2.6 hade support for python 3

Is this going to be addresed soon obi  Reichi

What is the python version for OE 2.6???

You have to set a password from:

Menu >> System >> Password to get access to your box

I have no issue with recordings but did read that you need a gutemines user script plugin installed

Just search this forum and you find the info

Not sure about the 1080p and older plasma TV have you try 1080i settings.

I use my box and a Samsung UHD Tv but as a test i moved the box to my old computer screen and it scales perfect from UHD to FHD over a DVI port

This issue seems to be fixed with the latest update of image so do an software update and problem should be gone.

I have a good access to the plugin and if it was an issue with all other skins i would instantly agree with you

But why would anyone have to open up the skin.xml of any skin and find what the color code is and then use only them if they create a plugin??

You must missunderstand me somehow.

Its not a problem as long as your skin gets used with default settings as downloaded. But when using the styles and change the skin apperance

i assume that color code gets copied from the main skin.xml into the styles.xml file?

Now for some reason the skin also try and copy the color code from the plugin

In this case the color code "Header" and of cause this code is not in the main skin.xml so this fails and cause the GreenScreen from ....

But if i put the color code into the main skin.xml for your skin of cause it gets copied and therfor all is good again.

So please explain to me how this can be the Plugin causing the problem?

Really want to now so i can fix this problem if thats the case.

But i am still more into an issue with DreamOS or how the styles have been setup to work?

Accully after further investigation and test with manufactor image, this is probably a bug in DreamOS or your plugin Styles or a combination.

Because the color code color 'header' is part of the skin.xml for the plugin not your skin.xml

so why it get picked up of your skin is a real mystery?

Yes but for IPTV we need to add a custom source from the provider thats not in any source list of any plugin.

But with JedimakerXtream and the OpenSource plugin EPGImport this can be done.

I ported this plugin over to DreamOS (DreamElite) but all hell broke loose even if i was very clear this is not my plugin and all credit goes to the author of the plugin

JediMakerXtream i can answer for

Jedi creates a source in plugin EPG Importer.

I know there is a Plugin with same name for DreamOS (DreamElite) but that plugin is not the same as the OpenSource EPG Importer you are used to in your OE-Alliance image.

So the custom add of source does not work.

Sorry about the posting just delete this thread if its agains any rules or your own policy

Hi zombi

I use your skin in my Dream One UltarHD with image DreamElite7 and i have a question tou you.

I guess that styles are only for merlin image? or should styles also work with other DreamOS Images like DreamElite?

I have also try GP4 with same issu

Reason i am asking is when using styles i get a crash of missing or wrong color code when open a skinned plugin?

I.f i put the color code for header into the skin.xm of skin Zombie-FHD then all works fine and i can also use styles.

Is it something in the plugin i can add so it does not mix up with your skin, or is this a known bug in the Styles or a compatibility problem?

This is my crashlog:

Traceback (most recent call last):

File "/usr/lib/enigma2/python/enigma.py", line 9643, in __call__

return ret (* args, ** kwargs)

File "/usr/lib/enigma2/python/Components/ActionMap.py", line 72, in action

res = act ()

File "/usr/lib/enigma2/python/Screens/PluginBrowser.py", line 48, in save

self.run ()

File "/usr/lib/enigma2/python/Screens/PluginBrowser.py", line 52, in run

plugin (session = self.session)

File "/usr/lib/enigma2/python/Plugins/Extensions/XStreamity/plugin.py", line 117, in main

session.open (main.XStreamity_Main)

File "/usr/lib/enigma2/python/mytest.py", line 490, in open

dlg = self.current_dialog = self.instantiateDialog (screen, * arguments, ** kwargs)

File "/usr/lib/enigma2/python/mytest.py", line 391, in instantiateDialog

return self.doInstantiateDialog (screen, arguments, kwargs, self.desktop)

File "/usr/lib/enigma2/python/mytest.py", line 433, in doInstantiateDialog

dlg.applySkin ()

File "/usr/lib/enigma2/python/Components/GUISkin.py", line 117, in applySkin

self.createGUIScreen (self.instance, self.desktop)

File "/usr/lib/enigma2/python/Components/GUISkin.py", line 27, in createGUIScreen

if not val.applySkin (desktop, self):

File "/usr/lib/enigma2/python/Components/GUIComponent.py", line 39, in applySkin

skin.applyAllAttributes (self.instance, desktop, self.skinAttributes, parent.scale)

File "/usr/lib/enigma2/python/skin.py", line 447, in applyAllAttributes

applySingleAttribute (guiObject, desktop, background_key, background_val, scale)

File "/usr/lib/enigma2/python/skin.py", line 363, in applySingleAttribute

guiObject.setBackgroundColor (parseColor (value))

File "/usr/lib/enigma2/python/skin.py", line 197, in parseColor

raise SkinError ("color '% s' must be #aarrggbb or valid named color"% (str))

-------

skin.SkinError: {Zombi-FHD / skin.xml}: color 'header' must be #aarrggbb or valid named color

Best regards Seagen

I know that DreamOS only support thoose servicetypes but there are many users out there who use this amazing software for other Images then DreamOS

so they might get an hickup if Dreambox Edit hade stop support for other service types

Ayway thanks for an amazing software