Screen names for GP3 Skins (en): Unterschied zwischen den Versionen
Zeile 47: | Zeile 47: | ||
===Why should we do this?=== | ===Why should we do this?=== | ||
− | GP3 contains | + | GP3 contains 9 basic screens used as User Interface in GP3: |
* Config2Button | * Config2Button | ||
+ | * Config3Button | ||
+ | * VariableList3Button | ||
+ | * VariableList3ButtonSmallIcon | ||
+ | * VariableList4Button | ||
* VariableListNoButton | * VariableListNoButton | ||
− | * | + | * VariableList2Lines |
− | * | + | * VariableListCover |
+ | * VList3Button2Entry | ||
+ | |||
All GP3-Plugins that need a VariableList3Button screen, make use of the base screen. | All GP3-Plugins that need a VariableList3Button screen, make use of the base screen. |
Version vom 10. März 2014, 21:55 Uhr
- in Deutsch | - in English |
This article is meant for all experienced skinners, who like to develop or mod skins for the GP3 plugin. The main focus of the article is to find out the relevant screen names and to support people who are interested in developing or modding skins.
Inhaltsverzeichnis
Pre-Conditions
- Experience in Skin development Modding
Finding out the GP3 screen names
After installation of the GP3-plugins, you can find the file skin.xml
in the directory:
/usr/lib/enigma2/python/Plugins/Bp/geminimain
This file contains the following items:
- Infobar Renderer
- Basis Screens
- OLED Screens
It is also helpful to amend the file skin.py
in
/usr/lib/enigma2/python
as described below:
Search for the routine readSkin
in skin.py
.
You can find a for-loop in the routine some lines later starting with for n in names
: (Approx. at line 524 )
# try all skins, first existing one have priority for n in names: myscreen, path = lookupScreen(n, style_id) if myscreen is not None: # use this name for debug output name = n print names break
Add the following line "print names" before the break entry and execute the following command in Telnet :
init 4 && sleep 5 && einigma2
If you now open the menus of the GP3 plugins and screens, the screen names will be printed in the console for each screen you open.
e.g. VariableList3Button_geminiweather
Why should we do this?
GP3 contains 9 basic screens used as User Interface in GP3:
- Config2Button
- Config3Button
- VariableList3Button
- VariableList3ButtonSmallIcon
- VariableList4Button
- VariableListNoButton
- VariableList2Lines
- VariableListCover
- VList3Button2Entry
All GP3-Plugins that need a VariableList3Button screen, make use of the base screen.
If you want to create a different screen for the Gemini weather plugin,
you will need the name of the screen in the plugin to create the according design.
You get the proper screen names via the above described way.
Base screen for allp lugins that use this screen --> VariableList3Button Plugin screen for the Gemini weather plugin --> VariableList3Button_geminiweather
You can compare this to the relation between skin.xml
and skin_user.xml
.
Known GP3 screen names
Please find a list of the currently known GP3 screen names:
- gDesktopHD
- Config2Button
- Config2Button_SatList
- Config2Button_gSimpleList
- VariableListNoButton
- VariableListNoButton_gMultiQuickButton
- VariableListNoButton_RssReader
- VariableListNoButton_MountPoints
- VariableListNoButton_InfoHardware
- VariableListNoButton_KernelInfo
- RssLister
- RssReader
- RssView
- VariableList4Button
- VariableList2Lines
- VariableList2Lines_gAddons
- VariableList2Lines_gAddonsCat
- VariableList2Lines_BrowserFavo
- VariableList3Button
- VariableList3Button_geminidreamnetcast
- VariableList3Button_WidgetXmlList
- VariableList3Button_WebCamViewer
- VariableList3Button_geminiweather
- PrioListSetup
- VariableList3Button_Automount
- VariableList3Button_ProcessInfo
- VariableList3Button_GeminiConfList
- VariableList3Button_DeviceManager
- VariableList3Button_PartitionsManager
- VariableList3Button_gMenu_confgDesktop
- VariableList3Button_Satconfig
- VariableListCover_gBrowser
- WeatherView
- Jukebox_XD
- Jukebox_HD
- Jukebox_SD
- HotplugScreen