Project Hosting Application - Wordsearch

[Phyrum Tea]

Hello

I want to contribute and start a new project for OLPC. I believe that
it's well
suited for OLPC and for targeted users. Samuel Klein told me that no similar
project has been started yet.

1. Project name             : Wordsearch
2. Existing website, if any : http://tea.ch/olpc/wordsearch/

http://tea.ch/olpc/wordsearch/wordsearch.tar.gz
3. One-line description     : It's a Word search puzzle game.

4. Longer description       :

What is a Word search puzzle?
-----------------------------
It's a puzzle game. Within a field of random letters, find all words
that were
placed in that field. Generally you have to find sequences of pictograms
out of
random field of pictograms. So even an analphabet player can solve the
puzzles
as well. It helps when you can read. In the following example, egyptian
hieroglyphs could be used instead.

Example:
--------
K C N O V W I M G T D X O G E
T O O T H E D W H A L E E E P
V X S A L M O N K X S L Q H E
I Q D O L P H I N T A Q Y X I
A X N A R P B M J H E P L R B
U Y C E K K L T W O R A V M B
M R J B A L E E N W H A L E J
O T X T R O U T Y L Q M Y T Q
T G O Y C L W R K M E L I X E
Y R D O B U V I C P E R C H A

Find these words:
BALEENWHALE
BLUEWHALE
DOLPHIN
ORCA
PERCH
SALMON
TOOTHEDWHALE
TROUT

Solution:
. . . . . . . . . . . . . . .
T O O T H E D W H A L E E . .
. . S A L M O N . . . L . . .
. . D O L P H I N . A . . . .
. . . A . . . . . H . . . . .
. . C . . . . . W . . . . . .
. R . B A L E E N W H A L E .
O . . T R O U T . . . . . . .
. . . . . L . . . . . . . . .
. . . . B . . . . P E R C H .

Purpose:
--------
Teaching: Work different and joyfull way on a subject. Children could
appreciate it as some fun

Recreation: Many puzzle magazines world wide exists where you can solve Word
search puzzles. So there are people paying for these kinds of puzzles. Maybe
children would solve Word searches in theire spare time as well.

Use cases:
---------
Quickly play Word search: Here a Word search is played as casual game. The
program selects subject at random and creates new Word search for immediate
solving. Size, is allways the same. Rows and columns are optimized for OLPC
laptops.

Create and play Word search: User can specify a list of words or select
prepared wordlists of different subjects, specify range of random letters
and size.

Create and play Word search out of other activities: Program can be started
with parameters which are provided by other activities. If
Wordsearch.activity
is allready running, new game can be started through inter-activity
communication.

Word search from neighbouring laptops: Word search can be shared among
children.

Continue a saved Word search: A previously saved Word search can be
loaded and
played. Word search and status are automatically saved through the
Journal.activity and can be continued anytime.

Word search by download: Browse through online word search repositories and
download.

Competition mode: Among a group of children, the same given Word search
should
be solved as fast as possible.

Advanced use cases:
-------------------
Customize Word search by adding background image and sound or music.

Change visual properties of Word searches such as font and colors.

Teacher mode: Organize competition and distribute Word search to children.
Create and distribute wordlists.

5. URLs of similar projects :

6. Committer list
   Please list the maintainer (lead developer) as the first entry. Only
list
   developers who need to be given accounts so that they can commit to your
   project's code repository, or push their own. There is no need to list
   non-committer developers.

      Username   Full name             SSH2 key URL
E-mail
      --------   ---------             ------------
------
   #1 ptea       Phyrum Tea, , phyrum.tea at sign.ch
   #2
   #3
      ...

   If any developers don't have their SSH2 keys on the web, please
attach them
   to the application e-mail.

7. Preferred development model

   [X] Central tree. Every developer can push his changes directly to the
       project's git tree. This is the standard model that will be
familiar to
       CVS and Subversion users, and that tends to work well for most
projects.

   [ ] Maintainer-owned tree. Every developer creates his own git tree, or
       multiple git trees. He periodically asks the maintainer to look
at one
       or more of these trees, and merge changes into the maintainer-owned,
       "main" tree. This is the model used by the Linux kernel, and is
       well-suited to projects wishing to maintain a tighter control on
code
       entering the main tree.

   If you choose the maintainer-owned tree model, but wish to set up some
   shared trees where all of your project's committers can commit
directly,
   as might be the case with a "discussion" tree, or a tree for an
individual
   feature, you may send us such a request by e-mail, and we will set
up the
   tree for you.

8. Set up a project mailing list:

   [ ] Yes, named after our project name
   [ ] Yes, named ______________________
   [X] No

   When your project is just getting off the ground, we suggest you eschew
   a separate mailing list and instead keep discussion about your project
   on the main OLPC development list. This will give you more input and
   potentially attract more developers to your project; when the volume of
   messages related to your project reaches some critical mass, we can
   trivially create a separate mailing list for you.

   If you need multiple lists, let us know. We discourage having many
   mailing lists for smaller projects, as this tends to
   stunt the growth of your project community. You can always add more
lists
   later.

9. Commit notifications

   [ ] Notification of commits to the main tree should be e-mailed to
the list
       we chose to create above
   [ ] A separate mailing list, <projectname>-git, should be created
for commit
       notifications
   [X] No commit notifications, please

10. Shell accounts

   As a general rule, we don't provide shell accounts to developers unless
   there's a demonstrated need. If you have one, please explain here, and
   list the usernames of the committers above needing shell access.

11. Notes/comments:


Phyrum Tea