From: Hans Ronne <hronne@telia.com>
To: <robert.segal@rogers.com>
Cc: xconq7@sources.redhat.com
Subject: Re: XConq design tools
Date: Thu, 01 May 2003 20:49:00 -0000 [thread overview]
Message-ID: <l03130302bad6f9228c55@[212.181.162.155]> (raw)
In-Reply-To: <20030501160856.JPBZ4557.fep02-mail.bloor.is.net.cable.rogers.com@localhos t>
>Been looking through the hacking manuals for XConq. From what I can tell
>the only way to manipulate rules or data used by XConq is through text
>files is that right? Meaning there is no standalone design tools. I'd be
>interested in setting up some tools if that was the case. Preferrably on
>a Windows platform, I could probably pull of an SDL or
>X11 version if it would benefit alot of people. I'm guessing the majority
>of XConq developers are not big Microsoft users?
You are right about the last point, though a lot of users ask for Windows
binaries :-).
As for design tools, both the tcltk and mac interfaces have sophisticated
design tools that you can access through the "Design" menu item. This is
for game design in terms of the data, however. To change the rules you have
to hack the game file. If you want to build a graphic interface for this
(GDL programming) you are certainly up for a major task. But I guess it
could be done.
If you want something everybody (Mac, Unix, Windows) can run, you should
use tcltk, or looking ahead, sdl. The x11 interface only runs on Unix with
x11. There are some x11 emulators for Mac and Windows, but I have not
tested the x11 interface on any of them. Anyway, this interface is obsolete.
The hacking manual (and the other manuals as well) is obsolete. Its
excellent for the stuff it covers, but lots of stuff is missing.
Hans
next parent reply other threads:[~2003-05-01 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030501160856.JPBZ4557.fep02-mail.bloor.is.net.cable.rogers.com@localhos t>
2003-05-01 20:49 ` Hans Ronne [this message]
2003-05-01 16:37 robert.segal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='l03130302bad6f9228c55@[212.181.162.155]' \
--to=hronne@telia.com \
--cc=robert.segal@rogers.com \
--cc=xconq7@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).