1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
|
Things to do (in no particular order) as of QTads 1.7.
(The list is somewhat incomplete. Ironic, isn't it?)
You can also search through the sources for the string "TODO:".
- The context-menu should include an "add word/selection to command"
entry. This is usefull for cases where a word is too complicated to
type by hand, especially for non-english folks (or
non-whatever-language the game is written in).
- Make QTads behave like a native OS X application when running in
MacOS X. (Mostly done by now.)
- Reimplement keyPressEvent() in src/qtadsgamewindow.cc to have total
control over the input. The current implementation is very hairy;
it acts as a wrapper around the default QTextEdit implementation. A
lot of problems arise because of this. And more will arise as soon
as a key-binding changes in a future version of Qt. The only way to
have an input-line in the game window that really works, is to
handle *every* key-press ourselves.
- Make it possible to "tie" themes to individual games. For example,
it might make sense to create a "text-only" theme that uses a
fixed-width font to run games like "Till Death Makes [...]" and
others. QTads should switch automaticly to this theme when these
games are started.
- Maybe add the context menu's items to the "Display" menu?
- Incorporate Leif Huhn's modifications/enhancements of the
QTadsGameWindow widget (as used in his KFrotz interpreter) into
QTads. Merging the two versions into a single one could be useful.
- Add support for Qt 3.0.x (as of now, QTads needs 3.1.x).
- Don't "flash" (disable/enable) the toolbar's buttons between
input-prompts during game-play; this is very distracting.
- Implement timed input (for Tads 3; we already have it for Tads 2).
- Add Tads 3 banner support as soon as possible. It is likely that
this will require a complete rewrite of some parts of QTads.
- Make the font that is used for input *fully* configurable? (Not
just attributes applied to the main font.) I don't know how useful
this would be. Feedback is welcome.
- Make the game's statusline-height configurable. Also provide an
option to hide it and/or make it behave like a toolbar (so it can be
moved, as in WinTADS).
- Implement GNU-like command-line options.
- Provide some predefined themes, like "Infocom" (white on blue),
"Infocom Classic" (white on black), "Legend" (black on white), and
maybe "Web" (sans-serif black on white). The difficult part is to
find out which font to use.
- Provide a "Game Information" menu that displays the information
embedded in the game (if any), like HTML TADS does.
- Provide an option to disable font-antialiasing (might be usefull on
*really* slow systems, like 486 machines).
- Fix os_locate() (maybe don't just look-up the game's directory)
- Fix os_input_dialog() (implement default button).
- Fix the QTadsDialog class (os_input_dialog() uses it).
- Implement os_sleep_ms().
- Implement page-review (for text that has been cleared).
- Make the maximum width of lines configurable (because if margins are
used for this, they have to be changed when the window is resized or
another font is selected).
- Being able to run compressed games (gzip and bzip2) would be nice.
- Make QTads run z-code/adrift/hugo games. (Mostly half-kidding here.
Don't expect it to happen soon.)
- Find the meaning of life, invent time travel, feed the cat.
|
