Up to Main Index                              Up to Journal for June, 2013

                      JOURNAL FOR MONDAY 3RD JUNE, 2013
______________________________________________________________________________

SUBJECT: Continuing on the current path
   DATE: Mon  3 Jun 21:05:04 BST 2013

Oops, it seems that my musing of maybe starting WolfMUD over again last Thursday
caused more then a few concerns. Fear not! I am continuing on my current path.

With Go 1.1 out and the fact that the current WolfMUD has changed a lot since
the initial PROTOTYPE1 was released 8 months ago I am considering releasing a
PROTOTYPE2.

This itself raises a few interesting questions and lots to do. Now WolfMUD has
resources that need distributing, what is going to be the best way to package
everything? Using 'go get' or Git will pull down the resources, but what about
the binary downloads? I was considering a common resources bundle that can be
downloaded - or possibly not providing binaries at all?

Should I keep the old downloads for WolfMUD and archive them or just let
people pull old versions out of Git if they need them?

I'll also need to update the 'Getting Started' guide. Then there is the
documenting of the .wrj files for the types currently implemented: starting
location, basic location and basic items.

Documentation is something that needs looking at more thoroughly. The 'Getting
Started' guide could be improved. Maybe I should start putting together the
'Book Of WolfMUD' - BOW - for this version? *sigh* more work...

I quite like writing documentation as can been seen by my copious comments in
the WolfMUD code - which people tell me they actually *enjoy* reading!? I
can't remember why; but for the Java version BOW was prepared using DocBook.
However I'm much more comfortable using Groff/troff/nroff. I could use
something more modern like TeX/LaTeX but for some reason I just love troff[1].

I also need to decide if the documentation should be in the main repository or
a separate repository. Or even the same repository but on an orphaned branch
just for documentation?

Looks like WolfMUD Wednesday is going to be an interesting session ;)

--
Diddymus

  [1] Maybe I should use godoc, but I don't relish that thought.


  Up to Main Index                              Up to Journal for June, 2013