From 174f9798da6bd486219fed971c0a0abe432df693 Mon Sep 17 00:00:00 2001 From: paul Date: Wed, 25 Oct 2006 20:11:59 +0000 Subject: [PATCH] Renamed LiveSupport to Campcaster, for ticket #1883 --- .../autoconfConfigureConventions.html | 6 +- .../buildEnvironment.html | 18 +-- .../cxxHeaderFileConventions.html | 26 ++-- .../cxxSourceFileConventions.html | 12 +- .../directoryStructure.html | 50 +++---- .../fileConventions.html | 8 +- .../htmlFileConventions.html | 10 +- .../doc/developmentEnvironment/index.html | 16 +-- .../developmentEnvironment/installation.html | 12 +- .../makefileConventions.html | 12 +- .../phpFileConventions.html | 20 +-- .../shellScriptConventions.html | 6 +- .../templates/htmlDocumentTemplate.html | 2 +- campcaster/doc/developmentTools.html | 16 +-- campcaster/doc/gettingStarted.html | 88 ++++++------- campcaster/doc/gui/designs/index.html | 2 +- campcaster/doc/index.html | 14 +- campcaster/doc/install.html | 92 ++++++------- campcaster/doc/manual/index.html | 124 +++++++++--------- .../doc/model/Authentication/index.html | 8 +- campcaster/doc/model/LocalStorage/index.html | 50 +++---- campcaster/doc/model/MediaArchive/index.html | 8 +- .../doc/model/PlaylistEditor/index.html | 8 +- campcaster/doc/model/Scheduler/index.html | 16 +-- .../doc/model/SoftwareArchitecture/index.html | 15 +-- campcaster/doc/model/index.html | 32 ++--- campcaster/doc/quickstart/index.html | 18 +-- campcaster/doc/release.html | 50 +++---- campcaster/doc/studioLocalization.html | 32 ++--- .../doc/userLocalizationInstructions.html | 28 ++-- 30 files changed, 399 insertions(+), 400 deletions(-) diff --git a/campcaster/doc/developmentEnvironment/autoconfConfigureConventions.html b/campcaster/doc/developmentEnvironment/autoconfConfigureConventions.html index 6c092eee4..22aaa5cfc 100644 --- a/campcaster/doc/developmentEnvironment/autoconfConfigureConventions.html +++ b/campcaster/doc/developmentEnvironment/autoconfConfigureConventions.html @@ -7,7 +7,7 @@

Preface

-This document is part of the LiveSupport +This document is part of the Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.
@@ -18,10 +18,10 @@ Development Loan Fund, under the GNU

Scope

This document describes the autoconf configure file conventions for the -LiveSupport +Campcaster project. See also the generic description of the file -conventions in the LiveSupport +conventions in the Campcaster project.

Introduction

Autoconf configure input files are processed by GNU - - + + - - - - + + + + Build environment @@ -23,7 +23,7 @@

Preface

-This document is part of the LiveSupport +This document is part of the Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.
@@ -38,7 +38,7 @@ Development Loan Fund, under the GNU LiveSupport +This document is part of the Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.
@@ -18,10 +18,10 @@ Development Loan Fund, under the GNU

Scope

This document describes C++ header file conventions for the -LiveSupport +Campcaster project. See also the generic description of the file -conventions in the LiveSupport +conventions in the Campcaster project.

Introduction

C++ header files are files containing declarations of structures, @@ -32,7 +32,7 @@ based files, thus they should adhere to the generic text-based conventions.

-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:
#include "Foo.h"
the identity macro is defined as Foo_h. For a header file that is expected to be included as:
-
#include "LiveSupport/Foo/Bar.h"
-the identity macro is defined as LiveSupport_Foo_Bar_h.
+
#include "Campcaster/Foo/Bar.h"
+the identity macro is defined as Campcaster_Foo_Bar_h.

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).

Sample

A sample for a C++ header file header follows, where the file itself -would be expected to be included as "LiveSupport/Foo/Bar.h".
+would be expected to be included as "Campcaster/Foo/Bar.h".

-
/*------------------------------------------------------------------------------

    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$
                                                                                
------------------------------------------------------------------------------*/
#ifndef LiveSupport_Foo_Bar_h
#define LiveSupport_Foo_Bar_h
                                                                                
#ifndef __cplusplus
#error This is a C++ include file
#endif

+
/*------------------------------------------------------------------------------

    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$
                                                                                
------------------------------------------------------------------------------*/
#ifndef Campcaster_Foo_Bar_h
#define Campcaster_Foo_Bar_h
                                                                                
#ifndef __cplusplus
#error This is a C++ include file
#endif

Include files & namespace

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.

-After the includes, namespace definitions follow. Each LiveSupport -object is contained in its own namespace inside the LiveSupport +After the includes, namespace definitions follow. Each Campcaster +object is contained in its own namespace inside the Campcaster namespace, thus this is a nested namespace declaration.

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.

Sample

A sample include files & namespaces section follows.
-
/* =============================================== include files & namespaces */

#ifdef HAVE_CONFIG_H
#include "configure.h"
#endif

#if HAVE_STDLIB_H
#include <stdlib.h>
#else
#error need stdlib.h
#endif

#include <string>


namespace LiveSupport {
namespace Foo {

using namespace LiveSupport::Core;

+
/* =============================================== include files & namespaces */

#ifdef HAVE_CONFIG_H
#include "configure.h"
#endif

#if HAVE_STDLIB_H
#include <stdlib.h>
#else
#error need stdlib.h
#endif

#include <string>


namespace Campcaster {
namespace Foo {

using namespace Campcaster::Core;

Constants

The constants section contains static constant values defined in the header file. @@ -189,7 +189,7 @@ identity macro #ifdef section opened in the header.

Sample

A sample footer section follows.

-
} // namespace Foo
} // namespace LiveSupport

#endif // LiveSupport_Foo_Bar_h
+
} // namespace Foo
} // namespace Campcaster

#endif // Campcaster_Foo_Bar_h

Template

See a template C++ header file. You may freely copy this diff --git a/campcaster/doc/developmentEnvironment/cxxSourceFileConventions.html b/campcaster/doc/developmentEnvironment/cxxSourceFileConventions.html index 42dbc01e2..63d0131f1 100644 --- a/campcaster/doc/developmentEnvironment/cxxSourceFileConventions.html +++ b/campcaster/doc/developmentEnvironment/cxxSourceFileConventions.html @@ -7,7 +7,7 @@

Preface

-This document is part of the LiveSupport +This document is part of the Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.
@@ -18,10 +18,10 @@ Development Loan Fund, under the GNU

Scope

This document describes C++ source file conventions for the -LiveSupport +Campcaster project. See also the generic description of the file -conventions in the LiveSupport +conventions in the Campcaster project.

Introduction

C++ source files are files containing implementations of functions and @@ -30,7 +30,7 @@ based files, thus they should adhere to the generic text-based conventions.

-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.
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.

@@ -100,7 +100,7 @@ most specific, the last one being the namespace of the class this source file implements.

Sample

A sample include files & namespaces section follows.
-
/* =============================================== include files & namespaces */

#ifdef HAVE_CONFIG_H
#include "configure.h"
#endif

#if HAVE_STDLIB_H
#include <stdlib.h>
#else
#error need stdlib.h
#endif

#include <string>

#include <LiveSupport/Foo/Bar.h>


using namespace LiveSupport::Core;
using namespace LiveSupport::Foo;

+
/* =============================================== include files & namespaces */

#ifdef HAVE_CONFIG_H
#include "configure.h"
#endif

#if HAVE_STDLIB_H
#include <stdlib.h>
#else
#error need stdlib.h
#endif

#include <string>

#include <Campcaster/Foo/Bar.h>


using namespace Campcaster::Core;
using namespace Campcaster::Foo;

Local data structures

The constants section contains locally defined data structures, that diff --git a/campcaster/doc/developmentEnvironment/directoryStructure.html b/campcaster/doc/developmentEnvironment/directoryStructure.html index e100a3c0c..fdd63dd40 100644 --- a/campcaster/doc/developmentEnvironment/directoryStructure.html +++ b/campcaster/doc/developmentEnvironment/directoryStructure.html @@ -2,11 +2,11 @@ - + - - + + Directory structure @@ -16,7 +16,7 @@

Preface

-This document is part of the LiveSupport +This document is part of the Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.
@@ -27,7 +27,7 @@ Development Loan Fund, under the GNU autoconf-style configuring the whole LiveSupport project. This involves running configure in all tool, module and product directories, and creating a top-level Makefile.
+The top-level configure script takes care of autoconf-style configuring the whole Campcaster project. This involves running configure in all tool, module and product directories, and creating a top-level Makefile.

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.

Documentation directory

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.
@@ -146,7 +146,7 @@ Each module has the same directory structure, which is as follows:

-
moduleX
|-- configure
|-- bin
|-- etc
|-- include
|   `-- LiveSupport
|       `-- ModuleX
|-- lib
|-- src
|-- tmp
`-- var
+
moduleX
|-- configure
|-- bin
|-- etc
|-- include
|   `-- Campcaster
|       `-- ModuleX
|-- lib
|-- src
|-- tmp
`-- var

configure

@@ -166,12 +166,12 @@ All configuration files go here.
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 Foo.h -for ModuleX would be contained in the directory include/LiveSupport/ModuleX/Foo.h, +for ModuleX would be contained in the directory include/Campcaster/ModuleX/Foo.h, and would be included with the line:

-
#include "LiveSupport/ModuleX/Foo.h"
+
#include "Campcaster/ModuleX/Foo.h"

lib

@@ -180,9 +180,9 @@ by building the module. All external, third-party libraries used by this module should be installed into the ../../../usr/lib 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 liblivesupport_modulex.so, and thus would +would be named libcampcaster_modulex.so, and thus would be linked to with the linker option -L../../modules/moduleX/lib --llivesupport_modulex.
+-lcampcaster_modulex.

src

@@ -213,8 +213,8 @@ an include directory.

Tools structure

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.
+for either building or running the Campcaster system. These tools are +installable to the usr directory of the Campcaster directory tree.
Each tool has its own directory, where several versions of the same tool may reside. Thus the generic directory structure is as follows:
@@ -239,9 +239,9 @@ be contained in the etc directory.
The usr directory is similar to the /usr system directory on UNIX systems (see the Filesystem Hierarchy Standard). 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.

diff --git a/campcaster/doc/developmentEnvironment/fileConventions.html b/campcaster/doc/developmentEnvironment/fileConventions.html index 261afdfec..9013ce628 100644 --- a/campcaster/doc/developmentEnvironment/fileConventions.html +++ b/campcaster/doc/developmentEnvironment/fileConventions.html @@ -8,7 +8,7 @@

Preface

-This document is part of the LiveSupport +This document is part of the Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.
@@ -19,7 +19,7 @@ Development Loan Fund, under the GNU

Scope

This document describes the conventions used for files in the -LiveSupport project.
+Campcaster project.

Introduction

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:
The header of the file holds:

Scope

-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 file conventions in the LiveSupport + href="fileConventions.html">file conventions in the Campcaster project.

Introduction

-HTML pages written as part of the LiveSupport documentation should +HTML pages written as part of the Campcaster documentation should conform to either the HTML 4.01 Transitional or XHTML 1.0 Transitional specifications.
@@ -59,7 +59,7 @@ element for the HTML page:
This section holds the following specific text:

This document is part of the LiveSupport project, + href="http://campcaster.campware.org/">Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.

Scope

-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 file conventions in the LiveSupport + href="fileConventions.html">file conventions in the Campcaster project.

Introduction

PHP scripts are text-based files containing PHP class definitions and/or commands.
@@ -76,26 +76,26 @@ column wide partitioning delimiter enclosing the header.
 /*------------------------------------------------------------------------------
     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.

 Is much safer to use include_once or require_once, not the original versions
 of this statement.

diff --git a/campcaster/doc/developmentEnvironment/shellScriptConventions.html b/campcaster/doc/developmentEnvironment/shellScriptConventions.html
index 5f615fca6..4bf069e4e 100644
--- a/campcaster/doc/developmentEnvironment/shellScriptConventions.html
+++ b/campcaster/doc/developmentEnvironment/shellScriptConventions.html
@@ -7,7 +7,7 @@
 
 
 
Preface

-This document is part of the LiveSupport
+This document is part of the Campcaster
 project, Copyright © 2004 Media
 Development Loan Fund, under the GNU GPL.

@@ -18,10 +18,10 @@ Development Loan Fund, under the GNU 
 
Scope

 This document describes the shell script file conventions for the
-LiveSupport
+Campcaster
 project. See also the generic description of the file
-conventions in the LiveSupport
+conventions in the Campcaster
 project.

 
Introduction

 Shell scripts are text-based executable shell command files. As text
diff --git a/campcaster/doc/developmentEnvironment/templates/htmlDocumentTemplate.html b/campcaster/doc/developmentEnvironment/templates/htmlDocumentTemplate.html
index 1d86688ab..b3d8f282f 100644
--- a/campcaster/doc/developmentEnvironment/templates/htmlDocumentTemplate.html
+++ b/campcaster/doc/developmentEnvironment/templates/htmlDocumentTemplate.html
@@ -8,7 +8,7 @@
 
 
 
Preface

-This document is part of the LiveSupport
+This document is part of the Campcaster
 project, Copyright © 2004 Media
 Development Loan Fund, under the GNU GPL.

diff --git a/campcaster/doc/developmentTools.html b/campcaster/doc/developmentTools.html
index b79afbe48..e4dac8a48 100644
--- a/campcaster/doc/developmentTools.html
+++ b/campcaster/doc/developmentTools.html
@@ -2,12 +2,12 @@
 
 
   
-  LiveSupport developer tools
+  Campcaster developer tools
   
 
 
 
Preface

-This document is part of the LiveSupport
+This document is part of the Campcaster
 project, Copyright © 2004 Media
 Development Loan Fund, under the GNU GPL.

@@ -18,9 +18,9 @@ Development Loan Fund, under the GNU 
 
Scope

 This document lists the development tools that are expected to be on a
-system that intends to compile and develop LiveSupport.

+system that intends to compile and develop Campcaster.

 
Introduction

-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.

@@ -60,7 +60,7 @@ environment variable WANT_AUTOCONF_2_5="1" before compiling the tools.)
 
Libraries

 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 libpng and 
+libpng, you might need to install the libpng and
 libpng-dev packages.  The package names vary by distribution.)
 

 
Required libraries

@@ -91,10 +91,10 @@ system:

 
 
 
Recommended libraries

-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.

 
    
   
  • boost >= 1.33.1
    • 
diff --git a/campcaster/doc/gettingStarted.html b/campcaster/doc/gettingStarted.html
index 0259093b0..fc6199b9c 100644
--- a/campcaster/doc/gettingStarted.html
+++ b/campcaster/doc/gettingStarted.html
@@ -2,12 +2,12 @@
 
 
   
-  Getting started with the LiveSupport development environment
+  Getting started with the Campcaster development environment
   
 
 
 
    Preface
    
-This document is part of the LiveSupport
+This document is part of the Campcaster
 project, Copyright © 2004 Media
 Development Loan Fund, under the GNU GPL.
    
@@ -17,23 +17,23 @@ Development Loan Fund, under the GNU Location: $URL$
 

 
Scope

-This document describes how to set up the LiveSupport development
+This document describes how to set up the Campcaster development
 environment.

 
 
Introduction

-LiveSupport uses a well-defined development environment.
-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.

+used to develop Campcaster as well.

 

 There is a simplified and Ubuntu-centric version of this document in the
-
-LiveSupport Trac wiki.
+
+Campcaster Trac wiki.
 
 
Steps

 

-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.

 
    
   
  • install development tools
    
@@ -42,25 +42,25 @@ development environment.
    
   
  • check out the sources
    • 
   
  • configure the environment
    
   
    • 
-  
  • set up tools used by LiveSupport
    • 
+  
  • set up tools used by Campcaster
    • 
   
  • personalize your development environment
    
   
    • 
 

 
Install development tools

-Install all the tools needed for the development of LiveSupport. Please
+Install all the tools needed for the development of Campcaster. Please
 see the development tools document
 for a list of tools needed.

 
Set up additional system resources

-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.

 
Test database

 

 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.

+applications within the Campcaster development environment.

 

-First, LiveSupport expects a PostgreSQL
+First, Campcaster expects a PostgreSQL
 database, and an ODBC
 Data Source accessible to it through unixODBC.
 Please refer to the documentation of these tools to set them up.

@@ -77,7 +77,7 @@ are enabled by default. If you are using an older version, do the following:
 

 
tcpip_socket = true

 

-    
  •  and also edit pg_hba.conf (usually 
+    
  •  and also edit pg_hba.conf (usually
     /var/lib/postgres/data/pg_hba.conf)
     to include the following line, before other lines related to access
     through localhost:
    
@@ -91,7 +91,7 @@ restart the postgresql daemon.
    
 
 
    Web server
    
 
    
-Second, LiveSupport expects:
+Second, Campcaster expects:
 
      
   
    • Apache httpd server
 running on the development computer
      • 
@@ -113,41 +113,41 @@ called www-data.
 
 
      Apache configuration
      
 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 AllowOverride directive in the 
+To enable them, find the configuration file for the userdir module of
+apache, and change the AllowOverride directive in the
 <Directory /home/*/public_html> section to All.
 

      
 
 
      Check out the sources
      
-The LiveSupport development directory tree can be accessed anonymously via
+The Campcaster development directory tree can be accessed anonymously via
 Subversion, at
-svn+ssh://code.campware.org/home/svn/repo/livesupport/trunk/livesupport.
+svn+ssh://code.campware.org/home/svn/repo/campcaster/trunk/campcaster.
 The following Subversion command
 would check out the development tree:

      
-
      svn checkout svn+ssh://code.campware.org/home/svn/repo/livesupport/trunk/livesupport

      
-This will check out and create the LiveSupport development svn checkout svn+ssh://code.campware.org/home/svn/repo/campcaster/trunk/campcaster

    • +This will check out and create the Campcaster development     directory structure.

    Configure the environment

    First, you need to create the database and ODBC data source used by -LiveSupport. This is done most easily by running the script -livesupport/bin/user_setup_db.sh. -Run the scripts as root, and provide your user name with the +Campcaster. This is done most easily by running the script +campcaster/bin/user_setup_db.sh. +Run the scripts as root, and provide your user name with the --user option: 
    
-cd livesupport
+cd campcaster
 sudo ./bin/user_setup_db.sh --user=<ls_developer_user>

    The script will set up the following resources:

    Scope

    -This document collects LiveSupport developer documentation, both +This document collects Campcaster developer documentation, both generated and handwritten.

    Introduction

    -The links below provide useful documentation for the LiveSupport +The links below provide useful documentation for the Campcaster developer.

    Static documentation

    @@ -32,11 +32,11 @@ developer.

    Developer documentation

    Scope

    -This document describes how to compile and install LiveSupport on your +This document describes how to compile and install Campcaster on your system.

    Introduction

    -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:
    • installing required compilation tools
    • installing and configuring required external services
      • -
    • obtaining LiveSupport sources
      • -
    • compiling LiveSupport
      • -
    • installing LiveSupport
      • +
    • obtaining Campcaster sources
      • +
    • compiling Campcaster
      • +
    • installing Campcaster
    • try it out

    For the impatient

    Those who think they know everything, the quick steps to install -LiveSupport are the following. (To run make, you need write +Campcaster are the following. (To run make, you need write permissions in the prefix directory; to run make install and postInstallStation.sh, you need to be root.) 
    
-wget http://switch.dl.sourceforge.net/sourceforge/livesupport/livesupport-<version>.tar.bz2
-wget http://switch.dl.sourceforge.net/sourceforge/livesupport/livesupport-libraries-<version>.tar.bz2
-tar xfj livesupport-<version>.tar.bz2
-tar xfj livesupport-libraries-<version>.tar.bz2
-cd livesupport-<version>
-./configure --prefix=/usr/local/livesupport --with-apache-group=apache --with-www-docroot=/var/www
+wget http://switch.dl.sourceforge.net/sourceforge/campcaster/campcaster-<version>.tar.bz2
+wget http://switch.dl.sourceforge.net/sourceforge/campcaster/campcaster-libraries-<version>.tar.bz2
+tar xfj campcaster-<version>.tar.bz2
+tar xfj campcaster-libraries-<version>.tar.bz2
+cd campcaster-<version>
+./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
    -Then try the URL http://localhost/livesupport/ +Then try the URL http://localhost/campcaster/ and log in using username: root, password: q.

    Everyone else, please read the lines below carefully.
    @@ -63,11 +63,11 @@ them from the URLs listed, and compile them yourself (follow the instructions included with each tool and library).

    Installing and configuring required external services

    -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).

    Database

    -LiveSupport expects a     PostgreSQL +Campcaster expects a PostgreSQL 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.
    @@ -89,7 +89,7 @@ to include the following line, before any other lines starting with "host":
    These changes will make sure that the PostgreSQL database is accessible via TCP/IP from localhost.

    Web server

    -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:


    @@ -455,7 +455,7 @@ Navigation Menu consists of the following functions:

    Clicking on the ‘Live Mode’ button in the Navigation Menu opens up a new palette on -the screen below the Master Panel. +the screen below the Master Panel.


    @@ -468,11 +468,11 @@ contains:

  • preview (cue) buttons – play/pause and stop button – gives users the option of pre-listening to audio files before - playing them on air. + playing them on air.

  • Space under the preview and play buttons is set to contain the list of audio - slots (playlists, single files…) created by the user . + slots (playlists, single files…) created by the user .


    @@ -569,7 +569,7 @@ advertising blocks and have a pre-determined time for broadcast.

    than can simply upload the complete advert playlist from the sales department, instead of inserting ads file by file.

    -

    1.6 +

    1.6 Upload file


    @@ -601,7 +601,7 @@ Upload file

    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.

    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:

  • Main, Music and Talk tabs – where metadata information (such as the information stored in an MP3 file's ID3 tags) can be added or - edited. + edited.

  • The Main tab is the default @@ -650,7 +650,7 @@ palette consists of the following elements:


    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.

    • @@ -706,7 +706,7 @@ it appears at the top of the ScratchPad list).


      -

      As in LiveSupport +

      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…) you find necessary for creating your program. The @@ -721,16 +721,16 @@ palette. It consists of the following elements:

      buttons – play/pause and stop button - gives you the option of pre-listening and quick-checking audio files before using them in Live Mode or a playlist.

      -

    • The Type column – +

    • The Type column – contains icons indicating the type of item you are working with. An - icon's appearance is the same as in LiveSupport Station – + icon's appearance is the same as in Campcaster Station – audioclips are marked with a green note, playlists with a red note, and webstreams with a blue transmission symbol.

    • The Title column – displays the title of the items (audioclips, playlists, webstreams)

    • Add to playlist 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.

    • Clear list button – deletes all items from the ScratchPad

      @@ -762,7 +762,7 @@ the audioclips and playlists):

    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:

    • Edit @@ -809,7 +809,7 @@ playlist, additional actions offered will include:

      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.

      This function allows you to execute various operations such as:

      @@ -830,10 +830,10 @@ to the active or new empty playlist by:

      • right- clicking on the item (either a sound file or playlist) in the - ScratchPad and + ScratchPad and

      • selecting Add - to playlist. + to playlist.



      @@ -845,7 +845,7 @@ by:

    • right-clicking on the playlist in the ScratchPad and

    • selecting Edit - from the popup menu + from the popup menu

    The @@ -860,10 +860,10 @@ Playlists palette will then appear, displaying:

    file, starting from zero. Start time for the next item is calculated automatically.

  • The Title - column displays names of the files, playlists or streams. + column displays names of the files, playlists or streams.

  • The Length - column lists the duration of each item + column lists the duration of each item

  • The Fade in and Fade out column displays the increasing/decreasing curve @@ -885,7 +885,7 @@ field remains blank.

    • The Save button - enables you to save all your changes and your work. + enables you to save all your changes and your work.

    @@ -925,7 +925,7 @@ palette allows you to automate (schedule) your playlist for broadcast at a predefined date and time.

    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:

    • Monthly @@ -950,10 +950,10 @@ will be available in the ScratchPad and can be added to the Scheduler by:

      • - right- clicking on the saved playlist in the ScratchPad and + right- clicking on the saved playlist in the ScratchPad and

      • selecting - Schedule option from the popup menu. + Schedule option from the popup menu.

      That @@ -983,15 +983,15 @@ scheduled playlist in the table and selecting Delete. 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.

      -

      1.10 +

      1.10 Search

      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.

      The main part of the Search palette are tabs that gives you the option to @@ -1034,7 +1034,7 @@ and webstreams.

      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 -Search button. +Search button.

      In the simple search option, the search process is based on keywords @@ -1062,7 +1062,7 @@ Advanced Search

      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.

      Advanced Search tab contains the following elements:

      • - Search field with three types of criteria in one row; + Search field with three types of criteria in one row;

      • 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).

      • The middle pulldown menu enables you to refine your search by selecting @@ -1091,7 +1091,7 @@ Advanced Search tab contains the following elements:

        located on the right allows you to add extra sets of criteria by 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.

      @@ -1118,11 +1118,11 @@ precise and narrow your search results.



      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.

      The browsing process is divided into three columns with the same list of @@ -1136,7 +1136,7 @@ offered criteria.

      category, the pulldown menu of the second column allows you to choose one of the options that appear in the chosen category, which refines the number of displayed - files. + files.

    • The third column works the same way and lets you continue refining @@ -1151,7 +1151,7 @@ file quickly among the thousands of files in the server.

      you choose simple Search, Advanced search or Browse option, the search results will appear at the bottom of the palette in the table containing Type, Title, Creator and Length of the resulting -file. +file.

      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:

      2. Additional information

      2.1 Where to go for more help

      You -can visit LiveSupport's discussion forums online at -http://livesupport.campware.org. +can visit Campcaster's discussion forums online at +http://campcaster.campware.org. There you will also find program updates and other useful information.


      2.2 How to report bugs

      -

      LiveSupport +

      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 http://code.campware.org/projects/livesupport. -That way, the LiveSupport team can keep track of your problem and you +trouble ticket at http://code.campware.org/projects/campcaster. +That way, the Campcaster team can keep track of your problem and you can check to see whether it has been fixed.

      \ No newline at end of file diff --git a/campcaster/doc/model/Authentication/index.html b/campcaster/doc/model/Authentication/index.html index 421ebf15f..23183745c 100644 --- a/campcaster/doc/model/Authentication/index.html +++ b/campcaster/doc/model/Authentication/index.html @@ -3,12 +3,12 @@ - LiveSupport Authentication specification - + Campcaster Authentication specification +

      Preface

      -This document is part of the LiveSupport +This document is part of the Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.
      @@ -18,7 +18,7 @@ Development Loan Fund, under the GNU Location: $URL$

    Scope

    -This document contains the specification of the LiveSupport +This document contains the specification of the Campcaster Authentication component.

    This document contains embedded     - LiveSupport Local storage specification - + Campcaster Local storage specification +

    Preface

    -This document is part of the     LiveSupport +This document is part of the Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.
    @@ -18,7 +18,7 @@ Development Loan Fund, under the GNU Location: $URL$

    • Scope

    -This document contains the specification of the LiveSupport Local +This document contains the specification of the Campcaster Local storage component.

    This document contains embedded     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.

    System functions

    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. purpose - To modify an existing Playlist in the local + To modify an existing Playlist in the local storage
    @@ -1124,7 +1124,7 @@ storage
    overview 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.
    @@ -1172,8 +1172,8 @@ and grants access
    5.
    - The system verifies that there is a Playlist -in the Local storage with the given ID, and it is not currently + The system verifies that there is a Playlist +in the Local storage with the given ID, and it is not currently being edited
    @@ -1184,7 +1184,7 @@ being edited
    6.
    - The system marks the Playlist with the given ID + The system marks the Playlist with the given ID as being edited
    @@ -1228,8 +1228,8 @@ Playlist earlier
    11.
    - The system stores the new Playlist metafile in -place of the old one, marks it as no longer being edited, + 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
    @@ -1261,7 +1261,7 @@ and notifies the Storage maintainer of the actions taken
  • action 3: if the Storage maintainer can not be authenticated, she is notified, and the use case ends.
  • action 5: 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.
  • action 10: 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.
    • overview 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.
    @@ -1344,7 +1344,7 @@ Playlist to be deleted
    5.
    - The system verifies that there is a Playlist + The system verifies that there is a Playlist in the Local storage with the given ID, and it is not currently being edited
    @@ -1389,7 +1389,7 @@ and notifies the Storage maintainer of the action taken
  • action 3: if the Storage maintainer can not be authenticated, she is notified, and the use case ends.
  • action 5: 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.

    • @@ -1417,14 +1417,14 @@ the user is notified and the use case ends. purpose - To access a Playlist metafile in order to + To access a Playlist metafile in order to execute (play) it
    overview 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.
    @@ -1623,7 +1623,7 @@ extra (fade in / fade out) information
    Token
    - An identifier used to match the parts of two-part + An identifier used to match the parts of two-part operations, e.g., access--release or edit--save
    @@ -2726,7 +2726,7 @@ being edited, report as an error
    Output
    - a URL of a Playlist + a URL of a Playlist metafile, and a token identifying it
    @@ -2812,7 +2812,7 @@ the newPlaylist argument looks like
    Exceptions
    - if the playlistToken argument + if the playlistToken argument does not match a token generated earlier in this session by editPlaylist(), report as an error
    @@ -2996,7 +2996,7 @@ given playlistId exists, report as an error
    Output
    - a URL of a Playlist + a URL of a Playlist metafile, and a token identifying it
    @@ -3072,7 +3072,7 @@ obtained earlier by accessPlaylist().
    Exceptions
    - if the playlistToken argument + if the playlistToken argument does not match a token generated earlier in this session by accessPlaylist(), report as an error
    @@ -3306,7 +3306,7 @@ given audioClipId exists, report as an error
    Output
    - a URL of an AudioClip + a URL of an AudioClip metafile, and a token identifying it
    @@ -3382,7 +3382,7 @@ obtained earlier by accessAudioClip().
    Exceptions
    - if the audioClipToken argument + if the audioClipToken argument does not match a token generated earlier in this session by accessAudioClip(), report as an error
    diff --git a/campcaster/doc/model/MediaArchive/index.html b/campcaster/doc/model/MediaArchive/index.html index eed29fc80..326c1c9d5 100644 --- a/campcaster/doc/model/MediaArchive/index.html +++ b/campcaster/doc/model/MediaArchive/index.html @@ -3,12 +3,12 @@ - LiveSupport Media archive specification - + Campcaster Media archive specification +

    Preface

    -This document is part of the     LiveSupport +This document is part of the Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.
    @@ -18,7 +18,7 @@ Development Loan Fund, under the GNU Location: $URL$

    Scope

    -This document contains the specification of the LiveSupport Media +This document contains the specification of the Campcaster Media archive component.

    This document contains embedded     - LiveSupport Playlist editor specification - + Campcaster Playlist editor specification +

    Preface

    -This document is part of the     LiveSupport +This document is part of the Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.
    @@ -18,7 +18,7 @@ Development Loan Fund, under the GNU Location: $URL$

    Scope

    -This document contains the specification of the LiveSupport Playlist +This document contains the specification of the Campcaster Playlist editor component.

    This document contains embedded     - LiveSupport Scheduler specifications - + Campcaster Scheduler specifications +

    Preface

    -This document is part of the     LiveSupport +This document is part of the Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.
    @@ -18,7 +18,7 @@ Development Loan Fund, under the GNU Location: $URL$

    Scope

    -This document contains the specification of the LiveSupport Scheduler +This document contains the specification of the Campcaster Scheduler daemon.

    This document contains embedded     Requirements

    Overview

    -The purpose of the LiveSupport Scheduler daemon is to execute +The purpose of the Campcaster Scheduler daemon is to execute playlists.

    Goals

    @@ -2832,7 +2832,7 @@ editing
    Notes
    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.
    @@ -3263,8 +3263,8 @@ is at a given relative offset.
    Exceptions
    - If there is no Audio clip -with a start time at the given relative offset in the playlist, indicate + If there is no Audio clip +with a start time at the given relative offset in the playlist, indicate as an error.
    diff --git a/campcaster/doc/model/SoftwareArchitecture/index.html b/campcaster/doc/model/SoftwareArchitecture/index.html index f0eb18e16..2dd90bab3 100644 --- a/campcaster/doc/model/SoftwareArchitecture/index.html +++ b/campcaster/doc/model/SoftwareArchitecture/index.html @@ -3,12 +3,11 @@ - LiveSupport Software Architecture - + Campcaster Software Architecture

    Preface

    -This document is part of the     LiveSupport +This document is part of the Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.
    @@ -18,7 +17,7 @@ Development Loan Fund, under the GNU Location: $URL$

    Scope

    -This document describes the software architecture of LiveSupport.
    +This document describes the software architecture of Campcaster.

    This document contains embedded     SVG figures, thus an SVG @@ -42,13 +41,13 @@ The software architecture for the Playlist Editor:
    A brief summary of the software components appearing in the figures above:

    Scheduler

    -The LiveSupport Scheduler, responsible for executing playlists.
    +The Campcaster Scheduler, responsible for executing playlists.

    Playlist editor

    -The LiveSupport Playlist editor, a graphical user interface component.
    +The Campcaster Playlist editor, a graphical user interface component.

    Media Archive

    -The LiveSupport Media Archive component.
    +The Campcaster Media Archive component.

    Local storage

    -The LiveSupport Local Storage component.
    +The Campcaster Local Storage component.

    Helix Client Library

    A media library developed by the Helix Community and Real Networks. diff --git a/campcaster/doc/model/index.html b/campcaster/doc/model/index.html index 9fb3cae83..4cde1aa33 100644 --- a/campcaster/doc/model/index.html +++ b/campcaster/doc/model/index.html @@ -3,12 +3,12 @@ - LiveSupport Architecture - + Campcaster Architecture +

    Preface

    -This document is part of the LiveSupport +This document is part of the Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.
    @@ -18,7 +18,7 @@ Development Loan Fund, under the GNU Location: $URL$

    Scope

    -This document describes the architecture of LiveSupport.
    +This document describes the architecture of Campcaster.

    This document contains embedded     SVG figures, thus an SVG @@ -54,13 +54,13 @@ The Playlist editor component is the user interface tool to create playlists.

    Feature - component mapping

    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.
    -

    LiveSupport Feature List

    -For convenience the features listed in section 3.3 of the LiveSupport +

    Campcaster Feature List

    +For convenience the features listed in section 3.3 of the Campcaster proposal are quoted below, with their original section numbers.

    3.3.1 Intuitive User Interface

    -

    LiveSupport will feature an +

    Campcaster will feature an easily-localizable and intuitive user interface that draws on the applicants’ extensive previous project experience.

    3.3.2 Storing Metadata

    @@ -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 – essential for spoken word productions, such as educational or news material.

    -

    LiveSupport will use existing open +

    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.

    3.3.3 Automation and Scheduling

    -

    LiveSupport will provide a scheduler, +

    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.

    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.

    3.3.5 Proof of Broadcast

    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.

    +and analyze logs created by individual Campcaster installations.

    3.3.6 Mixing Local Audio Sources

    -

    A producer running LiveSupport in a +

    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.

    3.3.7 Mixing Local and Remote Sources

    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’s hard disk), remote files (stored anywhere on the Internet) or include audio streams from the Internet as part of the local transmission – all of which could also become part of a playlist.

    3.3.8 Remote Control of Transmitter Locations

    A radio reporter/producer will be able -to remotely access all of LiveSupport’s scheduling features over +to remotely access all of Campcaster’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.

    Feature - component mapping

    diff --git a/campcaster/doc/quickstart/index.html b/campcaster/doc/quickstart/index.html index 2a7ef8908..5198a6219 100644 --- a/campcaster/doc/quickstart/index.html +++ b/campcaster/doc/quickstart/index.html @@ -18,7 +18,7 @@ -

    LiveSupport 1.0
    +

    Campcaster 1.0
    Demo and Install CD

    @@ -27,32 +27,32 @@  

    This CD is a bootable version of Linux for PCs that includes a demo version - of LiveSupport preinstalled.

    + of Campcaster preinstalled.

    To start, insert this CD into your CD-ROM drive and restart your computer.
    You will be prompted for a boot option. Type ‘knoppix’ and the enter key and the startup procedure will continue.

    The K Desktop environment (KDE), which is very similar to Windows, will appear. To - start the LiveSupport Studio application, click on its desktop icon.

    + start the Campcaster Studio application, click on its desktop icon.

    For both - LiveSupport Studio and web access, The username is ‘root,’ and + Campcaster Studio and web access, The username is ‘root,’ and the password is ‘q’ for the demo.

    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.

    In the - URL field, type: http://localhost/livesupport.

    + URL field, type: http://localhost/campcaster.

    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.

    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 http://livesupport.campware.org

    + at http://campcaster.campware.org

    diff --git a/campcaster/doc/release.html b/campcaster/doc/release.html index dc201fc01..b0ad6b2bb 100644 --- a/campcaster/doc/release.html +++ b/campcaster/doc/release.html @@ -2,12 +2,12 @@ - LiveSupport release process documentation + Campcaster release process documentation

    Preface

    -This document is part of the LiveSupport +This document is part of the Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.
    @@ -18,17 +18,17 @@ Development Loan Fund, under the GNU

    Scope

    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.

    Introduction

    -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.

    The release process boils down to the following steps:
      -
    • getting LiveSupport sources
      • +
    • getting Campcaster sources
    • checking the distribution script
    • updating release version and changelog
      • @@ -41,9 +41,9 @@ The release process boils down to the following steps:
    • announcing the release
    -

    Getting LiveSupport sources

    +

    Getting Campcaster sources

    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:
      @@ -51,10 +51,10 @@ exported, so as to insure that:
      control system
    • there are no generated files in the release
    -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:

    -
    svn export svn+ssh://<username>@code.campware.org/home/svn/repo/livesupport/trunk/livesupport
    +
    svn export svn+ssh://<username>@code.campware.org/home/svn/repo/campcaster/trunk/campcaster

    Where <username> is the user name for accessing the repository of the person making the release.
    @@ -79,10 +79,10 @@ is a mismatch between the release version and the topmost entry in the debian changelog file.

    Curently, only the debian changelog keeps track of the changes and the -version of LiveSupport. To update the changelog, edit etc/debian/changelog, +version of Campcaster. To update the changelog, edit etc/debian/changelog, by inserting a section onto the top of the file:

    -
    livesupport (<ls-version>-1) unstable; urgency=low

      * Changes listed here

     -- Package Maintainer <maintainer@foo.bar>  <timestamp>

    +
    campcaster (<ls-version>-1) unstable; urgency=low

      * Changes listed here

     -- Package Maintainer <maintainer@foo.bar>  <timestamp>

    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 date -R command. Please note that the debian package @@ -101,13 +101,13 @@ with the release version as its single parameter:

    This will create two tarballs in the current directory:
      -
    • livesupport-<ls-version>.tar.bz2
      • -
    • livesupport-libraries-<ls-version>.tar.bz2
      • +
    • campcaster-<ls-version>.tar.bz2
      • +
    • campcaster-libraries-<ls-version>.tar.bz2

    Testing the tarballs

    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     installation document.

    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:

    -
    tar xfj livesupport-<ls-version>.tar.bz2
    tar xfj livesupport-libraries-<ls-version>.tar.bz2
    cd livesupport-<ls-version>
    ./bin/createDebianPackages.sh -d .. -v <ls-version> -m "Package Maintainer <maintainer@foo.bar>" -o ..
    cd ..
    +
    tar xfj campcaster-<ls-version>.tar.bz2
    tar xfj campcaster-libraries-<ls-version>.tar.bz2
    cd campcaster-<ls-version>
    ./bin/createDebianPackages.sh -d .. -v <ls-version> -m "Package Maintainer <maintainer@foo.bar>" -o ..
    cd ..

    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:

    -
    livesupport_<ls-version>-1.dsc
    livesupport_<ls-version>-1.diff.gz
    livesupport_<ls-version>.orig.tar.gz

    +
    campcaster_<ls-version>-1.dsc
    campcaster_<ls-version>-1.diff.gz
    campcaster_<ls-version>.orig.tar.gz

    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.
    Building is best done in an empty directory as follows:

    -
    rm -rf /opt/livesupport
    rm -rf debian_build
    mkdir debian_build
    cd debian_build
    dpkg-source -x ../livesupport_<ls_version>-1.dsc
    cd livesupport-<ls-version>
    dpkg-buildpackage -rfakeroot
    cd ../..

    +
    rm -rf /opt/campcaster
    rm -rf debian_build
    mkdir debian_build
    cd debian_build
    dpkg-source -x ../campcaster_<ls_version>-1.dsc
    cd campcaster-<ls-version>
    dpkg-buildpackage -rfakeroot
    cd ../..

    The above commands will result in the following debian packages:

    -
    livesupport-libs_<ls-version>-1_<arch>.deb
    livesupport-station_<ls-version>-1_<arch>.deb
    livesupport-studio_<ls-version>-1_<arch>.deb
    +
    campcaster-libs_<ls-version>-1_<arch>.deb
    campcaster-station_<ls-version>-1_<arch>.deb
    campcaster-studio_<ls-version>-1_<arch>.deb

    Tagging the sources

    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:

    -
    svn copy svn+ssh://<username>@code.campware.org/home/svn/repo/livesupport/trunk/ \
-         svn+ssh://<username>@code.campware.org/home/svn/repo/livesupport/tags/livesupport-<ls-version>
    +
    svn copy svn+ssh://<username>@code.campware.org/home/svn/repo/campcaster/trunk/ \
+         svn+ssh://<username>@code.campware.org/home/svn/repo/campcaster/tags/campcaster-<ls-version>

    -This will tag the current state of the repository with the tag livesupport-<ls-version>, +This will tag the current state of the repository with the tag campcaster-<ls-version>, enabling later retrieval of this specific state.

    Updating Trac

    Add the new version number to the Version pull-down menu in Trac by executing -
    trac-admin /usr/local/trac-projects/livesupport version add <ls-version>
    +
    trac-admin /usr/local/trac-projects/campcaster version add <ls-version>
    on code.campware.org.

    Publishing the tarballs

    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: http://sourceforge.net/projects/livesupporthttp://sourceforge.net/projects/campcaster    . 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:
  • PRweb (http://www.prweb.com)
  • MDLF's press person
    • -
  • LiveSupport developers' list, urging everyone to send it to +
  • Campcaster developers' list, urging everyone to send it to friends and contacts
  • Other Campware developers' lists on major releases
  • Other mailing lists and friendly/relevant organizations
    • diff --git a/campcaster/doc/studioLocalization.html b/campcaster/doc/studioLocalization.html index 4db95dc3d..3cbc50acc 100644 --- a/campcaster/doc/studioLocalization.html +++ b/campcaster/doc/studioLocalization.html @@ -2,12 +2,12 @@ - LiveSupport documentation for LS Studio localization + Campcaster documentation for LS Studio localization

    Preface

    -This document is part of the LiveSupport +This document is part of the Campcaster project, Copyright © 2004 Media Development Loan Fund, under the GNU GPL.
    @@ -18,28 +18,28 @@ Development Loan Fund, under the GNU

    Scope

    -This document describes the process of adding a new language to the -LiveSupport Studio localization. It is written for developers.
    +This document describes the process of adding a new language to the +Campcaster Studio localization. It is written for developers.

    Introduction

    -LiveSupport Studio (a.k.a. the C++ GUI) uses IBM's +Campcaster Studio (a.k.a. the C++ GUI) uses IBM's     ICU library for localization. This library supports a fallback mechanism: if the locale is set to es_GT (Guatemalan Spanish), it first tries to read the es_GT table for localized strings; if there is no such table, -it tries the es table; and if that is missing, too, it reads the +it tries the es table; and if that is missing, too, it reads the root table.
    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 products/gLiveSupport/var directory with a txt extension: e.g., es_GT.txt. -Before these files can be used by the program, they need to be converted into -binary resource bundle files using ICU's genrb program +Before these files can be used by the program, they need to be converted into +binary resource bundle files using ICU's genrb program (which is in usr/bin, and is called by the Makefile).

    Modifying an existing language

      -
    • Edit the text file (e.g., +
    • Edit the text file (e.g., products/gLiveSupport/var/es_GT.txt).
    • Run make in products/gLiveSupport.
    @@ -47,13 +47,13 @@ binary resource bundle files using ICU's genrb program

    Adding a new language