592 replies to this topic

[littlesat]

What I mean is that the 'website' from the images somehow parses the image list from the image builders.... and then 'adjust' the json file... instead of enigma2 letting parse multiple feeds....

Then also the differences of boxnames could be compensated... as the boxname is in the URL....(and the filename etc is from the image).

 

So let the image builder feed solve it... then also only one json needs to be read... The only thing what you can add in enigma2 is an 'image filter' that could filter out some images....

 

It is still not a good idea to have a feedlist from multiple images in the enigma2 code... hard-codes...

 

 

Alternativaly it is always better to have at least this

FEED_URLS = [
("openATV", "https://images.mynon.../openatv/json/"),
("OpenBH", "https://images.openbh.net/json/"),
("Open Vision", "https://images.openv...dedyn.io/json/"),
("OpenViX", "https://www.openvix.co.uk/json/"),
("OpenHDF", "https://flash.hdfrea.../openhdf/json/"),
("TeamBlue", "https://images.teamblue.tech/json/"),
("Open8eIGHT", "http://openeight.de/json/"),
("OpenDROID", "https://opendroid.org/json/"),
("EGAMI", "https://image.egami-image.com/json/")
]

in a config file... minimal! I think it is not done to have this hard-coded.

Edited by littlesat, 24 April 2023 - 10:33.

[Huevos]

Well like I said in my post you should not be parsing multiple feeds. You should decide which distro you want to download from and load the list from that distro.

 

The way it has currently been done in PLi mean you are downloading 10 json resources at the same time, instead of just one like other distros do it.

Edited by Huevos, 24 April 2023 - 10:39.

[Taapat]

I agree with Huevos that it is better to choose a distro first, and only then download json with available images.

 

How the download of the json file is implemented does not change this logic.

 

I personally don't see anything wrong with the fact that the distros is hard-coded in enigma.

Anyone can fix this and test the fixes if they notice something isn't working.

If you create a feed maintained by one person, it will be difficult to explain from the outside what needs to be changed and test the changes.

[Ev0]

What I mean is that the 'website' from the images somehow parses the image list from the image builders.... and then 'adjust' the json file... instead of enigma2 letting parse multiple feeds....

Then also the differences of boxnames could be compensated... as the boxname is in the URL....(and the filename etc is from the image).

 

So let the image builder feed solve it... then also only one json needs to be read... The only thing what you can add in enigma2 is an 'image filter' that could filter out some images....

 

It is still not a good idea to have a feedlist from multiple images in the enigma2 code... hard-codes...

 

 

Alternativaly it is always better to have at least this

FEED_URLS = [
("openATV", "https://images.mynon.../openatv/json/"),
("OpenBH", "https://images.openbh.net/json/"),
("Open Vision", "https://images.openv...dedyn.io/json/"),
("OpenViX", "https://www.openvix.co.uk/json/"),
("OpenHDF", "https://flash.hdfrea.../openhdf/json/"),
("TeamBlue", "https://images.teamblue.tech/json/"),
("Open8eIGHT", "http://openeight.de/json/"),
("OpenDROID", "https://opendroid.org/json/"),
("EGAMI", "https://image.egami-image.com/json/")
]

in a config file... minimal! I think it is not done to have this hard-coded.

 

OpenBH should be OpenBh
 

[littlesat]

I agree with Huevos that it is better to choose a distro first, and only then download json with available images.

 

Please no!

Better to get your own distributions directly and have an option with a  button or so to select one or more from the others.

 

Yellow is remove downloaded. It can be adapted when you are not on the downloaded to 'select feeds'.

 

I have the idea to remove the alternative feed from the image and go for a feedlist in a kind of config format (where you also can manually add your own build-server as feed).

 

The box name is also a thing that should be resolved here....

Edited by littlesat, 24 April 2023 - 14:35.

[neo]

 

Just change the "alternative url for images listed on Flashimage" (Menu - Setup - System - Customize) into 'all' and all images will be visable.

 

And If I do, where do I leave my alternative URL?

 

 

Can we get this back please? I need to be able to flash my homebuilds, like many other developers and testers I assume?

[littlesat]

Put the list in a config file so you can add your home builds in this list and change it to a dict with the image names as
Key

[Huevos]

 1.jpg   122.61KB   4 downloads

[Huevos]

 1.jpg   122.61KB   4 downloads

 

"My build" is a user config and shows if the URL variable is not empty.

Edited by Huevos, 24 April 2023 - 22:47.

[littlesat]

@Huovos,

 

That was exactly I was thought about.... a yellow or blue button, then select the image and go back with the list of that specific image. And indeed having an option alternative when it has a value starting with http. And when you enter the flash screen just show your own image feeds by default... (then also the imagte screen itself does not have extreme long options)

 

What we also miss is the box names.... I hope it is possible for OE-A to finally go for the box names the manufacturers themselves did suggest.... Otherwise this will be a real tricky thing. In the FEEDS list (I prefer to change this in a dict) you need something to add, e.g. a boxname conversion tupple or so, to arrange renaming... brrrrr....

 

I also see that most image need to change something in the naming of the images... as it is not really the standard I suggested with the flashimage code I started years ago.

Edited by littlesat, 25 April 2023 - 09:22.

[Huevos]

What we also miss is the box names.... I hope it is possible for OE-A to finally go for the box names the manufacturers themselves did suggest.... Otherwise this will be a real tricky thing. In the FEEDS list (I prefer to change this in a dict) you need something to add, e.g. a boxname conversion tupple or so, to arrange renaming... brrrrr....

I think most boxes have the same names. Main difference is boxes such as h9twin and h9combo where OE-Alliance has separate images and PLi uses the same image for both.

 

But anyway if there is a name difference the request will just return empty.

[littlesat]

Yesterday I tried it with "all" on an vuultimo4k and only from a few feeds I get something back....

 

Getting an empty return is I think not really optimal. 

 

Looks like for the h9twin/combo the manufacturer offers on BSP which is the same for two slightly different boxes... 

Edited by littlesat, 25 April 2023 - 10:15.

[Frenske]

I can’t contribute to this topic but I wonder what Zgemma hardware has to do with VU+ 4K multiboot.

[neo]

Put the list in a config file so you can add your home builds in this list and change it to a dict with the image names as
Key

 

Pretend I am an end-user who currently has a homebuild feed configured and has no clue what a "dict" is...

[littlesat]

Zgemma hardware has to do with VU+ 4K multiboot.

Good point... but due to this thread the multi images multiboot feature was somehow triggered....

[littlesat]

Dict(ionay)

FEED_URLS = {
"openATV": "https://images.mynon.../openatv/json/",
"OpenBH": "https://images.openbh.net/json/",
"Open Vision": "https://images.openv...dedyn.io/json/",
"OpenViX": "https://www.openvix.co.uk/json/",
"OpenHDF": "https://flash.hdfrea.../openhdf/json/",
"TeamBlue": "https://images.teamblue.tech/json/",
"Open8eIGHT": "http://openeight.de/json/",
"OpenDROID": "https://opendroid.org/json/",
"EGAMI": "https://image.egami-image.com/json/"
}

Edited by littlesat, 25 April 2023 - 15:11.

[neo]

I know what that is, but you don't honestly expect an end-user to start hacking that?

 

Point is: there was a config item in the GUI to enter my homebuild URI, and that is now gone. Please reinstate it.

[Taapat]

I guess the neo homebuild URI doesn't contain "http".

Therefore, it no longer works after this changes.

 

Therefore, you should not assume that alternative_imagefeed is a url that must contain "http".

[neo]

My point is that that field has been repurposed, and I need to enter "all" to be able to flash other images. And that forces me to remove my own URL.

 

So I can have my home builds, or all other builds except my home build, but not both?

 

edit: and yes, my homebuild url is a full http URL to my local webserver.

Edited by neo, 25 April 2023 - 16:02.

[Huevos]

I can’t contribute to this topic but I wonder what Zgemma hardware has to do with VU+ 4K multiboot.

So topic is multiboot Vu.

 

With that topic comes the opportunity run images from other distros, and download images directly from those distros.

 

Dima73 added the possibility to download from other distros into PLi's ImageManager. This works for all multiboot hardware, not just Vu+.

 

Later Littlesat talked about boxname differences.

 

Boxnames differ between PLi and OE-Alliance on some hardware.

 

Zgemma h9twin/combo is one example of this.