anthonycicc/PySolFC
1
0
Fork 0
mirror of https://github.com/shlomif/PySolFC.git synced 2025-04-05 00:02:29 -04:00
Code Releases Activity

+ added dir data/html-src

Browse source 
git-svn-id: file:///home/shlomif/Backup/svn-dumps/PySolFC/svnsync-repos/pysolfc/PySolFC/trunk@94 efabe8c0-fbe8-4139-b769-b5e6d273206e
This commit is contained in:
skomoroh 2006-11-12 02:42:04 +00:00
parent ed9b76e84f
commit 7cd1031851
421 changed files with 18258 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7275
data/html-src/all.htm Normal file
View file

File diff suppressed because it is too large Load diff

98
data/html-src/credits.html Normal file
View file

@ -0,0 +1,98 @@
<h2>PySol credits go to</h2>
<ul>
<li> Volker Weidner for getting me into Solitaire
<li> Guido van Rossum for the initial example program
<li> <a href="http://www.inetarena.com/~grania/">T. Kirk</a> for lots of contributed games and cardsets
<li> the Gnome AisleRiot team for parts of the documentation
<li> the AfterStep and KDE teams for some icons
<li> the Python, Tcl/Tk &amp; Linux crews for making this program possible
</ul>
<h2>Game contributors are</h2>
<ul>
<li> T. Kirk &lt;grania@mailcity.com&gt;<br>
lots of Ganjifa
<a href="ganjifa.html">Ganjifa</a>,
<a href="hanafuda.html">Hanafuda</a>
and Tarock type games.
<li> Andrew Csillag &lt;andrew@starmedia.net&gt;
<ul>
<li> <a href="rules/canfield.html">Canfield</a>
</ul>
<li> Deon Ramsey &lt;miavir@furry.de&gt;
<ul>
<li> <a href="rules/nomad.html">Nomad</a>
</ul>
<li> Galen Brooks &lt;galen@nine.com&gt;
<ul>
<li> <a href="rules/numerica.html">Numerica</a>
</ul>
<li> Matthew Hohlfeld &lt;hohlfeld@cs.ucsd.edu&gt;
<ul>
<li> <a href="rules/larasgame.html">Lara's Game</a>
</ul>
</ul>
<h2>Cardset contributors are</h2>
<ul>
<li> Bao Trinh &lt;bao@cs.umd.edu&gt;
<li> DJ Delorie &lt;dj@delorie.com&gt;
<li> Donald R. Woods &lt;woods@sun.com&gt;
<li> Felix Bellaby &lt;felix@pooh.u-net.com&gt;
<li> Heiko Eissfeldt &lt;heiko@colossus.escape.de&gt;
<li> Jochen Tuchbreiter &lt;whynot@mabi.de&gt;
<li> John Fitzgibbon
<li> John Heidemann &lt;johnh@isi.edu&gt;
<li> Jonathan Blandford &lt;jrb@mit.edu&gt;
<li> Joseph L. Traub &lt;jtraub@zso.dec.com&gt;
<li> Michael Bischoff &lt;mbi@mo.math.nat.tu-bs.de&gt;
<li> Mike Naylor &lt;mike.naylor@5x5poker.com&gt;
<li> Oliver Xymoron &lt;oxymoron@waste.org&gt;
<li> Rene Seindal &lt;rene@seindal.dk&gt;
<li> Rudy Muller &lt;rudy.muller@net.HCC.nl&gt;
<li> Ryu Changwoo &lt;cwryu@eve.kaist.ac.kr&gt;
<li> T. Kirk &lt;grania@mailcity.com&gt;
<li> The Papa &lt;papalini@biancaneve.ing.unifi.it&gt;
</ul>
<h2>Music contributors are</h2>
<ul>
<li> <a href="http://hem.passagen.se/dachande/">Carl Larsson</a> aka <i>Nightbeat</i>
&lt;nightbeat@traxinspace.com&gt;
</ul>
<h2>Special thanks to</h2>
<ul>
<li> Andy Markebo &lt;flognat@fukt.hk-r.se&gt;
<li> Charles B. Dorsett
<li> Christian Tismer &lt;tismer@tismer.com&gt;
<li> Dylan Thurston &lt;Dylan.Thurston@math.unige.ch&gt;
<li> Jan Nijtmans &lt;j.nijtmans@chello.nl&gt;
<li> Jordan Russel &lt;jordanr@iname.com&gt;
<li> Kevin O'Connor &lt;koconnor@cse.Buffalo.EDU&gt;
<li> Marc-Andre Lemburg &lt;mal@lemburg.com&gt;
<li> Mark Hammond &lt;MHammond@skippinet.com.au&gt;
<li> Neil Schemenauer &lt;nascheme@enme.ucalgary.ca&gt;
<li> Thomas Gellekum &lt;tg@ihf.rwth-aachen.de&gt;
<li> Vladimir Marangozov &lt;Vladimir.Marangozov@inrialpes.fr&gt;
<li> Zachary Roadhouse &lt;Zachary_Roadhouse@brown.edu&gt;
<li> Natascha
</ul>
<h2>PySol uses the following OpenSource technologies</h2>
<ul>
<li> <a href="http://www.python.org/">The Python Programming Language</a>
<li> <a href="http://www.scriptics.com/">The Tcl/Tk GUI Toolkit</a>
<li> <a href="http://www.devolution.com/~slouken/projects/SDL/index.html">The SDL Simple DirectMedia Layer</a>
<li> <a href="http://www.lokigames.com/development/smpeg.php3">The SDL MPEG Player Library</a>
<li> <a href="http://mikmod.darkorb.net/">The MikMod Sound Library</a>
</ul>
<h2>PySol was created using the following OpenSource technologies</h2>
<ul>
<li> <a href="http://www.linux.org/">The Linux Operating System</a>
<li> <a href="http://www.xfree86.org/">The XFree86 X Window System</a>
<li> <a href="http://www.kde.org/">The KDE Desktop Environment</a>
<li> <a href="http://fte.sourceforge.net/">The FTE Text Editor</a>
<li> <a href="http://www.jordanr.dhs.org/">The Inno Setup Win32 Installer</a>
</ul>

13
data/html-src/ganjifa.html Normal file
View file

@ -0,0 +1,13 @@
<h1>General Ganjifa Card Rules</h1>
Ganjifa are playing cards from India and other nations in the region.
Usually round, some rectangular decks have been produced. The most significant
difference between Ganjifa and other types of cards is that Ganjifa cards have
traditionally been individually hand painted. There are any where from eight
to twelve or more suits per deck, each suit having usually twelve ranks. The
two most common Ganjifa decks are the Mughal which has eight suits and the
Dashavatara which has ten. The suits have pip cards numbered from Ace through
ten and two court cards, the Wazir and the Mir. Ganjifa solitaire games play
the same as games that use the standard deck but the larger number of different
cards in a deck (96 or 120) adds an element of complexity. The fact that each
suit has it's own color makes things quite interesting in games that use
"Alternate Color" row stacks.

234
data/html-src/gen-html.py Executable file
View file

@ -0,0 +1,234 @@
#!/usr/bin/env python
# -*- mode: python; coding: koi8-r; -*-
#
# $Id$
#
#outdir = '../html'
pysollib_dir = '../..'
import sys, os, re
from glob import glob
import gettext
gettext.install('pysol', 'locale', unicode=True)
try: os.mkdir('html')
except: pass
try: os.mkdir('html/rules')
except: pass
pysollib_path = os.path.join(sys.path[0], pysollib_dir)
sys.path[0] = os.path.normpath(pysollib_path)
#print sys.path
import pysollib.games
import pysollib.games.special
import pysollib.games.ultra
import pysollib.games.mahjongg
from pysollib.gamedb import GAME_DB
from pysollib.gamedb import GI
from pysollib.mfxutil import latin1_to_ascii
files = [
('credits.html', 'PySol Credits'),
('ganjifa.html', 'PySol - General Ganjifa Card Rules'),
('general_rules.html', 'PySol - General Rules'),
('glossary.html', 'PySol - Glossary'),
('hanafuda.html', 'PySol - Rules for General Flower Card Rules'),
('hexadeck.html', 'PySol - General Hex A Deck Card Rules'),
('howtoplay.html', 'How to play PySol'),
('index.html', 'PySol - a Solitaire Game Collection'),
('install.html', 'PySol - Installation'),
('intro.html', 'PySol - Introduction'),
('license.html', 'PySol Software License'),
('news.html', 'PySol - a Solitaire Game Collection'),
#('rules_alternate.html', 'PySol - a Solitaire Game Collection'),
#('rules.html', 'PySol - a Solitaire Game Collection'),
]
rules_files = [
#('hanoipuzzle.html', ),
('mahjongg.html', 'PySol - Rules for Mahjongg'),
('matrix.html', 'PySol - Rules for Matrix'),
('pegged.html', 'PySol - Rules for Pegged'),
('shisensho.html', 'PySol - Rules for Shisen-Sho'),
('spider.html', 'PySol - Rules for Spider'),
('freecell.html', 'PySol - Rules for FreeCell'),
]
wikipedia_files = [
('houseinthewood.html', 'PySol - Rules for House in the Woods'),
('fourseasons.html', 'PySol - Rules for Four Seasons'),
]
main_header = '''<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<title>%s</title>
<meta name="license" content="Distributed under the terms of the GNU General Public License">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#F7F3FF" link="#0000FF" vlink="#660099" alink="#FF0000">
<img src="images/pysollogo03.gif" alt="">
<br>
'''
main_footer = '''
<p>
<br>
%s
</body>
</html>'''
rules_header = '''<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<title>%s</title>
<meta name="license" content="Distributed under the terms of the GNU General Public License">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#F7F3FF" link="#0000FF" vlink="#660099" alink="#FF0000">
<img src="../images/pysollogo03.gif" alt="">
<br>
'''
rules_footer = '''
<p>
%s
<br>
<a href="../glossary.html">Glossary</a>
<br>
<a href="../general_rules.html">General rules</a>
<p>
<a href="../index.html">Back to the index</a>
</body>
</html>'''
wikipedia_header = '''<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<title>%s</title>
<meta name="license" content="Distributed under the terms of the GNU Free Documentation License">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#F7F3FF" link="#0000FF" vlink="#660099" alink="#FF0000">
<img src="../images/pysollogo03.gif" alt="">
<br>
'''
def getGameRulesFilename(n):
if n.startswith('Mahjongg'): return 'mahjongg.html'
##n = re.sub(r"[\[\(].*$", "", n)
n = latin1_to_ascii(n)
n = re.sub(r"[^\w]", "", n)
n = n.lower() + ".html"
return n
def gen_main_html():
for infile, title in files:
outfile = open(os.path.join('html', infile), 'w')
print >> outfile, main_header % title
print >> outfile, open(infile).read()
s = '<a href="index.html">Back to the index</a>'
if infile == 'index.html':
s = ''
print >> outfile, main_footer % s
def gen_rules_html():
##ls = glob(os.path.join('rules', '*.html'))
rules_ls = os.listdir('rules')
rules_ls.sort()
wikipedia_ls = os.listdir('wikipedia')
wikipedia_ls.sort()
games = GAME_DB.getGamesIdSortedByName()
rules_list = []
files_list = []
for fn, tt in rules_files:
rules_list.append(('rules', fn, tt, ''))
files_list.append(fn)
for fn, tt in wikipedia_files:
rules_list.append(('wikipedia', fn, tt, ''))
files_list.append(fn)
altnames = []
# open file of list of all rules
out_rules = open(os.path.join('html', 'rules.html'), 'w')
print >> out_rules, main_header % 'PySol - a Solitaire Game Collection'
print >> out_rules, open('rules.html').read()
for id in games:
# create list of rules
gi = GAME_DB.get(id)
rules_fn = gi.rules_filename
if not rules_fn:
rules_fn = getGameRulesFilename(gi.name)
if rules_fn in files_list:
continue
if rules_fn in rules_ls:
rules_dir = 'rules'
elif rules_fn in wikipedia_ls:
rules_dir = 'wikipedia'
else:
print 'missing rules for %s (file: %s)' \
% (gi.name.encode('utf-8'), rules_fn)
continue
##print '>>>', rules_fn
title = 'PySol - Rules for ' + gi.name
s = ''
if gi.si.game_type == GI.GT_HANAFUDA:
s = '<a href="../hanafuda.html">General Flower Card rules</a>'
elif gi.si.game_type == GI.GT_DASHAVATARA_GANJIFA:
s = '<a href="../ganjifa.html">About Ganjifa</a>'
elif gi.si.game_type == GI.GT_HEXADECK:
s = '<a href="../hexadeck.html">General Hex A Deck rules</a>'
elif gi.si.game_type == GI.GT_MUGHAL_GANJIFA:
s = '<a href="../ganjifa.html">About Ganjifa</a>'
#print '***', gi.name, '***'
rules_list.append((rules_dir, rules_fn, title, s))
files_list.append(rules_fn)
#rules_list.append((rules_fn, gi.name))
print >> out_rules, '<li><a href="rules/%s">%s</a>' \
% (rules_fn, gi.name.encode('utf-8'))
for n in gi.altnames:
altnames.append((n, rules_fn))
print >> out_rules, '</ul>\n' + \
main_footer % '<a href="index.html">Back to the index</a>'
# create file of altnames
out_rules_alt = open(os.path.join('html', 'rules_alternate.html'), 'w')
print >> out_rules_alt, main_header % 'PySol - a Solitaire Game Collection'
print >> out_rules_alt, open('rules_alternate.html').read()
altnames.sort()
for name, fn in altnames:
print >> out_rules_alt, '<li> <a href="rules/%s">%s</a>' \
% (fn, name.encode('utf-8'))
print >> out_rules_alt, '</ul>\n' + \
main_footer % '<a href="index.html">Back to the index</a>'
# create rules
for dir, filename, title, footer in rules_list:
outfile = open(os.path.join('html', 'rules', filename), 'w')
if dir == 'rules':
print >> outfile, (rules_header % title).encode('utf-8')
else: # d == 'wikipedia'
print >> outfile, (wikipedia_header % title).encode('utf-8')
print >> outfile, open(os.path.join(dir, filename)).read()
print >> outfile, rules_footer % footer
gen_main_html()
gen_rules_html()

38
data/html-src/general_rules.html Normal file
View file

@ -0,0 +1,38 @@
<h1>General Rules</h1>
<p>
There are some characteristics common to all the games in this package.
Most of them are played with standard 52-card decks, either one or two. The
cards in each suit are ranked King high. K stands for King, Q stands for
Queen and J stands for Jack. In each game, the cards are piled up in either
ascending or descending order, on stacks in the main playing area, called
the Tableau, or piles off to the side, called Foundations. Some piles must
be built up in sequence within the same suit, and others are built up in
suits of alternating colors.
<p>
The Talon is the stack of cards remaining in the deck, not yet played
upon any of the piles, and not yet placed in the discard pile. Some people
also call it the Stock or the Hand.
<p>
The object of each of these games is to use up all the cards in
building Foundations, or to use up all cards in the Talon according to the
rules of the particular game. If all the cards are used up, you win. If
not, you lose.
<p>
In all of the games, you deal cards from the Talon to the discard pile
by clicking once on the Talon with the left mouse button, or pressing &lt;D&gt;.
Where permitted by the rules, you can turn over any face-down card with a
single click of the left mouse button. You pick up and move a card by
clicking on it and holding the button down while you drag it to its intended
destination. If the move would violate the rules, the card will not go
anywhere. If any card or cards can be put on a
Foundation, or in the Ace discard pile of Picture Gallery, a single press of
the &lt;A&gt; key will do all of them, a handy way to quickly finish certain
games. Sometimes the &lt;A&gt; key will build up the Foundations more than you
would like, and these rules allow you to put cards back into the Tableau
from the Foundations. Of course, you can also use the Undo key &lt;Z&gt;.
<p>
If you're confused by all this, just watch a demo game :-)

240
data/html-src/glossary.html Normal file
View file

@ -0,0 +1,240 @@
<h1>Glossary</h1>
<p>Author's note: These definitions are meant as a guideline only.
See individual game rules as any game has the right to redefine or
modify the rules to make it fun.</p>
<dl>
<dt><b>BASE CARD</b></dt>
<dd>
<p>The first card dealt into a foundation pile. Other foundations
usually have to start with a card of this rank. See: FOUNDATION</p>
</dd>
<dt><b>BUILD BY ALTERNATE COLOR</b></dt>
<dd>
<p>Building by placing a card on to another card of the opposite
color is permitted. Example: Placing a Diamond on a Spade is good,
but placing a Diamond on a Heart is not.</p>
</dd>
<dt><b>BUILD BY ANY SUIT BUT OWN</b></dt>
<dd>
<p>Building by placing a card on to another card of any suit but
the suit of the original card is permitted. Example: Placing a
Diamond on a Heart is good, but placing a Heart on a Heart is
not.</p>
</dd>
<dt><b>BUILD BY COLOR</b></dt>
<dd>
<p>Building by placing a card on to another card of the same color
is permitted. Example: Placing a Diamond on a Heart is good, but
Placing a Diamond on a Club is not.</p>
</dd>
<dt><b>BUILD BY RANK</b></dt>
<dd>
<p>BUILD DOWN or UP ignoring color and suit.</p>
</dd>
<dt><b>BUILD REGARDLESS OF SUIT</b></dt>
<dd>
<p>See BUILD BY RANK.</p>
</dd>
<dt><b>BUILD BY SUIT</b></dt>
<dd>
<p>Building by placing a card on to another card of the same suit
is permitted. Example: Placing a Spade on a Spade is good, but
placing a Spade on a Club is not.</p>
</dd>
<dt><b>BUILD DOWN</b></dt>
<dd>
<p>Building by placing a card of a lower rank on to a card of a
higher rank is permitted. Usually implies a difference of only one
ranking between the two cards. Example: Placing a 10 on a Jack is
good, but placing a 10 on a 9 is not.</p>
</dd>
<dt><b>BUILD DOWN BY *</b></dt>
<dd>
<p>Building by placing a card of a lower rank on to a card of a
higher rank by * is permitted. Example: If * is 2, placing a 10 on
a Queen is good, but placing a 10 on a Jack is not.</p>
</dd>
<dt><b>BUILD UP</b></dt>
<dd>
<p>Building by placing a card of a higher rank on to a card of a
lower rank is permitted. Usually implies a difference of only one
ranking between the two cards. Example: Placing a Queen on a Jack
is good, but placing a Queen on a King is not.</p>
</dd>
<dt><b>BUILD UP BY *</b></dt>
<dd>
<p>Building by placing a card of a higher rank on to a card of a
lower rank by * is permitted. Example: If * is 2, placing a 10 on
an 8 is good, but placing a 10 on a 9 is not.</p>
</dd>
<dt><b>BUILD UP OR DOWN</b></dt>
<dd>
<p>Building by placing a card on to a card of one higher or one
lower rank is permitted. Example: Placing a Jack on a Queen or a 10
is good, but placing a 10 on a Queen is not.</p>
</dd>
<dt><b>BUILDING</b></dt>
<dd>
<p>The ability to place a card (or group of cards) on another card.
In regards to rank, you can BUILD UP, BUILD DOWN, or BUILD UP/DOWN
BY *. In regards to suit/color, you can BUILD BY SUIT, BUILD BY
COLOR, BUILD BY ALTERNATE COLOR, BUILD BY ANY SUIT BUT OWN, or
BUILD REGARDLESS OF SUIT. Note that all games that build will
follow two of these rules, one from each list.</p>
</dd>
<dt><b>DECK</b></dt>
<dd>
<p>The set of cards used. Most games use a STANDARD DECK, but games
that use a DOUBLE DECK, a JOKER DECK, or a STRIPPED DECK are not
uncommon.</p>
</dd>
<dt><b>DOUBLE DECK</b></dt>
<dd>
<p>A deck of cards consisting of two STANDARD DECKS making a total
of 104 cards.</p>
</dd>
<dt><b>FOUNDATION</b></dt>
<dd>
<p>If a game has a foundation, the game is usually won by placing
all the cards in the foundation pile(s).</p>
</dd>
<dt><b>JOKER DECK</b></dt>
<dd>
<p>A deck of cards consisting of a STANDARD DECK and two jokers
making a total of 54 cards.</p>
</dd>
<dt><b>PILE</b></dt>
<dd>
<p>A designated area where cards can exist.</p>
</dd>
<dt><b>RANK</b></dt>
<dd>
<p>The value of the card. Numbered cards usually have the rank of
the associated number. Aces can either be high or low. If high,
aces are ranked 1. If low, aces are ranked as 14. J, Q, and K are
usually ranked 11, 12, and 13 respectively. However, some games may
rank these cards as 10. In such a case, a high ace might be ranked
as 11.</p>
</dd>
<dt><b>RESERVE</b></dt>
<dd>
<p>Cards in the reserve are usually available to play anywhere.
Usually cannot be built on.</p>
</dd>
<dt><b>SLOT</b></dt>
<dd>
<p>See PILE.</p>
</dd>
<dt><b>STANDARD DECK</b></dt>
<dd>
<p>A 52 card deck. There are four suits of thirteen cards
each. Each suit contains an Ace, 2 through 10, Jack, Queen, and
King. These suits are usually Clubs, Spades, Hearts and Diamonds.
These suits can be grouped into two colors, usually black and red.
The Clubs and the Spaces are black while the Hearts and the
Diamonds are red. PySol allows the possibility of using
different decks. In this case, the new colors and/or suits are
substituted into this paradigm.</p>
</dd>
<dt><b>STRIPPED DECK</b></dt>
<dd>
<p>A 32 card deck. There are four suits of eight cards
each. Each suit contains an Ace, 7 through 10, Jack, Queen, and
King.</p>
</dd>
<dt><b>STOCK</b></dt>
<dd>
<p>See TALON.</p>
</dd>
<dt><b>SUIT</b></dt>
<dd>
<p>Four different kinds in a STANDARD DECK. Usually Clubs, Spades,
Hearts, and Diamonds.</p>
</dd>
<dt><b>TABLEAU</b></dt>
<dd>
<p>The playing field, where the main action occurs. Usually allows
building.</p>
</dd>
<dt><b>TALON</b></dt>
<dd>
<p>The remainder of the deck after all the original cards have been
dealt and are usually kept faced down.</p>
</dd>
<dt><b>VALUE</b></dt>
<dd>
<p>See RANK.</p>
</dd>
<dt><b>WASTE</b></dt>
<dd>
<p>A stack of cards face up, usually next to the TALON. Top card
usually in play.</p>
</dd>
<dt><b>WRAP AROUND</b></dt>
<dd>
<p>In some games card sequences may wrap around.
When BUILDING UP this means you can place an Ace on a King.
When BUILDING DOWN this means you can place a King on an Ace.</p>
</dd>
</dl>

21
data/html-src/hanafuda.html Normal file
View file

@ -0,0 +1,21 @@
<h1>General Flower Card Rules</h1>
<p>
There are some characteristics common to all the games played with Hanafuda
cards. They are all played with one or more of the Asian flower card decks.
This deck is common in a number of Pacific regions including Hawaii. There are
twelve suits of four cards each. The suits are associated with the twelve
months of the year. For a good explanation of what the suits are, try Graham
Leonard's Hanafuda and Kabufuda site at
<a href="http://hana.kirisame.org/">http://hana.kirisame.org/</a>
<p>
Most of the flower card solitaire games are played like western deck games
with minor changes. See the <a href="general_rules.html">General Rules</a> for
basic instructions on how to play solitaire. The object in most cases is to
move all the cards from the tableau to the foundations. Probably the most
difficult part of learning to play with hanafuda cards is learning which cards
belong in which suits and what their ranking is. The ranking of the suits is
sometimes as important as the ranking of the cards in the suit. Try keeping
this hanafuda help image displayed where you can refer to it as you play.
<img alt="" src="images/hanahelp.gif">

21
data/html-src/hexadeck.html Normal file
View file

@ -0,0 +1,21 @@
<h1>General Hex A Deck Card Rules</h1>
The Hex A Deck is similar to a few card packs published in the early 20th
century that had sixteen cards in each suit. Those decks were intended to
be used when popular games of the period such as Whist were played by five
or more players. The extra cards meant that each player had more cards in their
hand which added interest to the play. The Wizards in the Hex A Deck corresponds
to the Jokers in a regular pack. Their main purpose in most Hex A Deck games
is to show up at the worst possible time. Either that or at the best possible
time. They're very successful at doing that. In games that use alternate
color stacks they may be played as either color. They have ranks from one
through four and sometimes can only be played in rank order. The ranks may
or may not be indicated on the cards. If they are not indicated there is
usually a way to tell which is which. The rank can be determined by comparing
some distinctive element of the images. The first rank Wizard will be the most
elaborate in some way such as the fattest, having the tallest hat etc. They
play on their foundation (if any) in descending order of rank. That is first
through fourth. In some games the Wizards will not move off of the tableau
until all the other cards have been moved to the foundations. In some games
they don't actually enter into play at all. They are just there to make
things interesting. Which is to say make things difficult. And they are
very good at doing that.

131
data/html-src/howtoplay.html Normal file
View file

@ -0,0 +1,131 @@
<h1>How to play PySol</h1>
<h2>Mouse Usage</h2>
<p>
Left mouse button:
<ul type="disc">
<li> Drag cards around
<li> Click on the Talon to deal new cards
</ul>
<p>
Right mouse button (or double-click the left button):
<ul type="disc">
<li> Drop cards to the Foundations
<li> Quick play (if enabled)
</ul>
<p>
Middle mouse button (or Ctrl-click the right button):
<ul type="disc">
<li> View partially overlapped cards
</ul>
<p>
Ctrl-click the left mouse button:
<ul type="disc">
<li> Highlight all matching cards on the table
</ul>
<p>
Shift-click the left mouse button:
<ul type="disc">
<li> Highlight all cards with the same rank.
</ul>
<h2>Two-handed play</h2>
<p>
Put three fingers of one hand on '<i>A</i>' (auto drop),
'<i>S</i>' (undo) and '<i>D</i>' (deal).
You can also reach '<i>R</i>' (redo) from there.
<p>
Left-handed people may prefer using '<i>L</i>' (auto drop),
'<i>K</i>' (undo) and '<i>J</i>' (deal).
<!--
<h2>Point-and-Click play</h2>
<p>
If you prefer Point-and-Click over Drag-and-Drop you can enable
<i>Quick play</i> and use the right mouse button. See below.
-->
<h2>Automatic play</h2>
<p>
Note that automatic play can spoil the gameplay, so purists should
not enable any option but maybe <i>Auto face up</i>. Also, some games
disable certain features as they would be trivial otherwise.
<p>
Auto face up
<ul type="disc">
<li> Automatically face up all cards.
</ul>
Auto drop
<ul type="disc">
<li> Automatically drop cards to the Foundations.
</ul>
Auto deal
<ul type="disc">
<li> Automatically deal cards to the Waste stack if it is empty.
</ul>
Quick play
<ul type="disc">
<li> Use the right mouse button to move piles around quickly.
The logic involved is not too clever on purpose
(i.e. it does not consult the hint system).
</ul>
<h2>The animation is too slow...</h2>
<p>
Unfortunately the Tcl/Tk toolkit lacks a sprite concept, so
there is a lot of (invisible double-buffered) redraw going on
when dragging cards around.
<p>
Disabling <i>Card shadow</i>, <i>Shade legal moves</i>,
background table tiles and sound will somewhat improve the display speed.
<h2>The table tiles look strange</h2>
<p>
Background table tiles should only be enabled when using
a true-color video mode - otherwise they may look bad
because of dithering.
<p>
BTW, you can add your own background tiles by copying the images
to the main <i>data/tiles</i> or your home <i>~/.PySolFC/tiles</i> directory.
<!-- They must be in GIF or PPM format. -->
<h2>Some notes about scoring</h2>
<p>
<ul type="disc">
<li> Scoring only begins after you make your first move.
Also, if you undo all your moves back to the start
the game won't score either.
<li> You will lose a game if you consume a hint or start demo mode.
<li> You can restart any time to get another chance to win this game.
<li> If you don't want to score a lost game you can temporarily change
the player options.
<li> Loaded games don't count.
<li> If you win a game without using <i>Undo</i>, <i>Quick play</i> and
any other of the assist functions you will be given special awards.
<!--
<li> There are no score values in PySol - you win a game, or you lose it.
And don't even think about asking me to implement this nonsense - get
a nice pinball game if you're a highscore freak...
-->
<li> And finally always remember that this is a <b>Patience</b> game.
Relax and enjoy.
</ul>
<h2>Undocumented key bindings</h2>
<ul type="disc">
<li> <i>Space</i> - Deal
<li> <i>S</i> - Undo
<li> <i>Backspace</i> - Undo
<li> <i>Ctrl-A</i> - Auto drop and face up cards in one step
<li> <i>Ctrl-B</i> - Change card background
<li> <i>Ctrl-H</i> - Show internal rating when giving a hint
<li> <i>Ctrl-I</i> - Change table tile
<li> <i>Ctrl-N</i> - Start a new game with the next game number
<li> <i>Ctrl-P</i> - Change player name
<li> <i>Ctrl-U</i> - Play the next music song
</ul>

BIN
data/html-src/images/c.gif Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 80 B

BIN
data/html-src/images/camelot-goal.gif Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 30 KiB

BIN
data/html-src/images/d.gif Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 70 B

BIN
data/html-src/images/h.gif Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 73 B

BIN
data/html-src/images/hanahelp.gif Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 76 KiB

BIN
data/html-src/images/pysollogo00.gif Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 2.2 KiB

BIN
data/html-src/images/pysollogo01.gif Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 18 KiB

BIN
data/html-src/images/pysollogo02.gif Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 13 KiB

BIN
data/html-src/images/pysollogo03.gif Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 4 KiB

BIN
data/html-src/images/s.gif Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 76 B

29
data/html-src/index.html Normal file
View file

@ -0,0 +1,29 @@
<h1>PySol - a Solitaire Game Collection</h1>
<hr>
<p> <a href="intro.html">Introduction</a>
<p> <a href="install.html">Installation</a>
<p> <a href="howtoplay.html">How to play</a>
<h2>Rules</h2>
<ul>
<li> <a href="glossary.html">Glossary</a>
<li> <a href="general_rules.html">General Rules</a>
<li> <a href="rules.html">Individual Game Rules</a>
<li> <a href="rules_alternate.html">Alternate Names</a>
</ul>
<!-- <p> <a href="news.html">What's new ?</a> -->
<p> <a href="license.html">PySol license terms</a>
<p>
<hr>
<!--
<p> Visit the official <a href="http://www.oberhumer.com/pysol">PySol Home Page</a>
<p>Copyright (C) 1998, 1999, 2000, 2001, 2002, 2003 by <a href="mailto:markus@oberhumer.com">Markus F.X.J. Oberhumer</a>.<br>
All Rights Reserved.
-->
<p>
PySol is distributed under the terms of the
<a href="license.html">GNU General Public License</a>.

47
data/html-src/install.html Normal file
View file

@ -0,0 +1,47 @@
<h1>Installation</h1>
<p>
There is no need to compile anything since the whole program is just
a Python script. Just run it, and that's all.
<p>
PySol requires Python 1.5.2 and Tcl/Tk 8.0.5 or better. Both packages are
freely available for Unix, Windows and Macintosh platforms.
<p>
PySol is free <i>Open Source</i> software distributed under the terms of the
<a href="license.html">GNU GPL</a>.
<h2>Windows 95/98/ME/NT/2000</h2>
PySol now ships as a completely self-contained setup file, so there's
no need to install anything else.
<p>
If you want to modify the PySol source code or write your own
Python programs you can get the development system from
<a href="http://www.python.org/download/download_windows.html">http://www.python.org/download/download_windows.html</a>
<h2>Unix</h2>
There are good chances that your system already ships with Python and Tcl/Tk.<br>
Otherwise visit
<a href="http://www.python.org/download/">http://www.python.org/download/</a>
for full source code.
<p>
Also, installable packages exist for all major Linux distributions,
FreeBSD and HPUX.
<h2>Macintosh</h2>
Self installing exectuables for Python and Tcl/Tk are available from<br>
<a href="http://www.python.org/download/download_mac.html">http://www.python.org/download/download_mac.html</a>
<p>
As I don't have access to a Mac I'd appreciate any detailed feedback on
installation and look & feel. "Porting" from X11 to Windows only required some
minor changes in the default font settings, so I hope the situation on Macs is
similar.
<p>
[ I have been told that PySol works fine on a Mac - just drop "pysol.py"
on the Python interpreter and that's it. But for some reason you must
assign a large amount of memory to the Python interpreter. ]

39
data/html-src/intro.html Normal file
View file

@ -0,0 +1,39 @@
<h1>Introduction</h1>
<p>
"Why yet another solitaire game ?" you may ask.
The answer is simple...
<h3>PySol highlights</h3>
<ul>
<li> currently supports more than 200 distinct solitaire games
<li> based upon an extensible solitaire engine
<li> lots of classic games like Forty Thieves, FreeCell, Klondike and Spider
<li> special games like Ganjifa, Hanafuda, Poker and Tarock type games
<li> very nice look and feel
<li> multiple cardsets and backgrounds
<li> background table tiles
<li> unlimited undo &amp; redo
<li> persistent bookmarks
<li> load &amp; save games
<li> player statistics
<li> hint system
<li> demo games
<li> support for user written plug-ins
<li> sound samples and background music
<li> integrated HTML help browser
<li> lots of documentation
<li> portable across Unix/X11, Windows 95/98/2000/NT and MacOS
<li> written in 100% pure Python
<li> distributed under the terms of the GNU General Public License
<li> <i>Commercial Quality Freeware</i>
</ul>
<!--
<h3>Legal terms</h3>
<p>
PySol is Copyright (C) 1998, 1999, 2000, 2001, 2002, 2003 by <a href="mailto:markus@oberhumer.com">Markus F.X.J. Oberhumer</a>.<br>
All Rights Reserved.
<p>
PySol is distributed under the terms of the
<a href="license.html">GNU General Public License</a>.
-->

331
data/html-src/license.html Normal file
View file

@ -0,0 +1,331 @@
<p align="center">
<b>GNU GENERAL PUBLIC LICENSE</b><br>
Version 2, June 1991
</p>
<p align="center">
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
675 Mass Ave, Cambridge, MA 02139, USA
<br>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
</p>
<hr>
<p align="center"><b>Preamble</b>
<p>
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
Foundations 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.
<p>
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.
<p>
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.
<p>
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.
<p>
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.
<p>
Also, for each authors 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.
<p>
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 everyones free use or not licensed at all.
<p>
The precise terms and conditions for copying, distribution and
modification follow.
<hr>
<p align="center">
<b>
GNU GENERAL PUBLIC LICENSE<br>
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
</b>
<p>
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".
<p>
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.
<p>
1. You may copy and distribute verbatim copies of the Programs
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.
<p>
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.
<p>
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:
<blockquote>
<p>
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
<p>
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.
<p>
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.)
</blockquote>
<p>
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.
<p>
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.
<p>
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.
<p>
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:
<blockquote>
<p>
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,
<p>
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,
<p>
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.)
</blockquote>
<p>
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.
<p>
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.
<p>
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.
<p>
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.
<p>
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.
<p>
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.
<p>
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.
<p>
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.
<p>
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.
<p>
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.
<p>
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.
<hr>
<p align="center"><b>NO WARRANTY</b>
<p>
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.
<p>
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.
<p align="center"><b>END OF TERMS AND CONDITIONS</b>

221
data/html-src/news.html Normal file
View file

@ -0,0 +1,221 @@
<pre>
==================================================================
User visible changes for PySol - a solitaire game collection
==================================================================
Changes in 4.82 (02 Sep 2003, 202 games)
* support Python 2.3
- a number of small bug fixes
+ stay tuned for Pysol 5 with *lots* of improvements :-)
Changes in 4.81 (24 Jun 2002, 202 games)
* adapted for new pysol-sound-server 3.00
- fixed Spider-type games
Changes in 4.80 (28 Nov 2001, 202 games)
* support Python 2.2
Changes in 4.73 (28 Sep 2001, 202 games)
- fixed rules of Irmgard
- a number of other bug fixes
Changes in 4.72 (31 May 2001, 202 games)
- fixed a problem when using hints in Black Hole
Changes in 4.71 (20 Apr 2001, 202 games)
* improved dynamic scrollbar handling
* support both Python 1.5, Python 2.0 and Python 2.1 within one package
Changes in 4.70 (05 Mar 2001, 202 games)
* 1 new game
* added dynamic scrollbars
* support both Python 1.5 and Python 2.0 within one package
* fixed some minor problems
Changes in 4.60 (02 Aug 2000, 201 games)
* 6 new games
* added persistent bookmarks
* implemented smart playing that keeps the redo history
* new statistics dialog featuring real 3D bar charts
- Windows: fixed a problem where the sound could cause crashes
- corrected a number of game rules and descriptions
Changes in 4.50 (11 Jun 2000, 195 games)
* added support for small toolbar icons
* added "Alternate Names" to the game selection dialog
* improved the sound dialog
- moved the Mahjongg games to the new PyJongg package
Changes in 4.41 (30 May 2000, 195 games)
* 6 new games
- Windows: avoid loading incompatible DLLs from the system directory
Changes in 4.30 (23 May 2000, 189 games)
* 6 new games
- fixed an internal error in Grasshopper and Double Grasshopper
- corrected rules of Penguin
Changes in 4.20 (27 Apr 2000, 183 games)
* 14 new games, including HexADeck and Memory type variants
* added a "Recent games" menubar entry
* improved statistics dialog
- really fixed the detection of Straights in Poker type games
- fixed a problem when changing the card background
Changes in 4.10 (18 Apr 2000, 169 games)
- fixed a memory leak
Changes in 4.00 (12 Apr 2000, 169 games)
* PySol now plays Tarock type games
* display a floating "Demo" logo while playing demo games
* options are now saved automatically at program exit
- Poker type games: cards for a Straight can now be in any sequence
- fixed a scoring problem in Casino Klondike and Vegas Klondike
Changes in 3.40 (12 Feb 2000, 161 games)
* 3 new games
* updated the pysol-sound-server
- fixed a problem with winning in Golf type games
- some other minor fixes
Changes in 3.30 (26 Jan 2000, 158 games)
* 7 new games
* converted the pysol-sound-server into a Python extension module
Changes in 3.21 (21 Jan 2000, 151 games)
* 2 new games
* updated the pysol-sound-server
- Windows: added the missing PyWinTypes15.dll to the setup file
Changes in 3.20 (18 Jan 2000, 149 games)
* added 8 Hanafuda type games (Oonsoo, Pagoda, MatsuKiri, ...)
* added 2 Poker type games (Poker Shuffle, Poker Square)
* added 13 other new games (Der Katzenschwanz, Perpetual Motion,
Die Schlange, Three Shuffles and a Draw, Vegas Klondike, ...)
* background music is supported under Win32 as well
- corrected redeal rules of La Belle Lucie and Trefoil
- corrected rules of Aces Up
Changes in 3.10 (21 Dec 1999, 126 games)
* 17 new games
* new sound support (including background MP3 and MOD music under Unix)
* added a playable preview dialog (yes, you can play games there :-)
* nice cardset and table-tile select dialogs
* added "Hold and quit" to continue a game on next start
- quite a number of bug and feature fixes
Changes in 3.00 (04 Nov 1999, 111 games)
* bought a new solitaire book and implemented 67 new games :-)
* added a menubar entry for popular games
* new assist function: highlight all cards with the same rank
(shift-click the left mouse button)
* added images for the Talon redeal state
* FreeCell game numbers are now compatible to the FreeCell FAQ
* added a "Next number" button to the game number dialog
* improved statistics and log views
* the bundled version now ships as pre-compiled Python bytecode
because it loads faster and uses much less memory
- corrected some layout problems
Changes in 2.99 (13 Oct 1999, 44 games)
* 1 new game: Lara's Game
* re-enabled the relaxed game variants
* due to popular demand I've finally implemented "Quick play"
* statistics and logs can be exported to a file
* a huge number of other improvements
- saved games are not compatible with previous versions
- some changes in key and mouse bindings
Changes in 2.91 (23 Jun 1999, 43 games)
- check for Python 1.5.2 at program startup
- some other minor fixes
Changes in 2.90 (16 Jun 1999, 43 games)
* added 19 new games (2 games disabled)
* implemented a nice select-game tree dialog
* starting a new game is noticeably faster now
* documentation updated
- PySol now requires Python 1.5.2
Changes in 2.14 (26 May 1999, 24 games)
- fixed rules of Calculation which got broken in 2.02
Changes in 2.13 (13 May 1999, 24 games)
- fixed a small bug in "Select game by number..."
Changes in 2.12 (20 Apr 1999, 24 games)
- another small bug fix
Changes in 2.11 (07 Apr 1999, 24 games)
- some finor fixes
Changes in 2.10 (11 Mar 1999, 24 games)
* major display speed improvements
* added support for background table tiles
* rearranged source code to prepare for a future Gnome, KDE,
wxWindows or JPython/Swing version
- fixed rules of Spider and Divorce which got broken in 2.02
Changes in 2.02 (20 Jan 1999, 24 games)
* 1 new game: Canfield
* new assist function: autoplay
* new assist function: automatic face up
* new assist function: highlight all matching cards
(control-click the left mouse button)
* can change card background
* support for timer-based animations
* improved interaction with the window manager (X11)
Changes in 2.01 (21 Dec 1998, 23 games)
* 4 new games: Eight Off, Dead King Golf, Relaxed Golf and Grandfather's Clock
* created new package PySol-Cardsets - get it from the PySol home page
* implemented a statusbar
* new assist function: highlight all moveable piles
* enabled tearoff menus under Unix
* improved table layout with small and large cardsets
Changes in 2.00 (30 Nov 1998, 19 games)
* 2 new games: Calculation and Numerica
* implemented support for plugins - now you can easily add your own games
* new option to automatically shade legal moves
* added additional cardsets for low and high screen resolutions
* major source code rearrangements
Changes in 1.12 (13 Oct 1998, 17 games)
* display a progress bar during startup
Changes in 1.11 (09 Oct 1998, 17 games)
* 3 new games: Big Harp, Eiffel Tower and Matriarchy
* enhanced statistics, can change player name
* added "Select game by number"
* implemented tooltips
- some fixes for Windows (vanishing menubar, problems when $HOME was
not set, better toplevel geometry)
- corrected rules of Ground for a Divorce
Changes in 1.10 (02 Oct 1998, 14 games)
* 1 new game: Ground for a Divorce
* added a toolbar
* implemented shadows
Changes in 1.03 (26 Sep 1998, 13 games)
* 4 new games: Spider, Relaxed Spider, Braid and Forty Thieves
* middle mouse button (or Control-left) shows partially hidden cards
* menus restructured
* major source code rearrangements
Changes in 1.02 (16 Sep 1998, 9 games)
* 1 new game: Picture Gallery
* added strict-rules variants of FreeCell and Seahaven Towers
* added a small manual page
* improved animation speed
Changes in 1.01 (14 Sep 1998, 6 games)
* 2 new games: FreeCell and Seahaven Towers
* the Undo key is now bound both to 'z' as well as 's'
Changes in 1.00 (10 Sep 1998, 4 games)
* includes 4 games: Gypsy, Irmgard, 8x8 and Klondike
* first public release
</pre>

10
data/html-src/rules.html Normal file
View file

@ -0,0 +1,10 @@
<h1>PySol - Game Rules</h1>
<hr>
<h2>Basic Concepts</h2>
<ul>
<li> <a href="glossary.html">Glossary</a>
<li> <a href="general_rules.html">General Rules</a>
</ul>
<h2>Game Rules</h2>
<ul>

20
data/html-src/rules/10x8.html Normal file
View file

@ -0,0 +1,20 @@
<h1>10 x 8</h1>
Klondike type. Two decks. Unlimited redeals.
<h3>Object</h3>
Move all cards to the Foundations.
<h3>Quick description</h3>
Similar to <a href="8x8.html">8 x 8</a>
with ten rows and
<a href="../hexadeck.html">Hex A Deck</a>
variations.
<h3>Rules</h3>
Game play is like 8 x 8. The rows build down in rank in alternate
color. The Wizards will play in their proper rank position on the
tableau as the alternate of either red or black. Any card or sequence
may be played on an empty row. Cards are dealt from the talon one at
a time. Cards may be played from the foundations.
<h3>Strategy</h3>
Try to open a row to the canvas.

24
data/html-src/rules/8x8.html Normal file
View file

@ -0,0 +1,24 @@
<h1>8 x 8</h1>
<p>
Klondike type. 2 decks. Unlimited redeals.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
As the name implies, the eight playing
piles in the tableau all start with eight cards face-up.
<p>
Piles build down by alternate color, and an empty space can be filled
with any card or sequence.
<p>
When you click on the talon, one card is turned over onto the waste pile.
There is no limit to the number of times you go through the talon.
<p>
You are also permitted to move cards back out of the foundation.
<h3>Strategy</h3>
<p>
Try to go for an empty space.

38
data/html-src/rules/abacus.html Normal file
View file

@ -0,0 +1,38 @@
<h1>Abacus</h1>
<p>
Yukon type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the Foundations.
<h3>Quick Description</h3>
<p>
A combination of
<a href="yukon.html">Yukon type</a>
and
<a href="calculation.html">Calculation type</a>
game elements.
<h3>Rules</h3>
<p>
The four Foundations build up by suit the following way:
The first pile from Ace, by one. The second pile from Two, by two.
The third pile from Three, by three. The fourth pile from Four, by four.
<pRE>
Club: A 2 3 4 5 6 7 8 9 T J Q K
Spade: 2 4 6 8 T Q A 3 5 7 9 J K
Heart: 3 6 9 Q 2 5 8 J A 4 7 T K
Diamond: 4 8 Q 3 7 J 2 6 T A 5 9 K
</pRE>
<p>
Cards in Tableau are built down by suit, the ranks going
the opposite way as the foundations:
Club down by one, Spade down by two, Heart down by three and
Diamond down by four.
<p>
Groups of cards can be moved regardless of sequence,
and an empty space can be filled with any card or sequence.
<p>
When no more moves are possible, click on the Talon. One card will be
added to each of the playing piles.

27
data/html-src/rules/acesup.html Normal file
View file

@ -0,0 +1,27 @@
<h1>Aces Up</h1>
<p>
One-Deck game type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards except the four Aces to the single foundation.
<h3>Rules</h3>
<p>
Any top card that is of lower rank and of the same suit of another
top card may be dropped to the foundation. Aces rank high.
<p>
There is no building on the tableau, except that an empty pile
may be filled with any card.
<p>
When no more moves are possible, click on the talon. One card will be
added to each of the playing piles.
<h3>Notes</h3>
<p>
<i>Autodrop</i> is disabled for this game.
<h3>History</h3>
<p>
This simple game is known by many names, such as
<i>Aces High</i>, <i>Drivel</i> and <i>Idiot's Delight</i>.

16
data/html-src/rules/acesup5.html Normal file
View file

@ -0,0 +1,16 @@
<h1>Ace Up 5</h1>
<p>
One-Deck game type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards except the four Aces to the single foundation.
<h3>Quick Description</h3>
<p>
Like <a href="acesup.html">Aces Up</a>,
but five piles.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

25
data/html-src/rules/agnessorel.html Normal file
View file

@ -0,0 +1,25 @@
<h1>Agnes Sorel</h1>
<p>
Gypsy type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
Cards in the Tableau are built down by same color. Groups of cards in sequence
and same color can be moved as a unit.
<p>
Each deal flips one card from the Stock to each pile of the Tableau. There are
no redeals.
<p>
Foundations are built up in suit in sequence, wrapping from King to Ace when
necessary. Cards in Foundations are still in play. Double clicking on a card
in the Tableau will move it to the appropriate Foundation pile if such a move
is possible.
<h3>Strategy</h3>
<p>
Try to build down in suit whenever possible. Try to score as many points as
you can as this game is very hard to win.

31
data/html-src/rules/akbarsconquest.html Normal file
View file

@ -0,0 +1,31 @@
<h1>Akbar's Conquest</h1>
Braid type. Two decks. Two redeals.
<h3>Object</h3>
Move all cards to the Foundations.
<h3>Quick description</h3>
Similar to <a href="braid.html">Braid</a>
played with two Mughal
<a href="../ganjifa.html">Ganjifa</a>
decks.
<h3>Rules</h3>
Game play is like Braid. In this variation there are two Braid
stacks that each have their own set of Braid reserve stacks. The
game lay out starts with the sixteen foundations in the outer most columns.
The next two columns inwards are the eight Braid reserves. Then there
are two columns with four general reserves each. The inner most two
columns are the two Braid stacks. Each Braid starts with sixteen cards.
When one of the Braid reserves becomes open the card at the top of the
corresponding Braid will be moved there. When all the cards from one
of the Braids are removed a card from the other Braid will be used.
<p>
The game is named after the reputed inventor of a twelve suited Ganjifa
deck of singular splendor. It was engraved on ivory and hand painted
by court artisans. No cards from this pack are known to still exist.
<h3>Strategy</h3>
Build sequences on the rows that will play when the correct card turns
over from the talon. This game type requires careful strategy to win.
<p>
<br>
<a href="../ganjifa.html">General Ganjifa Rules</a>

28
data/html-src/rules/akbarstriumph.html Normal file
View file

@ -0,0 +1,28 @@
<h1>Akbar's Triumph</h1>
Braid type. One deck. Two redeals.
<h3>Object</h3>
Move all cards to the Foundations.
<h3>Quick description</h3>
Similar to <a href="braid.html">Braid</a>
played with a single Mughal
<a href="../ganjifa.html">Ganjifa</a>
deck.
<h3>Rules</h3>
Game play is like Braid. In this variation there are two Braid
stacks that each have their own set of Braid reserve stacks. The
game lay out starts with the eight foundations in the outer most columns.
The next two columns inwards are the eight Braid reserves. Then there
are two columns with four general reserves each. The inner most two
columns are the two Braid stacks. Each Braid starts with twelve cards.
When one of the Braid reserves becomes open the card at the top of the
corresponding Braid will be moved there. When all the cards from one
of the Braids are removed a card from the other Braid will be used.
<p>
The game is named after the reputed inventor of a twelve suited Ganjifa
deck of singular splendor. It was engraved on ivory and hand painted
by court artisans. No cards from this pack are known to still exist.
<h3>Strategy</h3>
Build sequences on the rows that will play when the correct card turns
over from the talon. This game type requires careful strategy to win.

16
data/html-src/rules/alaska.html Normal file
View file

@ -0,0 +1,16 @@
<h1>Alaska</h1>
<p>
Yukon type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="yukon.html">Yukon</a>,
but the rows build <b>up or down</b> in suit.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

17
data/html-src/rules/americantoad.html Normal file
View file

@ -0,0 +1,17 @@
<h1>American Toad</h1>
<p>
Canfield type. 2 decks. 1 redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="doublecanfield.html">Double Canfield</a>,
but the 8 piles build down in suit, cards are dealt singly,
the reserve is face-up, and only one redeal.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

27
data/html-src/rules/appachanswaterfall.html Normal file
View file

@ -0,0 +1,27 @@
<h1>Appachan's Waterfall</h1>
Dashavatara Ganjifa game type. 1 deck. No redeal.
<h3>Object</h3>
Move all cards to the Foundation.
<h3>Quick description</h3>
Build complete suits in descending rank order on the tableau then move
them to the single foundation in ascending rank and suit order. Refer
to the general <a href="../ganjifa.html">Ganjifa</a>
description for the suit order used.
<h3>Rules</h3>
Cards will play on the tableau in descending rank order without regard
to suit. They can only be moved to the single foundation when a complete
suit of twelve cards is finished and only in ascending suit order. The
suit of the Fish Incarnation is first, the Tortoise next etc. When a
suit is ready to be moved to the foundation, press (a)uto or play with
auto drop enabled and all twelve cards will move there in order. Four
cards are dealt to each of the ten rows when the game begins. Press
(d)eal or click the talon to deal the next round of one card to each
row. The reserve stacks to either side of the foundation will take one
card each. Cards on the reserves may only be played to the rows.
<h3>Strategy</h3>
Make every play possible before dealing the next round. While the cards
will play in rank order only, it's helpful to also work on playing them by
suit.

22
data/html-src/rules/ashrafi.html Normal file
View file

@ -0,0 +1,22 @@
<h1>Ashrafi</h1>
Mughal Ganjifa type. One deck. No redeal.
<h3>Object</h3>
Move all cards to the foundations.
<h3>Quick description</h3>
Play is similar to
<a href="freecell.html">Free Cell</a>.
The rows build down by rank only, no more than twelve to a row.
<h3>Rules</h3>
The cards on the tableau build down by rank regardless of suit. No more
than twelve cards may be placed in one row. The four reserve stacks
below the foundations will hold one card each. The foundations build
up in rank by suit starting with the Ace. Only the Mirs (Kings) may
be played on empty rows.
<h3>Strategy</h3>
Move the tableau cards with the objective of releasing the Aces first.
Keep the reserve stacks open as much as possible. Build piles on
the Mirs so they can be moved to open rows.

36
data/html-src/rules/ashtadikapala.html Normal file
View file

@ -0,0 +1,36 @@
<h1>Ashta Dikapala</h1>
<p>
One Moghul Ganjifa deck. No redeal.
<h3>Object</h3>
<p>
Arrange the Eight Guardians in order.
<h3>Rules</h3>
<p>
Play is similar to <a href="picturegallery.html">Picture Gallery</a>.
The layout consists of three rows of playing piles, a row for newly
dealt cards and three free cells that will hold one card each.
<p>
The cards must be arranged in the top three rows as follows:
<ul>
<li>The top row must start with a three and build by suit in increments of three,
<li>the second row must with a two,
<li>and the third row must start with an Ace.
</ul>
<p>
If you clear a space at the bottom it will be automatically filled
with a card from the talon. But if the talon is gone and you clear a space
at the bottom, then you can fill it with any card. You may move any card
to the free cells from the tableau on top or the rows below, but only as
long as there are cards left in the talon. When the talon is empty, you
may only move cards from, not to the free cells.
When no further moves are possible, click on the talon for a fresh row
of cards at the bottom.
<p>
You win when all of the suits are arranged in order.
<h3>Strategy</h3>
<p>
Because of the many piles involved the Picture Gallery requires some
concentration, but it is not too hard to win.

24
data/html-src/rules/ashwapati.html Normal file
View file

@ -0,0 +1,24 @@
<h1>Ashwapati</h1>
Mughal Ganjifa type. One deck. Unlimited redeals.
<h3>Object</h3>
Move all cards to the foundations.
<h3>Quick description</h3>
Play is similar to
<a href="klondike.html">Klondike</a>.
The rows build down by rank in the same suit.
<h3>Rules</h3>
The cards on the tableau build down by ranks of the same suit. The
foundations build up in rank by suit starting with the Ace. Any
card or movable pile may be played on an empty row. Cards are dealt
from the talon one at a time. There is no limit on the number of
redeals. Cards may be played from the foundations.
<p>
This game is one of a series of games that have names ending in "pati"
which transliterates as "lord of". Ashwapati means "Lord of Horses".
The names are the names of the suits in a twelve suit Ganjifa deck.
<h3>Strategy</h3>
Move cards off of the deepest stacks first.

22
data/html-src/rules/auldlangsyne.html Normal file
View file

@ -0,0 +1,22 @@
<h1>Auld Lang Syne</h1>
<p>
Numerica type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
The foundations build up by rank ignoring suit.
At game start the four Aces are dealt here.
<p>
There is no building on the tableau piles - cards can only be
moved to the foundations, and spaces are not filled.
<p>
When no more moves are possible, click on the talon. One card will be
added to each of the playing piles.
<h3>Notes</h3>
<p>
<i>Autodrop</i> is disabled for this game.

18
data/html-src/rules/babyspiderette.html Normal file
View file

@ -0,0 +1,18 @@
<h1>Baby Spiderette</h1>
<p>
Spider type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Group all the cards in sets of 13 cards in descending sequence
by suit from King to Ace and move such sets to the foundations.
<h3>Quick Description</h3>
<p>
Just like <a href="spiderette.html">Spiderette</a>,
but somewhat easier as groups of cards can be moved
if they <i>build down by rank</i>.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

13
data/html-src/rules/badseven.html Normal file
View file

@ -0,0 +1,13 @@
<h1>Bad Seven (Die b&ouml;se Sieben)</h1>
<p>
Two-Deck game type. 2 stripped decks. 1 redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
This game is played with two stripped decks.
<p>
<i>[To be written]</i>

15
data/html-src/rules/bakersdozen.html Normal file
View file

@ -0,0 +1,15 @@
<h1>Baker's Dozen</h1>
<p>
Baker's Dozen type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
The piles build down by rank regardless of suit.
Only one card can be moved at a time.
<p>
Empty piles cannot be filled - therefore all Kings are placed
at the bottom of a pile during the initial dealing.

31
data/html-src/rules/bakersgame.html Normal file
View file

@ -0,0 +1,31 @@
<h1>Baker's Game</h1>
<p>
FreeCell type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="freecell.html">FreeCell</a>,
but the piles build down by suit.
<h3>Rules</h3>
<p>
All cards are dealt at the start of the game. To compensate for this
there are 4 free cells which can hold any - and just one - card.
<p>
Cards may only be moved onto cards of the same suit.
<p>
The number of cards you can move as a sequence is restricted by
the number of free cells - the number of free cells required is the
same as if you would make an equivalent sequence of moves with single cards.
(As a shortcut, the computer also considers the number of free piles so
that you can move even more cards as one single sequence.)
<h3>History</h3>
<p>
<i>Baker's Game</i> is named after the mathematician C.L. Baker
and was first published in Martin Gardner's June 1968
<i>Mathematical Games</i> column in <i>Scientific American</i>.

16
data/html-src/rules/balarama.html Normal file
View file

@ -0,0 +1,16 @@
<h1>Balarama</h1>
Dashavatara Ganjifa type. One deck. No redeal.
<h3>Object</h3>
Move all cards to the foundations.
<h3>Quick description</h3>
The cards build down by rank in alternate colors on the tableau, no more
than twelve to a row. Any card or sequence may be played on an empty row.
<h3>Rules</h3>
All cards are dealt to the sixteen rows when the games begins. Cards
on the tableau build down in rank in alternating colors. See the general
<a href="../ganjifa.html">Ganjifa</a>
card rules for information on that. The foundations build up by suit.
Any card or sequence may be played on an empty row. The four reserve
stacks hold one card each.
<h3>Strategy</h3>
An empty row is more useful than the reserve stacks. Try for an empty row.

17
data/html-src/rules/batsford.html Normal file
View file

@ -0,0 +1,17 @@
<h1>Batsford</h1>
<p>
Klondike type. 2 decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="doubleklondike.html">Double Klondike</a>,
but 10 piles, no redeal, and an extra reserve that can
hold up to 3 Kings.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

19
data/html-src/rules/beleagueredcastle.html Normal file
View file

@ -0,0 +1,19 @@
<h1>Beleaguered Castle</h1>
<p>
Beleaguered Castle type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
At game start the four Aces are dealt to the foundations.
<p>
The eight piles build down by rank regardless of suit.
Only one card can be moved at a time and
empty piles can be filled with any single card.
<h3>Strategy</h3>
<p>
Build evenly on to foundations. Try to get an empty pile.

35
data/html-src/rules/betsyross.html Normal file
View file

@ -0,0 +1,35 @@
<h1>Betsy Ross</h1>
<p>
One-Deck game type. 1 deck. 2 redeals.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="calculation.html">Calculation</a>,
but using a waste with 2 redeals instead of row stacks.
<h3>Rules</h3>
<p>
The four foundations at the top are out of play.
<p>
The four foundations below build regardless of suit the following way:
The first pile from Two, by one. The second pile from Four, by two.
The third pile from Six, by three. The fourth pile from Eight, by four.
<pRE>
1: 2 3 4 5 6 7 8 9 T J Q K
2: 4 6 8 T Q A 3 5 7 9 J K
3: 6 9 Q 2 5 8 J A 4 7 T K
4: 8 Q 3 7 J 2 6 T A 5 9 K
</pRE>
<p>
When you click on the talon, one card is turned over onto the waste pile.
There are 2 redeals.
<h3>History</h3>
<p>
This game is known by many names, such as
<i>Fairest</i>, <i>Four Kings</i>, <i>Musical Patience</i>,
<i>Quadruple Alliance</i> and <i>Plus Belle</i>.

16
data/html-src/rules/bigbraid.html Normal file
View file

@ -0,0 +1,16 @@
<h1>Big Braid</h1>
<p>
Napoleon type. 3 decks. 2 redeals.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="braid.html">Braid</a>,
but with three decks.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

16
data/html-src/rules/bigdivorce.html Normal file
View file

@ -0,0 +1,16 @@
<h1>Big Divorce</h1>
<p>
Spider type. 3 decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="groundforadivorce.html">Ground for a Divorce</a>,
but with three decks and 13 playing piles.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

25
data/html-src/rules/bigeasy.html Normal file
View file

@ -0,0 +1,25 @@
<h1>Big Easy</h1>
Hanafuda type. 2 decks. Unlimited redeals.
<h3>Object</h3>
Move all cards to the foundations.
<h3>Quick description</h3>
This is a double deck version of
<a href="littleeasy.html">Little Easy</a>.
The rows build down by rank in the same suit. The foundations
build with cards of the same rank in suit order. Only first rank
cards may be played on an empty row.
<h3>Rules</h3>
The rules are the same as in
<a href="littleeasy.html">Little Easy</a>.
<h3>Strategy</h3>
Disable auto drop and build on the rows until all cards are face up.
These games may be easy by name and easy to play but they're not easy
to win.
<h3>Author</h3>
This game and documentation has been written by
<a href="mailto:grania@mailcity.com">T. Kirk</a>.

28
data/html-src/rules/bigharp.html Normal file
View file

@ -0,0 +1,28 @@
<h1>Big Harp (Die gro&szlig;e Harfe)</h1>
<p>
Klondike type. 2 decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="doubleklondike.html">Double Klondike</a>,
but ten piles, anything on an empty space, and no redeal.
<h3>Rules</h3>
<p>
Piles build down by alternate color, and an empty space can be filled
with any card or sequence.
<p>
Cards from the talon are turned over to the waste pile, one at a time.
You can move the top card to the playing piles or the foundations.
There is no redeal.
<p>
You are also permitted to move cards back out of the foundations.
<h3>History</h3>
<p>
<i>Small Harp</i> and <i>Big Harp</i> are the German ways of playing
<i>Klondike</i> and <i>Double Klondike</i>.

16
data/html-src/rules/bigspider.html Normal file
View file

@ -0,0 +1,16 @@
<h1>Big Spider</h1>
<p>
Spider type. 3 decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="spider.html">Spider</a>,
but with three decks and 13 playing piles.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

27
data/html-src/rules/bigsumo.html Normal file
View file

@ -0,0 +1,27 @@
<h1>Big Sumo</h1>
Hanafuda type. 2 decks. No redeal.
<h3>Object</h3>
Move all cards to the foundations.
<h3>Quick description</h3>
Play is similar to
<a href="freecell.html">Free Cell</a>.
Cards build from first to fourth rank on the tableau by suit and
from fourth to first on the foundations. Only first rank cards
may be played on an empty row.
<h3>Rules</h3>
This is a two deck version of
<a href="sumo.html">Sumo</a>.
Cards build down in rank on the rows and up in rank on the foundations.
Third and fourth rank (trash) cards are not interchangeable. Only a first
rank card or correctly ordered pile may be played on an empty row.
<h3>Strategy</h3>
Don't play cards on the reserves unless they can be removed.
<h3>Author</h3>
<p>
This game and documentation has been written by
<a href="mailto:grania@mailcity.com">T. Kirk</a>.

40
data/html-src/rules/bitsnbytes.html Normal file
View file

@ -0,0 +1,40 @@
<h1>Bits n Bytes</h1>
<p>
Hex A Deck type. 1 deck. One redeal.
<h3>Object</h3>
<p>
Fill all row stacks.
<h3>Quick description</h3>
<p>
Fill Byte stacks by matching the goal card's byte value, fill bit
stacks by matching the corresponding bit value.
<h3>Rules</h3>
<p>
When play begins the four left most columns are filled with four
goal cards of different ranks, one from each suit. The next two
columns to the right are the byte stacks. They can be filled
with cards of the same rank as the goal card in that row. The
four right most columns are the bit stacks. They can be filled
with cards of the same suit as the goal card in the respective
row if their least significant bit matches the corresponding
bit on the goal card.
<p>
Cards from the talon are turned over to the waste pile, two at a
time. There is only one redeal.
<p>
The only function of the Wizards in this game is to block the
waste stack at the worst possible time.
<h3>Strategy</h3>
<p>
Since there are only four cards of any one rank, it's important
to fill the byte columns first.
<h3>Author</h3>
<p>
This game and documentation has been written by
<a href="mailto:grania@mailcity.com">T. Kirk</a>
and is part of the official PySol distribution.

26
data/html-src/rules/blackhole.html Normal file
View file

@ -0,0 +1,26 @@
<h1>Black Hole</h1>
<p>
Fan game type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the single foundation.
<h3>Rules</h3>
<p>
The foundation (the <i>Black Hole</i>) builds up or down by rank
ignoring color and suit, wrapping around from King to Ace
and from Ace to King.
<p>
There is no building on the tableau piles, and spaces
are not filled.
Only the top card can be moved.
<h3>Notes</h3>
<p>
<i>Autodrop</i> is disabled for this game.
<h3>Strategy</h3>
<p>
Plan carefully - one wrong move and you may never
be able to untangle the mess.

18
data/html-src/rules/blackwidow.html Normal file
View file

@ -0,0 +1,18 @@
<h1>Black Widow</h1>
<p>
Spider type. 2 decks. No redeal.
<h3>Object</h3>
<p>
Group all the cards in sets of 13 cards in descending sequence
by suit from King to Ace and move such sets to the foundations.
<h3>Quick Description</h3>
<p>
Just like <a href="spider.html">Spider</a>,
but somewhat easier as groups of cards can be moved
if they <i>build down by rank</i>.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

23
data/html-src/rules/blindalleys.html Normal file
View file

@ -0,0 +1,23 @@
<h1>Blind Alleys</h1>
<p>
Klondike type. 1 deck. 1 redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="klondike.html">Klondike</a>,
but 6 piles, anything on an empty space, and one redeal.
<h3>Rules</h3>
<p>
Piles build down by alternate color, and an empty space can be filled
with any card or sequence.
<p>
Cards from the talon are turned over to the waste pile, one at a time.
You can move the top card to the playing piles or the foundations.
There is one redeal.
<p>
You are also permitted to move cards back out of the foundations.

11
data/html-src/rules/blondesandbrunettes.html Normal file
View file

@ -0,0 +1,11 @@
<h1>Blondes and Brunettes</h1>
<p>
Terrace type. 2 decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

31
data/html-src/rules/bluemoon.html Normal file
View file

@ -0,0 +1,31 @@
<h1>Blue Moon</h1>
<p>
Montana type. 1 deck. 2 redeals.
<h3>Object</h3>
<p>
Group all the cards in sets of 13 cards in ascending sequence
by suit from Ace to King.
<h3>Quick Description</h3>
<p>
Just like <a href="montana.html">Montana</a>,
but the Aces are moved to the left.
<br>Gameplay is completely equivalent.
<h3>Rules</h3>
<p>
This 52-card solitaire starts with the entire deck shuffled and dealt
out in four rows. The aces are then moved to the left end of the layout,
making 4 initial free spaces. You may move to a space only the card that
matches the left neighbor in suit, and is one greater in rank. Kings are
high, so no cards may be placed to their right (they create dead spaces).
<p>
When no moves can be made, cards still out of sequence are reshuffled
and dealt face up after the ends of the partial sequences, leaving a card
space after each sequence, so that each row looks like a partial sequence
followed by a space, followed by enough cards to make a row of 14.
<h3>Notes</h3>
<p>
<i>Autodrop</i> is disabled for this game.

44
data/html-src/rules/braid.html Normal file
View file

@ -0,0 +1,44 @@
<h1>Braid (Der Zopf)</h1>
<p>
Napoleon type. 2 decks. 2 redeals.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
This game is somewhat harder and requires thoughtful strategy.
<p>
The layout consist of a Braid of 20 cards, two groups of four helper
fields, four braid fields (each showing a picture of a braid), the waste
pile, and the eight foundations. The first card automatically dealt to a
Foundation sets the beginning value for all foundations, and an indicator
displays the value of that card.
<p>
You choose whether the sequences on the foundations will be ascending
or descending, and your choice is displayed in an indicator. The choice is
made when you place the first card on a foundation which is not the
already-determined base card.
It must follow suit and must have a numerical value
of either one more or one less than the base card. Ace is considered one
higher than King, and at the same time one less than Two.
<p>
You may place cards on the foundation from anywhere on the table,
including the end of the Braid. The eight helper fields can be filled from
the waste pile but not from the Braid or the braid fields. When you move
a card from a braid field to the foundation, that field is automatically
filled with the last card on the Braid itself.
<p>
In going through the talon, you are limited to three rounds, and an
indicator reports on that status.
<h3>Strategy</h3>
<p>
You can use the helper fields to temporarily store cards you expect to
use soon, and you can leave them open until the right card comes up from the
Talon.
<h3>History</h3>
<p>
This is a solitaire variant of German origin.

39
data/html-src/rules/bridgetsgame.html Normal file
View file

@ -0,0 +1,39 @@
<h1>Bridget's Game</h1>
Hex A Deck game type. 2 decks. 1 redeal.
<h3>Object</h3>
Move all cards to the Foundations.
<h3>Quick description</h3>
Similar to <a href="larasgame.html">Lara's Game</a>
with sixteen rows, one redeal and
<a href="../hexadeck.html">Hex A Deck</a>
variations.
<h3>Rules</h3>
Refer to the description of the deal in Lara's Game. The differences
are that the cards are dealt to seventeen piles instead of fourteen
and if a dealt card is of rank eleven or over one card is dealt to
the talon. Otherwise the dealing rules are the same.
<p>
Play is the same as Lara's Game with two exceptions. The first exception
is that there is one redeal. When the talon is empty after the first
round the cards are gathered up from the tableau and dealt to the rows
without being shuffled using the same dealing rules as in the first round.
<p>
The other exception is the extra reserve stack just to the right of the
rows and the top foundations. This reserve stack has the potential to
save a game that would otherwise be lost. The way it works is this.
When empty it will accept any Wizard card, but only from a foundation.
Once a Wizard has been played on it, it will accept one card only from
any row stack. Once played on the stack, cards can only be remove from
it to a foundation.
<h3>Strategy</h3>
Don't play on the extra reserve stack unless you are sure the
top card will play to a foundation soon.
<h3>Notes</h3>
This game is dedicated to the memory of Bridget Bishop, hanged as a
witch on June 10, 1692 in Salem Massachusetts, U. S. A. and to the
nineteen other victims of that notorious witch hunt.

41
data/html-src/rules/bridgetsgamedoubled.html Normal file
View file

@ -0,0 +1,41 @@
<h1>Double Bridget's Game</h1>
Hex A Deck game type. 4 decks. 2 redeals.
<h3>Object</h3>
Move all cards to the Foundations.
<h3>Quick description</h3>
Similar to <a href="larasgame.html">Lara's Game</a>
with sixteen rows, one redeal and
<a href="../hexadeck.html">Hex A Deck</a>
variations. This is the same as
<a href="bridgetsgame.html">Bridget's Game</a>
with four decks and two redeals.
<h3>Rules</h3>
Refer to the description of the deal in Lara's Game. The differences
are that the cards are dealt to seventeen piles instead of fourteen
and if a dealt card is of rank eleven or over one card is dealt to
the talon. Otherwise the dealing rules are the same.
<p>
Play is the same as Lara's Game with two exceptions. The first exception
is that there is one redeal. When the talon is empty after the first
round the cards are gathered up from the tableau and dealt to the rows
without being shuffled using the same dealing rules as in the first round.
<p>
The other exception is the extra reserve stack just to the right of the
rows and the top foundations. This reserve stack has the potential to
save a game that would otherwise be lost. The way it works is this.
When empty it will accept any Wizard card, but only from a foundation.
Once a Wizard has been played on it, it will accept any two cards from
any of the row stacks. Once played on the stack, cards can only be removed
by playing them to a foundation.
<h3>Strategy</h3>
Don't play on the extra reserve stack unless you are sure the
top card will play to a foundation soon.
<h3>Notes</h3>
This game is dedicated to the memory of Bridget Bishop, hanged as a
witch on June 10, 1692 in Salem Massachusetts, U. S. A. and to the
nineteen other victims of that notorious witch hunt.

14
data/html-src/rules/bristol.html Normal file
View file

@ -0,0 +1,14 @@
<h1>Bristol</h1>
<p>
Fan game type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
<i>[To be written]</i>
<p>
Empty piles cannot be filled - therefore all Kings are placed
at the bottom of a pile during the initial dealing.

17
data/html-src/rules/brunswick.html Normal file
View file

@ -0,0 +1,17 @@
<h1>Brunswick</h1>
<p>
Yukon type. 2 decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Just like <a href="lexingtonharp.html">Lexington Harp</a>,
but deal all cards face-up.
<br>Very easy.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

16
data/html-src/rules/busyaces.html Normal file
View file

@ -0,0 +1,16 @@
<h1>Busy Aces</h1>
<p>
Forty Thieves type. 2 decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="fortythieves.html">Forty Thieves</a>,
but with 12 piles.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

24
data/html-src/rules/calculation.html Normal file
View file

@ -0,0 +1,24 @@
<h1>Calculation</h1>
<p>
One-Deck game type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
The four foundations build regardless of suit the following way:
The first pile from Ace, by one. The second pile from Two, by two.
The third pile from Three, by three. The fourth pile from Four, by four.
<pRE>
1: A 2 3 4 5 6 7 8 9 T J Q K
2: 2 4 6 8 T Q A 3 5 7 9 J K
3: 3 6 9 Q 2 5 8 J A 4 7 T K
4: 4 8 Q 3 7 J 2 6 T A 5 9 K
</pRE>
Once on a stack, a card can only be moved onto a foundation.
<h3>Notes</h3>
<p>
The auto-solver is completely clueless.

53
data/html-src/rules/camelot.html Normal file
View file

@ -0,0 +1,53 @@
<h1>Camelot</h1>
<h3>Object</h3>
<p>
Remove all cards but picture cards (Jacks, Queens, and Kings). You have
won if your Tableau looks like this -- <br>
<img src="../images/camelot-goal.gif" alt="The Winning Tableau.">
<p>
-- and your Stock and Waste are empty. The suits do not matter.
<h3>Rules</h3>
<p>
There are two phases to this game. Alternate between the two phases
until game is lost or won. Start with Phase One until Tableau is
completely filled. At that point, move to Phase Two. Please note that
you cannot begin Phase Two unless Tableau is completely filled. At any
point, you can return to Phase One, but remember that you cannot go back
to Phase Two unless the tableau is once again filled. An exception to
this rule is if the stock and waste are empty.
<p>
Phase One -- Click on the Stock to move a card into the empty Waste pile. If
card is a:
<ul type="disc">
<li>
King: Place in one of the empty four corner spaces.
</li>
<li>
Queen: Place in one of the empty middle two spaces of the top or bottom row.
</li>
<li>
Jack: Place in any of the empty middle two spaces of the leftmost or rightmost
column.
</li>
<li>
Any other card: Place in any empty space.
</li>
</ul>
<p>
Phase Two -- Remove 10's singly by clicking on them. Remove pairs that
add up to 10 by dragging one card on top of its pair.
<h3>Strategy</h3>
<p>
It is always safest in the middle. During Phase One of play, deal in
the middle before going to the edges. If you see a possible pair, place
that card on the edge so as to free more edge spaces during Phase Two of
play.

44
data/html-src/rules/canfield.html Normal file
View file

@ -0,0 +1,44 @@
<h1>Canfield</h1>
<p>
Canfield type. 1 deck. Unlimited redeals.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
Canfield is played with one deck. The object is to build all four
of the foundations at the top right from the rank of the first card
dealt into there (varies from game to game), all in the same suit.
<p>
The tableau consists of four piles, starting with one card each. The
cards can be stacked according to the following rules
<ul>
<li> Red cards may be only played on black cards, and black only on
red.
<li> Only the next smaller card may be played, so that the stacks
are in descending sequence except when the previous card is an Ace,
in which only the King may be played.
<li> You may not move parts of a sequence except the top card.
<li> Empty spaces in the tableau will be filled automatically from
the reserve (the pile below the talon) until it is exhausted. When
the reserve is exhausted, the empty spaces can be filled with any
card.
</ul>
<p>
When there are no more possible moves, click on the talon. Three
cards will be moved from the talon to the waste pile directly to its
right.
<h3>Notes</h3>
<p>
The auto-solver is hopeless. Don't believe the hints. They tend to
be right but it doesn't figure everything out (there may be valid
moves that it won't guess).
<h3>Author</h3>
<p>
This game and documentation has been written by
<a href="mailto:drew_csillag@geocities.com">Drew Csillag</a>
and is part of the official PySol distribution.

16
data/html-src/rules/carlton.html Normal file
View file

@ -0,0 +1,16 @@
<h1>Carlton</h1>
<p>
Yukon type. 2 decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the Foundations.
<h3>Quick Description</h3>
<p>
Just like <a href="milliganharp.html">Milligan Harp</a>,
but deal all cards face-up.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

16
data/html-src/rules/carpet.html Normal file
View file

@ -0,0 +1,16 @@
<h1>Carpet</h1>
<p>
One-Deck game type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
The four foundations are built up in suit from Ace to King.
<p>
The 20 reserve piles can hold any single card.
<p>
When you click on the talon, one card is turned over onto the waste pile.
There is no redeal.

23
data/html-src/rules/casinoklondike.html Normal file
View file

@ -0,0 +1,23 @@
<h1>Casino Klondike</h1>
<p>
Klondike type. 1 deck. 2 redeals.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Just like <a href="klondike.html">Klondike</a>,
but only two redeals.
<h3>Rules</h3>
<p>
<i>[To be written]</i>
<h3>Notes</h3>
<p>
There is a simple casino scoring system here - you debit $52 for each game
and for every card you bear off, you get $5 credit.
Your balance is reset whenever you select a different game.
Loaded games and manually entered game numbers don't count.

13
data/html-src/rules/castlesinspain.html Normal file
View file

@ -0,0 +1,13 @@
<h1>Castles in Spain</h1>
<p>
Baker's Dozen type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
The piles build down by alternate color.
Only one card can be moved at a time, and empty piles
can be filled with any card.

25
data/html-src/rules/catstail.html Normal file
View file

@ -0,0 +1,25 @@
<h1>Cat's Tail (Der Katzenschwanz)</h1>
<p>
FreeCell type. 2 decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="snake.html">Snake</a>,
but the number of cards you can move as a sequence is not restricted.
<h3>Rules</h3>
<p>
All cards are dealt to 9 piles at the start of the game, each King
starting a new pile.
To compensate for this there are 8 free cells which can hold any
- and just one - card.
<p>
Piles build down by alternate color, and an empty space cannot be filled.
<h3>History</h3>
<p>
This is a solitaire variant of German origin.

25
data/html-src/rules/cavalier.html Normal file
View file

@ -0,0 +1,25 @@
<h1>Cavalier</h1>
Tarock type. 1 deck. No redeal.
<h3>Object</h3>
Move all cards to the foundations.
<h3>Quick description</h3>
This is a
<a href="bakersdozen.html">Baker's Dozen</a>
type game played with the 78 card Tarock deck. Piles build down
in rank in alternate colors. The Trumps can play as either color.
<h3>Rules</h3>
Rows build down in rank by alternate color with the Trumps playing
as either color. A pile may be moved to another location but only
a single card may be played on an empty row. Cards may be played
from the foundations.
<h3>Strategy</h3>
Use the Trumps to open spots for suit cards.
<h3>Author</h3>
<p>
This game and documentation has been written by
<a href="mailto:grania@mailcity.com">T. Kirk</a>.

22
data/html-src/rules/chameleon.html Normal file
View file

@ -0,0 +1,22 @@
<h1>Chameleon</h1>
<p>
Canfield type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="canfield.html">Canfield</a>,
but the three piles build down by rank,
cards are dealt singly, and no redeal.
<h3>Rules</h3>
<p>
<i>[To be written]</i>
<h3>History</h3>
<p>
This game is also known under names such as
<i>Kansas</i>.

27
data/html-src/rules/cherrybomb.html Normal file
View file

@ -0,0 +1,27 @@
<h1>Cherry Bomb</h1>
Hanafuda type. 2 decks. No redeal.
<h3>Object</h3>
Move all cards to the foundations.
<h3>Quick description</h3>
This is a double deck version of
<a href="firecracker.html">Fire Cracker</a>.
The rows build down in rank in the same suit. The foundations
build with cards of the same rank in suit order.
<h3>Rules</h3>
The rows build from first rank to fourth rank by suit. The foundations
build in ascending suit order from Pine to Phoenix by rank. The third
and fourth rank (trash) cards are interchangeable on the tableau. Cards
may not be played from the foundations. Any card or correctly ordered
pile may be played on an empty row.
<h3>Strategy</h3>
Build sequences on the tableau. Since the trash cards are interchangeable
it's possible to build a valid sequence that has more than four cards in
a two deck game.
<h3>Author</h3>
This game and documentation has been written by
<a href="mailto:grania@mailcity.com">T. Kirk</a>.

18
data/html-src/rules/chessboard.html Normal file
View file

@ -0,0 +1,18 @@
<h1>Chessboard</h1>
<p>
Beleaguered Castle type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
The foundations build up in suit, wrapping around from King to Ace.
The first card moved to the foundations determines the base rank.
<p>
The ten piles build <b>up or down</b> in suit, wrapping around from
King to Ace and from Ace to King.
<p>
Only one card can be moved at a time and
empty piles can be filled with any single card.

25
data/html-src/rules/chinesediscipline.html Normal file
View file

@ -0,0 +1,25 @@
<h1>Chinese Discipline</h1>
<p>
Yukon type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the Foundations.
<h3>Quick Description</h3>
<p>
Like <a href="yukon.html">Yukon</a>,
but don't deal all cards at game start.
<h3>Rules</h3>
<p>
Cards in Tableau are built down by alternate color.
Groups of cards can be moved regardless of sequence.
An empty pile in the Tableau can be filled with a King or a group
of cards with a King on the bottom.
<p>
Foundations are built up in suit from Ace to King.
Cards in Foundations are no longer in play.
<p>
When no more moves are possible, click on the Talon.
Three more cards will be dealt.

19
data/html-src/rules/chinesesolitaire.html Normal file
View file

@ -0,0 +1,19 @@
<h1>Chinese Solitaire</h1>
<p>
Yukon type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the Foundations.
<h3>Quick Description</h3>
<p>
Just like <a href="chinesediscipline.html">Chinese Discipline</a>,
but anything on an empty space.
<h3>Rules</h3>
<p>
<i>[To be written]</i>
<p>
When no more moves are possible, click on the Talon.
Three more cards will be dealt.

16
data/html-src/rules/citadel.html Normal file
View file

@ -0,0 +1,16 @@
<h1>Citadel</h1>
<p>
Beleaguered Castle type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Just like <a href="beleagueredcastle.html">Beleaguered Castle</a>,
but matching cards are moved to the foundations during initial dealing.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

23
data/html-src/rules/cluitjarslair.html Normal file
View file

@ -0,0 +1,23 @@
<h1>Cluitjar's Lair</h1>
Klondike type. One deck. No redeal.
<h3>Object</h3>
Move all cards to the Foundations.
<h3>Quick description</h3>
Similar to <a href="klondike.html">Klondike</a>
with <a href="../hexadeck.html">Hex A Deck</a>
variations.
<h3>Rules</h3>
Game play is like Klondike. The rows build down in rank in alternate
color. Any card or sequence may be played on an empty row. The Wizards
will play in their proper rank position on the tableau regardless of
color. While two or more Wizards will play on top of each other, the stack
must still be of alternating colors to be a movable sequence. Cards are
dealt from the talon one at a time. There is no redeal. Cards may be
played from the foundations.
<h3>Strategy</h3>
The Wizards will not play to their foundation until all the suit cards
are on theirs. That can make the end game a bit of a puzzle. Use an
empty row to move them out of the way.

13
data/html-src/rules/cockroach.html Normal file
View file

@ -0,0 +1,13 @@
<h1>Cockroach</h1>
<p>
Tarock type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
Play is identical to
<a href="grasshopper.html">Grasshopper</a>
except there is no redeal.

26
data/html-src/rules/concentration.html Normal file
View file

@ -0,0 +1,26 @@
<h1>Concentration</h1>
<p>
Memory game type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Flip all pairs of matching cards and get a score of 50 points or more.
<h3>Rules</h3>
<p>
At game start 52 cards are dealt to the tableau piles.
<p>
Flip any 2 cards that match in rank.
<p>
Any pair that matches will gain you 5 points, while a pair that
doesn't match will cost you 1 point.
<p>
You win if your final score reaches 50 points.
<h3>Notes</h3>
<p>
To get awarded for a perfect game you must reach the maximum score of
130 points. You can reach this by restarting the game.
<p>
<i>Undo</i>, <i>Bookmarks</i>, <i>Autodrop</i> and <i>Quickplay</i>
are disabled for this game.

17
data/html-src/rules/congress.html Normal file
View file

@ -0,0 +1,17 @@
<h1>Congress</h1>
<p>
Forty Thieves type. 2 decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="fortythieves.html">Forty Thieves</a>,
but the 8 piles build down by rank ignoring suit,
and empty piles are automatically filled from the waste or talon,
<h3>Rules</h3>
<p>
<i>[To be written]</i>

19
data/html-src/rules/convolution.html Normal file
View file

@ -0,0 +1,19 @@
<h1>Convolution</h1>
<p>
FreeCell type. Two Hex A Decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="snake.html">Snake</a>,
with the Hex A Deck Variations and the number of cards you can move as a
sequence is not restricted.
<h3>Rules</h3>
<p>
All cards are dealt to 9 piles at the start of the game, each King or "Ten"
(hexadecimal) starting a new pile. Rows build down in rank regardless of
color and empty rows cannot be filled. The Wizards play as any color.

19
data/html-src/rules/corkscrew.html Normal file
View file

@ -0,0 +1,19 @@
<h1>Corkscrew</h1>
<p>
FreeCell type. Two Tarock Decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="snake.html">Snake</a>,
using two 78 card Tarock decks and the number of cards you can move as a
sequence is not restricted.
<h3>Rules</h3>
<p>
All cards are dealt to 9 piles at the start of the game, each King or Skiz
starting a new pile. Rows build down in rank regardless of suit.
Empty rows cannot be filled. The eight free cells will hold one card each.

16
data/html-src/rules/corona.html Normal file
View file

@ -0,0 +1,16 @@
<h1>Corona</h1>
<p>
Forty Thieves type. 2 decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="fortythieves.html">Forty Thieves</a>,
but empty piles are automatically filled from the waste or talon.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

17
data/html-src/rules/courtyard.html Normal file
View file

@ -0,0 +1,17 @@
<h1>Courtyard</h1>
<p>
Forty Thieves type. 2 decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="fortythieves.html">Forty Thieves</a>,
but with 12 piles, sequences can be moved,
and empty piles are automatically filled from the waste or talon.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

15
data/html-src/rules/cruel.html Normal file
View file

@ -0,0 +1,15 @@
<h1>Cruel</h1>
<p>
Baker's Dozen type. 1 deck. Unlimited redeals.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
The piles build down by suit.
Only one card can be moved at a time, and empty spaces cannot be filled.
<p>
When no more moves are possible click on the talon for a redeal.
The cards are not re-shuffled, but re-dealt in packs of 4 cards.

20
data/html-src/rules/danda.html Normal file
View file

@ -0,0 +1,20 @@
<h1>Danda</h1>
<p>
FreeCell type. One Moghul Ganjifa Deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="snake.html">Snake</a>,
using the eight suit Moghul Ganjifa deck and the number of cards you can move
as a sequence is not restricted.
<h3>Rules</h3>
<p>
All cards are dealt to 9 piles at the start of the game, each Raja or King
starting a new pile. Rows build down in rank by alternate force suits.
Refer to the general <a href="ganjifa.html">Ganjifa</a> page.
Empty rows cannot be filled. The eight free cells will hold one card each.

36
data/html-src/rules/dashavatara.html Normal file
View file

@ -0,0 +1,36 @@
<h1>Dashavatara</h1>
<p>
One Dashavatara Ganjifa deck. No redeal.
<h3>Object</h3>
<p>
Arrange the Ten Avatars in order.
<h3>Rules</h3>
<p>
Play is similar to <a href="picturegallery.html">Picture Gallery</a>.
The layout consists of three rows of playing piles, a row for newly
dealt cards and three free cells that will hold one card each.
<p>
The cards must be arranged in the top three rows as follows:
<ul>
<li>The top row must start with a three and build by suit in increments of three,
<li>the second row must with a two,
<li>and the third row must start with an Ace.
</ul>
<p>
If you clear a space at the bottom it will be automatically filled
with a card from the talon. But if the talon is gone and you clear a space
at the bottom, then you can fill it with any card. You may move any card
to the free cells from the tableau on top or the rows below, but only as
long as there are cards left in the talon. When the talon is empty, you
may only move cards from, not to the free cells.
When no further moves are possible, click on the talon for a fresh row
of cards at the bottom.
<p>
You win when all of the suits are arranged in order.
<h3>Strategy</h3>
<p>
Because of the many piles involved the Picture Gallery requires some
concentration, but it is not too hard to win.

14
data/html-src/rules/dashavataracircles.html Normal file
View file

@ -0,0 +1,14 @@
<h1>Dashavatara Circles</h1>
Dashavatara Ganjifa type. One deck. No redeal.
<h3>Object</h3>
Move all cards to the foundations.
<h3>Quick description</h3>
The cards build down by rank and by suit on the tableau. Any card may be
played on an empty row. Only one card may be moved at a time.
<h3>Rules</h3>
All cards are dealt to the thirty two rows when the games begins. Cards
on the tableau build down by suit in descending rank order. The foundations
build up by suit. Any card may be played on an empty row. The reserve stacks
hold one card each. Only one card at a time may be moved.
<h3>Strategy</h3>
Try to keep a reserve stack open. Play higher ranked cards on empty rows.

19
data/html-src/rules/deadkinggolf.html Normal file
View file

@ -0,0 +1,19 @@
<h1>Dead King Golf</h1>
<p>
Golf type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the waste stack.
<h3>Quick Description</h3>
<p>
Just like <a href="golf.html">Golf</a>,
but <em>nothing</em> may be placed on a King.
<h3>Rules</h3>
<i>[To be written]</i>
<h3>Notes</h3>
<p>
<i>Autodrop</i> is disabled for this game.

17
data/html-src/rules/derfreienapoleon.html Normal file
View file

@ -0,0 +1,17 @@
<h1>Der freie Napoleon</h1>
<p>
Napoleon type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Just like <a href="derkleinenapoleon.html">Der kleine Napoleon</a>,
only with a different screen layout.
<br>Gameplay is completely equivalent.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

46
data/html-src/rules/derkleinenapoleon.html Normal file
View file

@ -0,0 +1,46 @@
<h1>Der kleine Napoleon</h1>
<p>
Napoleon type. 1 deck. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Rules</h3>
<p>
This game is somewhat harder and requires thoughtful strategy.
<p>
The layout consist of 4 foundations in the middle,
8 row stacks (4 on each of the left and right side),
2 reserve stacks (one on each of the left and right side),
and a free cell in the middle.
<p>
The row stacks and reserve stacks grow from the middle and are laid out
open, but only the outer card is in play.
<p>
The foundations build either up or down in suit, depending on the
first card you play there.
They wrap around from King to Ace and Ace to King.
<p>
The 8 row stacks build both up and down in suit, also wrapping around.
Only a single card can be moved, and free rows can be filled with
any single card.
<p>
There is no building on the 2 reserve stacks. Cards can only be moved
to other stacks from there.
<p>
Finally there is one extra free cell that can hold any single card.
But to move a card back from the free cell at least one of the
two "blocking" reserve stacks must have been cleared.
<h3>Notes</h3>
<p>
Try <a href="derfreienapoleon.html">Der freie Napoleon</a> if
you have troubles understanding the rules - it is the exactly
same game in a different layout.
<h3>Strategy</h3>
<p>
Decide carefully if you build the foundations up or down.
<p>
Getting a free row stack should be one of your highest priorities.

16
data/html-src/rules/deuces.html Normal file
View file

@ -0,0 +1,16 @@
<h1>Deuces</h1>
<p>
Forty Thieves type. 2 decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="fortythieves.html">Forty Thieves</a>,
but the foundations build up from Two to Ace.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

26
data/html-src/rules/dhanpati.html Normal file
View file

@ -0,0 +1,26 @@
<h1>Dhanpati</h1>
Mughal Ganjifa type. One deck. One redeal.
<h3>Object</h3>
Move all cards to the foundations.
<h3>Quick description</h3>
Play is similar to
<a href="klondike.html">Klondike</a>.
The rows build down by rank regardless of suit.
<h3>Rules</h3>
The cards on the tableau build down by rank. The foundations build
up in rank by suit starting with the Ace. Only the Mirs (Kings) may
be played on an empty row. Cards are dealt from the talon three at
a time. There is only one redeal. Cards may not be played from the
foundations.
<p>
This game is one of a series of games that have names ending in "pati"
which transliterates as "lord of". Dhanpati means "Lord of Treasure".
The names are the names of the suits in a twelve suit Ganjifa deck.
<h3>Strategy</h3>
Move cards back and forth on the rows to make every play possible on
the first pass through the talon. Don't let the waste stack get too
deep on the second pass.

19
data/html-src/rules/diekoenigsbergerin.html Normal file
View file

@ -0,0 +1,19 @@
<h1>Die K&ouml;nigsbergerin</h1>
<p>
Gypsy type. 2 decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="gypsy.html">Gypsy</a>,
but Aces go off during dealing, and cards in the foundations
are no longer in play.
<h3>Rules</h3>
<p>
<i>[To be written]</i>
<p>
You are <em>not</em> permitted to move cards back out of the foundations.

16
data/html-src/rules/diplomat.html Normal file
View file

@ -0,0 +1,16 @@
<h1>Diplomat</h1>
<p>
Forty Thieves type. 2 decks. No redeal.
<h3>Object</h3>
<p>
Move all cards to the foundations.
<h3>Quick Description</h3>
<p>
Like <a href="fortythieves.html">Forty Thieves</a>,
but the 8 piles build down by rank ignoring suit.
<h3>Rules</h3>
<p>
<i>[To be written]</i>

Some files were not shown because too many files have changed in this diff Show more