diff --git a/The-VDR-Plugin-System.md b/The-VDR-Plugin-System.md index 73de212..f15df90 100644 --- a/The-VDR-Plugin-System.md +++ b/The-VDR-Plugin-System.md @@ -7,7 +7,7 @@

Copyright © 2021 Klaus Schmidinger
vdr@tvdr.de
-www.tvdr.de +www.tvdr.de

VDR provides an easy to use plugin interface that allows additional functionality @@ -46,7 +46,6 @@ structures and allows it to hook itself into specific areas to perform special a

  • Main menu entry
  • User interaction
  • Housekeeping -
  • Main thread hook
  • Activity
  • Wakeup
  • Setup parameters @@ -138,7 +137,7 @@ is used: VDR/PLUGINS/src VDR/PLUGINS/src/hello VDR/PLUGINS/lib -VDR/PLUGINS/lib/libvdr-hello.so.1.1.0 +VDR/PLUGINS/lib/libvdr-hello.so.1 The src directory contains one subdirectory for each plugin, which carries @@ -157,7 +156,7 @@ The lib directory contains the dynamically loadable libraries of all available plugins. Note that the names of these files are created by concatenating

    - +
    libvdr-hello.so.1.1.0
    libvdr-hello.so.1
    VDR plugin
    library prefix    		name of
    the plugin    		shared object
    indicator    		API version number
    this plugin was
    compiled for

    @@ -168,6 +167,11 @@ the current VDR version. That way minor fixes to VDR, that don't require changes to the VDR header files, can be made without requiring all plugins to be recompiled.

    +While in earlier versions of VDR the API version number was closely related to the +VDR version number, starting with VDR version 2.7.2 the API version number was changed +from a dot separated, three part number to a single integer, completely unrelated to +the VDR version. This was done to avoid confusion. +

    The plugin library files can be stored in any directory. If the default organization is not used, the path to the plugin directory has be be given to VDR through the -L option. @@ -363,13 +367,7 @@ just like shown in the above example. This is a convention that allows the M to extract the version number when generating the file name for the distribution archive.

    A new plugin project should start with version number 0.0.1 and should reach -version 1.0.0 once it is completely operative and well tested. Following the -Linux kernel version numbering scheme, versions with even release numbers -(like 1.0.x, 1.2.x, 1.4.x...) should be stable releases, -while those with odd release numbers (like 1.1.x, 1.3.x, -1.5.x...) are usually considered "under development". The three parts of -a version number are not limited to single digits, so a version number of 1.2.15 -would be acceptable. +version 1.0.0 once it is completely operative and well tested.

    Description

    @@ -665,27 +663,6 @@ interaction is possible. If a specific action takes longer than a few seconds, the plugin should launch a separate thread to do this. -

    Main thread hook

    - -
    Pushing in...

    - -Normally a plugin only reacts on user input if directly called through its -main menu entry, or performs some background -activity in a separate thread. However, sometimes a plugin may need to do -something in the context of the main program thread, without being explicitly -called up by the user. In such a case it can implement the function - -

    -virtual void MainThreadHook(void);
-
    - -in which it can do this. This function is called for every plugin once during -every cycle of VDR's main program loop, which typically happens once every -second. -Be very careful when using this function, and make sure you return from it -as soon as possible! If you spend too much time in this function, the user -interface performance will become sluggish! -

    Activity

    Now is not a good time!

    diff --git a/Version-History.md b/Version-History.md index a5f37e0..e3b881b 100644 --- a/Version-History.md +++ b/Version-History.md @@ -301,3 +301,4 @@ | 2.7.1 | 2024-09-09 | 2.6.9 | | 2.7.2 | 2024-09-27 | 5 | | 2.7.3 | 2024-10-12 | 5 | +| 2.7.4 | 2025-02-26 | 6 |