BEFORE cutting release: GFX command needs to be generalized

[brad-colbert]

By generalization, the protocol needs to break out the gfx mode command to include the target system and pertinent mode information for that system.

Example(s):

gfx atari antic 8
gfx atari antic 9
gfx atari vbxe 320x240@256

gfx apple hgr

ymmv

This will require a breaking out of the graphics handling routines, mainly the conversion routines. Grouping into there respective systems and then they should handle the post parameters on their own. Keep the "knowledge" of what the param's mean outside of the the main().

[brad-colbert]

Maybe this should be moved to a discussion but maybe we can, instead, have mode descriptions that may be specific as well as general.

Examples for Atari:

Instead of antic 8, antic 9, vbxe 320x240@256 we could provide something like:

gfx general XxY@b

where... X - width
Y - height
b - bit precision

I believe there are a few systems that can do 1 bit per pixel, 8 pixels per byte so for our atari modes:

antic 8 -> gfx general 320x220@1
antic 9 -> gfx general 80x220@4
vbxe -> gfx general 320x240@8

[NZSPY]

can the zero and * option be removed from the menu too, They don't appear to do anything.. but do appear to poll the server for something