Docs for Kigo

Hi,

I did a Go game for KDE called Kigo, which is currently in kdereview and
planned to move to kdegames. Currently, I am improving documentation but I'm
having a hard time with docbook. Therefore I'd like to ask for help here. I
already wrote a short guide to Kigo (see attachment) and Ian Wadham proposed
some Go facts/hints that should be part of the docs. Furthermore, If someone
knows a good tool that makes docbook editing easier, feel free to point me to
it. My current effort is found here:

trunk/kdereview/docs/kigo

p.s.: Please CC me, I'm not subscribed to this list
--
Kind regards,
Sascha Peilicke
http://saschpe.wordpress.com

There is a good reference on rules and strategy for Go at
http://en.wikipedia.org/wiki/Go_game  (where else?).

I guess the most important things to keep in mind are ...

- Go is more about surrounding territory (empty space) than
   capturing your opponent's pieces.

- Territory is easiest to surround near the corners (on two sides)
   then near the edges (on three sides) and lastly in the center.

- At the start of the game, space your pieces out.  Only fill in
  your fence-lines when your opponent starts to intrude.

- Do not play unsupported stones right next to your opponent's
  stones when attacking.  They will tend to get swallowed and
  GnuGo is very good at that.  It is often better to attack indirectly.

- To avoid capture, a group of stones must have two "eyes" or be
  able to make them if attacked.  "Eyes" are disconnected spaces.
  Think of a doughnut with two holes.  Your opponent can surround
  the outside, but cannot fill both holes at once.

- On the 19x19 board there are typically several territories being
  created, attacked or defended.  You have to fight several battles
  simultaneously.  The strategy involves evaluating the strengths
  and weaknesses in various areas and allocating your moves
  between them.  Is it better to attack there or defend here?

- As the board fills up and the end-game approaches, it becomes
  important to play closer up, nibbling at your opponent's fences or
  reinforcing your own.  Small mistakes and omissions can become
  very costly.

Hope this helps, Ian W.

P.S. I have forgotten too much about detailed tactics and how to
evaluate groups of stones after forty years or so and Kigo/GnuGo
can easily beat me ... :-( ... but I am hoping to re-learn fast, with
Kigo's help.
_______________________________________________
kde-games-devel mailing list
kde-games-devel@...
https://mail.kde.org/mailman/listinfo/kde-games-devel



_______________________________________________
kde-doc-english mailing list
kde-doc-english@...
https://mail.kde.org/mailman/listinfo/kde-doc-english

[Yuri Chornoivan]

Hi!

На Sun, 25 Oct 2009 16:02:19 +0200, Sascha Peilicke <sasch.pe@...>  
написав:

> Hi,
>
> I did a Go game for KDE called Kigo, which is currently in kdereview and
> planned to move to kdegames. Currently, I am improving documentation but  
> I'm
> having a hard time with docbook. Therefore I'd like to ask for help  
> here. I
> already wrote a short guide to Kigo (see attachment) and Ian Wadham  
> proposed
> some Go facts/hints that should be part of the docs. Furthermore, If  
> someone
> knows a good tool that makes docbook editing easier, feel free to point  
> me to
> it. My current effort is found here:
>
> trunk/kdereview/docs/kigo
>
> p.s.: Please CC me, I'm not subscribed to this list

I've tried to add all your information to DocBook (attached). I used to  
make it with Kate, but you can use Syntex Serna  
(http://www.syntext.com/products/serna/) or even OO.o Writer to create  
docbooks in a visual manner.

Please, do not be too strict. This is my first try.

Yuri.

_______________________________________________
kde-doc-english mailing list
kde-doc-english@...
https://mail.kde.org/mailman/listinfo/kde-doc-english

Am Sonntag 25 Oktober 2009 18:28:26 schrieb Yuri Chornoivan:
>
> I've tried to add all your information to DocBook (attached). I used to
> make it with Kate, but you can use Syntex Serna
> (http://www.syntext.com/products/serna/) or even OO.o Writer to create
> docbooks in a visual manner.
>
> Please, do not be too strict. This is my first try.
>
And not far from perfect, so please commit.
(Yuri, the following is really not your fault, you just used the current doc
template)

But I would like to discuss some changes to this doc, which apply to all
others and the doc template (main + kdegames) as well:

* Do we really need the chapter Interface Overview / Menu Refence here?
- items common to all apps like setting + help menu, game open etc
  should not be explained over and over again in each docbook, for experienced
  kde users it is only boring, for new user a link to a centralized piece of
  documentation via a link is sufficient.
- no description for obvious actions (Game->New), if there is no additional
  Information needed
- reference only in case the user needs additional/special infos for an
  action or in case of apps with many menuitems to get an overview
  where to find stuff

* Do we really need a FAQ, when there are no real question?

* Do we really need an appendix with instruction where to get the source and
  how to build it?
- the intended audience of a doc like this should be the user installing
  distro packages
- for users building from source the information provided in the appendix is
  not sufficient, they need a lot more info e.g. from techbase.

@Sascha:
- Could you please add the screenshots in default theme/style?
- GHNS does not work here, error message is "There was an error loading data
providers."

--
Burkhard Lück
_______________________________________________
kde-doc-english mailing list
kde-doc-english@...
https://mail.kde.org/mailman/listinfo/kde-doc-english

[Yuri Chornoivan]

На Sun, 25 Oct 2009 22:26:37 +0200, Burkhard Lück <lueck@...>  
написав:

> Am Sonntag 25 Oktober 2009 18:28:26 schrieb Yuri Chornoivan:
> But I would like to discuss some changes to this doc, which apply to all
> others and the doc template (main + kdegames) as well:
>
> * Do we really need the chapter Interface Overview / Menu Refence here?
> - items common to all apps like setting + help menu, game open etc
>   should not be explained over and over again in each docbook, for  
> experienced
>   kde users it is only boring, for new user a link to a centralized  
> piece of
>   documentation via a link is sufficient.
> - no description for obvious actions (Game->New), if there is no  
> additional
>   Information needed
> - reference only in case the user needs additional/special infos for an
>   action or in case of apps with many menuitems to get an overview
>   where to find stuff
>

Removed. I've added new section on shortcuts. It may be useful to see them  
all at once.

But with Userguide in its current state it is the tricky thing to find  
common instruction on menu items. Should I link it to the Userguide?

> * Do we really need a FAQ, when there are no real question?
>

Removed.

> * Do we really need an appendix with instruction where to get the source  
> and
>   how to build it?
> - the intended audience of a doc like this should be the user installing
>   distro packages
> - for users building from source the information provided in the  
> appendix is
>   not sufficient, they need a lot more info e.g. from techbase.

Not removed. Maybe it is worth to keep this info at least for the period  
before we the new doc template (or whatever replacement) will be created  
with some common universal instructions?
_______________________________________________
kde-doc-english mailing list
kde-doc-english@...
https://mail.kde.org/mailman/listinfo/kde-doc-english