"http://www.w3.org/TR/REC-html40/frameset.dtd">
<html>
<head>
-<title>deal.II Development Information</title>
- <link href="../screen.css" rel="StyleSheet">
- <meta name="author" content="the deal.II authors <authors@dealii.org>">
- <meta name="keywords" content="deal.II">
+ <title>deal.II Development Information</title>
+ <link href="../screen.css" rel="StyleSheet">
+ <meta name="author" content="the deal.II authors <authors@dealii.org>">
+ <meta name="copyright" content="Copyright (C) 1998, 1999, 2000, 2002, 2003, 2004, 2005 by the deal.II authors">
+ <meta name="date" content="$Date$">
+ <meta name="CVS_ID" content="$Id$">
+ <meta http-equiv="content-language" content="en">
</head>
<frameset rows="70,*" border=0>
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
-<title>deal.II Development Navigation Bar</title>
- <link href="../screen.css" rel="StyleSheet" media="screen">
- <meta name="author" content="the deal.II authors <authors@dealii.org>">
- <meta name="keywords" content="deal.II">
-</head>
-<body style="background-image:url(../pictures/deal.II-text.jpg);" lang="en">
+ <title>deal.II Development Navigation Bar</title>
+ <link href="../screen.css" rel="StyleSheet">
+ <meta name="author" content="the deal.II authors <authors@dealii.org>">
+ <meta name="copyright" content="Copyright (C) 1998, 1999, 2000, 2002, 2003, 2004, 2005 by the deal.II authors">
+ <meta name="date" content="$Date$">
+ <meta name="CVS_ID" content="$Id$">
+ <meta http-equiv="content-language" content="en">
+ </head>
+<body class="navbar">
<p>
<strong>Table of contents</strong>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
- <head>
- <link href="../screen.css" rel="StyleSheet" media="screen">
- <title>The deal.II Recent Changes</title>
- <meta name="author" content="the deal.II authors <authors@dealii.org>">
- <meta name="keywords" content="deal.II"></head>
- <body>
-
+<head>
+ <link href="../screen.css" rel="StyleSheet" media="screen">
+ <title>The deal.II Recent Changes</title>
+ <meta name="author" content="the deal.II authors <authors@dealii.org>">
+ <meta name="copyright" content="Copyright (C) 1998, 1999, 2000, 2002, 2003, 2004, 2005 by the deal.II authors">
+ <meta name="date" content="$Date$">
+ <meta name="CVS_ID" content="$Id$">
+ <meta http-equiv="content-language" content="en">
+<body>
- <h2>Information on recent changes</h2>
+ <h1>Information on recent changes</h1>
<p>
In case you want to stay informed about what has happened recently
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
- <head>
- <link href="../screen.css" rel="StyleSheet" media="screen">
- <title>The deal.II Testsuite</title>
- <meta name="author" content="the deal.II authors <authors@dealii.org>">
- <meta name="keywords" content="deal.II"></head>
- <body>
+<head>
+ <link href="../screen.css" rel="StyleSheet">
+ <title>The deal.II Testsuite</title>
+ <meta name="author" content="the deal.II authors <authors@dealii.org>">
+ <meta name="copyright" content="Copyright (C) 1998, 1999, 2000, 2002, 2003, 2004, 2005 by the deal.II authors">
+ <meta name="date" content="$Date$">
+ <meta name="CVS_ID" content="$Id$">
+ <meta name="keywords" content="deal dealii finite elements fem triangulation">
+ <meta http-equiv="content-language" content="en">
+</head>
+<body>
- <h2>The deal.II Testsuite</h2>
+ <h1>The deal.II Testsuite</h1>
<p>
deal.II has a testsuite that, at the time this article is written,
</p>
- <h3>Running it</h3>
+ <h2>Running it</h2>
<p>
To run the testsuite, you first need CVS access to our source
- <h3>Adding new tests</h3>
+ <h2>Adding new tests</h2>
<p>
As mentioned above, we usually add a new test these days every
.
</p>
- <h4>The testcase</h4>
+ <h3>The testcase</h3>
<p>
For the testcase, we usually start from a template like this:
<pre>
</p>
- <h4>An entry in the Makefile</h4>
+ <h3>An entry in the Makefile</h3>
<p>
In order for the Makefiles to pick up your new test, you have to
- <h4>An expected output</h4>
+ <h3>An expected output</h3>
<p>
If you run your new test executable, you will get an output file
- <h4>Checking everything in</h4>
+ <h3>Checking in</h3>
<p>
Tests are a way to make sure everything keeps working. If they
</p>
- <h3>Adding a new system</h3>
+ <h2>Adding a new system</h2>
<p>
If you are working on a system or with a compiler for which test
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
-<!-- deal.II tutorial template
- The deal.II authors <authors@dealii.org> 1999 - 2005
--->
-
-<title>deal.II Tutorial</title>
- <link href="../screen.css" rel="StyleSheet" media="screen">
- <meta name="author" content="the deal.II authors <authors@dealii.org>">
- <meta name="keywords" content="deal.II">
+ <title>deal.II Tutorial</title>
+ <link href="../screen.css" rel="StyleSheet">
+ <meta name="author" content="the deal.II authors <authors@dealii.org>">
+ <meta name="copyright" content="Copyright (C) 1998, 1999, 2000, 2002, 2003, 2004, 2005 by the deal.II authors">
+ <meta name="date" content="$Date$">
+ <meta name="CVS_ID" content="$Id$">
+ <meta name="keywords" content="deal dealii finite elements fem triangulation">
+ <meta http-equiv="content-language" content="en">
</head>
<body class="title">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
- <head>
- <link href="../screen.css" rel="StyleSheet" media="screen">
- <title>The deal.II Development Page</title>
- <meta name="author" content="the deal.II authors <authors@dealii.org>">
- <meta name="keywords" content="deal.II"></head>
+<head>
+ <link href="../screen.css" rel="StyleSheet">
+ <title>The deal.II Development Page</title>
+ <meta name="author" content="the deal.II authors <authors@dealii.org>">
+ <meta name="copyright" content="Copyright (C) 1998, 1999, 2000, 2002, 2003, 2004, 2005 by the deal.II authors">
+ <meta name="date" content="$Date$">
+ <meta name="CVS_ID" content="$Id$">
+ <meta name="keywords" content="deal dealii finite elements fem triangulation">
+ <meta http-equiv="content-language" content="en">
+</head>
<body>
-
- <h2>Information on development with <acronym>deal.II</acronym></h2>
+ <h1>Information on development with <acronym>deal.II</acronym></h1>
<p>
Apart from the online API references and the tutorial, which is
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
- <head>
- <link href="../screen.css" rel="StyleSheet" media="screen">
- <title>Writing documentation</title>
- <meta name="author" content="the deal.II authors <authors@dealii.org>">
- <meta name="keywords" content="deal.II"></head>
- <body>
+<head>
+ <link href="../screen.css" rel="StyleSheet">
+ <title>Writing documentation</title>
+ <meta name="author" content="the deal.II authors <authors@dealii.org>">
+ <meta name="copyright" content="Copyright (C) 1998, 1999, 2000, 2002, 2003, 2004, 2005 by the deal.II authors">
+ <meta name="date" content="$Date$">
+ <meta name="CVS_ID" content="$Id$">
+ <meta name="keywords" content="deal dealii finite elements fem triangulation">
+ <meta http-equiv="content-language" content="en">
+</head>
+<body>
-
- <h2>Writing Documentation</h2>
+ <h1>Writing Documentation</h1>
<p>
It is our firm belief that software can only be successful if it
<a name="API"></a>
- <h3>Writing API documentation</h3>
+ <h2>Writing API documentation</h2>
<p>
In order to extract documentation from the header files of the
</p>
- <h4>Basic layout of documentation</h4>
+ <h3>Basic layout of documentation</h3>
<p>
Basically, every declaration, whether class or member
</p>
- <h4>Extended Layout</h4>
+ <h3>Extended Layout</h3>
<p>
In order to allow better structured output for long comments,
<a name="examples"></a>
- <h3>Writing example programs</h3>
+ <h2>Writing example programs</h2>
- <h4>The Tutorial</h4>
+ <h3>The Tutorial</h3>
<p>
At present, the tools that extract information from the example
programs are rather dumb. They are, to be precise, two Perl
allow for higher quality printing than what we get from HTML.
</p>
- <h4>Code examples for the usage of single classes</h4>
+ <h3>Code examples for the usage of single classes</h3>
<p>
Writing example files for classes is supported by
<acronym>doxygen</acronym>. These example files go into