mirror/JUCE
1
0
Fork 0
mirror of https://github.com/juce-framework/JUCE.git synced 2026-01-09 23:34:20 +00:00
Code Activity

Restructured folder and Updated Readme

Browse source
This commit is contained in:
Felix Faire 2014-11-12 17:18:18 +00:00
parent 8980ed2b9c
commit b01383e8d0
282 changed files with 6 additions and 753 deletions
Download patch file Download diff file Expand all files Collapse all files

220
docs/JUCE readme.html
View file

@ -1,220 +0,0 @@
<?xml version="1.0" encoding="windows-1250"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<meta http-equiv="Content-Language" content="en-us" />
<meta name="description" content="Raw Material Software" />
<meta name="keywords" content="audio, music, juce, tracktion, c++, sequencer, library, programming, software, julian storer$otherkeywords" />
<meta name="robots" content="index,follow" />
<title>JUCE - installation and compiling</title>
<link href="rawmat.css" rel="stylesheet" type="text/css" media="all" />
</head>
<body>
<div class="pageholder">
<div class="banner">
<a href="http://www.rawmaterialsoftware.com">
<img src="images/rms_logo.gif" alt="raw material software" title="raw material software"/></a>
</div>
<p><a href="#intro">Introduction</a> - <a href="#license">License</a> -
<a href="#install">Installation</a> -
<a href="#buildvc">Building with Visual Studio</a> -
<a href="#buildvc6">Building with VC6</a> -
<a href="#buildxcode">Building with XCode</a> -
<a href="#buildlinux">Building on Linux</a> -
<a href="#buildandroid">Building with Android</a> -
</p>
<h1>JUCE</h1>
<h2><a name="intro"></a>Introduction</h2>
<p>JUCE is an all-encompassing C++ class library for developing cross-platform applications and plugins.</p>
<p>For lots more help and information, please visit the <a href="http://www.rawmaterialsoftware.com/juce">JUCE website</a>.</p>
<p>A complete set of class documentation is available <a href="http://www.rawmaterialsoftware.com/juce/api/index.html" target="juce api">here</a>.</p>
<h2><a name="license"></a>License</h2>
<p>JUCE is released under the <a href="http://www.gnu.org/copyleft/gpl.html">Gnu Public License</a>,
which means it can be freely copied and distributed, and costs nothing to use in open-source applications.</p>
<p>If you'd like to release a closed-source application that uses JUCE, commercial licenses are available
for a fee - click <a href="http://www.rawmaterialsoftware.com/jucelicense.php">here</a> for more information
on pricing and terms.</p>
<h2><a name="install"></a>Installation</h2>
<h3>Installing the source code</h3>
<p>There are a few ways to install a copy of JUCE:</p>
<ul>
<li>You can download a zip file containing the last stable release from <a href="http://sourceforge.net/projects/juce/files/juce/">the JUCE downloads section on SourceForge</a></li>
<li>Download the GIT repository: To grab the latest bleeding-edge version of the code, you can use the command:
<br><code>git clone --depth 1 git://juce.git.sourceforge.net/gitroot/juce/juce</code></li>
<li>Download via the Introjucer: The Introjucer is JUCE's tool for creating and managing JUCE projects, and it also
includes a handy tool which lets you download the latest (bleeding-edge) version of JUCE without needing to install GIT. To use this,
just download a binary of the Introjucer from <a href="http://sourceforge.net/projects/juce/files/juce/">SourceForge</a>,
and run it - its 'update' menu contains an option to download JUCE.</li>
</ul>
<p>The JUCE source code all lives in a folder called, unsurprisingly, <code>juce</code>, which you can unzip
and put somewhere on your system.</p>
<h3>Building the demo applications</h3>
<p>In the <code>juce/extras</code> folder, there are a few demo apps to get you started and to show off JUCE's features.
Each one contains a folder called <code>Builds</code>, containing various projects for different compilers and platforms.
These should all work straight out-of-the-box if you load them into the appropriate development environment. Some of them
(e.g. the audio plugin demo) may require 3rd party libraries or headers to have been installed, but I've made sure that any
include statements that may not be present have comments with a detailed explanation of what's going on, so if you hit a compile
error, just have a look at the code it's pointing to and everything should become clear.</p>
<h2>Creating a new application with the Introjucer</h2>
<p>By far the easiest way to create a new cross-platform JUCE app (or audio plugin) is to let the Introjucer
do the hard work of creating all your projects with the correct settings.</p>
<p>You can either build the Introjucer yourself from the source (in <code>juce/extras/Introjucer</code>), or download
a pre-built binary from <a href="http://sourceforge.net/projects/juce/files/juce/">SourceForge</a>.
<p>If you run it and select the 'new project' menu item, it'll walk you through the stages in setting up an app or
plugin project, and will automatically spit out a collection of project files for all the different platforms and compilers
that you need.</p>
<h1>Requirements for building on different platforms</h1>
<h3><a name="buildvc"></a>Microsoft Visual Studio 2005 or later</h3>
<p>JUCE projects should build and run with no extra set-up needed in all versions of Visual Studio from 2005 onwards.</p>
<p>By far the easiest way to create a new project is by letting the Introjucer do all the hard work, as explained above. But
if you really insist on creating one manually, here are a few tips:</p>
<ol>
<li>Create your new application project as an 'empty' WIN32 application - avoid saying yes to
MFC or any of the other rubbish that Visual Studio might offer you.</li>
<li>Make sure that your project has exception handling and run-time type information (RTTI) turned ON.</li>
<li>Have a look at the example projects, demo projects, or the API documentation about the
<code>JUCEApplication</code> class to find out how to create the application launch code.</li>
</ol>
<h3><a name="buildvc6"></a>Microsoft Visual Studio 6</h3>
<p>JUCE can still be compiled with VC6, although support for this will be dropped at some point in the future...
but here are some tips for getting it going:</p>
<ol>
<li>Install the latest Platform SDK from Microsoft.</li>
<li>Set up your include and library search paths. The first few items on your include path
should look like this (obviously you might have things installed in different places, but the
order is important!):
<pre>C:\Program Files\Microsoft Platform SDK\include
C:\Program Files\Microsoft Platform SDK\include\crt
C:\Program Files\Microsoft Platform SDK\include\mfc
C:\mycode\juce
...</pre>
And the library search path should begin like this:
<pre>C:\Program Files\Microsoft Visual Studio\VC98\LIB
C:\Program Files\Microsoft Platform SDK\lib
C:\mycode\juce\bin
...</pre>
</li>
</ol>
<p>Note that there's a rather lame bug in VC6 that causes an internal compiler error if you include
filenames that are too long. This can get triggered if you put the juce folder in a deeply-nested
directory (such as your user home directory). Unfortunately I think the only workaround for this
is to move the source tree to a shallower directory.</p>
<h3><a name="buildxcode"></a>XCode on OSX</h3>
<p>Use XCode 3 or later. You might want to tick the option to install the 10.4 SDK if you want to build binaries
that are backward-compatible with 10.4 and PPCs. If you're going to build for iOS, you'll obviously need the iOS version of XCode.</p>
<p>The easiest way to create a new application is by using the Intojucer, but here are a few tips if you're mad enough
to want to set one up manually:</p>
<ul>
<li>You'll need to add some or all of the following OSX frameworks to your "External Frameworks and Libraries" list,
depending on what features your application uses:
<pre>Cocoa.framework
Carbon.framework
IOKit.framework
CoreAudio.framework
CoreMIDI.framework
WebKit.framework
DiscRecording.framework
QTKit.framework
QuickTime.framework
QuartzCore.framework
AudioUnit.framework
AudioToolbox.framework
OpenGL.framework
AppKit.framework
CoreAudioKit.framework
CoreFoundation.framework</pre>
In future there may be other frameworks that you'll need to link with to support new JUCE features.
(It should be pretty obvious from the link-time error when one of these is missing).
</li>
<li>If you need to link to the JUCE static library rather than using the amalgamated files, you'll need to drag-and-drop
the <code>juce.xcodeproj</code> file into your project's "External Frameworks and Libraries" list. Then, expand this
item in the treeview, and inside there'll be an item "libjuce.a" or "libjucedebug.a" - drag-and-drop
this into the "link binary with libraries" phase inside the xcode target. When you select either a debug
or release juce build these entries will (usually) update themselves to show the correct debug or release library
name. If you want your project to automatically rebuild JUCE when you make changes to a JUCE file, you can
also add JUCE to your target's "Direct Dependency" list (show information for the target, and this is on the
"general" tab).<br/>Alternative ways of linking to JUCE would be to add the libjuce.a or libjucedebug.a library to
your "External Frameworks and Libraries" list, or to add switch to the linker's command-line of either "-ljuce"
or "-ljucedebug".</li>
</ul>
<h3><a name="buildlinux"></a>Linux with GCC</h3>
<p>Most linux distros should come with the tools you need. You may need to install the development packages of
freetype, X11 and pthreads if they're not already available.</p>
<p>If you've enabled the <code>JUCE_USE_XINERAMA</code> option, then you'll also need to install the Xinerama package.
And you'll need the <code>GL</code> and <code>GLU</code> libraries if you've enabled <code>JUCE_OPENGL</code></p>
<p>The makefiles that are generated by the Introjucer can be run by "<code>make CONFIG=Debug</code>",
or "<code>make CONFIG=Release</code>". You can also use "<code>make clean</code>" to delete the
intermediate files.</p>
<h3><a name="buildandroid"></a>Android</h3>
<ul>
<li>First of all, get yourself over to <a href="http://www.android.com">www.android.com</a>, and install the latest
Android SDK and NDK. Follow their instructions for installing Eclipse, and get to the point where you can
build and run some of the Android NDK demo apps in Eclipse before even thinking about trying to do anything with JUCE. The
Android development environment is a hugely complicated mish-mash of random bits of software, lashed together with scripts,
so don't expect a slick installation experience - be prepared to mess about. Once it's installed though, it all more-or-less
seems to work..</li>
<li>The only sensible way to create an Android JUCE project is with the Introjucer - doing it with Eclipse is a nightmare and if
you want to do it manaually, good luck. The Introjucer will produce a folder containing a whole heap of files, and you can open the
folder in Eclipse as a new project (use the "create project" option in Eclipse).</li>
<li>Eclipse should be able to automatically build the project and run it, but you can also build it from the command-line,
by setting your CWD to the Android build folder and using "<code>ant debug</code>" or "<code>ant release</code>"</li>
<li>Be careful that your project folder doesn't contain any spaces in its path - the Android tools can't handle this (!)</li>
<li>The structure that a JUCE app uses is to have a couple of boilerplate java classes which load and run a big native
library containing the juce library and all your app code. JUCE uses JNI internally to call java classes to interact with
the OS.</li>
<li>When you change some of your app code and need to recompile and re-test the app, Eclipse will usually (but certainly
not always) detect the change and re-compile the library. Unfortunately, if there are any errors during compilation, it'll
ignore them, and carry on trying to run the app, after having cleared the console so you can no longer see the errors that
occurred. In these cases, you probably want to build it using the command-line 'ant debug' so you can actually see what happened.</li>
<li>Although Eclipse does manage to rebuild the native library when you change some c++ code, it will fail utterly to re-package the
new library file or to re-install it on the target device. So far, my way of getting it to do this has been to touch one of the
java files whenever I change any c++, and this seems to kick it into life. If anyone has ever had the patience to become an
Eclipse expert and can suggest a proper solution to this, please let me know!!</li>
<li>Often, Eclipse gets confused and insist that there are "mistakes" in the java which prevent it from running the app. Needless
to say, there aren't really any mistakes, and usually doing a "clean" sorts it out.</li>
</ul>
<div class="ad">
<p class="ad">***</p>
</div>
<div class="bottomsection">
<p class="bottombar">- Copyright 2005 Raw Material Software Ltd -</p>
</div>
</div>
</body>
</html>

340
docs/gpl.txt
View file

@ -1,340 +0,0 @@
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program 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.
This program 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 this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.

BIN
docs/images/rms_logo.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 3.4 KiB

193
docs/rawmat.css
View file

@ -1,193 +0,0 @@
body {
color: #444444;
font-family: Tahoma, Geneva, Arial, Helvetica, sans-serif;
font-size: 0.8em;
line-height: 1.5em;
text-align: left;
background: #e0e0e0;
}
a { color: #005888; }
a:hover { color: #1c90b0; }
a:visited { color: #006699; }
a:visited:hover { color: #1c90b0; }
h1 {
font-family: "Arial Narrow", Tahoma, Geneva, Arial, Helvetica, sans-serif;
font-size: 1.6em;
color: #006b95;
margin: 15px 0 15px 0;
padding-left: 15px;
}
h2 {
font-family: "Arial Narrow", Tahoma, Geneva, Arial, Helvetica, sans-serif;
font-size: 1.3em;
color: #007aac;
margin: 15px;
}
h3 {
font-family: "Arial Narrow", Tahoma, Geneva, Arial, Helvetica, sans-serif;
font-size: 1.1em;
color: #56a7c1;
margin: 15px;
}
p {
margin: 10px 15px 5px 15px;
}
pre {
font-family: monospace;
font-size: 1.1em;
line-height: 1.1em;
}
code {
font-family: monospace;
font-size: 1.2em;
line-height: 1.1em;
}
.pageholder {
width: 800px;
min-width: 800px;
margin: 10px auto 0 auto;
background: #ffffff none;
padding: 0 !important; position: relative; }
.banner {
height: 90px;
background: #3366cc none; line-height: 20px; font-family: Arial, Tahoma, Geneva, Helvetica, sans-serif; }
.banner img {
float: left;
color: #ffffff;
margin: 15px 0 0 16px;
border: 0;
background: none; font-family: sans-serif; font-size: 25px;
}
.mainsections {
margin: 6px 0px 6px 0px;
padding: 0; position: absolute; left: 390px; top: 56px;
float: left;
font-size: 13px; }
.mainsections ul {
margin: 0;
padding: 0 0 0 10px; background-color: #3366cc; background-image: none; }
.mainsections li {
list-style-type: none;
float: left;
width: auto;
min-width: 50;
min-height: 22px; max-height: 22px;
text-align: center; margin: 6px 4px 0px 4px;
font-size: 12px; background: url(images/inactiverightcorner.gif) no-repeat top right; }
.mainsections a:link, .mainsections a:visited {
display: block;
color: #d0eef3; text-decoration: none;
padding: 2px 8px 0px 10px;
background: url(images/inactiveleftcorner.gif) no-repeat top left;
max-height: 20px; }
.mainsections a:hover, .mainsections a:visited:hover {
color: #ffffff;
text-decoration: none;
padding: 2px 8px 0px 10px;
}
.currentsection {
margin-top: 4px;
background-image: url(images/activerightcorner.gif) !important;
}
.currentsection a:link, .currentsection a:visited {
color: #006b95 !important;
background-image: url(images/activeleftcorner.gif) !important;
}
.currentsection a:hover, .currentsection a:visited:hover {
color: #2c93b0 !important;
}
.subsections {
clear: both;
}
.subsections ul {
margin: 0;
padding: 0 6px 0 6px;
}
.subsections li {
list-style-type: none;
float: left;
margin: 0px 4px 0 4px;
background-image: url(images/inactivesubsection.gif);
background-repeat: no-repeat;
background-position: center left;
padding-left: 10px; }
.subsections a:link, .subsections a:visited {
padding: 0 4px 0 4px;
text-decoration: none;
}
.currentsubsection a:link, .currentsubsection a:visited {
font-weight: bold;
color: #000099;
}
.currentsubsection {
background-image: url(images/activesubsection.gif) !important;
}
.content {
clear: both;
float: none;
padding: 2px 5px 0 5px;
min-height: 500px;
background-image: none;
font-family: Georgia, Helvetica, sans-serif;
}
.prop {
float: right;
width: 1px;
height: 400px;
}
.bottomsection {
clear: both;
text-align: center;
background-image: none;
margin: 0;
padding: 15px 0 12px 0;
}
.bottombar {
padding: 5px;
background: #3366cc none;
margin: 10px 0 10px 0 !important;
color: #ffffff; height: 26px;
font-size: 0.8em;
}
.bottombar a, .bottombar a:visited {
color: #d0eef0 !important;
}
.bottomtext a:hover, .bottomtext a:visited:hover {
color: #ffffff !important;
}
.ad {
clear: both;
padding: 30px 0 0 0;
text-align: center;
}