fenics team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

Looks good. I noticed a couple of things:

1. It would be good if class names were in another font (like courier
style), \texttt{VariationalProblem} etc

2. Would it be better with another variable name instead of h since
that will be used as mesh size in other demos. Why not g?

3. Is the normal flux + or - grad(u).n? I think of it as -grad(u).n.

4. Typo in "The implemented in a single Python file"

5. g is used in (f, g) instead of h (but maybe h should be changed to g)

The documentation seems to be coming along pretty well. It may be time
for you to ask people to contribute specific parts. For example,
Johannes and Harish could contribute with some documentation of how to
get Debian/Ubuntu packages and building with Dorsal. Others can
contribute with writing specific pages for the programmer's
reference, and Hans Petter can contribute with preparing his tutorial
in reST (and split it in Python and C++ versions).

--
Anders


On Wed, Jun 16, 2010 at 06:31:42PM +0200, Kristian Oelgaard wrote:
> Hello,
>
> I've finished a first iteration on documenting the Poisson demo (from
> dolfin/demo/pde/poisson).
>
> Check it out and let me know what you think.
>
> The Python version is here:
>
>  http://www.fenics.org/newdoc/demos/python/pde/poisson/poisson.html
>
> and the C++ version is here:
>
> http://www.fenics.org/newdoc/demos/cpp/pde/poisson/poisson.html
>
> Note that I need to finish the Programmer's reference part of the
> documentation before I can insert links to the relevant classes used
> in the demos.
>
> http://www.fenics.org/newdoc/programmers-reference/index.html
>
> Kristian
>
> _______________________________________________
> Mailing list: https://launchpad.net/~fenics
> Post to     : fenics@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fenics
> More help   : https://help.launchpad.net/ListHelp

Attachment: signature.asc
Description: Digital signature