Congegni
/
libretime
mirror of https://github.com/libretime/libretime.git
7
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Renamed LiveSupport to Campcaster, for ticket

This commit is contained in:
paul 2006-10-25 20:11:59 +00:00
parent 5124344b3c
commit 174f9798da
30 changed files with 399 additions and 400 deletions

6
campcaster/doc/developmentEnvironment/autoconfConfigureConventions.html
View File

@ -7,7 +7,7 @@
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://campcaster.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright © 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,10 +18,10 @@ Development Loan Fund</a>, under the GNU <a
</ul>
<h1>Scope</h1>
This document describes the autoconf configure file conventions for the
LiveSupport
Campcaster
project. See also the generic description of the <a
href="fileConventions.html">file
conventions</a> in the LiveSupport
conventions</a> in the Campcaster
project.<br>
<h1>Introduction</h1>
Autoconf configure input files are processed by GNU <a

18
campcaster/doc/developmentEnvironment/buildEnvironment.html
View File

@ -3,15 +3,15 @@
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type">
<title>Build environment</title>
<meta content="$Author$" name="author">
</head>
@ -23,7 +23,7 @@
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright &copy; 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -38,7 +38,7 @@ Development Loan Fund</a>, under the GNU <a href="http://www.gnu.org/licenses/gp
<li>Location: $URL:
svn+ssh://maroy@code.campware.org/home/svn/repo/livesupport/trunk/livesupport/doc/developmentEnvironment/buildEnvironment.html
svn+ssh://maroy@code.campware.org/home/svn/repo/campcaster/trunk/campcaster/doc/developmentEnvironment/buildEnvironment.html
$<br>
@ -52,7 +52,7 @@ $<br>
This document describes the build environment for components of the
LiveSupport project.<br>
Campcaster project.<br>
<h1>Introduction</h1>

26
campcaster/doc/developmentEnvironment/cxxHeaderFileConventions.html
View File

@ -7,7 +7,7 @@
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://campcaster.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright © 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,10 +18,10 @@ Development Loan Fund</a>, under the GNU <a
</ul>
<h1>Scope</h1>
This document describes C++ header file conventions for the
LiveSupport
Campcaster
project. See also the generic description of the <a
href="fileConventions.html">file
conventions</a> in the LiveSupport
conventions</a> in the Campcaster
project.<br>
<h1>Introduction</h1>
C++ header files are files containing declarations of structures,
@ -32,7 +32,7 @@ based files, thus they should adhere to the <a
href="fileConventions.html#textConventions">generic text-based
conventions</a>.<br>
<br>
The LiveSupport project uses a strong object oriented approach. Part of
The Campcaster project uses a strong object oriented approach. Part of
this approach is to group declarations of classes into their own files:
one header file and one source file for each class. Therefore each C++
header file contains the declaration of exactly one C++ class, although
@ -84,27 +84,27 @@ For a header file that will be included with the line:<br>
<pre><code>#include "Foo.h"</code><br></pre>
the identity macro is defined as <code>Foo_h</code>. For a header file
that is expected to be included as:<br>
<pre><code>#include "LiveSupport/Foo/Bar.h"<br></code></pre>
the identity macro is defined as <code>LiveSupport_Foo_Bar_h</code>.<br>
<pre><code>#include "Campcaster/Foo/Bar.h"<br></code></pre>
the identity macro is defined as <code>Campcaster_Foo_Bar_h</code>.<br>
<br>
After the identity macro, a preprocessor check is performed to see if
the file is being processessed by a C++ compiler (and say not a C
compiler).<br>
<h3>Sample</h3>
A sample for a C++ header file header follows, where the file itself
would be expected to be included as <code>"LiveSupport/Foo/Bar.h"</code>.<br>
would be expected to be included as <code>"Campcaster/Foo/Bar.h"</code>.<br>
<br>
<pre>/*------------------------------------------------------------------------------<br><br> Copyright (c) 2004 Media Development Loan Fund<br> <br> This file is part of the Campcaster project.<br> http://campcaster.campware.org/<br> To report bugs, send an e-mail to bugs@campware.org<br> <br> Campcaster is free software; you can redistribute it and/or modify<br> it under the terms of the GNU General Public License as published by<br> the Free Software Foundation; either version 2 of the License, or<br> (at your option) any later version.<br> <br> Campcaster is distributed in the hope that it will be useful,<br> but WITHOUT ANY WARRANTY; without even the implied warranty of<br> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the<br> GNU General Public License for more details.<br> <br> You should have received a copy of the GNU General Public License<br> along with Campcaster; if not, write to the Free Software<br> Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA<br> <br> <br> Author : $Author$<br> Version : $Revision$<br> Location : $URL$<br> <br>------------------------------------------------------------------------------*/<br>#ifndef LiveSupport_Foo_Bar_h<br>#define LiveSupport_Foo_Bar_h<br> <br>#ifndef __cplusplus<br>#error This is a C++ include file<br>#endif<br><br></pre>
<pre>/*------------------------------------------------------------------------------<br><br> Copyright (c) 2004 Media Development Loan Fund<br> <br> This file is part of the Campcaster project.<br> http://campcaster.campware.org/<br> To report bugs, send an e-mail to bugs@campware.org<br> <br> Campcaster is free software; you can redistribute it and/or modify<br> it under the terms of the GNU General Public License as published by<br> the Free Software Foundation; either version 2 of the License, or<br> (at your option) any later version.<br> <br> Campcaster is distributed in the hope that it will be useful,<br> but WITHOUT ANY WARRANTY; without even the implied warranty of<br> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the<br> GNU General Public License for more details.<br> <br> You should have received a copy of the GNU General Public License<br> along with Campcaster; if not, write to the Free Software<br> Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA<br> <br> <br> Author : $Author$<br> Version : $Revision$<br> Location : $URL$<br> <br>------------------------------------------------------------------------------*/<br>#ifndef Campcaster_Foo_Bar_h<br>#define Campcaster_Foo_Bar_h<br> <br>#ifndef __cplusplus<br>#error This is a C++ include file<br>#endif<br><br></pre>
<h2>Include files &amp; namespace <br>
</h2>
This section contains all the include files that the header file needs
to include, plus namespace declarations. The include files are listed
in a most generic to most specific order: firts system include files,
then other LiveSupport module include files, and finnally include files
then other Campcaster module include files, and finnally include files
from the same module / product are listed.<br>
<br>
After the includes, namespace definitions follow. Each LiveSupport
object is contained in its own namespace inside the <code>LiveSupport</code>
After the includes, namespace definitions follow. Each Campcaster
object is contained in its own namespace inside the <code>Campcaster</code>
namespace, thus this is a nested namespace declaration.<br>
<br>
After the namespace declarations, the namespaces used within the
@ -114,7 +114,7 @@ strictly within the namespace declaration clauses, so that they only
take effect within the header file, but not afterwards.<br>
<h3>Sample</h3>
A sample include files &amp; namespaces section follows.<br>
<pre>/* =============================================== include files &amp; namespaces */<br><br>#ifdef HAVE_CONFIG_H<br>#include "configure.h"<br>#endif<br><br>#if HAVE_STDLIB_H<br>#include &lt;stdlib.h&gt;<br>#else<br>#error need stdlib.h<br>#endif<br><br>#include &lt;string&gt;<br><br><br>namespace LiveSupport {<br>namespace Foo {<br><br>using namespace LiveSupport::Core;<br><br></pre>
<pre>/* =============================================== include files &amp; namespaces */<br><br>#ifdef HAVE_CONFIG_H<br>#include "configure.h"<br>#endif<br><br>#if HAVE_STDLIB_H<br>#include &lt;stdlib.h&gt;<br>#else<br>#error need stdlib.h<br>#endif<br><br>#include &lt;string&gt;<br><br><br>namespace Campcaster {<br>namespace Foo {<br><br>using namespace Campcaster::Core;<br><br></pre>
<h2>Constants</h2>
The constants section contains static constant values defined in the
header file.
@ -189,7 +189,7 @@ identity macro #ifdef section opened in the header.<br>
<h3>Sample</h3>
A sample footer section follows.<br>
<br>
<pre>} // namespace Foo<br>} // namespace LiveSupport<br><br>#endif // LiveSupport_Foo_Bar_h<br></pre>
<pre>} // namespace Foo<br>} // namespace Campcaster<br><br>#endif // Campcaster_Foo_Bar_h<br></pre>
<h1>Template</h1>
See a <a href="templates/Bar.h">template
C++ header file</a>. You may freely copy this

12
campcaster/doc/developmentEnvironment/cxxSourceFileConventions.html
View File

@ -7,7 +7,7 @@
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://campcaster.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright © 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,10 +18,10 @@ Development Loan Fund</a>, under the GNU <a
</ul>
<h1>Scope</h1>
This document describes C++ source file conventions for the
LiveSupport
Campcaster
project. See also the generic description of the <a
href="fileConventions.html">file
conventions</a> in the LiveSupport
conventions</a> in the Campcaster
project.<br>
<h1>Introduction</h1>
C++ source files are files containing implementations of functions and
@ -30,7 +30,7 @@ based files, thus they should adhere to the <a
href="fileConventions.html#textConventions">generic text-based
conventions</a>.<br>
<br>
The LiveSupport project uses a strong object oriented approach. Part of
The Campcaster project uses a strong object oriented approach. Part of
this approach is to group implementations of classes into their own
files: one header file and one source file for each class. Therefore
each C++ source file contains implementation of exactly one C++ class,
@ -89,7 +89,7 @@ A sample for a C++ source file header follows.<br>
This section contains all the include files that the source file needs
to include, plus namespace references. The include files are listed in
a most generic to most specific order: first system include files, then
other LiveSupport module include files, and finally include files from
other Campcaster module include files, and finally include files from
the same module / product are listed. The last one is the header file
for the class this source file implements.<br>
<br>
@ -100,7 +100,7 @@ most specific, the last one being the namespace of the class this
source file implements.<br>
<h3>Sample</h3>
A sample include files &amp; namespaces section follows.<br>
<pre>/* =============================================== include files &amp; namespaces */<br><br>#ifdef HAVE_CONFIG_H<br>#include "configure.h"<br>#endif<br><br>#if HAVE_STDLIB_H<br>#include &lt;stdlib.h&gt;<br>#else<br>#error need stdlib.h<br>#endif<br><br>#include &lt;string&gt;<br><br>#include &lt;LiveSupport/Foo/Bar.h&gt;<br><br><br>using namespace LiveSupport::Core;<br>using namespace LiveSupport::Foo;<br><br></pre>
<pre>/* =============================================== include files &amp; namespaces */<br><br>#ifdef HAVE_CONFIG_H<br>#include "configure.h"<br>#endif<br><br>#if HAVE_STDLIB_H<br>#include &lt;stdlib.h&gt;<br>#else<br>#error need stdlib.h<br>#endif<br><br>#include &lt;string&gt;<br><br>#include &lt;Campcaster/Foo/Bar.h&gt;<br><br><br>using namespace Campcaster::Core;<br>using namespace Campcaster::Foo;<br><br></pre>
<h2>Local data structures<br>
</h2>
The constants section contains locally defined data structures, that

50
campcaster/doc/developmentEnvironment/directoryStructure.html
View File

@ -2,11 +2,11 @@
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type">
<title>Directory structure</title>
<meta content="$Author$" name="author">
</head>
@ -16,7 +16,7 @@
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright &copy; 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -27,7 +27,7 @@ Development Loan Fund</a>, under the GNU <a href="http://www.gnu.org/licenses/gp
<li>Version: $Revision$</li>
<li>Location: $URL:
svn+ssh://maroy@code.campware.org/home/svn/repo/livesupport/trunk/livesupport/doc/developmentEnvironment/directoryStructure.html
svn+ssh://maroy@code.campware.org/home/svn/repo/campcaster/trunk/campcaster/doc/developmentEnvironment/directoryStructure.html
$<br>
</li>
@ -37,7 +37,7 @@ $<br>
<h1>Scope</h1>
This document describes the directory structure used for all component
of the LiveSupport project.<br>
of the Campcaster project.<br>
<h1>Introduction</h1>
@ -55,13 +55,13 @@ Hierarchy Standard</a>.<br>
<h1>Overall structure</h1>
The base livesupport directory contains all the special tools needed to
build, test and run LiveSupport, along with all the source code that
constitutes LiveSupport itself.<br>
The base campcaster directory contains all the special tools needed to
build, test and run Campcaster, along with all the source code that
constitutes Campcaster itself.<br>
<br>
The self written part of LiveSupport project consists of re-usable
The self written part of Campcaster project consists of re-usable
modules, and products.
Modules are components that do not execute by themselves, but have a
useful, preferably generic functionality. Products are the executable
@ -75,8 +75,8 @@ circular reference is not allowed.<br>
<br>
Other needed parts of the directory structure are involved with
external libraries LiveSupport depends on, and a running environment
where LiveSupport can run.<br>
external libraries Campcaster depends on, and a running environment
where Campcaster can run.<br>
<br>
@ -85,7 +85,7 @@ The directory structure is organized in the following way:<br>
<br>
<code></code>
<pre>livesupport<br>|-- configure<br>|-- bin<br>|-- doc<br>|-- etc<br>|-- src<br>| |-- modules<br>| | |-- module1<br>| | |-- module2<br>| ...<br>| | `-- moduleN<br>| |-- products<br>| | |-- product1<br>| | |-- product2<br>| | ...<br>| | `-- productN<br>| `-- tools<br>| |-- tool1<br>| |-- tool2<br>| ...<br>| `-- tool3<br>|-- tmp<br>|-- usr<br>`-- var<br></pre>
<pre>campcaster<br>|-- configure<br>|-- bin<br>|-- doc<br>|-- etc<br>|-- src<br>| |-- modules<br>| | |-- module1<br>| | |-- module2<br>| ...<br>| | `-- moduleN<br>| |-- products<br>| | |-- product1<br>| | |-- product2<br>| | ...<br>| | `-- productN<br>| `-- tools<br>| |-- tool1<br>| |-- tool2<br>| ...<br>| `-- tool3<br>|-- tmp<br>|-- usr<br>`-- var<br></pre>
<br>
@ -101,7 +101,7 @@ same module, it can be sure that it is located at <code>../../modules/moduleX</c
<br>
Furthermore, if a module or product is referencing the running
environment under <code>livesupport/usr</code>, it can also be sure
environment under <code>campcaster/usr</code>, it can also be sure
that it is located at <code>../../../usr</code> from either the module or
the product directory.<br>
@ -118,7 +118,7 @@ no assumptions on the relative locations of other components.<br>
<h1>Top-level configure script</h1>
The top-level <code>configure</code> script takes care of <a href="http://www.gnu.org/software/autoconf/">autoconf</a>-style configuring the whole LiveSupport project. This involves running <code>configure</code> in all tool, module and product directories, and creating a top-level <code>Makefile</code>.<br>
The top-level <code>configure</code> script takes care of <a href="http://www.gnu.org/software/autoconf/">autoconf</a>-style configuring the whole Campcaster project. This involves running <code>configure</code> in all tool, module and product directories, and creating a top-level <code>Makefile</code>.<br>
<br>
The configure script is expected to run autoconf in case the
autoconf-style environment has not yet been set up. This typically
@ -129,7 +129,7 @@ involves executing an autogen.sh script from the bin directory.<br>
<h1>Documentation directory</h1>
The doc directory contains generic documentation with respect to the
whole LiveSupport project. Documentation pertaining to a module or
whole Campcaster project. Documentation pertaining to a module or
products should go under the modules' or products' directory,
respectively.<br>
@ -146,7 +146,7 @@ Each module has the same directory structure, which is as follows:<br>
<br>
<pre>moduleX<br>|-- configure<br>|-- bin<br>|-- etc<br>|-- include<br>| `-- LiveSupport<br>| `-- ModuleX<br>|-- lib<br>|-- src<br>|-- tmp<br>`-- var<br></pre>
<pre>moduleX<br>|-- configure<br>|-- bin<br>|-- etc<br>|-- include<br>| `-- Campcaster<br>| `-- ModuleX<br>|-- lib<br>|-- src<br>|-- tmp<br>`-- var<br></pre>
<h4>configure</h4>
@ -166,12 +166,12 @@ All configuration files go here.<br>
The public C/C++ header files for this module. The include files are
stored in a subdirectory that completely replicates the namespacing of
the module itself, in a case-sensitive manner. Thus a header file name <code>Foo.h</code>
for <code>ModuleX</code> would be contained in the directory <code>include/LiveSupport/ModuleX/Foo.h</code>,
for <code>ModuleX</code> would be contained in the directory <code>include/Campcaster/ModuleX/Foo.h</code>,
and would be included with the line:<br>
<br>
<pre>#include "LiveSupport/ModuleX/Foo.h"<br></pre>
<pre>#include "Campcaster/ModuleX/Foo.h"<br></pre>
<h4>lib</h4>
@ -180,9 +180,9 @@ by building the module. All external, third-party libraries used by
this module should be installed into the <code>../../../usr/lib</code>
directory. The libraries are named resembling the full namespacing of
the module, but all lower cased. For example, the library for moduleX
would be named <code>liblivesupport_modulex.so</code>, and thus would
would be named <code>libcampcaster_modulex.so</code>, and thus would
be linked to with the linker option <code>-L../../modules/moduleX/lib
-llivesupport_modulex</code>.<br>
-lcampcaster_modulex</code>.<br>
<h4>src</h4>
@ -213,8 +213,8 @@ an <code>include</code> directory.<br>
<h1>Tools structure</h1>
The tools directory is an archive of tools and external libraries used
for either building or running the LiveSupport system. These tools are
installable to the usr directory of the LiveSupport directory tree.<br>
for either building or running the Campcaster system. These tools are
installable to the usr directory of the Campcaster directory tree.<br>
Each tool has its own directory, where several versions of the same
tool may reside. Thus the generic directory structure is as follows:<br>
@ -239,9 +239,9 @@ be contained in the <code>etc</code> directory.<br>
The usr directory is similar to the /usr system directory on UNIX
systems (see the <a href="http://www.pathname.com/fhs/">Filesystem
Hierarchy Standard</a>). This directory contains all the external tools
needed by either developing or running the LiveSupport system. This
needed by either developing or running the Campcaster system. This
directory is separate from the system /usr directory in order to
facilitate changing the configuration for LiveSupport related libraries
facilitate changing the configuration for Campcaster related libraries
and tools in user space.<br>
<br>

8
campcaster/doc/developmentEnvironment/fileConventions.html
View File

@ -8,7 +8,7 @@
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://campcaster.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright &#169; 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -19,7 +19,7 @@ Development Loan Fund</a>, under the GNU <a
</ul>
<h1>Scope</h1>
This document describes the conventions used for files in the
LiveSupport project.<br>
Campcaster project.<br>
<h1>Introduction</h1>
To facilitate cooperation between multiple contributors, it is
advisable to have common file conventions, so as the result of
@ -42,7 +42,7 @@ In general, all documents have the following structure:<br>
</h2>
The header of the file holds:<br>
<ul>
<li>a reference to the LiveSupport project itself</li>
<li>a reference to the Campcaster project itself</li>
<li>copyright information</li>
<li>reference to the license of the file</li>
<li>the latest author of the file</li>
@ -72,7 +72,7 @@ nature of the file itself.<br>
<h2><a name="textConventions"></a>Generic text-based conventions</h2>
The majority (if not) all sources files are text-based. As a general
rule, text-based files adhere to the following conventions in the
LiveSupport project:<br>
Campcaster project:<br>
<h3>UTF-8</h3>
Whenever possible, the text files should be saved in the <a
href="http://www.unicode.org/glossary/#UTF_8">UTF-8</a> character

10
campcaster/doc/developmentEnvironment/htmlFileConventions.html
View File

@ -8,7 +8,7 @@
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright &#169; 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,12 +18,12 @@ Development Loan Fund</a>, under the GNU <a
<li>Location: $URL$</li>
</ul>
<h1>Scope</h1>
This document describes the HTML file conventions for the LiveSupport
This document describes the HTML file conventions for the Campcaster
project. See also the generic description of the <a
href="fileConventions.html">file conventions</a> in the LiveSupport
href="fileConventions.html">file conventions</a> in the Campcaster
project.<br>
<h1>Introduction</h1>
HTML pages written as part of the LiveSupport documentation should
HTML pages written as part of the Campcaster documentation should
conform to either the <a href="http://www.w3.org/TR/html4/">HTML 4.01
Transitional</a> or <a href="http://www.w3.org/TR/xhtml1/">XHTML 1.0
Transitional</a> specifications.<br>
@ -59,7 +59,7 @@ element for the HTML page:<br>
This section holds the following specific text:<br>
<br>
<blockquote>This document is part of the <a
href="http://livesupport.campware.org/">LiveSupport</a> project,
href="http://campcaster.campware.org/">Campcaster</a> project,
Copyright &#169; 2004 <a href="http://www.mdlf.org/">Media Development Loan
Fund</a>, under the GNU <a href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
<ul>

16
campcaster/doc/developmentEnvironment/index.html
View File

@ -2,12 +2,12 @@
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type">
<title>LiveSupport development environment</title>
<title>Campcaster development environment</title>
<meta content="$Author$" name="author">
</head>
@ -16,7 +16,7 @@
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright &copy; 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -27,19 +27,19 @@ Development Loan Fund</a>, under the GNU <a href="http://www.gnu.org/licenses/gp
<li>Version: $Revision$</li>
<li>Location: $URL:
svn+ssh://maroy@code.campware.org/home/svn/repo/livesupport/trunk/livesupport/doc/developmentEnvironment/index.html
svn+ssh://maroy@code.campware.org/home/svn/repo/campcaster/trunk/campcaster/doc/developmentEnvironment/index.html
$</li>
</ul>
<h1>Scope</h1>
This document gives an overview of the LiveSupport development
This document gives an overview of the Campcaster development
environment.<br>
<h1>Introduction</h1>
The LiveSupport project defines a uniform development environment to
The Campcaster project defines a uniform development environment to
enhance collaboration of participants in the project. The following
aspects of the environment are defined so far:<br>

12
campcaster/doc/developmentEnvironment/installation.html
View File

@ -2,11 +2,11 @@
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type">
<title>Component Installation Guidelines</title>
<meta content="$Author$" name="author">
</head>
@ -16,7 +16,7 @@
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright &copy; 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -27,7 +27,7 @@ Development Loan Fund</a>, under the GNU <a href="http://www.gnu.org/licenses/gp
<li>Version: $Revision$</li>
<li>Location: $URL:
svn+ssh://maroy@code.campware.org/home/svn/repo/livesupport/trunk/livesupport/doc/developmentEnvironment/buildEnvironment.html
svn+ssh://maroy@code.campware.org/home/svn/repo/campcaster/trunk/campcaster/doc/developmentEnvironment/buildEnvironment.html
$<br>
</li>
@ -36,7 +36,7 @@ $<br>
<h1>Scope</h1>
This document describes the installation procedures used by the components of the LiveSupport project.<br>
This document describes the installation procedures used by the components of the Campcaster project.<br>
<h1>Introduction</h1>
Component installation is a process more tricky than it seems at first.

12
campcaster/doc/developmentEnvironment/makefileConventions.html
View File

@ -7,7 +7,7 @@
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://campcaster.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright © 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,10 +18,10 @@ Development Loan Fund</a>, under the GNU <a
</ul>
<h1>Scope</h1>
This document describes the Makefile file conventions for the
LiveSupport
Campcaster
project. See also the generic description of the <a
href="fileConventions.html">file
conventions</a> in the LiveSupport
conventions</a> in the Campcaster
project. This document does not describe the mandatory targets for
Makefiles, see the <a href="buildEnvironment.html">build environment</a>
description for such details.<br>
@ -81,12 +81,12 @@ directories or files change.<br>
No directories or external files may be directory referenced outside
this section.<br>
<br>
When referencing other LiveSupport modules, typically the following
When referencing other Campcaster modules, typically the following
variables are defined for them:<br>
<pre><code>MODULEX_DIR = ${MODULES_DIR}/moduleX<br>MODULEX_INCLUDE_DIR = ${MODULEX_DIR}/include<br>MODULEX_LIB_DIR = ${MODULEX_DIR}/lib<br>MODULEX_LIB = livesupport_modulex<br></code></pre>
<pre><code>MODULEX_DIR = ${MODULES_DIR}/moduleX<br>MODULEX_INCLUDE_DIR = ${MODULEX_DIR}/include<br>MODULEX_LIB_DIR = ${MODULEX_DIR}/lib<br>MODULEX_LIB = campcaster_modulex<br></code></pre>
<h3>Sample</h3>
A sample directory and file definition section follows.<br>
<pre>#-------------------------------------------------------------------------------<br># Basic directory and file definitions<br>#-------------------------------------------------------------------------------<br>BASE_DIR = .<br>DOC_DIR = ${BASE_DIR}/doc<br>DOXYGEN_DIR = ${DOC_DIR}/doxygen<br>ETC_DIR = ${BASE_DIR}/etc<br>SRC_DIR = ${BASE_DIR}/src<br>TMP_DIR = ${BASE_DIR}/tmp<br><br><br>USR_DIR = ${BASE_DIR}/../../usr<br>USR_INCLUDE_DIR = ${USR_DIR}/include<br>USR_LIB_DIR = ${USR_DIR}/lib<br>BOOST_INCLUDE_DIR = ${USR_INCLUDE_DIR}/boost-1_31<br>LIBXMLPP_INCLUDE_DIR = ${USR_INCLUDE_DIR}/libxml++-1.0<br><br>MODULES_DIR = ${BASE_DIR}/../../modules<br><br>HELLOLIB_DIR = ${MODULES_DIR}/hello<br>HELLOLIB_INCLUDE_DIR = ${HELLOLIB_DIR}/include<br>HELLOLIB_LIB_DIR = ${HELLOLIB_DIR}/lib<br>HELLOLIB_LIB = livesupport_hello<br><br>VPATH = ${SRC_DIR}<br><br>HELLO_EXE = ${TMP_DIR}/hello<br><br>DOXYGEN_CONFIG = ${ETC_DIR}/doxygen.config<br><br></pre>
<pre>#-------------------------------------------------------------------------------<br># Basic directory and file definitions<br>#-------------------------------------------------------------------------------<br>BASE_DIR = .<br>DOC_DIR = ${BASE_DIR}/doc<br>DOXYGEN_DIR = ${DOC_DIR}/doxygen<br>ETC_DIR = ${BASE_DIR}/etc<br>SRC_DIR = ${BASE_DIR}/src<br>TMP_DIR = ${BASE_DIR}/tmp<br><br><br>USR_DIR = ${BASE_DIR}/../../usr<br>USR_INCLUDE_DIR = ${USR_DIR}/include<br>USR_LIB_DIR = ${USR_DIR}/lib<br>BOOST_INCLUDE_DIR = ${USR_INCLUDE_DIR}/boost-1_31<br>LIBXMLPP_INCLUDE_DIR = ${USR_INCLUDE_DIR}/libxml++-1.0<br><br>MODULES_DIR = ${BASE_DIR}/../../modules<br><br>HELLOLIB_DIR = ${MODULES_DIR}/hello<br>HELLOLIB_INCLUDE_DIR = ${HELLOLIB_DIR}/include<br>HELLOLIB_LIB_DIR = ${HELLOLIB_DIR}/lib<br>HELLOLIB_LIB = campcaster_hello<br><br>VPATH = ${SRC_DIR}<br><br>HELLO_EXE = ${TMP_DIR}/hello<br><br>DOXYGEN_CONFIG = ${ETC_DIR}/doxygen.config<br><br></pre>
<h2>Configuration parameters</h2>
This section contains the parameters passed to the building tools
(compiler, linker, etc.) When invoking building tools, they should be

20
campcaster/doc/developmentEnvironment/phpFileConventions.html
View File

@ -8,7 +8,7 @@
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://campcaster.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright &#169; 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,9 +18,9 @@ Development Loan Fund</a>, under the GNU <a
<li>Location: $URL$</li>
</ul>
<h1>Scope</h1>
This document describes the PHP script file conventions for the LiveSupport
This document describes the PHP script file conventions for the Campcaster
project. See also the generic description of the <a
href="fileConventions.html">file conventions</a> in the LiveSupport
href="fileConventions.html">file conventions</a> in the Campcaster
project.<br>
<h1>Introduction</h1>
PHP scripts are text-based files containing PHP class definitions and/or commands.<br/>
@ -76,26 +76,26 @@ column wide partitioning delimiter enclosing the header.<br>
<pre>
/*------------------------------------------------------------------------------
Copyright (c) 2004 Media Development Loan Fund
This file is part of the Campcaster project.
http://campcaster.campware.org/
To report bugs, send an e-mail to bugs@campware.org
Campcaster is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
Campcaster is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with Campcaster; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Author : $Author$
Version : $Revision$
Location : $URL$
@ -116,7 +116,7 @@ This section contains all the include files that the script needs
to include.
The include files are listed in
a most generic to most specific order: first PEAR classes, then
other LiveSupport module include files, and finally include files from
other Campcaster module include files, and finally include files from
the same module / product are listed.<br>
Is much safer to use <code>include_once</code> or <code>require_once</code>, not the original versions
of this statement.<br/>

6
campcaster/doc/developmentEnvironment/shellScriptConventions.html
View File

@ -7,7 +7,7 @@
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://campcaster.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright © 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,10 +18,10 @@ Development Loan Fund</a>, under the GNU <a
</ul>
<h1>Scope</h1>
This document describes the shell script file conventions for the
LiveSupport
Campcaster
project. See also the generic description of the <a
href="fileConventions.html">file
conventions</a> in the LiveSupport
conventions</a> in the Campcaster
project.<br>
<h1>Introduction</h1>
Shell scripts are text-based executable shell command files. As text

2
campcaster/doc/developmentEnvironment/templates/htmlDocumentTemplate.html
View File

@ -8,7 +8,7 @@
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright &#169; 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>

16
campcaster/doc/developmentTools.html
View File

@ -2,12 +2,12 @@
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type">
<title>LiveSupport developer tools</title>
<title>Campcaster developer tools</title>
<meta content="$Author$" name="author">
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright © 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,9 +18,9 @@ Development Loan Fund</a>, under the GNU <a
</ul>
<h1>Scope</h1>
This document lists the development tools that are expected to be on a
system that intends to compile and develop LiveSupport.<br>
system that intends to compile and develop Campcaster.<br>
<h1>Introduction</h1>
LiveSupport expects a generic development environment on the system to
Campcaster expects a generic development environment on the system to
be built, which is basically a generic install of a POSIX-compliant
operating system, with a set of GNU development tools and some
utilities.<br>
@ -60,7 +60,7 @@ environment variable WANT_AUTOCONF_2_5="1" before compiling the tools.)</li>
<h1>Libraries</h1>
Note that if you are installing these libraries as binary packages, then you
will need to install the "development" package, as well. (For example, for
libpng, you might need to install the <code>libpng</code> and
libpng, you might need to install the <code>libpng</code> and
<code>libpng-dev</code> packages. The package names vary by distribution.)
<br>
<h2>Required libraries<br>
@ -91,10 +91,10 @@ system:<br>
</ul>
<h2>Recommended libraries</h2>
The following libraries are used by LiveSupport. If they are not found
on the system, LiveSupport will compile them from sources on its own.
The following libraries are used by Campcaster. If they are not found
on the system, Campcaster will compile them from sources on its own.
While having these libraries is not necessary, Compiling takes longer
without them, and the generated LiveSupport directory will be larger as
without them, and the generated Campcaster directory will be larger as
well.<br>
<ul>
<li><a href="http://www.boost.org/">boost</a> &gt;= 1.33.1</li>

88
campcaster/doc/gettingStarted.html
View File

@ -2,12 +2,12 @@
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type">
<title>Getting started with the LiveSupport development environment</title>
<title>Getting started with the Campcaster development environment</title>
<meta content="$Author$" name="author">
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright © 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -17,23 +17,23 @@ Development Loan Fund</a>, under the GNU <a
<li>Location: $URL$</li>
</ul>
<h1>Scope</h1>
This document describes how to set up the LiveSupport development
This document describes how to set up the Campcaster development
environment.<br>
<h1>Introduction</h1>
LiveSupport uses a well-defined <a
Campcaster uses a well-defined <a
href="developmentEnvironment/index.html">development environment</a>.
Most of the LiveSupport-specific files are included in the version
Most of the Campcaster-specific files are included in the version
control system, but some preparation and setup has to be made on system
used to develop LiveSupport as well.<br>
used to develop Campcaster as well.<br>
<br>
There is a simplified and Ubuntu-centric version of this document in the
<a href="http://code.campware.org/projects/livesupport/wiki/DevelopmentEnvironment">
LiveSupport Trac wiki</a>.
<a href="http://code.campware.org/projects/campcaster/wiki/DevelopmentEnvironment">
Campcaster Trac wiki</a>.
<h1>Steps<br>
</h1>
The following steps needed to be taken for setting up the LiveSupport
The following steps needed to be taken for setting up the Campcaster
development environment.<br>
<ul>
<li>install development tools<br>
@ -42,25 +42,25 @@ development environment.<br>
<li>check out the sources</li>
<li>configure the environment<br>
</li>
<li>set up tools used by LiveSupport</li>
<li>set up tools used by Campcaster</li>
<li>personalize your development environment<br>
</li>
</ul>
<h2>Install development tools</h2>
Install all the tools needed for the development of LiveSupport. Please
Install all the tools needed for the development of Campcaster. Please
see the <a href="developmentTools.html">development tools</a> document
for a list of tools needed.<br>
<h2>Set up additional system resources</h2>
The LiveSupport development environment uses some system resources,
The Campcaster development environment uses some system resources,
that are not reasonable to include in the environment itself.<br>
<h3>Test database<br>
</h3>
One such
resource is an ODBC datasource to a test database. This
database has to be accessible for executing the test suites and
applications within the LiveSupport development environment.<br>
applications within the Campcaster development environment.<br>
<br>
First, LiveSupport expects a <a href="http://www.postgresql.org/">PostgreSQL</a>
First, Campcaster expects a <a href="http://www.postgresql.org/">PostgreSQL</a>
database, and an ODBC
Data Source accessible to it through <a href="http://www.unixodbc.org/">unixODBC</a>.
Please refer to the documentation of these tools to set them up.<br>
@ -77,7 +77,7 @@ are enabled by default. If you are using an older version, do the following:
<br>
<pre><code>tcpip_socket = true</code></pre>
<br>
<li> and also edit <code>pg_hba.conf</code> (usually
<li> and also edit <code>pg_hba.conf</code> (usually
<code>/var/lib/postgres/data/pg_hba.conf</code>)
to include the following line, before other lines related to access
through localhost:<br>
@ -91,7 +91,7 @@ restart the postgresql daemon.<br>
<h3>Web server<br>
</h3>
Second, LiveSupport expects:
Second, Campcaster expects:
<ul>
<li><a href="http://httpd.apache.org/">Apache</a> httpd server
running on the development computer</li>
@ -113,41 +113,41 @@ called <code>www-data</code>.
<h3>Apache configuration</h3>
The storage server uses some directives which are not enabled by default.
To enable them, find the configuration file for the userdir module of
apache, and change the <code>AllowOverride</code> directive in the
To enable them, find the configuration file for the userdir module of
apache, and change the <code>AllowOverride</code> directive in the
<code>&lt;Directory /home/*/public_html&gt;</code> section to <code>All</code>.
<br><br>
<h2>Check out the sources</h2>
The LiveSupport development directory tree can be accessed anonymously via
The Campcaster development directory tree can be accessed anonymously via
<a href="http://subversion.tigris.org/">Subversion</a>, at
<code>svn+ssh://code.campware.org/home/svn/repo/livesupport/trunk/livesupport</code>.
<code>svn+ssh://code.campware.org/home/svn/repo/campcaster/trunk/campcaster</code>.
The following Subversion command
would check out the development tree:<br><br>
<pre><code>svn checkout svn+ssh://code.campware.org/home/svn/repo/livesupport/trunk/livesupport</code></pre><br>
This will check out and create the LiveSupport development <a
<pre><code>svn checkout svn+ssh://code.campware.org/home/svn/repo/campcaster/trunk/campcaster</code></pre><br>
This will check out and create the Campcaster development <a
href="developmentEnvironment/directoryStructure.html">directory
structure</a>.<br>
<br>
<h2>Configure the environment</h2>
First, you need to create the database and ODBC data source used by
LiveSupport. This is done most easily by running the script
<code>livesupport/bin/user_setup_db.sh</code>.
Run the scripts as root, and provide your user name with the
Campcaster. This is done most easily by running the script
<code>campcaster/bin/user_setup_db.sh</code>.
Run the scripts as root, and provide your user name with the
<code>--user</code> option:
<pre><code>
cd livesupport
cd campcaster
sudo ./bin/user_setup_db.sh --user=&lt;ls_developer_user&gt;
</code></pre>
<br>
The script will set up the following resources:<br>
<ul>
<li>a PostgreSQL user named <code>test</code> with the password
<li>a PostgreSQL user named <code>test</code> with the password
<code>test</code> (if it does not exist)</li>
<li>a PostgreSQL database named
<code>LiveSupport-&lt;ls_developer_user&gt;</code></li>
<li>a PostgreSQL database named
<code>Campcaster-&lt;ls_developer_user&gt;</code></li>
<li>an ODBC data source of the same name, with user name
and password <code>test</code></li>
</li>
@ -157,27 +157,27 @@ The script will set up the following resources:<br>
Next (and last), you compile the code and set up the configuration files.
Both are done by the script
<pre><code>
cd livesupport
cd campcaster
./bin/setupDevelopmentEnvironment.sh --apache-group=&lt;apache_group&gt;
</code></pre>
<br>
This script will set up the libraries used by LiveSupport (by compiling
and installing them under livesupport/usr), and set up the development
environment for all LiveSupport modules.<br>
This script will set up the libraries used by Campcaster (by compiling
and installing them under campcaster/usr), and set up the development
environment for all Campcaster modules.<br>
<br>
It will also create your personalized configuration files under
<code>~/.livesupport</code>, make certain directories writable for Apache
(this is where we need the current user to be a member of the
<code>apache</code> group), define a user-specific port for the scheduler
<code>~/.campcaster</code>, make certain directories writable for Apache
(this is where we need the current user to be a member of the
<code>apache</code> group), define a user-specific port for the scheduler
daemon, and create a symlink in <code>~/public_html/</code> to the PHP
entry points.<br>
<br>
After running the above script, the livesupport development environment
After running the above script, the campcaster development environment
for the current user will be unique on the system, and will not
conflict with resources used by other developers. For example, the
LiveSupport HTML user interface for the user will be reachable at:<br>
Campcaster HTML user interface for the user will be reachable at:<br>
<pre><code>
http://localhost/~&lt;ls_developer_user&gt;/livesupport/htmlUI/var
http://localhost/~&lt;ls_developer_user&gt;/campcaster/htmlUI/var
</code></pre>
<br>
@ -191,21 +191,21 @@ the commands in <code>setupDevelopmentEnvironment</code> up to, and not
including, the call to <code>user_setup.sh</code>; and manually execute
the "Setup storage server" and "Setup directory permissions" portions
of the <code>user_setup.sh</code> script. Finally, create a symlink
<code>livesupport</code> in the root data directory of the Apache server
which points to <code>livesupport/src/modules/</code>.
<code>campcaster</code> in the root data directory of the Apache server
which points to <code>campcaster/src/modules/</code>.
The address of the HTML interface will now be<br>
<pre><code>
http://localhost/livesupport/htmlUI/var
http://localhost/campcaster/htmlUI/var
</code></pre>
<br>
After this, the development environment should work, using the default
configuration files. NOTE: this single-user method has not been used by any
developers for quite some time, so these instructions may be
developers for quite some time, so these instructions may be
out of date or incomplete.<br>
<br>
<h1>Ready to roll</h1>
With the above steps completed, the LiveSupport modules and products
With the above steps completed, the Campcaster modules and products
are ready to be compiled and developed further. Have fun!<br>
<br>
<br>

2
campcaster/doc/gui/designs/index.html
View File

@ -1,4 +1,4 @@
<html><head><title>final designs : livesupport</title></head>
<html><head><title>final designs : campcaster</title></head>
<body>
<a href="livemode.gif" target="100%">master palette, live mode, cue, history, scratchpad and xfader</a><br>
<a href="advancedsearch.gif" target="100%">advanced search</a><br>

14
campcaster/doc/index.html
View File

@ -2,12 +2,12 @@
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type">
<title>LiveSupport developer documentation</title>
<title>Campcaster developer documentation</title>
<meta content="$Author$" name="author">
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright © 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -17,10 +17,10 @@ Development Loan Fund</a>, under the GNU <a
<li>Location: $URL$</li>
</ul>
<h1>Scope</h1>
This document collects LiveSupport developer documentation, both
This document collects Campcaster developer documentation, both
generated and handwritten.<br>
<h1>Introduction</h1>
The links below provide useful documentation for the LiveSupport
The links below provide useful documentation for the Campcaster
developer.<br>
<h1>Static documentation<br>
</h1>
@ -32,11 +32,11 @@ developer.<br>
<h2>Developer documentation</h2>
<ul>
<li><a href="gettingStarted.html">getting started</a> with
LiveSupport development</li>
Campcaster development</li>
<li><a href="developmentTools.html">development tools</a> needed to
compile LiveSupport<br>
compile Campcaster<br>
</li>
<li>LiveSupport <a href="developmentEnvironment/index.html">development
<li>Campcaster <a href="developmentEnvironment/index.html">development
environment</a></li>
<li>UML <a href="model/index.html">model</a></li>
<li><a href="install.html">installation instructions</a></li>

92
campcaster/doc/install.html
View File

@ -2,12 +2,12 @@
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type">
<title>LiveSupport installation documentation</title>
<title>Campcaster installation documentation</title>
<meta content="$Author$" name="author">
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright © 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -17,41 +17,41 @@ Development Loan Fund</a>, under the GNU <a
<li>Location: $URL$</li>
</ul>
<h1>Scope</h1>
This document describes how to compile and install LiveSupport on your
This document describes how to compile and install Campcaster on your
system.<br>
<h1>Introduction</h1>
LiveSupport has an installation procedure to make sure LiveSupport will
Campcaster has an installation procedure to make sure Campcaster will
work properly on your system. This procedure consists of the following
steps:<br>
<ul>
<li>installing required compilation tools</li>
<li>installing and configuring required external services</li>
<li>obtaining LiveSupport sources</li>
<li>compiling LiveSupport</li>
<li>installing LiveSupport</li>
<li>obtaining Campcaster sources</li>
<li>compiling Campcaster</li>
<li>installing Campcaster</li>
<li>try it out</li>
</ul>
<h2>For the impatient</h2>
Those who think they know everything, the quick steps to install
LiveSupport are the following. (To run <code>make</code>, you need write
Campcaster are the following. (To run <code>make</code>, you need write
permissions in the <code>prefix</code> directory; to run
<code>make install</code> and <code>postInstallStation.sh</code>,
you need to be root.)
<pre><code>
wget http://switch.dl.sourceforge.net/sourceforge/livesupport/livesupport-&lt;version&gt;.tar.bz2
wget http://switch.dl.sourceforge.net/sourceforge/livesupport/livesupport-libraries-&lt;version&gt;.tar.bz2
tar xfj livesupport-&lt;version&gt;.tar.bz2
tar xfj livesupport-libraries-&lt;version&gt;.tar.bz2
cd livesupport-&lt;version&gt;
./configure --prefix=/usr/local/livesupport --with-apache-group=apache --with-www-docroot=/var/www
wget http://switch.dl.sourceforge.net/sourceforge/campcaster/campcaster-&lt;version&gt;.tar.bz2
wget http://switch.dl.sourceforge.net/sourceforge/campcaster/campcaster-libraries-&lt;version&gt;.tar.bz2
tar xfj campcaster-&lt;version&gt;.tar.bz2
tar xfj campcaster-libraries-&lt;version&gt;.tar.bz2
cd campcaster-&lt;version&gt;
./configure --prefix=/usr/local/campcaster --with-apache-group=apache --with-www-docroot=/var/www
make
make install
./bin/postInstallStation.sh -d /usr/local/livesupport -g apache -r /var/www
/usr/local/livesupport/bin/scheduler.sh start
./bin/postInstallStation.sh -d /usr/local/campcaster -g apache -r /var/www
/usr/local/campcaster/bin/scheduler.sh start
<br></code></pre>
Then try the URL <code>http://localhost/livesupport/</code>
Then try the URL <code>http://localhost/campcaster/</code>
and log in using username: <code>root</code>, password: <code>q</code>.<br>
<br>
Everyone else, please read the lines below carefully.<br>
@ -63,11 +63,11 @@ them from the URLs listed, and compile them yourself (follow the instructions
included with each tool and library).<br>
<h1>Installing and configuring required external services</h1>
LiveSupport depends on some external services to be able to run, most
Campcaster depends on some external services to be able to run, most
importantly a PHP-capable web server (we assume apache), and a database
server (we assume PostgreSQL). <br>
<h2>Database</h2>
LiveSupport expects a <a href="http://www.postgresql.org/">PostgreSQL</a>
Campcaster expects a <a href="http://www.postgresql.org/">PostgreSQL</a>
database, version 7.4 or later, to be installed on your system. You will
also need a postgresql driver for unixODBC; this may be in the unixODBC
package, or may need to be installed separately.<br>
@ -89,7 +89,7 @@ to include the following line, before any other lines starting with "host":<br>
These changes will make sure that the PostgreSQL database is accessible
via TCP/IP from localhost.<br>
<h2>Web server</h2>
LiveSupport expects an apache web server with PHP and some additional
Campcaster expects an apache web server with PHP and some additional
PHP modules installed. In particular:
<ul>
<li><a href="http://httpd.apache.org/">Apache</a> httpd server,
@ -128,32 +128,32 @@ or one other from <a href="http://packages.debian.org/cgi-bin/search_packages.pl
Then run "alsaconf" and check /proc/asound/cards again.
<h1>Obtaining LiveSupport sources</h1>
LiveSupport sources come in two different tarballs:<br>
<h1>Obtaining Campcaster sources</h1>
Campcaster sources come in two different tarballs:<br>
<ul>
<li><code>livesupport-&lt;version&gt;.tar.bz2</code> - the
LiveSupport source files<code><br>
<li><code>campcaster-&lt;version&gt;.tar.bz2</code> - the
Campcaster source files<code><br>
</code></li>
<li><code>livesupport-libraries-&lt;version&gt;.tar.bz2</code> -
external libraries used by LiveSupport<code><br>
<li><code>campcaster-libraries-&lt;version&gt;.tar.bz2</code> -
external libraries used by Campcaster<code><br>
</code></li>
</ul>
Both files can be downloaded from <a
href="http://sourceforge.net/projects/livesupport/"><code>http://sourceforge.net/projects/livesupport/</code></a>.
href="http://sourceforge.net/projects/campcaster/"><code>http://sourceforge.net/projects/campcaster/</code></a>.
<br>
<br>
After downloading the files, untar them in the same directory:<br>
<br>
<pre><code>tar xfj livesupport-&lt;version&gt;.tar.bz2<br>tar xfj livesupport-libraries-&lt;version&gt;.tar.bz2<br></code></pre>
<pre><code>tar xfj campcaster-&lt;version&gt;.tar.bz2<br>tar xfj campcaster-libraries-&lt;version&gt;.tar.bz2<br></code></pre>
<br>
which will create a <code>livesupport-&lt;version&gt;</code>
which will create a <code>campcaster-&lt;version&gt;</code>
directory, with all the required files to compile and install
LiveSupport.<br>
<h1>Compiling LiveSupport</h1>
To compile LiveSupport, enter the LiveSupport directory, and execute
Campcaster.<br>
<h1>Compiling Campcaster</h1>
To compile Campcaster, enter the Campcaster directory, and execute
the following commands:<br>
<br>
<pre><code>cd livesupport-&lt;version&gt;<br>./configure </code><code>--prefix=/usr/local/livesupport --with-apache-group=apache --with-www-docroot=/var/www<br></code><code>make<br></code></pre>
<pre><code>cd campcaster-&lt;version&gt;<br>./configure </code><code>--prefix=/usr/local/campcaster --with-apache-group=apache --with-www-docroot=/var/www<br></code><code>make<br></code></pre>
<br>
Note that you need to have write permissions in the <code>prefix</code> directory
when you run <code>make</code>.
@ -161,15 +161,15 @@ The configure options used above are the options most probably used:<br>
<br>
<pre><code>&nbsp; --prefix=PREFIX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; install architecture-independent files in PREFIX<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [/usr/local]</code></pre>
The installation directory. Supply the previously
decided LiveSupport installation directory here, <code>&lt;ls-installdir&gt;</code>
(as mentioned above). A sensible value to use here is <code>/usr/local/livesupport</code>.<br>
decided Campcaster installation directory here, <code>&lt;ls-installdir&gt;</code>
(as mentioned above). A sensible value to use here is <code>/usr/local/campcaster</code>.<br>
<pre><code><br> --with-apache-group use apache running in the specified group (apache)<br><br></code></pre>
The user group the apache web server daemon runs at (see the section
above on installing apache). Supply the <code>&lt;apache-group&gt;</code>
value here, as mentioned above, which is usually either <code>apache</code>
or <code>www-data</code>.<br>
<br>
<pre> --with-www-docroot deploy LiveSupport under the specified docroot<br> (/var/www)<br><br></pre>
<pre> --with-www-docroot deploy Campcaster under the specified docroot<br> (/var/www)<br><br></pre>
The document root of your apache installation (see the section above on
installing apache). Supply the <code>&lt;www-root&gt;</code>
value here, as mentioned above, which is usually <code>/var/www</code>
@ -182,39 +182,39 @@ movie, relax,
etc.<br>
<br>
If you want the installation script to create the database tables used
by LiveSupport, consider using the following configure options:<br>
by Campcaster, consider using the following configure options:<br>
<br>
<pre> --with-create-database specify whether the LiveSupport database and database<br> user should be created (no)<br> --with-create-odbc-data-source<br> specify whether the ODBC data source for LiveSupport<br> should be created (no)<br> --with-init-database specify whether the LiveSupport database tables<br> should be initialized (no)<br> --with-configure-apache specify whether apache should be configured for<br> LiveSupport through its conf.d directory (no)<br><br><br></pre>
<pre> --with-create-database specify whether the Campcaster database and database<br> user should be created (no)<br> --with-create-odbc-data-source<br> specify whether the ODBC data source for Campcaster<br> should be created (no)<br> --with-init-database specify whether the Campcaster database tables<br> should be initialized (no)<br> --with-configure-apache specify whether apache should be configured for<br> Campcaster through its conf.d directory (no)<br><br><br></pre>
For a full list of options, see <code>./configure --help</code><br>
<h1>Installing LiveSupport<br>
<h1>Installing Campcaster<br>
</h1>
After a successful compilation, to install LiveSupport, you can install
LiveSupport by typing:<br>
After a successful compilation, to install Campcaster, you can install
Campcaster by typing:<br>
<br>
<pre><code>make install</code><br></pre>
<br>
This will install LiveSupport into the directory specified to the
This will install Campcaster into the directory specified to the
configure script. It will also create necessary database tables,
depending on the invocation of the configure script. You need to run
<code>make install</code> as root.<br>
<br>
<h1>Try it out</h1>
After a successful installation, the LiveSupport scheduler has to be
After a successful installation, the Campcaster scheduler has to be
started. The scheduler has a System V runlevel-style startup script,
under &lt;ls-installdir&gt;/bin/scheduler.sh. To start the scheduler,
simply invoke:<br>
<br>
<pre><code>&lt;ls-installdir&gt;/bin/scheduler.sh start</code><br></pre>
<br>
The only thing left to do is to try out the LiveSupport web interface
The only thing left to do is to try out the Campcaster web interface
or the GUI application.<br>
<br>
For the web interface, point your browser to the following URL: <code>http://&lt;yourhost&gt;/livesupport/</code>
For the web interface, point your browser to the following URL: <code>http://&lt;yourhost&gt;/campcaster/</code>
.<br>
<br>
The GUI application can be started by issuing the following command:<br>
<br>
<pre><code>&lt;ls-installdir&gt;/bin/gLiveSupport.sh</code><br></pre>
<pre><code>&lt;ls-installdir&gt;/bin/campcaster-studio.sh</code><br></pre>
<br>
For your first login, use the following values:<br>
<ul>

124
campcaster/doc/manual/index.html
View File

@ -34,7 +34,7 @@
<H1 CLASS="western"><FONT SIZE=4 STYLE="font-size: 16pt"><B>1.0 LS
Studio: A live radio show assistant</B></FONT></H1>
<P CLASS="western" STYLE="margin-bottom: 0in">Live Support Studio is
the part of LiveSupport that completely does the on air playback
the part of Campcaster that completely does the on air playback
function inside a radio station's live studio but also includes all
known automation elements.</P>
<P CLASS="western" STYLE="margin-bottom: 0in"><BR>
@ -52,7 +52,7 @@ search criteria to the smallest search details.</P>
<P LANG="" CLASS="western" STYLE="margin-bottom: 0in"><BR>
</P>
<P CLASS="western" STYLE="margin-bottom: 0in"><FONT SIZE=2 STYLE="font-size: 11pt"><I><B>Note:</B>
LiveSupport Studio is not software for dynamic reduction
Campcaster Studio is not software for dynamic reduction
equalization or audio signal post processing - it doesn&rsquo;t make
any major dynamic signal improvement.</I></FONT></P>
<P CLASS="western" STYLE="margin-bottom: 0in"><BR>
@ -60,12 +60,12 @@ any major dynamic signal improvement.</I></FONT></P>
<P CLASS="western" STYLE="margin-bottom: 0in"><I><FONT SIZE=2 STYLE="font-size: 11pt">If
you want to edit and do additional processing of radio signals
afterwards, we recommend (before any distribution of audio signal
towards the transmitter) to use a known standalone dynamic reduction
towards the transmitter) to use a known standalone dynamic reduction
tool (dynamic compression, DeEsser, level maximizing) for pseudo
acoustic improvements of the sound spectrum and listening impression.</FONT></I></P>
<P CLASS="western" STYLE="margin-bottom: 0in"><BR>
</P>
<P CLASS="western" STYLE="margin-bottom: 0in">LiveSupport Studio is
<P CLASS="western" STYLE="margin-bottom: 0in">Campcaster Studio is
intended to be used on an independent playback machine that has two
working modes:</P>
<UL>
@ -128,7 +128,7 @@ song</U></B>.</I></P>
<P CLASS="western" STYLE="margin-bottom: 0in"><FONT SIZE=4><I><FONT SIZE=3>Note:
Live Automatic mode is currently the only mode LS Studio has. Changes
take place frequently<B>, </B><SPAN STYLE="font-weight: medium">so
check the LiveSupport homepage at </SPAN></FONT></I><A HREF="http://livesupport.campware.org/"><SPAN STYLE="font-weight: medium"><I><FONT SIZE=3>http://livesupport.campware.org</FONT></I></SPAN></A><SPAN STYLE="font-weight: medium"><I><FONT SIZE=3>
check the Campcaster homepage at </SPAN></FONT></I><A HREF="http://campcaster.campware.org/"><SPAN STYLE="font-weight: medium"><I><FONT SIZE=3>http://campcaster.campware.org</FONT></I></SPAN></A><SPAN STYLE="font-weight: medium"><I><FONT SIZE=3>
often. </FONT></I></SPAN></FONT>
</P>
<P CLASS="western" STYLE="margin-bottom: 0in"><BR>
@ -153,12 +153,12 @@ station&rsquo;s orientation).</P>
machine, Live Assist mode broadcasts audio files one by one (song by
song), according to the broadcast scheduler and previously-created
playlists. After the audio file is played, the list stops, waiting
for the user&rsquo;s next start command.
for the user&rsquo;s next start command.
</P>
<P CLASS="western" STYLE="margin-bottom: 0in">
<P CLASS="western" STYLE="margin-bottom: 0in">
</P>
<P CLASS="western" STYLE="margin-bottom: 0in">So that the broadcast
process looks like: <I><B><U>song &ndash; stop &ndash; manual play -
process looks like: <I><B><U>song &ndash; stop &ndash; manual play -
next song</U></B>.</I></P>
<P CLASS="western" STYLE="margin-bottom: 0in"><BR>
</P>
@ -200,18 +200,18 @@ next song</U></B>.</I></P>
</P>
<P CLASS="western" STYLE="margin-bottom: 0in"><BR>
</P>
<H2 CLASS="western"><FONT SIZE=4 STYLE="font-size: 16pt"><B>1.1
Accessing LiveSupport Studio</B></FONT></H2>
<H2 CLASS="western"><FONT SIZE=4 STYLE="font-size: 16pt"><B>1.1
Accessing Campcaster Studio</B></FONT></H2>
<P CLASS="western" STYLE="margin-bottom: 0in"><BR>
</P>
<P CLASS="western" STYLE="margin-bottom: 0in">When starting the
computer with LiveSupport installed from the demo/install CD - you
will find the LS Studio icon on the desktop.
computer with Campcaster installed from the demo/install CD - you
will find the LS Studio icon on the desktop.
</P>
<P CLASS="western" STYLE="margin-bottom: 0in"><BR>
</P>
<P CLASS="western" STYLE="margin-bottom: 0in">After starting the
LiveSupport application on your studio machine, the Master Panel will
Campcaster application on your studio machine, the Master Panel will
appear, allowing you to login into the system and giving you
essential information about the station time and logo as well as what
is currently in the program.</P>
@ -222,9 +222,9 @@ is currently in the program.</P>
<P CLASS="western" STYLE="margin-bottom: 0in"><BR>
</P>
<P CLASS="western" STYLE="margin-bottom: 0in">When starting
LiveSupport Studio, the Master Panel appears in the upper part of the
Campcaster Studio, the Master Panel appears in the upper part of the
screen, remaining on the screen as your friendly assistant the whole
time you work on your computer.
time you work on your computer.
</P>
<P CLASS="western" STYLE="margin-bottom: 0in"><BR>
</P>
@ -260,7 +260,7 @@ of LS Studio you are working in, the Master Panel displays:</P>
<FONT SIZE=2 STYLE="font-size: 11pt"><I>Note: The content of the
Next Playing and VU meter fields is currently neither available nor
visible. This is only a short description what these fields will
indicate in an upcoming version of LiveSupport.</I></FONT></P>
indicate in an upcoming version of Campcaster.</I></FONT></P>
<UL>
<LI><P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0in">
<FONT COLOR="#000000"><B>logo</B> of your radio station - this can
@ -272,7 +272,7 @@ indicate in an upcoming version of LiveSupport.</I></FONT></P>
<LI><P CLASS="western" STYLE="margin-bottom: 0in"><B>Exit </B>button,
which you need to click if you want to exit the whole application.
The popup window will then appear asking you to confirm if you are
sure in this action.
sure in this action.
</P>
</UL>
<P CLASS="western" STYLE="margin-left: 0.5in; margin-bottom: 0in"><BR>
@ -328,7 +328,7 @@ which displays the following :</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0in">The <STRONG>Language
<SPAN STYLE="font-weight: medium">drop-down menu</SPAN></STRONG> &ndash;
where you can select one of the available user interface
localizations of LiveSupport Studio from the list. The default
localizations of Campcaster Studio from the list. The default
language is English, but you can use one of the other localized
versions we supply.</P>
</UL>
@ -344,7 +344,7 @@ again if you quit LS Studio completely and start the program again.</P>
login or cancel the operation.</P>
</UL>
<P STYLE="margin-top: 0.19in; margin-bottom: 0.19in">After
successfully presenting on the system and logging in into LiveSupport
successfully presenting on the system and logging in into Campcaster
Studio, you will be able to see the following:</P>
<UL>
<LI><P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0in">
@ -353,7 +353,7 @@ Studio, you will be able to see the following:</P>
by the scheduler and play/stop functions of the audio slot.</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0.19in">The <STRONG>Navigation
Menu</STRONG> &ndash; buttons for all the main functions you need
for operating LiveSupport Studio, depending on your user rights and
for operating Campcaster Studio, depending on your user rights and
permissions (previously determined by administrator)</P>
</UL>
<P LANG="" CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in">
@ -381,7 +381,7 @@ in the ScratchPad the last time.</I></P>
Navigation Menu contains all the main functions you need for
operating Live Support Studio. It is located in the lower part of the
Master Panel, and is visible there throughout the whole user&rsquo;s
session.
session.
</P>
<P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in">The
Navigation Menu consists of the following functions:</P>
@ -403,7 +403,7 @@ Navigation Menu consists of the following functions:</P>
broadcast schedule</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0.19in"><B>Search
</B>button &ndash; search and browse audio clips available in the
LiveSupport storage server using the search criteria you set</P>
Campcaster storage server using the search criteria you set</P>
</UL>
<P CLASS="western" STYLE="margin-bottom: 0in"><BR>
</P>
@ -455,7 +455,7 @@ Navigation Menu consists of the following functions:</P>
</P>
<P CLASS="western" STYLE="margin-bottom: 0in">Clicking on the &lsquo;Live
Mode&rsquo; button in the Navigation Menu opens up a new palette on
the screen below the Master Panel.
the screen below the Master Panel.
</P>
<P CLASS="western" STYLE="margin-bottom: 0in"><BR>
</P>
@ -468,11 +468,11 @@ contains:</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0in"><B>preview</B>
(cue) buttons &ndash; <B>play/pause and stop button</B> &ndash;
gives users the option of pre-listening to audio files before
playing them on air.
playing them on air.
</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0in">Space under the
preview and play buttons is set to contain the <B>list of audio
slots</B> (playlists, single files&hellip;) created by the user .
slots</B> (playlists, single files&hellip;) created by the user .
</P>
</UL>
<P CLASS="western" STYLE="margin-left: 0.29in; margin-bottom: 0in"><BR>
@ -569,7 +569,7 @@ advertising blocks and have a pre-determined time for broadcast.</I></P>
than can simply upload the complete advert playlist from the sales
department, instead of inserting ads file by file. </I>
</P>
<H2 CLASS="western"><FONT SIZE=4 STYLE="font-size: 16pt"><B>1.6
<H2 CLASS="western"><FONT SIZE=4 STYLE="font-size: 16pt"><B>1.6
Upload file</B></FONT></H2>
<P CLASS="western" STYLE="margin-bottom: 0in"><BR>
</P>
@ -601,7 +601,7 @@ Upload file</B></FONT></H2>
</P>
<P CLASS="western" STYLE="margin-bottom: 0in">The 'upload file'
option allows you to upload files from your local computer,
LiveSupport server or any other available source into the system. It
Campcaster server or any other available source into the system. It
then appears in the ScratchPad.</P>
<P CLASS="western" STYLE="margin-bottom: 0in">Browsing the audio
archive or any other source or disc, user can find the audio file
@ -627,7 +627,7 @@ palette consists of the following elements:</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0in"><B>Main</B>, <B>Music</B>
and <B>Talk </B>tabs &ndash; where metadata information (such as the
information stored in an MP3 file's ID3 tags) can be added or
edited.
edited.
</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0.19in"><SPAN STYLE="font-weight: medium">The</SPAN><B>
Main</B> <SPAN STYLE="font-weight: medium">tab</SPAN> is the default
@ -650,7 +650,7 @@ palette consists of the following elements:</P>
<BR>
</P>
<P CLASS="western" STYLE="margin-left: 0.5in; margin-bottom: 0in"><I>Note:
If an MP3 file is uploaded, LiveSupport will automatically use the
If an MP3 file is uploaded, Campcaster will automatically use the
information stored in its ID3 tags, if there is any.</I></P>
<UL>
<LI><P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0in">
@ -706,7 +706,7 @@ it appears at the top of the ScratchPad list).<SPAN STYLE="background: #000000">
</P>
<P CLASS="western" STYLE="margin-bottom: 0in"><BR>
</P>
<P CLASS="western" STYLE="margin-bottom: 0in">As in LiveSupport
<P CLASS="western" STYLE="margin-bottom: 0in">As in Campcaster
Station, the ScratchPad represents your workspace during your entire
session. It can be used for loading all the materials (audio files,
playlists&hellip;) you find necessary for creating your program. The
@ -721,16 +721,16 @@ palette. It consists of the following elements:</P>
buttons &ndash; <B>play/pause and stop button</B> - gives you the
option of pre-listening and quick-checking audio files before using
them in Live Mode or a playlist.</P>
<LI><P STYLE="margin-bottom: 0in">The<B> Type</B> column &ndash;
<LI><P STYLE="margin-bottom: 0in">The<B> Type</B> column &ndash;
contains icons indicating the type of item you are working with. An
icon's appearance is the same as in LiveSupport Station &ndash;
icon's appearance is the same as in Campcaster Station &ndash;
audioclips are marked with a green note, playlists with a red note,
and webstreams with a blue transmission symbol.</P>
<LI><P STYLE="margin-bottom: 0in">The <B>Title</B> column &ndash;
displays the title of the items (audioclips, playlists, webstreams)</P>
<LI><P STYLE="margin-bottom: 0in"><B>Add to playlist</B> button -
allows you to insert the selected file into a playlist by opening
the Playlist palette and placing the selected file into it.
the Playlist palette and placing the selected file into it.
</P>
<LI><P STYLE="margin-bottom: 0in"><B>Clear list</B> button &ndash;
deletes all items from the ScratchPad</P>
@ -762,7 +762,7 @@ the audioclips and playlists):</P>
</UL>
<P STYLE="margin-top: 0.19in; margin-bottom: 0.19in">The ScratchPad
has additional options for playlists only. If you right-click on a
playlist, additional actions offered will include:
playlist, additional actions offered will include:
</P>
<UL>
<LI><P STYLE="margin-top: 0.19in; margin-bottom: 0in"><FONT SIZE=2 STYLE="font-size: 11pt"><B>Edit
@ -809,7 +809,7 @@ playlist, additional actions offered will include:
</P>
<P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in">Playlists
can be edited and created in the Playlists palette, which, at the
same time, works as a simple playlist editor.
same time, works as a simple playlist editor.
</P>
<P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in">This
function allows you to execute various operations such as:</P>
@ -830,10 +830,10 @@ to the active or new empty playlist by:</P>
<UL>
<LI><P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0in">
right- clicking on the item (either a sound file or playlist) in the
ScratchPad and
ScratchPad and
</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0.19in">selecting <B>Add
to playlist</B>.
to playlist</B>.
</P>
</UL>
<P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in"><BR><BR>
@ -845,7 +845,7 @@ by:</P>
<LI><P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0in">
right-clicking on the playlist in the ScratchPad and</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0.19in">selecting <B>Edit</B>
from the popup menu
from the popup menu
</P>
</UL>
<P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in">The
@ -860,10 +860,10 @@ Playlists palette will then appear, displaying:</P>
file, starting from zero. Start time for the next item is
calculated automatically.</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0in">The <B>Title
</B>column displays names of the files, playlists or streams.
</B>column displays names of the files, playlists or streams.
</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0in">The <B>Length
</B>column lists the duration of each item
</B>column lists the duration of each item
</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0in">The <B>Fade in and
Fade out </B>column displays the increasing/decreasing curve
@ -885,7 +885,7 @@ field remains blank.</P>
<UL>
<LI><P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in">
<SPAN STYLE="font-weight: medium">The</SPAN><B> Save</B> button
enables you to save all your changes and your work.
enables you to save all your changes and your work.
</P>
</UL>
<P CLASS="western" STYLE="margin-left: 0.5in; margin-top: 0.19in; margin-bottom: 0.19in">
@ -925,7 +925,7 @@ palette allows you to automate (schedule) your playlist for broadcast
at a predefined date and time.</P>
<P STYLE="margin-top: 0.19in; margin-bottom: 0.19in">Clicking on the
Scheduler button in the Navigation menu opens up a palette similar to
the Scheduler Navigator from LiveSupport Station. The palette appears
the Scheduler Navigator from Campcaster Station. The palette appears
as a monthly calendar and contains the following elements:</P>
<UL>
<LI><P STYLE="margin-top: 0.19in; margin-bottom: 0in"><B>Monthly
@ -950,10 +950,10 @@ will be available in the ScratchPad and can be added to the Scheduler
by:</P>
<UL>
<LI><P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0in">
right- clicking on the saved playlist in the ScratchPad and
right- clicking on the saved playlist in the ScratchPad and
</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0.19in">selecting<B>
Schedule</B> option from the popup menu.
Schedule</B> option from the popup menu.
</P>
</UL>
<P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in">That
@ -983,15 +983,15 @@ scheduled playlist in the table and selecting <B>Delete</B>. This
removes the playlist from the Scheduler , but does not remove it
completely from the system. The playlist and the items inside it
stays in the ScratchPad for the next use.</P>
<H2 CLASS="western"><FONT SIZE=4 STYLE="font-size: 16pt"><B>1.10
<H2 CLASS="western"><FONT SIZE=4 STYLE="font-size: 16pt"><B>1.10
Search</B></FONT></H2>
<P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in">The
search palette allows you to search (on either a simple or advanced
level) and browse the archive of available files in LiveSupport's
level) and browse the archive of available files in Campcaster's
storage server, in order to use them for creating playlists,
scheduling or creating Live Mode lists. You can start looking for
audioclips not only by title, but also by general searching metadata
criteria down even to the smallest search details.
criteria down even to the smallest search details.
</P>
<P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in">The
main part of the Search palette are tabs that gives you the option to
@ -1034,7 +1034,7 @@ and webstreams.</P>
<P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in">The
Search (simple search) option works as a basic simple search engine.
The user types a keyword into the search field, and then presses the
<B>Search </B>button.
<B>Search </B>button.
</P>
<P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in">In
the simple search option, the search process is based on keywords
@ -1062,7 +1062,7 @@ Advanced Search</B></FONT></H3>
</P>
<P CLASS="western" STYLE="margin-bottom: 0in">Advanced Search also
works as a regular search engine. As in simple search mode, you can
search the metadata that you and other LiveSupport users have input
search the metadata that you and other Campcaster users have input
during the upload process. The main difference is that Advanced
Search allows you to select as much metadata criteria as you find
relevant to make your search successful. All the search results will
@ -1071,13 +1071,13 @@ appear at the bottom of the search palette.</P>
Advanced Search tab contains the following elements:</P>
<UL>
<LI><P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0in">
<B>Search field</B> with three types of criteria in one row;
<B>Search field</B> with three types of criteria in one row;
</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0in">The left pulldown
menu allows you to select one metadata criterium you find relevant
for the search. You can choose any metadata that LiveSupport offers
for the search. You can choose any metadata that Campcaster offers
and users have input to describe audio content (title, genre,
length, album, mood, bitrate).
length, album, mood, bitrate).
</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0in">The <B>middle
pulldown</B> menu enables you to refine your search by selecting
@ -1091,7 +1091,7 @@ Advanced Search tab contains the following elements:</P>
located on the right allows you to add <B>extra sets of criteria </B><SPAN STYLE="font-weight: medium"><SPAN STYLE="font-style: normal">by</SPAN></SPAN><B>
</B>clicking on the + sign located on the right of the search terms.
You can add as many rows you need to refine your search. Clicking on
the X sign removes a row.
the X sign removes a row.
</P>
</UL>
<P CLASS="western" STYLE="margin-left: 0.5in; margin-top: 0.19in; margin-bottom: 0.19in">
@ -1118,11 +1118,11 @@ precise and narrow your search results.</P>
<P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in"><BR><BR>
</P>
<P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in">Like
in LiveSupport Station, the Browse function in LiveSupport Studio
in Campcaster Station, the Browse function in Campcaster Studio
allows you to browse all files from the server according to general
criteria you specify. In order to narrow search results as much as
possible, the browse function gives you the opportunity to choose
between similar files that are in the same subcategory.
between similar files that are in the same subcategory.
</P>
<P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in">The
browsing process is divided into three columns with the same list of
@ -1136,7 +1136,7 @@ offered criteria.</P>
category, the pulldown menu of the second column allows you to
choose one of the options that appear in the chosen category, which
<B>refines</B> <B>the</B> <B>number</B> <B>of</B> <B>displayed</B>
<B>files</B>.
<B>files</B>.
</P>
<LI><P CLASS="western" STYLE="margin-bottom: 0.19in">The <B>third
column</B> works the same way and lets you <B>continue refining</B>
@ -1151,7 +1151,7 @@ file quickly among the thousands of files in the server.</I></P>
you choose simple Search, Advanced search or Browse option, the
search results will appear at the bottom of the palette in the table
containing <B>Type, Title, Creator and Length</B> of the resulting
file.
file.
</P>
<P CLASS="western" STYLE="margin-top: 0.19in; margin-bottom: 0.19in">By
right clicking on an item (audio file, playlist or a webstream) in
@ -1167,18 +1167,18 @@ the search result table, a menu appears offering operations:</P>
<H1 CLASS="western">2. Additional information</H1>
<H2 CLASS="western"><B>2.1 Where to go for more help</B></H2>
<P CLASS="western" STYLE="margin-bottom: 0in; font-weight: medium"><FONT SIZE=2 STYLE="font-size: 11pt"><FONT SIZE=3>You
can visit LiveSupport's discussion forums online at
</FONT><A HREF="http://livesupport.campware.org/"><FONT SIZE=3>http://livesupport.campware.org</FONT></A><FONT SIZE=3>.
can visit Campcaster's discussion forums online at
</FONT><A HREF="http://campcaster.campware.org/"><FONT SIZE=3>http://campcaster.campware.org</FONT></A><FONT SIZE=3>.
There you will also find program updates and other useful
information.</FONT></FONT></P>
<P CLASS="western" STYLE="margin-bottom: 0in; font-weight: medium"><BR>
</P>
<H2 CLASS="western">2.2 How to report bugs</H2>
<P CLASS="western" STYLE="margin-bottom: 0in; font-weight: medium"><FONT SIZE=3>LiveSupport
<P CLASS="western" STYLE="margin-bottom: 0in; font-weight: medium"><FONT SIZE=3>Campcaster
needs your input to constantly improve. If the software doesn't
behave as it should, please let us know about it by entering a
trouble ticket at <A HREF="http://code.campware.org/projects/livesupport">http://code.campware.org/projects/livesupport</A>.
That way, the LiveSupport team can keep track of your problem and you
trouble ticket at <A HREF="http://code.campware.org/projects/campcaster">http://code.campware.org/projects/campcaster</A>.
That way, the Campcaster team can keep track of your problem and you
can check to see whether it has been fixed.</FONT></P>
</BODY>
</HTML>

8
campcaster/doc/model/Authentication/index.html
View File

@ -3,12 +3,12 @@
<head>
<meta content="text/html; charset=ISO-8859-2"
http-equiv="content-type">
<title>LiveSupport Authentication specification</title>
<meta content="Ákos Maróy" name="author">
<title>Campcaster Authentication specification</title>
<meta content="<EFBFBD>kos Mar<61>y" name="author">
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright &#169; 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,7 +18,7 @@ Development Loan Fund</a>, under the GNU <a
<li>Location: $URL$</li>
</ul>
<h1>Scope</h1>
This document contains the specification of the LiveSupport
This document contains the specification of the Campcaster
Authentication component.<br>
<br>
This document contains embedded <a

50
campcaster/doc/model/LocalStorage/index.html
View File

@ -3,12 +3,12 @@
<head>
<meta content="text/html; charset=ISO-8859-2"
http-equiv="content-type">
<title>LiveSupport Local storage specification</title>
<meta content="Ákos Maróy" name="author">
<title>Campcaster Local storage specification</title>
<meta content="<EFBFBD>kos Mar<61>y" name="author">
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright &#169; 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,7 +18,7 @@ Development Loan Fund</a>, under the GNU <a
<li>Location: $URL$</li>
</ul>
<h1>Scope</h1>
This document contains the specification of the LiveSupport Local
This document contains the specification of the Campcaster Local
storage component.<br>
<br>
This document contains embedded <a
@ -36,7 +36,7 @@ Audio Clips contain audio data bundled with metadata describing it.
Storing locally means that the binary audio data is available not just
as a stream, but also as random seekable file.<br>
The local storage contains Playlists also. These are metadata
files containing a list of Audio Clip IDs with extra (fade in / fade out)
files containing a list of Audio Clip IDs with extra (fade in / fade out)
information.</br>
<h2>System functions</h2>
The main system functions are described below. There are three
@ -1116,7 +1116,7 @@ with the given ID, the user is notified and the use case ends.</li>
</tr>
<tr>
<td valign="top"><b>purpose</b> </td>
<td valign="top">To modify an existing Playlist in the local
<td valign="top">To modify an existing Playlist in the local
storage<br>
</td>
</tr>
@ -1124,7 +1124,7 @@ storage<br>
<td valign="top"><b>overview</b> </td>
<td valign="top">The Storage maintainer contacts the Local
storage with the aim of editing an existing Playlist. The Local
storage retrieves the Playlist and marks it as being edited. The Storage
storage retrieves the Playlist and marks it as being edited. The Storage
maintainer modifies the Playlist. The Storage maintainer saves the
modified Playlist, the Local storage stores it in place of the old
Playlist and marks it as no longer being edited.<br>
@ -1172,8 +1172,8 @@ and grants access<br>
</td>
<td valign="top"><b>5.</b><br>
</td>
<td valign="top">The system verifies that there is a Playlist
in the Local storage with the given ID, and it is not currently
<td valign="top">The system verifies that there is a Playlist
in the Local storage with the given ID, and it is not currently
being edited<br>
</td>
</tr>
@ -1184,7 +1184,7 @@ being edited<br>
</td>
<td valign="top"><b>6.</b><br>
</td>
<td valign="top">The system marks the Playlist with the given ID
<td valign="top">The system marks the Playlist with the given ID
as being edited<br>
</td>
</tr>
@ -1228,8 +1228,8 @@ Playlist earlier<br>
</td>
<td valign="top"><b>11.</b><br>
</td>
<td valign="top">The system stores the new Playlist metafile in
place of the old one, marks it as no longer being edited,
<td valign="top">The system stores the new Playlist metafile in
place of the old one, marks it as no longer being edited,
and notifies the Storage maintainer of the actions taken<br>
</td>
</tr>
@ -1261,7 +1261,7 @@ and notifies the Storage maintainer of the actions taken<br>
<li><b>action 3:</b> if the Storage maintainer can not be
authenticated, she is notified, and the use case ends.</li>
<li><b>action 5:</b> if there is no Playlist in the Local storage
with the given ID, or if the Playlist is already being edited,
with the given ID, or if the Playlist is already being edited,
the user is notified and the use case ends.</li>
<li><b>action 10:</b> if the user cannot be identified as the same
that opened the Playlist for editing, the user is notified, and the
@ -1297,7 +1297,7 @@ use case continues at point 8.</li></ul>
<tr>
<td valign="top"><b>overview</b> </td>
<td valign="top">The Storage maintainer contacts the Local
storage with the aim of deleting a Playlist. The system deletes the
storage with the aim of deleting a Playlist. The system deletes the
Playlist with the given ID from the Local storage.<br>
</td>
</tr>
@ -1344,7 +1344,7 @@ Playlist to be deleted<br>
</td>
<td valign="top"><b>5.</b><br>
</td>
<td valign="top">The system verifies that there is a Playlist
<td valign="top">The system verifies that there is a Playlist
in the Local storage with the given ID, and it is not currently being
edited<br>
</td>
@ -1389,7 +1389,7 @@ and notifies the Storage maintainer of the action taken<br>
<li><b>action 3:</b> if the Storage maintainer can not be
authenticated, she is notified, and the use case ends.</li>
<li><b>action 5:</b> if there is no Playlist in the Local storage
with the given ID, or if the Playlist is currently being edited,
with the given ID, or if the Playlist is currently being edited,
the user is notified and the use case ends.</li>
</ul>
<br>
@ -1417,14 +1417,14 @@ the user is notified and the use case ends.</li>
</tr>
<tr>
<td valign="top"><b>purpose</b> </td>
<td valign="top">To access a Playlist metafile in order to
<td valign="top">To access a Playlist metafile in order to
execute (play) it<br>
</td>
</tr>
<tr>
<td valign="top"><b>overview</b> </td>
<td valign="top">The Audio player contacts the Local
storage with the aim of accessing a Playlist. The Local storage
storage with the aim of accessing a Playlist. The Local storage
returns the requested Playlist metafile.<br>
</td>
</tr>
@ -1623,7 +1623,7 @@ extra (fade in / fade out) information<br>
<tr>
<td valign="top"><b>Token</b><br>
</td>
<td valign="top">An identifier used to match the parts of two-part
<td valign="top">An identifier used to match the parts of two-part
operations, e.g., access--release or edit--save<br>
</td>
</tr>
@ -2726,7 +2726,7 @@ being edited, report as an error<br>
<tr>
<td valign="top"><b>Output</b><br>
</td>
<td colspan="2" rowspan="1" valign="top">a URL of a Playlist
<td colspan="2" rowspan="1" valign="top">a URL of a Playlist
metafile, and a token identifying it<br>
</td>
</tr>
@ -2812,7 +2812,7 @@ the newPlaylist argument looks like<br>
<tr>
<td valign="top"><b>Exceptions</b><br>
</td>
<td colspan="2" rowspan="1" valign="top">if the playlistToken argument
<td colspan="2" rowspan="1" valign="top">if the playlistToken argument
does not match a token generated earlier in this session by editPlaylist(),
report as an error<br>
</td>
@ -2996,7 +2996,7 @@ given playlistId exists, report as an error<br>
<tr>
<td valign="top"><b>Output</b><br>
</td>
<td colspan="2" rowspan="1" valign="top">a URL of a Playlist
<td colspan="2" rowspan="1" valign="top">a URL of a Playlist
metafile, and a token identifying it<br>
</tr>
<tr>
@ -3072,7 +3072,7 @@ obtained earlier by accessPlaylist().<br>
<tr>
<td valign="top"><b>Exceptions</b><br>
</td>
<td colspan="2" rowspan="1" valign="top">if the playlistToken argument
<td colspan="2" rowspan="1" valign="top">if the playlistToken argument
does not match a token generated earlier in this session by accessPlaylist(),
report as an error<br>
</td>
@ -3306,7 +3306,7 @@ given audioClipId exists, report as an error<br>
<tr>
<td valign="top"><b>Output</b><br>
</td>
<td colspan="2" rowspan="1" valign="top">a URL of an AudioClip
<td colspan="2" rowspan="1" valign="top">a URL of an AudioClip
metafile, and a token identifying it<br>
</tr>
<tr>
@ -3382,7 +3382,7 @@ obtained earlier by accessAudioClip().<br>
<tr>
<td valign="top"><b>Exceptions</b><br>
</td>
<td colspan="2" rowspan="1" valign="top">if the audioClipToken argument
<td colspan="2" rowspan="1" valign="top">if the audioClipToken argument
does not match a token generated earlier in this session by accessAudioClip(),
report as an error<br>
</td>

8
campcaster/doc/model/MediaArchive/index.html
View File

@ -3,12 +3,12 @@
<head>
<meta content="text/html; charset=ISO-8859-2"
http-equiv="content-type">
<title>LiveSupport Media archive specification</title>
<meta content="Ákos Maróy" name="author">
<title>Campcaster Media archive specification</title>
<meta content="<EFBFBD>kos Mar<61>y" name="author">
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright &#169; 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,7 +18,7 @@ Development Loan Fund</a>, under the GNU <a
<li>Location: $URL$</li>
</ul>
<h1>Scope</h1>
This document contains the specification of the LiveSupport Media
This document contains the specification of the Campcaster Media
archive component.<br>
<br>
This document contains embedded <a

8
campcaster/doc/model/PlaylistEditor/index.html
View File

@ -3,12 +3,12 @@
<head>
<meta content="text/html; charset=ISO-8859-2"
http-equiv="content-type">
<title>LiveSupport Playlist editor specification</title>
<meta content="Ákos Maróy" name="author">
<title>Campcaster Playlist editor specification</title>
<meta content="<EFBFBD>kos Mar<61>y" name="author">
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright &#169; 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,7 +18,7 @@ Development Loan Fund</a>, under the GNU <a
<li>Location: $URL$</li>
</ul>
<h1>Scope</h1>
This document contains the specification of the LiveSupport Playlist
This document contains the specification of the Campcaster Playlist
editor component.<br>
<br>
This document contains embedded <a

16
campcaster/doc/model/Scheduler/index.html
View File

@ -3,12 +3,12 @@
<head>
<meta content="text/html; charset=ISO-8859-2"
http-equiv="content-type">
<title>LiveSupport Scheduler specifications</title>
<meta content="Ákos Maróy" name="author">
<title>Campcaster Scheduler specifications</title>
<meta content="<EFBFBD>kos Mar<61>y" name="author">
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright &#169; 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,7 +18,7 @@ Development Loan Fund</a>, under the GNU <a
<li>Location: $URL$</li>
</ul>
<h1>Scope</h1>
This document contains the specification of the LiveSupport Scheduler
This document contains the specification of the Campcaster Scheduler
daemon.<br>
<br>
This document contains embedded <a
@ -28,7 +28,7 @@ capable browser is needed to view it, or an SVG plugin like <a
<h1>Requirements</h1>
<h2>Overview<br>
</h2>
The purpose of the LiveSupport Scheduler daemon is to execute
The purpose of the Campcaster Scheduler daemon is to execute
playlists.<br>
<h2>Goals<br>
</h2>
@ -2832,7 +2832,7 @@ editing<br>
<td valign="top"><b>Notes</b><br>
</td>
<td colspan="2" rowspan="1" valign="top">A playlist is opened for
editing. Active (currently executing) playlists may not be opened for
editing. Active (currently executing) playlists may not be opened for
editing. The playlist may start executing while being edited: in this case,
editing is suspended while the playlist is executing and resumed afterwards.
This is in effect a lock, which is released by saving the playlist.<br>
@ -3263,8 +3263,8 @@ is at a given relative offset.<br>
<tr>
<td valign="top"><b>Exceptions</b><br>
</td>
<td colspan="2" rowspan="1" valign="top">If there is no Audio clip
with a start time at the given relative offset in the playlist, indicate
<td colspan="2" rowspan="1" valign="top">If there is no Audio clip
with a start time at the given relative offset in the playlist, indicate
as an error.<br>
</td>
</tr>

15
campcaster/doc/model/SoftwareArchitecture/index.html
View File

@ -3,12 +3,11 @@
<head>
<meta content="text/html; charset=ISO-8859-2"
http-equiv="content-type">
<title>LiveSupport Software Architecture</title>
<meta content="Akos Maroy" name="author">
<title>Campcaster Software Architecture</title>
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright &#169; 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,7 +17,7 @@ Development Loan Fund</a>, under the GNU <a
<li>Location: $URL$</li>
</ul>
<h1>Scope</h1>
This document describes the software architecture of LiveSupport.<br>
This document describes the software architecture of Campcaster.<br>
<br>
This document contains embedded <a
href="http://www.w3.org/Graphics/SVG/">SVG</a> figures, thus an SVG
@ -42,13 +41,13 @@ The software architecture for the Playlist Editor:<br>
A brief summary of the software components appearing in the figures
above:<br>
<h2>Scheduler</h2>
The LiveSupport Scheduler, responsible for executing playlists.<br>
The Campcaster Scheduler, responsible for executing playlists.<br>
<h2>Playlist editor</h2>
The LiveSupport Playlist editor, a graphical user interface component.<br>
The Campcaster Playlist editor, a graphical user interface component.<br>
<h2>Media Archive</h2>
The LiveSupport Media Archive component.<br>
The Campcaster Media Archive component.<br>
<h2>Local storage</h2>
The LiveSupport Local Storage component.<br>
The Campcaster Local Storage component.<br>
<h2>Helix Client Library</h2>
A media library developed by the <a href="https://helixcommunity.org/">Helix
Community</a> and <a href="http://www.realnetworks.com/">Real Networks</a>.

32
campcaster/doc/model/index.html
View File

@ -3,12 +3,12 @@
<head>
<meta content="text/html; charset=ISO-8859-2"
http-equiv="content-type">
<title>LiveSupport Architecture</title>
<meta content="Ákos Maróy" name="author">
<title>Campcaster Architecture</title>
<meta content="<EFBFBD>kos Mar<61>y" name="author">
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright &#169; 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,7 +18,7 @@ Development Loan Fund</a>, under the GNU <a
<li>Location: $URL$</li>
</ul>
<h1>Scope</h1>
This document describes the architecture of LiveSupport.<br>
This document describes the architecture of Campcaster.<br>
<br>
This document contains embedded <a
href="http://www.w3.org/Graphics/SVG/">SVG</a> figures, thus an SVG
@ -54,13 +54,13 @@ The <a href="PlaylistEditor/index.html">Playlist editor</a> component
is the user interface tool to create playlists.<br>
<h1>Feature - component mapping</h1>
This section contains a mapping from the features listed in section 3.3
the original LiveSupport proposal to the components that fulfill these
the original Campcaster proposal to the components that fulfill these
features.<br>
<h2>LiveSupport Feature List</h2>
For convenience the features listed in section 3.3 of the LiveSupport
<h2>Campcaster Feature List</h2>
For convenience the features listed in section 3.3 of the Campcaster
proposal are quoted below, with their original section numbers.<br>
<h3>3.3.1 Intuitive User Interface</h3>
<p>LiveSupport will feature an
<p>Campcaster will feature an
easily-localizable and intuitive user interface that draws on the
applicants&#8217; extensive previous project experience.</p>
<h3>3.3.2 Storing Metadata</h3>
@ -71,14 +71,14 @@ on artist, title, record, genre, track number and so on. It is
impossible to store essential information like the language of an
audio file &#8211; essential for spoken word productions, such as
educational or news material.</p>
<p>LiveSupport will use existing open
<p>Campcaster will use existing open
standards, such as RSS feed standards in XML format, to store all
information needed to describe a file sufficiently. Additionally,
this metadata information will fully support the Unicode format,
making the database of metadata available to all character sets and
fully searchable.</p>
<h3>3.3.3 Automation and Scheduling</h3>
<p>LiveSupport will provide a scheduler,
<p>Campcaster will provide a scheduler,
allowing stations to fill parts of the radio schedule with automated
broadcasts. Throughout automated broadcasting times, the station will
still be able to deliver advertisement, generating income while
@ -90,31 +90,31 @@ community.</p>
world mainly use playlists generated by audio player software such as
MusicMatch, Windows MediaPlayer or WinAMP. Such simple playlists
provide no more information than a list of file names, and are
inaccessible for full text search. As mentioned above, LiveSupport
inaccessible for full text search. As mentioned above, Campcaster
will use the potential of XML metadata in Unicode to manage and
archive playlists.</p>
<h3>3.3.5 Proof of Broadcast</h3>
<p>Proof of broadcast is essential to
establish serious business relationships with advertisers.
LiveSupport will provide accurate and detailed log files stating the
Campcaster will provide accurate and detailed log files stating the
precise time each item was broadcast over the system. In a
radio-network context, the proof of broadcast tool developed by MDLF
in conjunction with Radio 68H in Indonesia will be used to aggregate
and analyze logs created by individual LiveSupport installations.</p>
and analyze logs created by individual Campcaster installations.</p>
<h3>3.3.6 Mixing Local Audio Sources</h3>
<p>A producer running LiveSupport in a
<p>A producer running Campcaster in a
studio will be able to mix audio files (e.g. reports, music,
jingles), phone calls and the microphone into a live broadcast.</p>
<h3>3.3.7 Mixing Local and Remote Sources</h3>
<p>If connected to the Internet, and given
enough available bandwidth, LiveSupport will be able to play local
enough available bandwidth, Campcaster will be able to play local
files (stored on the system&#8217;s hard disk), remote files (stored
anywhere on the Internet) or include audio streams from the Internet
as part of the local transmission &#8211; all of which could also become
part of a playlist.</p>
<h3>3.3.8 Remote Control of Transmitter Locations</h3>
<p>A radio reporter/producer will be able
to remotely access all of LiveSupport&#8217;s scheduling features over
to remotely access all of Campcaster&#8217;s scheduling features over
the Internet using a standard web browser. She will be able to upload
audio programs as well as create playlists and schedule transmission.</p>
<h2>Feature - component mapping</h2>

18
campcaster/doc/quickstart/index.html
View File

@ -18,7 +18,7 @@
</tr>
<tr>
<td valign="top"><img src="livesupport_logo_blends.png" width="114" height="83" align="top"></td>
<td valign="top"><p><font size="+3" face="Bitstream Vera Sans, Verdana, Arial, sans-serif"><strong><font color="#F95916" size="6">LiveSupport 1.0</font><br>
<td valign="top"><p><font size="+3" face="Bitstream Vera Sans, Verdana, Arial, sans-serif"><strong><font color="#F95916" size="6">Campcaster 1.0</font><br>
</strong><font size="+2">Demo and Install CD
</font></font></p>
</td>
@ -27,32 +27,32 @@
<td width="24%" valign="top">&nbsp;</td>
<td width="76%"><p><font face="Bitstream Vera Sans, Verdana, Arial, sans-serif">This
CD is a bootable version of Linux for PCs that includes a demo version
of LiveSupport preinstalled.</font></p>
of Campcaster preinstalled.</font></p>
<p><font face="Bitstream Vera Sans, Verdana, Arial, sans-serif">To start,
insert this CD into your CD-ROM drive and restart your computer.<br>
You will be prompted for a boot option. Type &#8216;knoppix&#8217; and the
enter key and the startup procedure will continue.</font></p> <p><font face="Bitstream Vera Sans, Verdana, Arial, sans-serif">The <a href="http://www.kde.org">K
Desktop environment</a> (KDE), which is very similar to Windows, will appear. To
start the LiveSupport Studio application, click on its desktop icon.</font></p>
start the Campcaster Studio application, click on its desktop icon.</font></p>
<p><font face="Bitstream Vera Sans, Verdana, Arial, sans-serif"> For both
LiveSupport Studio and web access, The username is &#8216;root,&#8217; and
Campcaster Studio and web access, The username is &#8216;root,&#8217; and
the password is &#8216;q&#8217; for the demo.</font></p>
<p><font face="Bitstream Vera Sans, Verdana, Arial, sans-serif">You may
also access LiveSupport Station on this demo through a web browser.
also access Campcaster Station on this demo through a web browser.
Click the globe icon in the task bar to start the Mozilla Firefox browser.</font></p>
<p><font face="Bitstream Vera Sans, Verdana, Arial, sans-serif"> In the
URL field, type: <a href="http://localhost/livesupport">http://localhost/livesupport</a>.</font></p>
URL field, type: <a href="http://localhost/campcaster">http://localhost/campcaster</a>.</font></p>
<p><font face="Bitstream Vera Sans, Verdana, Arial, sans-serif"> You
may also choose to install the operating system and LiveSupport to
may also choose to install the operating system and Campcaster to
your
hard disk. Note: Installation to the hard disk is intended for experienced
users, and is intended for new computers. </font></p>
<p><font face="Bitstream Vera Sans, Verdana, Arial, sans-serif">As with
most open source software, LiveSupport is undergoing frequent updates.
most open source software, Campcaster is undergoing frequent updates.
For more information, including news about program updates, check our
website
frequently
at <a href="http://livesupport.campware.org">http://livesupport.campware.org</a></font></p></td>
at <a href="http://campcaster.campware.org">http://campcaster.campware.org</a></font></p></td>
</tr>
</table>
</div>

50
campcaster/doc/release.html
View File

@ -2,12 +2,12 @@
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type">
<title>LiveSupport release process documentation</title>
<title>Campcaster release process documentation</title>
<meta content="$Author$" name="author">
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright © 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,17 +18,17 @@ Development Loan Fund</a>, under the GNU <a
</ul>
<h1>Scope</h1>
This document describes the process of releasing a new version of
LiveSupport. Obviously this document is only relevant to people who
Campcaster. Obviously this document is only relevant to people who
have the rights and permissions to make such a release.<br>
<h1>Introduction</h1>
For all the releases of LiveSupport to remain consistent, it is
For all the releases of Campcaster to remain consistent, it is
preferable to have a repeatable release process, which will be followed
when creating releases. This ensures that no matter who creates the
releases, they will remain similar.<br>
<br>
The release process boils down to the following steps:<br>
<ul>
<li>getting LiveSupport sources</li>
<li>getting Campcaster sources</li>
<li>checking the distribution script</li>
<li>updating release version and changelog<br>
</li>
@ -41,9 +41,9 @@ The release process boils down to the following steps:<br>
<li>announcing the release<br>
</li>
</ul>
<h1>Getting LiveSupport sources</h1>
<h1>Getting Campcaster sources</h1>
It is assumed that the person doing the release has a read/write access
to the LiveSupport version control system. As a first step of the
to the Campcaster version control system. As a first step of the
release process, a fresh copy of the version control repository is
exported, so as to insure that:<br>
<ul>
@ -51,10 +51,10 @@ exported, so as to insure that:<br>
control system</li>
<li>there are no generated files in the release</li>
</ul>
To get a fresh copy of the LiveSupport repository, execute the
To get a fresh copy of the Campcaster repository, execute the
following in an empty directory:<br>
<br>
<pre><code>svn export svn+ssh://&lt;username&gt;@code.campware.org/home/svn/repo/livesupport/trunk/livesupport</code><br></pre>
<pre><code>svn export svn+ssh://&lt;username&gt;@code.campware.org/home/svn/repo/campcaster/trunk/campcaster</code><br></pre>
<br>
Where <code>&lt;username&gt;</code> is the user name for accessing the
repository of the person making the release.<br>
@ -79,10 +79,10 @@ is a mismatch between the release version and the topmost entry in the
debian changelog file.<br>
<br>
Curently, only the debian changelog keeps track of the changes and the
version of LiveSupport. To update the changelog, edit <code>etc/debian/changelog</code>,
version of Campcaster. To update the changelog, edit <code>etc/debian/changelog</code>,
by inserting a section onto the top of the file:<br>
<br>
<pre>livesupport (&lt;ls-version&gt;-1) unstable; urgency=low<br><br> * Changes listed here<br><br> -- <code>Package Maintainer &lt;maintainer@foo.bar&gt;</code> &lt;timestamp&gt;<br><br></pre>
<pre>campcaster (&lt;ls-version&gt;-1) unstable; urgency=low<br><br> * Changes listed here<br><br> -- <code>Package Maintainer &lt;maintainer@foo.bar&gt;</code> &lt;timestamp&gt;<br><br></pre>
The timestamp above must be preceeded by two spaces, and must be an RFC
2822 compliant date string, which is most easily produced by issuing
the <code>date -R</code> command. Please note that the debian package
@ -101,13 +101,13 @@ with the release version as its single parameter:<br>
<br>
This will create two tarballs in the current directory:<br>
<ul>
<li><code>livesupport-&lt;ls-version&gt;.tar.bz2</code></li>
<li><code>livesupport-libraries-&lt;ls-version&gt;.tar.bz2</code></li>
<li><code>campcaster-&lt;ls-version&gt;.tar.bz2</code></li>
<li><code>campcaster-libraries-&lt;ls-version&gt;.tar.bz2</code></li>
</ul>
<h1>Testing the tarballs</h1>
Having broken releases is very annoying, thus it is highly recommended
that the release tarballs are tested on a plain vanilla system. To test
the tarballs, follow the procedure described in the LiveSupport <a
the tarballs, follow the procedure described in the Campcaster <a
href="install.html">installation document</a>.<br>
<br>
Do not publish tarballs that have not been tested, or are known to be
@ -117,13 +117,13 @@ After the source tarballs have been tested, Debian source and binary
packages can be created. To do so, upload the source tarballs to a
Debian system, and do the following:<br>
<br>
<pre><code>tar xfj livesupport-&lt;ls-version&gt;.tar.bz2<br>tar xfj livesupport-libraries-&lt;ls-version&gt;.tar.bz2<br>cd livesupport-&lt;ls-version&gt;<br>./bin/createDebianPackages.sh -d .. -v &lt;ls-version&gt; -m "Package Maintainer &lt;maintainer@foo.bar&gt;" -o ..<br>cd ..<br></code></pre>
<pre><code>tar xfj campcaster-&lt;ls-version&gt;.tar.bz2<br>tar xfj campcaster-libraries-&lt;ls-version&gt;.tar.bz2<br>cd campcaster-&lt;ls-version&gt;<br>./bin/createDebianPackages.sh -d .. -v &lt;ls-version&gt; -m "Package Maintainer &lt;maintainer@foo.bar&gt;" -o ..<br>cd ..<br></code></pre>
<br>
The above command will create the Debain source package files next to
the original source tarballs. The script will generate the following
files, making up the Debian source package:<br>
<br>
<pre><code>livesupport_&lt;ls-version&gt;-1.dsc<br></code><code>livesupport_&lt;ls-version&gt;-1.diff.gz<br></code><code>livesupport_&lt;ls-version&gt;.orig.tar.gz<br><br></code></pre>
<pre><code>campcaster_&lt;ls-version&gt;-1.dsc<br></code><code>campcaster_&lt;ls-version&gt;-1.diff.gz<br></code><code>campcaster_&lt;ls-version&gt;.orig.tar.gz<br><br></code></pre>
Based on the source packages, the Debian package management system can
build the binaries for the current target platform, provided all the
necessary packages required to build are installed on the system. For a
@ -132,35 +132,35 @@ in extracted debianized source tree generated below.<br>
Building is best done
in an empty directory as follows:<br>
<br>
<pre><code>rm -rf /opt/livesupport<br>rm -rf debian_build<br>mkdir debian_build<br>cd debian_build<br></code>dpkg-source -x ../livesupport_&lt;ls_version&gt;-1.dsc<br>cd livesupport-&lt;ls-version&gt;<br>dpkg-buildpackage -rfakeroot<br>cd ../..<br><br></pre>
<pre><code>rm -rf /opt/campcaster<br>rm -rf debian_build<br>mkdir debian_build<br>cd debian_build<br></code>dpkg-source -x ../campcaster_&lt;ls_version&gt;-1.dsc<br>cd campcaster-&lt;ls-version&gt;<br>dpkg-buildpackage -rfakeroot<br>cd ../..<br><br></pre>
The above commands will result in the following debian packages:<br>
<br>
<pre><code>livesupport-libs_&lt;ls-version&gt;-1_&lt;arch&gt;.deb<br></code><code>livesupport-station_&lt;ls-version&gt;-1_&lt;arch&gt;.deb<br></code><code>livesupport-studio_&lt;ls-version&gt;-1_&lt;arch&gt;.deb</code><br></pre>
<pre><code>campcaster-libs_&lt;ls-version&gt;-1_&lt;arch&gt;.deb<br></code><code>campcaster-station_&lt;ls-version&gt;-1_&lt;arch&gt;.deb<br></code><code>campcaster-studio_&lt;ls-version&gt;-1_&lt;arch&gt;.deb</code><br></pre>
<pre><code></code><code></code></pre>
<h1>Tagging the sources</h1>
After the tarballs have been tested, the release can be finalized. As a
first step, the current state of the LiveSupport version control
first step, the current state of the Campcaster version control
repository has to be tagged, so that the the very versions in the
release can be retrieved at any later date. To tag the repository,
issue the following command:<br>
<br>
<pre><code>svn copy svn+ssh://&lt;username&gt;@code.campware.org/home/svn/repo/livesupport/trunk/ \
svn+ssh://&lt;username&gt;@code.campware.org/home/svn/repo/livesupport/tags/livesupport-&lt;ls-version&gt;<br></code></pre>
<pre><code>svn copy svn+ssh://&lt;username&gt;@code.campware.org/home/svn/repo/campcaster/trunk/ \
svn+ssh://&lt;username&gt;@code.campware.org/home/svn/repo/campcaster/tags/campcaster-&lt;ls-version&gt;<br></code></pre>
<br>
This will tag the current state of the repository with the tag <code>livesupport-&lt;ls-version&gt;</code>,
This will tag the current state of the repository with the tag <code>campcaster-&lt;ls-version&gt;</code>,
enabling later retrieval of this specific state.<br>
<h1>Updating Trac</h1>
Add the new version number to the Version pull-down menu in Trac by
executing
<pre><code>trac-admin /usr/local/trac-projects/livesupport version add &lt;ls-version&gt;</code></pre>
<pre><code>trac-admin /usr/local/trac-projects/campcaster version add &lt;ls-version&gt;</code></pre>
on <code>code.campware.org</code>.
<h1>Publishing the tarballs</h1>
To make the release available to the public, the created tarballs have
to be published. This is done by making the files accessible under the
LiveSupport project page on SourceForge: <code>http://sourceforge.net/projects/livesupport</code><span
Campcaster project page on SourceForge: <code>http://sourceforge.net/projects/campcaster</code><span
style="font-family: monospace;"></span><code></code>. Currently, only
MDLF support staff have access to publish into this
space, so after creating the tarballs, one should contact them
@ -180,7 +180,7 @@ are made:<br>
<li> PRweb (<a class="moz-txt-link-freetext"
href="http://www.prweb.com/">http://www.prweb.com</a>)</li>
<li>MDLF's press person</li>
<li> LiveSupport developers' list, urging everyone to send it to
<li> Campcaster developers' list, urging everyone to send it to
friends and contacts</li>
<li>Other Campware developers' lists on major releases</li>
<li> Other mailing lists and friendly/relevant organizations</li>

32
campcaster/doc/studioLocalization.html
View File

@ -2,12 +2,12 @@
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type">
<title>LiveSupport documentation for LS Studio localization</title>
<title>Campcaster documentation for LS Studio localization</title>
<meta content="$Author$" name="author">
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright © 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,28 +18,28 @@ Development Loan Fund</a>, under the GNU <a
</ul>
<h1>Scope</h1>
This document describes the process of adding a new language to the
LiveSupport Studio localization. It is written for developers.<br>
This document describes the process of adding a new language to the
Campcaster Studio localization. It is written for developers.<br>
<h1>Introduction</h1>
LiveSupport Studio (a.k.a. the C++ GUI) uses IBM's
Campcaster Studio (a.k.a. the C++ GUI) uses IBM's
<a href="http://www-306.ibm.com/software/globalization/icu/index.jsp">ICU</a>
library for localization. This library supports a fallback mechanism:
if the locale is set to <b>es_GT</b> (Guatemalan Spanish), it first tries to
read the <b>es_GT</b> table for localized strings; if there is no such table,
it tries the <b>es</b> table; and if that is missing, too, it reads the
it tries the <b>es</b> table; and if that is missing, too, it reads the
<b>root</b> table.<br>
These tables are stored as UTF-8 text files (with Unix line breaks, i.e., a
single 0x0A character at the end of each line) in the
single 0x0A character at the end of each line) in the
<code>products/gLiveSupport/var</code> directory with a <code>txt</code>
extension: e.g., <code>es_GT.txt</code>.
Before these files can be used by the program, they need to be converted into
binary <i>resource bundle</i> files using ICU's <code>genrb</code> program
Before these files can be used by the program, they need to be converted into
binary <i>resource bundle</i> files using ICU's <code>genrb</code> program
(which is in <code>usr/bin</code>, and is called by the Makefile).
<h1>Modifying an existing language</h1>
<ul>
<li>Edit the text file (e.g.,
<li>Edit the text file (e.g.,
<code>products/gLiveSupport/var/es_GT.txt</code>).</li>
<li>Run <code>make</code> in <code>products/gLiveSupport</code>.</li>
</ul>
@ -47,13 +47,13 @@ binary <i>resource bundle</i> files using ICU's <code>genrb</code> program
<h1>Adding a new language</h1>
<ul>
<li>Add the new text file to <code>products/gLiveSupport/var</code>.
(See the
(See the
<a href="http://icu.sourceforge.net/userguide/localizing.html#ICU4C">ICU
user guide</a> for the format of this file.)<br>
The first row of the file should be the locale name, followed by
":table". The locale name is of the form
<code>&lt;language-code&gt;[[_&lt;country-code&gt;]_&lt;variant&gt;]</code>,
where
where
<ul>
<li><code>&lt;language-code&gt;</code> is the
<a href="http://www.loc.gov/standards/iso639-2/langcodes.html">ISO 639-1</a>
@ -67,15 +67,15 @@ binary <i>resource bundle</i> files using ICU's <code>genrb</code> program
Note that this is slightly different from the normal ISO standard:
ICU uses it_IT_EURO where the standard would be it_IT@euro.<br>
Make sure the file is in UTF-8 encoding, has Unix line breaks,
and does not have a
and does not have a
<a href="http://www.unicode.org/faq/utf_bom.html#BOM">BOM</a>
character at the beginning.<br>
The file name should be the locale name, followed by ".txt".
<li>Add a new line for the new language in each of the files
<ul>
<li><code>gLiveSupport.xml</code></li>
<li><code>gLiveSupport.xml.template</code></li>
<li><code>gLiveSupport.xml.user-template</code></li>
<li><code>campcaster-studio.xml</code></li>
<li><code>campcaster-studio.xml.template</code></li>
<li><code>campcaster-studio.xml.user-template</code></li>
<li><code>Makefile.in</code></li>
</ul>
in the <code>products/gLiveSupport/etc</code> directory.</li>

28
campcaster/doc/userLocalizationInstructions.html
View File

@ -2,12 +2,12 @@
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type">
<title>LiveSupport user localization instructions</title>
<title>Campcaster user localization instructions</title>
<meta content="$Author$" name="author">
</head>
<body>
<h1>Preface</h1>
This document is part of the <a href="http://livesupport.campware.org/">LiveSupport</a>
This document is part of the <a href="http://campcaster.campware.org/">Campcaster</a>
project, Copyright © 2004 <a href="http://www.mdlf.org/">Media
Development Loan Fund</a>, under the GNU <a
href="http://www.gnu.org/licenses/gpl.html">GPL</a>.<br>
@ -18,15 +18,15 @@ Development Loan Fund</a>, under the GNU <a
</ul>
<h1>Scope</h1>
This document is written to help non-developers translate the LiveSupport
This document is written to help non-developers translate the Campcaster
software into new languages.<br>
<h1>Introduction</h1>
LiveSupport has two user interfaces: a web interface, intended mainly for
Campcaster has two user interfaces: a web interface, intended mainly for
radio station administrators (Station), and a stand-alone graphical user
interface, for disk jockeys and such (Studio).<br>
<h1>Localization of LiveSupport Station</h1>
<h1>Localization of Campcaster Station</h1>
Please do the localization at
<p><a href="http://ls-dev.campware.org/~sebastian/htmlUI/var/localizer/"><code>http://ls-dev.campware.org/~sebastian/htmlUI/var/localizer/</code></a></p>
<p>(user name is "root", and the password is "q"). When done, send a notice to
@ -34,31 +34,31 @@ the <a href="http://sympa.mdlf.org/wws/info/livesupport-dev">developers' mailing
list</a>.</p>
<font size="-1">
<p>If you must do the localization offline for some reason, please
<p>If you must do the localization offline for some reason, please
<ul>
<li>check out the latest files from CVS</li>
<li>log on to the local localizer at
<code>http://YOURSERVER/livesupport/localizer</code></li>
<code>http://YOURSERVER/campcaster/localizer</code></li>
<li>send the changed <code>locals.??_??.xml</code> file(s) from the folders
<ul>
<li><code><livesupport-cvs>/modules/htmlUI/var/</code> and</li>
<li><code><livesupport-cvs>/modules/htmlUI/var/localizer/</code></li>
<li><code><campcaster-cvs>/modules/htmlUI/var/</code> and</li>
<li><code><campcaster-cvs>/modules/htmlUI/var/localizer/</code></li>
</ul>
to the <a href="http://sympa.mdlf.org/wws/info/livesupport-dev">developers'
to the <a href="http://sympa.mdlf.org/wws/info/campcaster-dev">developers'
mailing list</a>.</li>
</ul>
</p>
</font>
<h1>Localization of LiveSupport Studio</h1>
<h1>Localization of Campcaster Studio</h1>
<p>
<ul>
<li>If editing an existing language: download the latest version of the
language file ??.txt or ??_??.txt from
<a href="http://code.campware.org/projects/livesupport/browser/trunk/livesupport/src/products/gLiveSupport/var/">this directory</a> (click on the file
<a href="http://code.campware.org/projects/campcaster/browser/trunk/campcaster/src/products/gLiveSupport/var/">this directory</a> (click on the file
name, scroll down to the bottom, right-click on Plain Text and choose
Save Target As or Save Link As, depending on your browser);
<p>if adding a new language: download <a href="http://code.campware.org/projects/livesupport/file/trunk/livesupport/src/products/gLiveSupport/var/root.txt?format=txt">the latest version of root.txt</a>;</li>
<p>if adding a new language: download <a href="http://code.campware.org/projects/campcaster/file/trunk/campcaster/src/products/gLiveSupport/var/root.txt?format=txt">the latest version of root.txt</a>;</li>
<li>edit the texts between the "..."s;</li>
<li>save it as a plain text file in UTF-8 encoding.
Please do not send Word documents or files in other encodings.</li>