Here a little documentation about the output from plugins...
(A little outdated, see: page_msg changes)
A plugin can response feedback to the users via the PyLucid page_msg function. The output can be simple colored and the functin is good for debugging.
The using is very easy. Here some example:
The sourcecode of the page_msg object can be found here:
The output displayed via a simple
django template "for loop". The output stored in the template context variable 'messages'. It's a simple list with every line of the output.
In the global template sould be exist something like this:
A plugin can change the page title with:
1 2 3 4 5 6 7 8 | from django.utils.translation import ugettext as _ ... # Change the global page title: self.context["PAGE"].title = _("A new page title") |
With changeset 1532 the page title would be automatic changes in every _command url. But only, if the plugin doesn't change the title themself.
Note: There should not exists a headline in the internal pages for a "page title replacement".
Every Plugin output are surrounded with a CSS anchor. At the moment we add a DIV tag around every plugin output in ./PyLucid/template_addons/lucidTag.py
The function add_css_tag() can be found here: ./PyLucid/system/context_processors.py
There exist a black list (CSS_TAG_BLACKLIST) in lucidTag.py Because Plugins how only insert a link into the page, should not have a Tag around the link. At the moment the blacklist looks like:
1 | CSS_TAG_BLACKLIST = ("page_style", "RSSfeedGenerator",) |
django-processinfo: 6.0 ms of 280.3 ms (2.2%)
there exist no comment for 'plugin output'
loading...
Leave a comment