2057 replies to this topic

[WanWizard]

Well if there is nothing extra in the python code how will OpenWebIf import it?

I meant besides the boxinfo class....

[littlesat]

As soon the enigma2.info file is extended with branding info and maybe more I will add the boxinfo global.
But I hope we do not need integers and floats, octal binaries and booleans because the design of the info file is not really designed for this.

Edited by littlesat, 16 December 2023 - 17:52.

[Huevos]

As soon the enigma2.info file is extended with branding info and maybe more I will add the boxinfo global.
But I hope we do not need integers and floats, octal binaries and booleans because the design of the info file is not really designed for this.

What global? BoxInfo is a python class and for compatibility you are going to need everything identical.

 

And also WanWizard already said most of the stuff will be coming direct from the image, not enigma.info.

[littlesat]

I think it is terrible. We tried to get something good but it sounds you lost patience. You check on text on content if it should be boolean, integer float or still a string or even list… in it not consistent and therefor loaded with work-a-rounds. Sorry to say when it was defined a detail was missed. So we tried to do something right here and again some lost patience and did go…
And we build differently so we cannot put all stuff in the enigma.info file. Most stuff is determined at runtime.
The enigma.info file missed something like variable type.
Actually boxinfo is a global the same for SystemInfo… and all system info’s are available by boxinfo as well. So somehow you also have two systems in one thing.

Edited by littlesat, 17 December 2023 - 11:30.

[Huevos]

@Littlesat, "lost patience"? This debate has been going on over 12 years. First, Branding Module, PLi didn't like. Then the Proc module, PLi didn't implement. Now BoxInfo, developed and in use for several years, and PLi don't like that either.

 

The real truth is the problem is PLi doesn't have the data in its build environment... and doesn't even want it either... WanWizard even calls it "litter"...

 

So do you really expect others not to lose patience? And they are not acting alone. It is PLi that is acting alone. All the other distros are acting together.

 

So now PLi is stuck with the obsolete version of OpenWebIf because PLi want to go in a different direction to everyone else (or do nothing at all).

[Huevos]

So Dimitar has added a repo for box logos: https://github.com/D...rCC/e2-boxlogos

 

And in OE-A repo we have added a recipe for that: https://github.com/o...d286ea8bf9793df

[Huevos]

Actually boxinfo is a global the same for SystemInfo… and all system info’s are available by boxinfo as well. So somehow you also have two systems in one thing.

This is not true. You cannot overwrite the values in BoxInfo that come from the text file. In SystemInfo it is a dict that can be written to from anywhere. So bad code in a plugin can affect values everywhere throughout enigma in the case of SystemInfo, but no so with BoxInfo (nor Branding Module).

Edited by Huevos, 17 December 2023 - 14:58.

[littlesat]

It is still a global… but it is the way it is done.. there is a function added to change something. Do you use it? Finally what is missed here is kind of control about the variable type. I just see the red flag and this is about the if then else the way “‘ are removed…. And the way booleans and none is arranged… and numbers…. And then a work around about release versions that could be floats. Maybe the discussion should took longer….. but I’m afraid again I’m afraid you have issues with critism.

Edited by littlesat, 17 December 2023 - 15:17.

[WanWizard]

The real truth is the problem is PLi doesn't have the data in its build environment... and doesn't even want it either... WanWizard even calls it "litter"...

 

No, I wrote "littered around in OE".

 

But all not every relevant, I promised I would take care of generating the complete enigma.info, sometime this week, and I will.

[WanWizard]

It is still a global… but it is the way it is done.

 

Everything but the kitchen sink is global in E2, so if that is an issue, a major rewrite is long overdue...

[littlesat]

Would be nice to have at least something in the enigma.info to indicate the type of variable…. The only way to do it consequently.m
Maybe we did not implement it because it was indeed not good again…. But some were convinced it was good. At least the location of the file is not good. It is not in a config ‘zone’ and the variable types are not good defined.

Edited by littlesat, 17 December 2023 - 15:21.

[WanWizard]

Maybe, but at the moment it is what it is, and it works. So lets not try to find new arguments to justify not implementing it again, it has taken long enough, simply to avoid a few lines of python code.

[littlesat]

Yes you right wanwizard. The discussion is over because waiting more than 12 months was too long to be patience. So now we have tricky code again…… but I think I do the variable types in a different way. For openpli we can do it… at least on a defined way.
The SystemInfo was also from legacy enigma2 and for a long time on nomination to change. When we have boxinfo we can change them anywhere…. And ban SystemInfo….(but maybe we still need it for plugins that use it)

[WanWizard]

Can someone send me a complete enigma.info file as an example? I'm on holiday and don't have access to a non-openpli box at the moment.

[Huevos]

Can someone send me a complete enigma.info file as an example? I'm on holiday and don't have access to a non-openpli box at the moment.

My one from OE-A looks like this.

architecture=cortexa15hf-neon-vfpv4
avjack=False
blindscanbinary=blindscan
brand=vuplus
ci=True
compiledate='20231217'
dboxlcd=False
developername=openvix
displaybrand=Vu+
displaydistro=OpenViX
displaymodel=Ultimo4K
displaytype=colorlcd800
distro=openvix
driversdate='20190424'
dvi=False
feedsurl=http://openvixdev.satellites-xml.org/feeds/openvix/developer/6.4/vuultimo4k
fhdskin=True
forcemode=no
fpu=hard
friendlyfamily=vuultimo4k 
hdmi=True
hdmifhdin=True
hdmihdin=False
hdmistandbymode=0
imagebuild='010'
imagedevbuild='019'
imagedir=vuplus/ultimo4k
imagefs=tar.bz2 
imagetype=developer
imageversion='6.4'
imglanguage=multilang
imgrevision='010'
imgversion='6.4'
kernel='3.14.28-1.12'
kexecmb=True
kernelfile=kernel_auto.bin
machinebuild=vuultimo4k
mediaservice=servicegstreamer
middleflash=False
mkubifs=-m 2048 -e 126976 -c  
model=vuultimo4k
mtdbootfs=
mtdkernel=mmcblk0p1
mtdrootfs=mmcblk0p4
multilib=False
multitranscoding=False
oe=OE-Alliance 5.3
platform=vuultimo4k
python='3.11'
rca=False
rcidnum=2
rcname=vu2
rctype=0
rootfile=rootfs.tar.bz2
scart=False
noscartswitch=
scartyuv=False
smallflash=False
socfamily='bcm7376'
svideo=False
timerwakeupmode=0
transcoding=True
ubinize=-m 2048 -p 128KiB
vfdsymbol=False
wol=True
wwol=True
yuv=False
checksum=b24743748d2c4b3bfaade400afb0e5aa

Note: things like python version are wrapped with quotes so they parse as strings. e.g. 3.10 becomes "3.10" in the enigma.info file. Otherwise it will parse as "3.1". Anyway anything that could be understood as numeric, but that is not needs to wrapped in quotes.

Edited by Huevos, 17 December 2023 - 16:16.

[Huevos]

Also note, things like "distro=openvix" and "model=vuultimo4k" should be uniform across all distros (except where model names don't match) because they are used if conditionals, but other things like displaydistro and displaymodel don't matter because they are only used in the GUI output, lot for code logic.

Edited by Huevos, 17 December 2023 - 16:21.

[littlesat]

A lot of them we do on runtime do we really need them in this info file?

[WanWizard]

A lot of them we do on runtime do we really need them in this info file?

 

I will remove them at runtime, that is the purpose of this exercise.

[WanWizard]

For items that need a specific value, is there documentation available of what those should be? Fields like "brand", "displaytype", "rcidnum", "timerwakeupmode", etc?

 

And what about data we don't have, like "imagedevbuild", "imgrevision"?

[4l3x2k]

Take a look at https://github.com/o...ter/doc/BOXINFO