I wanted to make a new thread because if all goes to plan this will get messy and I'd like to keep using the webserver thread to report on progress there (whereas this is a seperate project).
I've re-uploaded my original efforts at building a mouse driven graphical frontend here:
It has its own backend too. Please note that this was a broken version of a work in progress (previous versions had some spellcasting with animations, the autoexplore worked, and there were textual descriptions for things you moused over). I'm showing it only as example or a sketch of how something like this might work, although there's plenty of code I can re-use.
I've left debugging output on so it's possible to see the kind of outputs that might be used. Better to redesign the protocol from scratch though IMO.
t4nk, is this example illustrative enough for you to get started? I think our first task would be to draw up a list of inputs and a schema for outputs. I'm happy to do this myself but if you'd like to do it we start from your ideas of how it might work.
I've re-uploaded my original efforts at building a mouse driven graphical frontend here:
It has its own backend too. Please note that this was a broken version of a work in progress (previous versions had some spellcasting with animations, the autoexplore worked, and there were textual descriptions for things you moused over). I'm showing it only as example or a sketch of how something like this might work, although there's plenty of code I can re-use.
I've left debugging output on so it's possible to see the kind of outputs that might be used. Better to redesign the protocol from scratch though IMO.
t4nk, is this example illustrative enough for you to get started? I think our first task would be to draw up a list of inputs and a schema for outputs. I'm happy to do this myself but if you'd like to do it we start from your ideas of how it might work.