11 replies to this topic

[pcd]

Attached plugin MainmenuConf will add horizontal mainmenu options for any HD or Full-HD skins.

In the plugin - select configure option from :-

Horizontal animated
Horizontal icons
Vertical menu (normal skin menu)

Also two colour options :-

Black
Blue


Regards, pcd.

Attached Files

•  enigma2-plugin-extensions-mainmenuconf_4.0_r0_all.ipk   53.94KB   59 downloads
•  screenshot1.jpg   65.32KB   12 downloads
•  screenshot2.jpg   83.51KB   9 downloads
•  screenshot3.jpg   104.56KB   10 downloads
•  screenshot4.jpg   59.67KB   9 downloads

[Matrix10]

pcd

 

Already now it is possible to create vertical and horizontal menu panels without the addition of plugins.

We have a problem with the order in lists
not only in the Main Menu, but in all other Menus Setup/System/ etc.

Because plugins occupy unpredictable position, the position set out in the plugin and not within the image or some skin lists or file

This is what prevents the stable use of icon positions inside Menu panels.

I think someone should modify Menu.py
to read plugins positions from XML file as well as standard additions/screens in the images menu.xml.

 

Or any other suitable methods
this method in Menu.py does not meet modern skins and skinning.

Only if the plugin is not in the list he would have to go to the end of the Menu Panels
and not as far to the unplanned position.

 

Rgd MX

 

 

Attached Files

•  shot66.jpg   56.04KB   0 downloads
•  shot64.jpg   108.24KB   0 downloads

[Matrix10]

some shots

Attached Files

•  shot64.jpg   108.24KB   6 downloads
•  shot65.jpg   79.18KB   6 downloads
•  shot66.jpg   56.04KB   6 downloads
•  MX_HQ10XV2.jpg   60.75KB   7 downloads

[Matrix10]

Let me repeat once again this issue and problem for image/plugins developers
it would be good to those who are able to make better options and coding for Menu panels.Not only Main .
Better coding for graphical support.

Support for different types of Menu, Support for order in the menu panels,

horizontal / vertical menu support, support for icons ( for background and selected icons ) ,support for the buttons movement in all directions, etc.

Or at least part for the beginning.

At the moment the main problem is the order of the Menu panels,that is not fixed but more random with Plugins additions.

 

It is far too limited
This standard E2 coding is old for many years.

Edited by Matrix10, 20 September 2016 - 14:25.

[pcd]

Hi Matrix10,

 

I am not sure if I fully understand your proposals.

 

Menu.py is included in enigma in the image. The image enigma is changed frequently.  So - if Menu.py is changed in a plugin - with software update it will be overwritten. Therefore any plugin like MainmenuConf has to keep the image Menu.py. Same problem with setup.xml which does the order of menu items.

 

Regards, pcd.

Edited by pcd, 21 September 2016 - 00:28.

[Matrix10]

Hi Matrix10,

 

I am not sure if I fully understand your proposals.

 

Menu.py is included in enigma in the image. The image enigma is changed frequently.  So - if Menu.py is changed in a plugin - with software update it will be overwritten. Therefore any plugin like MainmenuConf has to keep the image Menu.py. Same problem with setup.xml which does the order of menu items.

 

Regards, pcd.

 

 

I am not a supporter of various plugins for Menu,System,Setup ....   panels  arrangement.
I would prefer a change in the Menu.py
Which now gives very limited possibilities for skins.

Subsequently/afterwards, installed plugins and additions using some of these panels , take place unexpectedly in the menu lists.

Because coding in Menu.py determines the position/order in the lists
based on defined positions in plugins or in the Menu.py (Weight 50)

 

example:

Menu.py

list.append((l[0], boundFunction(l[1], self.session), l[2], l[3] or 50))

 

Example plugin:

def menu(menuid, **kwargs):
 if menuid == "mainmenu":
  return [(_("Media player"), main, "media_player", 45)]
 return []

 

It's just one but an important problem.
Overall Menu.py is very limited the possibilities for skin coding .

 

But note that I am not a python coder.

 

It would be better if Menu.py first read
some plugin list, menu.xml, and if the plugin is not in the list/lists
puts plugin on the end of  menu panel .

Edited by Matrix10, 21 September 2016 - 10:47.

[pcd]

It is a matter for the image people. If any image maker asks me to look into changing Menu.py for their image - I will be pleased to look  into it.

I do not make any images myself.

[Matrix10]

It is a matter for the image people. If any image maker asks me to look into changing Menu.py for their image - I will be pleased to look  into it.

I do not make any images myself.

 

I do not see why you would not make,
own solutions and ideas.Which might or not be used by other teams and individuals.

This is not changed from the beginning of E2 for several years.

I'm not for the sort of individual solutions in the form of plugins
and skins with python additives related only to the single skin.

 

I think the time has come to modernize Menu.py
with the possibility of improvement by the community.

Of course I expect it will be joined by teams and their coders.

 

Ideas for skins are nearly exhausted and all look like each other
and it is because of these limits in the graphics processing / coding E2

[WanWizard]

The biggest challenge, and something we've been fighting with for years, is the discussion "progress" vs "backward compatibility". As long as people distrubute plugins in binary form, and as long as people expect everything to work flawlessly on everything remote resembling "enigma2", major architectural changes like these are difficult.

[Matrix10]

Still we need somewhere to begin.

As much as is possible.

It is strange to spend hours on coding less important things than good-looking skin/image and the possibility of creation of such graphics support.

 

I wanted from skin coding sides urge some changes.

What I think we can make possible even counting the "backward compatibility".

 

So some of the ideas...

 

The order in Menu lists controlled by the list (menu.xml,plugin list ) or the skin coding.(Currently the most important )

The horizontal and vertical list  Menu( not as now overload the image with graphical solutions where the coding will be efficient solution )

Using the icons in Menu lists (background and selected) arbitrary size and position, but related to add-ons , plugins image parts and  (menu.xml,plugin list )

The possibility of using the buttons in all directions vertical/horizontal (background and selected)

The possibility of the use of text for Menu items vertical/horizontal (background and selected)

 

etc.

[Matrix10]

^{I forgot to add}

 

^{that some of the above Wishlist are already possible
 in combination with graphical solutions and tricks ,which of course is not the most elegant solution.}

[WanWizard]

"less important" things are easy, and don't require much planning. Creating a new GUI architecture requires a lot of work up front, before you start coding.

 

If it were up to me, we abandon the entire current UI system, and we move to a html/javascript based UI, the current generation of hardware is fast enough for that, and with the introduction of ARM CPU's even more so. Supply the backend with a REST like interface to access the data, and leave all rendering to the UI templates. You could then even decouple the UI from the box itself, and just run it in a browser, on a phone or tablet.

 

I agree this should be done, the challenge is finding someone with the knowledge, the time and the stamina to undertake this job.