| 1 |
- Need a resource manager for shared things like common GC's and pixmaps. |
| 2 |
- Implement a resource-based system for keeping track of XPM paths, mapping |
| 3 |
resource names to files, configuration system, etc.. Currently this is |
| 4 |
just a lot of hardcoded ugliness and klunky local parametrization. |
| 5 |
- for runtime efficiency, consider using a compile-time generated .h file |
| 6 |
that compiles resource names into #define's, and use integer-based runtime |
| 7 |
resource ID's instead of strings. |
| 8 |
- we should separate static resource management and dynamic resource |
| 9 |
management. For static management, everything should be resolved at compile |
| 10 |
time and compiled into the program; for dynamic management, we'll need a |
| 11 |
real name-to-resource mapper, runtime loaders, etc.. |
| 12 |
- implement common algo's in a base class, and use derived classes to make |
| 13 |
a GC manager, a pixmap manager, etc.. Don't over-generalize already!! |
| 14 |
- Need to implement generic font-handling class(es) in xutil (or use a |
| 15 |
separate module - xtext - so that the core X11 utils are independent of |
| 16 |
any font-handling ugliness) |
| 17 |
- class xwindow should provide input selection funcs (eg., select_kbd(), |
| 18 |
select_mouse(), etc.) so that we can make sure resizes are always handled, |
| 19 |
e.g., so that we can update window dimensions properly. |
| 20 |
- maybe provide single wrapper around XSelectInput()? |
| 21 |
- Need to properly do an XMatchVisualInfo so that we fail correctly on |
| 22 |
color-challenged displays. Don't want users to get identical grey marbles |
| 23 |
on 2-bit displays :-) |
| 24 |
+ add facility for event handlers to indicate program quit. Quitting using |
| 25 |
an exception is lame :-) |
| 26 |
+ Need to fix xwindow::{width,height}(). Currently, they do not take into |
| 27 |
account the width of the border. |
| 28 |
+ probably need two sets of dimensions access funcs; one for internal dim |
| 29 |
and one for external dim ('cos some stuff does need to know exactly how |
| 30 |
big the internal part of the window is). |
| 31 |
+ Need to handle keyboard input processing (must put this in xutil, since it |
| 32 |
gets quite ugly with KeySym mappings and whatnot) |
| 33 |
* Let's stick with local KeySym handling until we come up with a better |
| 34 |
framework for handling keystrokes. |
| 35 |
+ Integrate with class triboard so that we can have a real underlying |
| 36 |
representation for things (makes it easier for experimenting) |
| 37 |
+ Integrate with main game engine. (Yeah, so this will break the ncurses UI, |
| 38 |
but who cares? :-P) |
| 39 |
+ Integrate into main binary already!!! |
| 40 |
+ Need to properly implement scoreboard panel so that we can see the progress |
| 41 |
of the game! :-) |
| 42 |
+ actually keep score |
| 43 |
+ show player turns |
| 44 |
+ show winner |
| 45 |
+ Need to re-do event-handling framework between XAtom4 subwindows. What we |
| 46 |
*really* want is to have the child windows ONLY process background tasks like |
| 47 |
exposures, mouse tracking, etc., events that cause game state changes should |
| 48 |
be handled by class xatom4. The subwindows should have a "slave" interface |
| 49 |
driven by class xatom4, not the other way round. |
| 50 |
X make xscoreboard independent of class atom4 |
| 51 |
+ move xtriboard button handler into class XAtom4 |
| 52 |
* might be hard to make xtriboard completely independent of class atom4, |
| 53 |
'cos there are too many gamestate-specific stuff in there. Unless we |
| 54 |
*totally* move all event handlers (eg. the cursor handling) into class |
| 55 |
XAtom4. |
| 56 |
+ BUG: in AI mode, after you win, the autocursor still shows up when you |
| 57 |
mouse over "legal" moves. |
| 58 |
* Was actually bug in atom4ai::is_local_turn(). |
| 59 |
M Need to generalize xsprite_engine: |
| 60 |
M what we *really* want is a graphics manager which is independent of |
| 61 |
server-side Pixmaps; |
| 62 |
M *and* another per-server, per-screen, -specific engine where server |
| 63 |
dependent GCs, Pixmaps, etc., can be kept. |
| 64 |
+ Fix refresh code in xscoreboard: it's very inefficient!! |