History Zap Selector by ©Dorik1972

UPDATE

1.0.25

1) Fixed crash when selecting the translation language in settings and by long pressing the "yellow" button (my "fault" made a mechanical typo)

2) Slightly redesigned pop-up messages when calling the EventView system window. Now it is clearer for the user what to "click" and why

3) Added wrap class for eServiceEvent and now it will be possible to translate everything on the skin screen. I will experiment and if it isn't "dumb" - I will add translation of program names by analogy with descriptions

4) Removed all locales with translations that are very outdated

On some Python2-based images there was a crash when calling EventView in version 1.0.25. I fixed it and updated it under the same version index. If you don't have a crash, you don't need to reinstall.

I did some experiments with the possibility of translating the entire list of channel changes along with descriptions and names of programs... In principle, it works quite fast provided that the list is not more than 20-30 entries. Processing speed directly depends on the speed of your internet connection and the number of records... On a list of 30 records on my VU+ Ultimo4K or DM900UHD with a 1Gbit/sec connection, the process takes about a second. This is tolerable and not particularly annoying to use. It looks like this and works if automatic translation to a given language is enabled

Снимок экрана 2023-10-27 в 12.41.27.png

This feature, as well as the ability to translate the names of programs, will be included in the next version and will be available only to "key" owners ... I will also have to limit the list size to 30 instead of the 60 allowed at the moment so that there are no complaints about "slowing down" ... Every time I have to explain that "miracles don't happen" I have no desire to do that

UPDATE

1.0.26

1) Fixed crash on Open ATV 7.4 and OpenVix 6.4 which was reported by some users by providing the log of this error.

2) The logic of the operation has been changed if the default translation language is set. Now, if the “Use default translation for EPG event descriptions” option is enabled, then when you call the plugin, all information on channels in the list of switches will be translated into the language specified in the settings (works only for those who donated for development)

Снимок экрана 2023-10-27 в 12.41.27.png

3) When calling the translation of an EPG event, the name of the event is now translated, as well as its description

4) In the settings menu, at the request of some users, information about the plugin version and the image used has been added

UPDATE

1.0.27

Added translation caching to avoid second requests to the API. This has significantly improved smoothness and usability when automatic translation to a given language is enabled

Enjoy!

I ended up decomposing the E2 source code into "atoms" and now I can, on any image, swap the InfoBar information when I want and for what I need

Снимок экрана 2023-10-31 в 12.31.27.png

I think that the next update will already have the ability to auto-translate the infobar content directly in the used image by analogy with the EventView window ...

Quote from Mahmoud Hussein

I think 2nd infobar bar will be a good target for translation especially the event description for current and next event......

I will be nice if you add extra option on/off for translation of 2nd infobar events in general manu settings of the plugin itself, similar to event view option.

It's nice that you're so savvy That's exactly how it will work ... Or rather it already works ... I originally thought of adding auto-translation of EPG information in SecondInfobar, because it is more "informative" in comparison with the standard InfoBar.

The screenshot below is an example from my DM900UHD ... this was the most difficult task .... The original language of the EPG on the channel is Russian ... The result of auto-translation - on SecondInfoBar

Снимок экрана 2023-10-31 в 22.26.26.png

And this is what it looks like on OpenPli ...

Снимок экрана 2023-11-01 в 00.07.06.png

Quote from Mahmoud Hussein

Moreover, I think history zap needs to support running text in it's man interface, history zap selector channel raw consist of (channel name, progress bar with event time, event name and event description)

EVENT description many invisible because the limited space, so we have two option

Why this "masquerade" of running lines? To make your eyes "scatter" when looking at the screen and you do not have time to read or perceive the information from the screen? Event description does not fit in a line? - USE the "green" (EPG-Info) button on the desired entry in the list

Quote from Mahmoud Hussein

1. To remove event description from the raw, might this make the plugin faster.

2. Reduce the number of raw and make space below to display the description

1. It's a fantasy due to a lack of understanding of how it works

2,. Make any skin to suit you. I've posted earlier how users have customised the plugin skin for their needs, there are even posters placed like yours on the screenshot in the post above. What does the plugin code have to do with it. Make whatever skins you want. You don't need to make any changes to the plugin code to do this ... Re-read your question in the other thread on this plugin and my answer to you in p1)-. RE: History Zap Selector for OpenPli (6.x-9.x) © Dorik1972

Is it necessary to display the translation of the event name on the second infobar or is only the translation of the description sufficient?

linuxsat-support.com/cms/attachment/242925/linuxsat-support.com/cms/attachment/242926/linuxsat-support.com/cms/attachment/242927/linuxsat-support.com/cms/attachment/242928/

Quote from Mahmoud Hussein

I love to get everything translated on my screen, may be you disagree with this idea but nothing depend on event name in 2nd infobar, i.e posterx and xtraevent already behave normally, so if it hard to translate, description will be enough.

OK ... I more or less agree with you on this one. On the first InfoBar I leave the original name of the event. When SecondInfobar is called, the event description will be translated as well as its description into the default language set in the HistorryZap plugin settings.

First InfoBar

Снимок экрана 2023-11-03 в 13.25.29.png

SecondInfoBar

Снимок экрана 2023-11-03 в 13.25.40.png

Quote from Mahmoud Hussein

if it hard to translate, description will be enough.

If you know what to do and how to do it - nothing complicated

UPDATE

1.0.28

1) Added SecondInfoBar translation function. Can be On/Off in plugin settings when translation to the default language is enabled. In theory, it should work on almost any skins, including "homemade" (not included in the original image). Just in case, I have added a message output to the system log if non-standard classes and methods are used in the skin you are using. If this feature does not work on your skin, just report what is displayed in the log when SecondInfoBar is enabled, and support for this skin will be added. But such skins, I hope, will be very few.

An example of how it looks on DreamOS-based images using the seconfinfobar plugin

Снимок экрана 2023-11-03 в 13.56.27.png

An example of how this looks on the OpenPli image

photo_2023-11-03 13.56.39.jpeg

Quote from Mahmoud Hussein

still same comment about deactivate the channels list, you have to perform full restart in order to restore it back.

I repeat 100500+ times that the HistoryZap plugin does not interact in any way with the list of channels in your image, nor with any image code responsible for the list of channels or their switching. It does not make any changes or modifications to this code. Installing any plugin is just unzipping the files into a given "folder" and nothing more. If you are ready to claim that everything you describe happens because of the plugin - provide a log where you can see it or a clear step-by-step description of how to repeat it.

All that you "describe" may be due to the fact that instead of the original "channel selector" you use some third-party plugin responsible for it, but not because of HistoryZap.

Quote from Mahmoud Hussein

(I am currently use the modern one, folders inside folders)

This is the greatest "modern" stupidity. Since the formation of the structure of "multibouquets" is hard-coded in the image itself and does NOT allow for "folder" within "folder"... In any image it is "root-bouquet"-"bouquet-sreviceref"-"srviceref" and no variants as "root-record"-"bouquet-sreviceref"-"bouquet-sreviceref"-"srviceref" ... In order to realise this possibility, drastic changes must be made in very many places in the python code of the image you are using. I have never seen ANY source code in any image where this has been done. If it is done by any third-party plugin, it is the stupidity of its author and a complete misunderstanding of how "bouquets" are formed in any E2 image.

Thanks for understanding!

p.s. To implement the "nesting" of folders (bouquets), it is necessary to rewrite the ChannelSelection.history list function, making it "recursive" for "forming"/"reading" history list elements... It is not difficult. However, it is not implemented in any of the image's source code which is available on GitHub. It is possible only by rewriting several "pieces" of code, first of all in Screens.ChannelSelection class and its subclasses... With the help of a third-party plugin, for example, by means of class definition, it is impossible to make it work universally everywhere. There are too many differences in different branches of "development" of E2-images in this code