From c6f8a149574f4e5196f802439e7439406ca82e71 Mon Sep 17 00:00:00 2001 From: Klaus Schmidinger Date: Sun, 10 Jun 2007 13:02:43 +0200 Subject: Freetype font support; full UTF-8 support; dropped pixel fonts --- PLUGINS.html | 45 ++++++++++++++++++++++++++++++++++++++------- 1 file changed, 38 insertions(+), 7 deletions(-) (limited to 'PLUGINS.html') diff --git a/PLUGINS.html b/PLUGINS.html index 64034538..dc725a51 100644 --- a/PLUGINS.html +++ b/PLUGINS.html @@ -6,7 +6,7 @@

The VDR Plugin System

-
Version 1.5.1
+
Version 1.5.3

Copyright © 2006 Klaus Schmidinger
@@ -14,12 +14,15 @@ Copyright © 2006 Klaus Schmidinger
www.cadsoft.de/vdr

-
  +
  Important modifications introduced in version 1.5.0 are marked like this.
-
  +
  Important modifications introduced in version 1.5.1 are marked like this.
+
  +Important modifications introduced in version 1.5.3 are marked like this. +

VDR provides an easy to use plugin interface that allows additional functionality to be added to the program by implementing a dynamically loadable library file. @@ -58,7 +61,7 @@ structures and allows it to hook itself into specific areas to perform special a

  • Housekeeping
  • Main thread hook
  • Activity -
      +
     
  • Wakeup
  • Setup parameters @@ -82,7 +85,7 @@ structures and allows it to hook itself into specific areas to perform special a
  • Devices
  • Audio
  • Remote Control -
      +
     
  • Conditional Access
    • @@ -681,7 +684,7 @@ be queried, and further prompts may show up. If all prompts have been confirmed, the shutdown will take place. As soon as one prompt is not confirmed, no further plugins will be queried and no shutdown will be done. -
      +
     

    Wakeup

    Wake me up before you go-go

    @@ -970,6 +973,19 @@ written to the log file, indicating that a translation is missing. Texts are first searched for in the Phrases registered for this plugin (if any) and then in the global VDR texts. So a plugin can make use of texts defined by the core VDR code. +

    +
      +The system VDR is running on may use a character encoding where a single character +(or symbol) consists of more than one byte (UTF-8, as opposed to, for instance, +ISO8859-1, where every character is represented by a single byte in memory). +In order to make sure a plugin works regardless of the character encoding the current +system uses, the VDR core code provides several functions and macros that allow accessing +text strings transparently without knowing whether this is a single or multi byte +character set. The names of these functions and macros are all of the form Utf8...(), +and are defined in VDR/tools.h. +Most of the time a plugin doesn't need to care about this, but when it comes to +handling individual characters these functions may come in handy. +

    Custom services

    @@ -1618,7 +1634,22 @@ Note that a plugin should always at first request a single drawing area with the full required resolution. Only if this fails shall it use alternate areas. Drawing areas are always rectangular and may not overlap (but do not need to be adjacent). +

    +
      +Special consideration may have to be given to color usage if the OSD provides +8bpp (256 colors). In that case, fonts may be drawn using anti-aliasing, +which requires several blended color values between the foreground and background +color. In order to not use up the whole color palette for a single color +combination (and thus be unable to draw any other colors at all), it may be +useful to call + +

    +osd->SetAntiAliasGranularity();
+

    +which allows the system to evenly distribute the palette entries to the various +color combinations (see VDR/osd.h for details). +

    Directly accessing the OSD is only allowed from the foreground thread, which restricts this to a cOsdObject returned from the plugin's MainMenuAction() @@ -2087,7 +2118,7 @@ Put(uint64 Code, bool Repeat = false, bool Release = false); The other parameters have the same meaning as in the first version of this function. -
      +
     

    Conditional Access

    Members only!

    -- cgit v1.2.3