From 130fc1bf26016aa7216d65a014d50bd8e4bb4ba8 Mon Sep 17 00:00:00 2001 From: Benny Lyons Date: Sat, 28 Jul 2012 22:08:22 +0100 Subject: [PATCH] Section Plugins/Interfaces: subsections added and text corrected. --- doc/user/intro/intro.txt | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/doc/user/intro/intro.txt b/doc/user/intro/intro.txt index 16f92ebb9..1e846a3f1 100644 --- a/doc/user/intro/intro.txt +++ b/doc/user/intro/intro.txt @@ -355,6 +355,11 @@ Configuration Plugins/Interfaces ~~~~~~~~~~~~~~~~~~ + + +What are Plugins? +^^^^^^^^^^^^^^^^^ + A Plug-in is a kind of generalisation of a library. All applications use, to varying degrees of intensity, libraries. A programmer @@ -379,7 +384,7 @@ libraries are being constantly improved. If the application wants to use new features, it will have to be recompiled with the new library which provides the new features. -_Dynamic Linking_ helps rectify the the necessity of having to recompile. If a +_Dynamic Linking_ helps rectify the necessity of having to recompile. If a new, improved library becomes available, all the user has to do is to install the new library onto the operating system, restart the application and the new features can be used by the application. The features provided by a dynamic @@ -393,7 +398,7 @@ available to an application is known as run-time linking, aka plug-ins. Plug-ins offer other benifits: the application can continue to use both the old features and the new features together, side-by-side, by using the version number associated with the plug-in. This saves the application from considerable -headaches associated with other linking methods, havocked library versiojn +headaches associated with other linking methods, havocked library version incompatibility. Most modern applications use plug-ins, some are heavily dependent on plug-ins @@ -403,6 +408,8 @@ functionality via well-designed, external code supplied to Lumiera by plug-ins. + + Rendering Video --------------- [red]#to be written#