kazdragon / paradice9 Goto Github PK

Implement a framework that will allow user interface objects to be painted 
via an abstraction instead of merely streaming text.

Telnet NAWS will achieve this.  See RFC1073.

All current files should have Doxygen comments applied to them in a manner 
similar to odin::io::datastream.

This is most visible when the terminal client is maximised.  It can be 
reproduced by changing focus from the command edit field to the output text 
field.

Mid-redraw, the client has opportunities to plot the cursor, and this causes it 
to appear briefly on several portions of the screen.  It may be worthwhile  
switching the cursor off briefly during redraw.

Implement the Paradice-specific components necessary to display information 
to the user.

This will be more familiar to more recent gamers from mmos, etc.

A help command that shows aliases and how to use a command would be helpful.   
This would replace some of the commands' existing "syntax" displays.

Dice rolls should have the following colouring:

* Roll totals should be emboldened.
* The ! for a maximum roll should be in bright green.

The command table, and many of its functions are in the Paradice9 driver, 
rather than the Paradice9 library.  they need moving.

Massive errors from the Spirit library.

What steps will reproduce the problem?
1. Make a title longer than 36 characters.

roll 1d0 crashes it.

It'll be worth testing 0d1 too.

See RFC 858

The template stuff for Munin, while cute and actually helpful as a testing 
scaffold during development, is not really useful any more.  Remove it.

Possibly due to showing rolls that were rolled by people who are offline.

The use case is for rolling initiative.  It's helpful to have a summary of 
the initiatives rolled by all.

Example:

> roll 1d10+4 initiative

You roll 1d10+4 (category: initiative) and score 6 [2].

Bob rolls 1d10+3 (category: initiative) and scores 7 [4].

Jihem rolls 1d10+2 (category: initiative) and scores 8 [6].

Jihem rolls 1d10+2 (category: initiative) and scores 12 [10].

[Note: optional ascending/descending argument, with descending being 
default.]
> show rolls initiative

The rolls for the initiative category are:
Jihem rolled 1d10+2 and scored 12.
Jihem rolled 1d10+2 and scored 8.
Bob rolled 1d10+3 and scored 7.
You rolled 1d10+4 and scored 6.

> clear rolls initiative

You clear the rolls from the initiative category.
> show rolls initiative

There are no rolls for the initiative category.

Possibly allow explicit adding and removal from the list to enable 
corrections as well.

The program's main callbacks are mostly free functions in Paradice9.cpp.  It 
would be nicer if, after collecting information from the command line, an 
object that abstracts the program and these callbacks away would be called.

During character creation, it's common to roll 2d20+25 about ten times.  
However, this becomes repetitious.  It would be nice to be able to ask the 
server to roll 10*2d20+25 and have it roll 2d20+25 ten times.

On Ubuntu telnet, home/end send the following sequences respectively:

\eOH
\eOF

Currently, we handle home/end with 

\e[1~
\e[4~

PgUp/PgDn work the same way.

Oddly enough, home/end on the keypad send the second set of negotiations and do 
work.

There appears to be no way of sending meta+home/meta+end in Ubuntu telnet.

Currently, the who list prints a list of all players online.  There is space 
enough for six entries, and after that it goes a little screwy by overwriting 
the graphical border and heading into the scrolling region (where it scrolls 
off).

Better would be a columnar output (for example, two columns of 35 characters) 
which can be "paged" by the user.

Some clients disconnect due to timeouts.  Some keepalive options should be 
used:

Silent client/server negotiations
Socket option.

Currently, do_draw has the signature:

void do_draw(canvas<> &cvs, point const &offset, rectangle const &region);

cvs is the canvas on which the component is drawn.  region is the area of the 
component that should be redrawn.

Finally, offset tracks the cumulative offset of the component via its parents.  
For example, if a component is contained in a container at position (5,5) and 
it is contained in a container at position (2,3), then offset comes in as 
(7,8).  This means that every draw operation looks like this:

cvs[position.x + offset.x + current_region_x_index]
   [position.y + offset.y + current_region_y_index] = some_element;

Ideally, this would be simply be:

cvs[current_region_x_index][current_region_y_index] = some_element;

This means that both position and offset would be contained in the canvas, and 
each component could pretend that it were drawing relative to (0,0).  Although 
repeating this task myself means that it's boilerplate, it was hard to get my 
head around the first time (as you can see from the gratuitous debug comments 
in munin::container<>.  This change would simplify the process greatly and make 
it far less error-prone.

It would be nice if a client's up and down arrows could navigate their 
command history.

Echoing input will provide a greater control over the client, at the cost of 
some perceived lag.

Further developments should be made using Test Driven Development.  A project 
must be put together to supply a framework for this.

To fit in with our current gaming culture, the following aliases have been 
requested:

surname for title
honorific for prefix

Add the ability to roll dice that only show for the roller.

One user requests that his commands be translated into actions.  That is, 
instead of:

    Bob says, "hi!"

    say hi!

    You say, "hi!"

you get

    Bob says, "hi!"

    You say, "hi!"

because your command vanishes when it is translated into an action.

For example:

> Help say

+======================================+
| SAY                                  |
+--------------------------------------|
| Speaks a message to all participants |
| in the same room.                    |
+======================================+

Once Munin and Hugin are completed, these need to be used with the existing 
Paradice application in order to present the new UI to the players.

Currently, it will only show the first 8 (on 80x24, more on wider screens) 
players.  A method for showing that there are more names in a particular 
direction and a method for scrolling the list of players should be implemented.

Connection should abstract the communications to the socket.  I.e. it should 
write and/or take special actions which involve data being send.

Client should abstract information about the player: their name, title, 
connection level, etc.

These must be unentangled.

The paradice library is not in a testable state currently (Odin is just 
fine).  The use of global variables (such as the connections list) and other 
similar techniques need to be refactored into a context interface.

For example, in:

   roll 2*2d6+3
   You roll 2d6+3 2 times and score 7 [2,2], 12 [3,6] for a grand total of 
19.


7, 12 and 19 should be highlighted.

http://www.frexx.de/xterm-256-notes/ gives an overview as to what this achieves.

In short:

To use foreground and background colors from the extension, you only have to 
remember two escape codes:
Set the foreground color to index N:    \033[38;5;${N}m
Set the background color to index M:    \033[48;5;${M}m

When renaming your character, the text sent to the room says that you've 
change from the name you're actually changing to.

When redrawing the window, to work with Teraterm, a change in graphics 
attribute first has some code that sets the attribute to 'default'.  The 
sequence sent is supposed to be:

\e[0m

Unfortunately, it is actually outputting:

\e[\0m

(that is, character 0, not number 0).

This is causing weird characters to get spewed across the screen in Ubuntu 
telnet.  The display appears properly when changing the output properly.

Reproduceable by maximising a PuTTY client on a 1280x1024 resolution display.

The built-in C++ random number generator is currently being used.  However, 
this is known to have a very poor distribution, which may be behind some of 
the issues observed with dice rolling.

Request: Change the RNG.

See RFC854.

In some MMOs that users are particularly familiar with, it is common for 
typing whatever without any prefix to be broadcast to the last used public 
channel, whereas commands are supported by using a leading slash (/).

e.g.

> emote bounces about
Player bounces about

If a player disconnects at the name prompt, then a message arrives: "#SERVER: 
has left the game" (i.e. there is no name provided).

Disconnection messages should not appear from connections with no name.

Tintin++ says it supports character mode on its website; therefore we must be 
missing something to hook it into that mode.

Create an image component that changes its appearance at timed intervals.

If client A connects while client B is at the title screen, the who list 
shows on client B's screen.

what is the current set up?
1. to roll dice we currently use the command something along the lines of 2
6 3 (roll 2d6+3).

What is the expected output? What do you see instead?
I would prefer to see/give the command 2d6+3 and have the result in a
similar way 


What version of the product are you using? On what operating system?


Please provide any additional information below.

In Tintin++, the default is to handle \eOA as arrow up and \e[A as ctrl-arrow 
up, whereas the default in PuTTY, etc., is the other way around.  Scandum says 
that this can be worked around by sending \e[?1l (DECCKM - Normal Cursor Keys).

Create a mechanism for creating, saving, and restoring accounts, including 
saving settings such as commandmode.

If someone does a sayto to me, this happens:

You say to Perdix, "my Google wave is up"

Perdix says to you, "my Google wave is up"