fit 1.1

data/README.txt

@@ -0,0 +1,203 @@
+= RubyFIT -- FIT for Ruby
+
+This is RubyFIT, a Ruby port of the original Framework for Interactive
+Testing written in Java by Ward Cunningham. See RubyFIT's home page at
+http://fit.rubyforge.org for further information.
+
+Author:: Giulio Piancastelli <giulio.piancastelli@gmail.com>
+Requires:: Ruby 1.8 or later
+License:: RubyFIT is Copyright 2004-2006 by Giulio Piancastelli.
+          FIT is Copyright 2002 by Cunningham & Cunningham, Inc.
+          Both FIT and RubyFIT are released under the terms of the GNU
+          General Public License version 2 or later.
+
+Document created on Saturday 11th December, 2004.
+Last revised on Saturday 20th May, 2006.
+
+== Quick Start
+
+=== Unit tests and examples
+
+If you want to be sure that at least something is working in the
+framework, the first thing you could do is to run the unit tests that
+accompany RubyFIT. You have the chance of running unit tests during
+the installation of RubyFIT as a gem on your system. (See RubyGems at
+http://rubygems.rubyforge.org and its documentation for details on how
+to do it.) When RubyFIT is installed, you still can run unit tests just
+by moving into its installation directory in the Ruby environment (e.g.
+<tt>$RUBY_HOME/lib/ruby/gems/1.8/gems/fit-1.1/</tt>) and typing +rake+
+at the Terminal or Command Prompt in that directory, which contains
+RubyFIT's Rakefile. If you don't have Rake installed, you can still
+manually run tests by executing the <tt>test/all_tests.rb</tt> script.
+
+But the RubyFIT gem also comes with a series of examples directly taken
+from the official FIT wiki (see http://fit.c2.com). HTML files
+containing test data in tables are stored under the
+<tt>doc/examples</tt> directory. If you want to run them to verify that
+the framework passes them, just type <tt>rake fit</tt> at the Terminal
+or Command Prompt in the directory containing RubyFIT's Rakefile.
+Typing <tt>rake fit_report</tt> instead will also have the effect of
+generating reports for those tests, so that you can see green, red,
+yellow and gray cells with your own eyes.
+
+The specification for FIT 1.1 compliant implementations is also
+included, in the <tt>doc/spec</tt> directory. Running
+<tt>rake fitspec</tt> or <tt>rake fitspec_report</tt> will have the
+same effects described above in the context of RubyFIT's examples.
+
+If you don't have Rake (see http://rake.rubyforge.org) installed, you
+can still running FIT examples and specifications using the command
+line tool provided with the RubyFIT distribution. See next section for
+a brief explanation of its usage.
+
+After having verified the capabilities of the framework, you would
+like to start writing your own fixtures testing your applications.
+Follow the online tutorials to understand how to plug into RubyFIT
+and create fixtures and HTML tables with test data.
+
+=== RubyFIT from the command line
+
+A sample command-line script is included in the +bin+ subdirectory of
+the RubyFIT gem to help you run tests in the most painless way. Being
+RubyFIT a gem, the executable scripts to be used as commands from a
+Terminal or Console prompt are made available at any file system
+location.
+
+You can invoke the +fit+ script passing two arguments: the first is the
+HTML file containing tables to be tested, the second is the name of the
+HTML file which will be created by RubyFIT and will contain the results
+of the tests.
+
+=== RubyFIT from a web server
+
+A sample CGI script is included in the +bin+ subdirectory of the
+RubyFIT gem, just to let you have a glance at how RubyFIT can be used
+behind a web server. Put <tt>fit.cgi</tt> in the <tt>cgi-bin</tt>
+directory under your web server tree (or in an equivalent appropriate
+location), then change the shebang line to point to the location of the
+Ruby interpreter on your machine. Finally, change the location to
+RubyFIT pointing to the directory you have downloaded the code, and the
+location to your fixtures to whatever directory you use to collect your
+Ruby classes derived from Fit::Fixture.
+
+You should now be able to use RubyFIT behind a web server. Write an
+HTML page containing tables for one of your fixtures, and remember to
+add a link to the <tt>fit.cgi</tt> script: serve it through the web
+server you have installed <tt>fit.cgi</tt> within, then click on the
+<tt>fit.cgi</tt> link to run the tests and get a result page in
+response.
+
+=== RubyFIT from Rake
+
+RubyFIT tests can also be run from within the Rake build tool. See the
+online RubyFIT documentation for a brief tutorial on how to use the
++FitTask+ task in your Rakefile. Visit http://rake.rubyforge.org for
+further details about Rake.
+
+=== RubyFIT in FitNesse
+
+You can now run RubyFIT tests in FitNesse. (See http://fitnesse.org
+for general information on FitNesse.) Define the command pattern like so:
+"!define COMMAND_PATTERN {/path/to/ruby/ruby -I %p -I /path/to/RubyFIT/lib 
+/path/to/RubyFIT/bin/FitServer.rb}" changing the paths as appropriate.
+
+There is no need to use a separate RubyFIT package to use it from
+within Fitnesse. After installing RubyFIT as a gem in your Ruby
+environment, you can reference the <tt>FitServer.rb</tt> script in
+Fitnesse from the location of the installed gem. For instance you can
+set the latest parameter defining the command pattern to the string
+<tt>/usr/lib/ruby/gems/1.8/gems/fit-1.1/bin/FitServer.rb</tt> for some
+Linux flavors.
+
+== RubyFIT Development Issues
+
+Being Ruby a much more different language than Java, RubyFIT carries
+some of those unique characteristics, sometimes bulding on them,
+sometimes suffering from them. Here follows a uncomplete list of
+issues in the development of RubyFIT, taken from the examples bundled
+with the RubyFIT distribution.
+
+==== Float Arithmetic
+
+In <tt>arithmetic.html</tt> Ruby does math differently from Java. A
+workaround is implemented in Fit::TypeAdapter#equals: if one of the
+object is a Float and the other is a Numeric, equality is tested on a
+1.0e-5 delta. Also, in <tt>CalculatorExample.html</tt> Ruby does Floats
+with much more precision than Java, so that even a 1.0e-15 or -1.0e-17
+difference is retained. A workaround in Fit::ScientificDouble has been
+implemented, so that if the precision is exactly zero, the values of
+two comparing objects must be equals in a 1.0e-5 delta.
+
+Note than in <tt>AllCombinations.html</tt> Ruby does even
+ScientificDouble with much more precision than the Java version. So,
+another workaround in <tt>==</tt> and <tt><=></tt> had to be employed,
+specifically to create another ScientificDouble to compare with and to
+pick the precision of the less precise of the two to make the
+comparison.
+
+==== Reflection in Fit::Fixture
+
+Being Ruby a dynamically typed programming language, it does not hold
+static typing information about fields and values returned from
+methods. The FIT framework instead uses those information to make
+automatic comparisons between expected and actual results while running
+tests using HTML tables as input data.
+
+RubyFIT covers that mechanisms for basic types only. When a fixture
+uses custom types instead, some additional static metadata must be
+provided to let the framework know about types of fields and return
+types of methods.
+
+The online tutorials provide some examples on using metadata in
+fixtures and related classes.
+
+==== Class names from 'eg.AllFiles$Example' strings in Fit::Fixture
+
+The syntax of fixtures class names into HTML tables is directly taken
+from the Java world, where FIT was originally being developed. The
+fully specified name of a class in Java is typically composed by a
+series of words separated by dots: the last word is the name of the
+class, while the other words identify the packages in which that class
+is contained. RubyFIT translates those names into Ruby class names: the
+name of the class remains unchanged, while package names (typically
+written in lower case as per Java conventions) get capitalized; the
+double colon is used instead of the dot as a separator between names.
+
+A particular syntax is used in the Java world for inner classes, i.e.
+classes defined inside other classes: in this case, a dollar sign is
+used as a separator between the names of the parent and the child
+classes. RubyFIT just translates the separator into a double colon,
+leaving class names untouched.
+
+==== Method names from HTML in Fit::TypeAdapter
+
+RubyFIT uses Fitnesse-style graceful naming, modified to suit Ruby's
+syntax and customs. For example, given any of these names in a row or
+column fixture: <tt>some_method()</tt>, <tt>some method()</tt>,
+<tt>some*method()</tt>, <tt>SomeMethod()</tt>, or
+<tt>Some Method()</tt>, it will call the method +some_method+,
+expecting it to be an output method (or getter), or the equivelent
+accessor generated by +attr_reader+. Given any of the above names, with
+the <tt>()</tt> replaced by <tt>?</tt>, such as <tt>some method?</tt>
+it will match the same methods, but will prefer a method named
+<tt>some_method?</tt>, if it exists. Any of the above names, with the
+<tt>()</tt> removed (and no <tt>?</tt>) will be interpreted as an input
+method (or setter) and will match <tt>some_method=(value)</tt>, as well
+as mutators generated by +attr_writer+.
+
+== Acknowledgements
+
+=== Credits
+
+The main developer and project maintainer is Giulio Piancastelli.
+
+Other developers have contributed code to the project:
+- Micah Martin
+- Jim Hughes
+- Brian Marick
+- Bret Pettichord
+
+=== Special Thanks
+
+Thanks to Ward Cunningham for creating FIT, and to Jim Shore for
+coordinating the effort of porting FIT to platforms other than Java.

data/Rakefile

@@ -0,0 +1,111 @@
+require 'rake/clean'
+
+$:.unshift File.join(File.dirname(__FILE__), 'lib')
+require 'fittask'
+
+desc "Run Fit TaskLib"
+Rake::FitTask.new(:fit) do |t|
+  # t.libs = ["lib/fit/*.rb"] # the fixture directory goes here
+
+  t.fail_on_failed_test = true
+  t.create_test_suite do |suite|
+    suite.test_path = 'doc/fitnesse/'
+    suite.report_path = 'doc/fitnesse/reports/'
+    test_files = Dir.glob(suite.test_path + '/*.html')
+    suite.tests = test_files.collect do |test_file| 
+       { :name => File.basename(test_file, '.html') } 
+    end
+  end
+
+  examples = []
+  examples << { :name => 'arithmetic',
+                :right => 39, :wrong => 8, :ignores => 0, :exceptions => 2 }
+  examples << { :name => 'BinaryChop',
+                :right => 95, :wrong => 0, :ignores => 0, :exceptions => 0 }
+  examples << { :name => 'CalculatorExample',
+                :right => 75, :wrong => 9, :ignores => 0, :exceptions => 0 }
+  examples << { :name => 'MusicExample',
+                :right => 95, :wrong => 0, :ignores => 0, :exceptions => 0 }
+  examples << { :name => 'MusicExampleWithErrors',
+                :right => 54, :wrong => 10, :ignores => 0, :exceptions => 0 }
+  # WebPageExample is not here because it needs an active Internet connection
+  examples << { :name => 'NetworkExample',
+                :right => 5, :wrong => 0, :ignores => 0, :exceptions => 0 }
+  examples << { :name => 'ColumnIndex',
+                :right => 51, :wrong => 3, :ignores => 8, :exceptions => 0 }
+  examples << { :name => 'AllFiles',
+                :right => 9, :wrong => 3, :ignores => 0, :exceptions => 0 }
+  examples << { :name => 'AllCombinations',
+                :right => 72, :wrong => 14, :ignores => 0, :exceptions => 0 }
+  examples << { :name => 'AllPairs',
+                :right => 39, :wrong => 9, :ignores => 0, :exceptions => 0 }
+  # Running the ExampleTests.html file is roughly equivalent to this test suite
+  t.create_test_suite do |suite|
+    suite.test_path = "doc/examples/"
+    suite.report_path = "doc/reports/"
+    suite.tests = examples
+  end
+  
+  t.test_suites.each do |suite|
+    CLOBBER.include(suite.report_path + "Report_*.html")
+    CLOBBER.include(suite.report_path + "footnotes/")
+  end
+  
+end
+
+Rake::FitTask.new(:fitspec) do |t|
+  t.create_test_suite do |suite|
+    suite.test_path = "doc/spec/"
+    suite.report_path = "doc/spec/"
+    suite << { :name => 'parse',
+               :right => 70, :wrong => 0, :ignores => 0, :exceptions => 0 }
+    suite << { :name => 'annotation',
+               :right => 47, :wrong => 0, :ignores => 0, :exceptions => 0 }
+  end
+end
+
+require 'rake/testtask'
+
+desc "Default task is to run FIT unit tests."
+task :default => :test
+
+desc "Run FIT unit tests."
+Rake::TestTask.new do |t|
+  t.test_files = FileList['test/all_tests.rb']
+  t.verbose = true
+  t.libs = ['lib','test'] # verify why is needed
+end
+
+### RubyGems related stuff
+
+require 'rake/gempackagetask'
+
+spec = Gem::Specification.new do |s|
+  s.name = 'fit'
+  s.version = '1.1'
+  s.author = 'Giulio Piancastelli'
+  # See the README for other authors/developers/contributors
+  s.email = 'giulio.piancastelli@gmail.com'
+  s.homepage = 'http://fit.rubyforge.org/'
+  s.rubyforge_project = 'fit'
+  s.platform = Gem::Platform::RUBY
+  s.summary = 'A Ruby port of FIT (Framework for Integrated Testing)'
+  s.files = FileList["{bin,lib,test,doc}/**/*"].to_a + ["Rakefile"]
+  s.require_path = 'lib'
+  # s.autorequire something?
+  # set for executable scripts in the bin/ subdirectory
+  s.bindir = 'bin'
+  s.executables << 'fit'
+  s.test_file = 'test/all_tests.rb'
+  s.has_rdoc = false # no RDoc comments in the code
+  s.extra_rdoc_files = ["README.txt"]
+  # no external dependencies on other gems
+end
+
+# Cygwin's ln fails under my Windows installation
+FileUtils::LN_SUPPORTED[0] = false
+
+Rake::GemPackageTask.new(spec) do |pkg|
+  pkg.need_tar = true
+  pkg.need_zip = true
+end

data/bin/FitServer.rb

@@ -0,0 +1,6 @@
+$:.unshift File.join(File.dirname(__FILE__), '..', 'lib')
+
+require 'fit/fit_server'
+
+exitCode = Fit::FitServer.new.run(ARGV)
+exit exitCode

data/bin/fit

@@ -0,0 +1,10 @@
+$:.unshift File.join(File.dirname(__FILE__), '..', 'lib')
+
+require 'fit/parse'
+require 'fit/file_runner'
+
+report = ARGV[1]
+unless report.nil?
+  Fit::Parse.footnote_path = File.dirname(report) + File::SEPARATOR
+end
+Fit::FileRunner.new.run ARGV

data/bin/fit.cgi

@@ -0,0 +1,36 @@
+#!C:/Programmi/Ruby18/bin/ruby
+
+require 'cgi'
+require 'open-uri'
+
+# Set the location of the RubyFIT installation on your machine
+rubyfit_location = "D:/Progetti/Ruby/Fit/lib"
+# Set the location of the newly-created pure-Ruby fixtures on your machine
+# rubyfit_fixtures = "D:/Progetti/Ruby/Fit/MyFixtures"
+rubyfit_fixtures = "D:/Progetti/Ruby/Fit/examples"
+
+$:.unshift(rubyfit_location, rubyfit_fixtures)
+
+require 'fit/file_runner'
+
+cgi = CGI.new
+
+input_name = 'fitDocument.html'
+output_name = 'fitReport.html'
+
+referer = cgi.referer
+begin
+  input = open(referer) {|stream| stream.read}
+  File.open(input_name, 'w') {|f| f.write(input)}
+  runner = Fit::FileRunner.new
+  runner.process_args [input_name, output_name]
+  runner.process
+
+  output = File.open(output_name) {|f| f.read}
+  cgi.out { output }
+
+  File.delete(output_name)
+  File.delete(input_name)
+rescue Exception => e
+  cgi.out {e.message + "\n" + e.backtrace.join("\n")}
+end

data/doc/examples/AllCombinations.html

@@ -0,0 +1,55 @@
+<html>
+<head>
+    <title>Wiki: All Combinations</title>
+<head>
+<body bgcolor=#FFFFFF link=#d06040 vlink=#806040>
+    <h1>All Combinations</h1>
+    <wiki>This is the second of a suite of fixtures that make up the AllPairsExample. Like with AllFiles, we expand wildcard characters in path specifications to get lists of tests. But this time we run all combinations of the tests. This is another warmup for AllPairs testing.
+<p><p><hr>
+<p>A project can expect to have dozens or hundreds of files testing specific features in a stand-alone way. We may wonder if there are any interactions between features that will cause any of these tests to fail. AllCombinations explores this. It is a fixture that enumerates cases by drawing one file at a time from each of a number of lists; running each in turn, and then repeating the drawing and running for all possible combinations.
+<p>For the purpose of illustration we've created a number of files that contain small tests of the CalculatorExample. We've categorized the files as <em>magnitudes, signs</em> and <em>functions,</em>  which enter values, changes signs, and compute functions, respectivly.
+<p><UL>
+<li> <a href="Release/Documents/AllPairs/">http:Release/Documents/AllPairs/</a>
+<p></UL>
+This table runs all possible sequences of magnitude, sign and function. Try it with <a href="run.cgi">http:run.cgi</a>.
+<p><table BORDER CELLSPACING=0 CELLPADDING=3>
+<tr><td ColSpan=2> eg.AllCombinations </td></tr>
+<tr><td> doc/examples/AllPairs/magnitude/*.html </td><td>&nbsp;</td></tr>
+<tr><td> doc/examples/AllPairs/sign/*.html </td><td>&nbsp;</td></tr>
+<tr><td> doc/examples/AllPairs/function/*.html </td><td>&nbsp;</td></tr>
+</table>
+<p>The number of cases will as large as the product of the size of each list of tests. The searches in the table find four magnitues, three signs and two functions.
+<p><UL>
+<li> 4 magnitudes  X  3 signs  X  2 functions  =  24 cases
+<p></UL>
+Any file of any case can fail. We save the results from failed tests only. A single file can fail different ways in different cases. Look for differences in the counts or examine each FileFootnote.
+<p>If the tests are intended to interact, as ours are here, then some care is required to be sure that checks in the tests are independent of this interaction. No checks at all my be suitable if we are only testing that there are no exceptions thrown. Or the simplest checks may be adaquate so long as features are tested well in isolation. It may be convenient to run a simulation, a so called <em>oracale</em>, along side the application to generate expected results.
+<p><hr>
+<p><strong>Implementation</strong>
+<p>The fixture inherits path expansion from AllFiles, but captures these by overrinding <em>doRows(Parse, List)</em> and saving the list of files in a list of lists. Then, at the end of <em>doTable</em>, the fixture gets to work computing and running combinations.
+<p>See source.
+<p><UL>
+<li> <a href="Release/Source/eg/AllCombinations.java">http:Release/Source/eg/AllCombinations.java</a>
+<p></UL>
+We had a little trouble setting up the test data for this example so we wrote this little <em>Trigonometry Refresher</em>.
+<p><table BORDER CELLSPACING=0 CELLPADDING=3>
+<tr><td ColSpan=3> eg.ArithmeticColumnFixture </td></tr>
+<tr><td> x </td><td> sin() </td><td> cos() </td></tr>
+<tr><td> 0     </td><td> 0.0000 </td><td> 1.0000 </td></tr>
+<tr><td> 30   </td><td> 0.5000 </td><td> 0.8660 </td></tr>
+<tr><td> 60   </td><td> 0.8660 </td><td> 0.5000 </td></tr>
+<tr><td> 90   </td><td> 1.0000 </td><td> 0.0000 </td></tr>
+<tr><td> 120 </td><td> 0.8660 </td><td> -0.5000 </td></tr>
+<tr><td> 150 </td><td> 0.5000 </td><td> -.8660 </td></tr>
+<tr><td> 180 </td><td> 0.0000 </td><td> -1.0000 </td></tr>
+</table>
+<p><hr>
+<p><p><table BORDER CELLSPACING=0 CELLPADDING=3>
+<tr><td ColSpan=2> fit.Summary </td></tr>
+</table>
+<p></wiki>
+<hr>
+    Last edited November 4, 2002
+</body>
+</html>
+

data/doc/examples/AllFiles.html

@@ -0,0 +1,60 @@
+<html>
+<head>
+    <title>Wiki: All Files</title>
+<head>
+<body bgcolor=#FFFFFF link=#d06040 vlink=#806040>
+    <h1>All Files</h1>
+    <wiki>This is the first of a suite of fixtures that make up the AllPairsExample. It and AllCombinations are warmups for AllPairs testing.
+<p><hr>
+<p>A project can expect to have dozens to hundreds of files filled with specifications, explainations and associated tests. The AllFiles fixture seeks out these files and runs them all, one after another, and reports a "rolled-up" accounting of their results.
+<p>Like the ExampleTests fixture, the AllFiles fixture will take as its tabular input a list of files to be run. But here, unlike that fixture, we will expand wildcard characters in order to find all the tests in a particular place, whether we know what they are now or not.
+<p>Here are wildcard path expressions that find lots of other tests. Try runing them with <a href="run.cgi">http:run.cgi</a>.
+<p><table BORDER CELLSPACING=0 CELLPADDING=3>
+<tr><td ColSpan=2> eg.AllFiles </td></tr>
+<tr><td> doc/examples/*Example.html </td><td>&nbsp;</td></tr>
+<tr><td> doc/examples/Music*.html </td><td>&nbsp;</td></tr>
+</table>
+<p>The AllFiles fixture adds rows to this table for each of the files it finds. The first column is the expanded file name, the second, the resulting counts for that run. We mark the results "wrong" if there are any wrongs or exceptions. That means the above tests will never pass because we have intentional errors in these files.
+<p>Use AllFiles when you expect all your tests to pass and only want to know when this expectation is unfounded. AllFiles does not create output files for the tests it runs unless there is a problem. Problem run results are saved and cited along with the counts in a FileFootnote that looks like [1], [2], and so on.
+<p>Test counts can sore when we start running files over and over. LessonsLearned advise us to not take big "right" counts too seriously so we don't. In fact a file with 100 right and no wrong counts as 1 right from this fixtures perspective. You can see this in the <em>counts</em> reported in the summary:
+<p><table BORDER CELLSPACING=0 CELLPADDING=3>
+<tr><td ColSpan=2> fit.Summary </td></tr>
+</table>
+<p>(Note: See more complete summary below.)
+<p>You will also note that the fixture reports total counts for the files it runs under <em>counts run</em> in the summary because, lessons not withstanding, we like to know.
+<p><hr>
+<p><strong>Implementation</strong>
+<p>The fixture distinguishes expandings the path specifications (doRow) from running the list of files produced (doFiles). This fixture does the files as they are expanded. The AllCombinations and AllPairs refinements expand all rows before they start doing.
+<p>The path expansion only expands one wildcard character, star (*), which means <em>any characters</em> here. The star can appear anywhere in a name and in any or all names that make up a path. But the expansion we've coded has the restriction that only one star is expanded in any component of the path.
+<p>The expanded file names will refer to files that may or may not use the &lt;wiki&gt; tag convention (See WikiRunner). This fixture is happy to run either file format and lets the presence of a &lt;wiki&gt; tag in the file indicate the need for its processing.
+<p>See the source.
+<p><UL>
+<li> <a href="Release/Source/eg/AllFiles.java">http:Release/Source/eg/AllFiles.java</a>
+<p></UL>
+This class includes an implementation of FileFootnote that is discussed on that page.
+<p><hr>
+<p><table BORDER CELLSPACING=0 CELLPADDING=3>
+<tr><td ColSpan=2> eg.AllFiles$Expand </td></tr>
+<tr><td> path </td><td> expansion() </td></tr>
+<tr><td> doc/examples/*Example.html </td><td> CalculatorExample.html,MusicExample.html,NetworkExample.html,WebPageExample.html </td></tr>
+<tr><td> doc/examples/Music*.html </td><td> MusicExample.html,MusicExampleWithErrors.html </td></tr>
+<tr><td> doc/examples/AllPairs/magnitude/*.html </td><td> 180+30.html,30.html,360+30.html,90-30.html </td></tr>
+<tr><td> doc/examples/AllPairs/sign/*.html </td><td> change-sign.html,multiply.html,no-change.html </td></tr>
+<tr><td> doc/examples/AllPairs/function/*.html </td><td> cosine.html,sine.html </td></tr>
+<tr><td> doc/examples/AllPairs/function/*sine.html </td><td> cosine.html,sine.html </td></tr>
+<tr><td> doc/examples/AllPairs/function/*.xml </td><td>&nbsp;</td></tr>
+<tr><td> doc/examples/AllPairs/func* </td><td>&nbsp;</td></tr>
+<tr><td> doc/examples/AllPairs/* </td><td>&nbsp;</td></tr>
+<tr><td> doc/examples/AllPairs* </td><td>&nbsp;</td></tr>
+<tr><td> doc/examples/* </td><td>&nbsp;</td></tr>
+</table>
+<p>We've added some more tests to this document so the totals in the summary increase.
+<p><table BORDER CELLSPACING=0 CELLPADDING=3>
+<tr><td ColSpan=2> fit.Summary </td></tr>
+</table>
+<p></wiki>
+<hr>
+    Last edited April 20, 2003
+</body>
+</html>
+

data/doc/examples/AllPairs/function/cosine.html

@@ -0,0 +1,57 @@
+<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
+<html>
+<head>
+   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+   <meta name="GENERATOR" content="Mozilla/4.77C-CCK-MCD {C-UDP; EBM-APPLE} (Macintosh; U; PPC) [Netscape]">
+   <title>change-sign.html</title>
+</head>
+<body>
+Check cosine function.
+<br>&nbsp;
+<table BORDER CELLSPACING=0 CELLPADDING=3 >
+<tr>
+<td>eg.Calculator</td>
+
+<td>&nbsp;</td>
+</tr>
+
+<tr>
+<td>key</td>
+
+<td>x()</td>
+</tr>
+
+<tr>
+<td>enter</td>
+
+<td></td>
+</tr>
+
+<tr>
+<td>cos</td>
+
+<td></td>
+</tr>
+
+<tr>
+<td>enter</td>
+
+<td></td>
+</tr>
+
+<tr>
+<td>*</td>
+
+<td></td>
+</tr>
+
+<tr>
+<td>sqrt</td>
+
+<td>0.8660</td>
+</tr>
+</table>
+
+<p>See <a href="http://fit.c2.com/wiki.cgi?AllPairsExample">AllPairsExample</a>.
+</body>
+</html>

data/doc/examples/AllPairs/function/sine.html

@@ -0,0 +1,57 @@
+<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
+<html>
+<head>
+   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+   <meta name="GENERATOR" content="Mozilla/4.77C-CCK-MCD {C-UDP; EBM-APPLE} (Macintosh; U; PPC) [Netscape]">
+   <title>change-sign.html</title>
+</head>
+<body>
+Check sine function.
+<br>&nbsp;
+<table BORDER CELLSPACING=0 CELLPADDING=3 >
+<tr>
+<td>eg.Calculator</td>
+
+<td>&nbsp;</td>
+</tr>
+
+<tr>
+<td>key</td>
+
+<td>x()</td>
+</tr>
+
+<tr>
+<td>enter</td>
+
+<td></td>
+</tr>
+
+<tr>
+<td>sin</td>
+
+<td></td>
+</tr>
+
+<tr>
+<td>enter</td>
+
+<td></td>
+</tr>
+
+<tr>
+<td>*</td>
+
+<td></td>
+</tr>
+
+<tr>
+<td>sqrt</td>
+
+<td>0.5000</td>
+</tr>
+</table>
+
+<p>See <a href="http://fit.c2.com/wiki.cgi?AllPairsExample">AllPairsExample</a>.
+</body>
+</html>

data/doc/examples/AllPairs/magnitude/180+30.html

@@ -0,0 +1,45 @@
+<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
+<html>
+<head>
+   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+   <meta name="GENERATOR" content="Mozilla/4.77C-CCK-MCD {C-UDP; EBM-APPLE} (Macintosh; U; PPC) [Netscape]">
+   <title>change-sign.html</title>
+</head>
+<body>
+Enter 180+30 degrees.
+<br>&nbsp;
+<table BORDER CELLSPACING=0 CELLPADDING=3 >
+<tr>
+<td>eg.Calculator</td>
+
+<td></td>
+</tr>
+
+<tr>
+<td>key</td>
+
+<td>x()</td>
+</tr>
+
+<tr>
+<td>180</td>
+
+<td>&nbsp;</td>
+</tr>
+
+<tr>
+<td>30</td>
+
+<td>&nbsp;</td>
+</tr>
+
+<tr>
+<td>+</td>
+
+<td>&nbsp;210.000</td>
+</tr>
+</table>
+
+<p>See <a href="http://fit.c2.com/wiki.cgi?AllPairsExample">AllPairsExample</a>.
+</body>
+</html>