| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
reread plugin list revisited
|
|
|
|
|
|
reenable plugin icons
|
|
|
|
|
|
reenable the try/except block for faulty plugin catching
don't expect a directory /usr/lib/tuxbox/plugins to be present by the tuxbox plugin starter
|
|
|
|
example:
def getMenuRegistrationList():
list = []
list.append(("setup", 2, "Softwareupdate", "Example"))
list.append(("mainmenu", 0, "Foo", "Bar"))
return list
this means, that we have 2 menu entries:
a menu entry "Softwareupdate" is added to the setup menu on position 2 which calls the Example screen of the plugin
and a menu entry Foo is added to the main menu on the first position which calls the screen Bar
|
|
|
|
c++ part supports it
|
|
change plugin interface: plugins can now have screens or functions as objects to call when plugin is selected
plugins can have multiple plugin menu entries
|
|
enigma2 execution
plugins supporting this functionality must have a function autostart and/or autoend in their code
|
|
add a try/except block around the plugin loading for faulty plugins
|
|
file called plugin.py in his directory
for example the update plugin now resides in /usr/lib/enigma2/python/Plugins/update
when you add a plugin, don't forget to put an empty __init__.py file into the directory, otherwise python doesn't recognize
the directory as module
|
|
menus have their own id now
the update plugin for example adds a menu item to the Setup menu with the id "setup"
|
|
|
|
to test it: uncomment the example.py in lib/python/Plugins/Makefile.am
plugins can be added at runtime
|
