Renamed files so that we don't have to change numbers to add parts.

Started adding functions to the Infrastructure part.


git-svn-id: http://svn.cactuscode.org/flesh/trunk@237 17b73243-c579-4c4c-a9d2-2d5706c11dac

1 files changed, 0 insertions, 62 deletions

diff --git a/doc/UsersGuide/UsersGuide_Part2.tex b/doc/UsersGuide/UsersGuide_Part2.tex
deleted file mode 100644
index fe4dfb99..00000000
--- a/doc/UsersGuide/UsersGuide_Part2.tex
+++ /dev/null
@@ -1,62 +0,0 @@
-
-\part{Application thorn writing}
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
-\chapter{Thorn concepts} 
-
-      (This section has to contain enough explanation to make the rest of
-       the writers guide readable the first time through)
-(The hardest bugs to find are
-those arising from plausible but incorrect assumptions about the
-behavior of someone else's thorn.)
-      a) Again probably emphasize collaboration, what are thorns,
-         toolkits, how to share them.
-      b) Things to think about before you start programming:
-             Language, read all the documentation, emphasize use of
-             standard supported Cactus infrastructure
-      c) Available data types
-         i)   Scalars
-         ii)  Arrays and GFs
-         iii) Groups
-      d) Ghost zones and parallelism
-      e) Understanding the RFR concept
-      f) Understanding the GH concept
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
-\chapter{Anatomy of a thorn}
-
-Each thorn must be in a toolkit. Toolkits are fairly informal. If you
-want, you can just make your own toolkit directory, and stick your new
-thorn into it.
-
-      a) Creating a thorn (gmake new thorn)
-      b) Thorn directory structure
-      c) Thorn make files
-      d) Thorn configuration
-         (i)   Parameters (param.ccl)
-         (ii)  Variables (interface.ccl)
-         (iii) Scheduler (schedule.ccl)
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
-\chapter{Putting code into your thorn}
-
-      a) What the flesh basically provides (header files, macros, ...)
-      b) Argument lists and parameters
-      c) A simple example (Baloney)
-      d) Differences between F and C with the interface
-      e) A more complex example (Wavetoy)
-      f) Error handling and code stopping
-      g) Calling C from F, F from C, (C++ from F? ....)
-      h) Good Cactus Style Programming Guidelines
-      i) Adding a test suite
-      j) Sharing your thorn with the world.
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
-