Project

General

Profile

Actions

Feature #3525

closed

Implement Service Name Picons (vs Service Reference Picons)

Added by Prof Yaffle about 9 years ago. Updated about 9 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
User Interface
Target version:
Start date:
2016-01-23
Due date:
% Done:

100%

Estimated time:

Description

The current picon code uses service references - so frequency, orbital position, etc. - to identify which icon to use on which channel. However, I've found this to be patchy at best, requiring a lot of manual work afterwards to fill the gaps.

There also seems to be a way to use service names, so more like the current channel name approach - but with a standardised way to 'slugify' the channel names, and also to build the icons through the picon process.

More information here:

https://github.com/picons/picons-source#snp---service-name-picons

and sample code used to generate the names here:

https://github.com/OpenViX/enigma2/blob/master/lib/python/Components/Renderer/Picon.py#L88-L89

Actions

Also available in: Atom PDF