public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "xconq" <xconq7@sources.redhat.com>
Subject: RE: Mono, anyone?
Date: Tue, 18 Nov 2003 21:01:00 -0000	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDAEPAGLAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <1069180897.29637.102436.camel@odysseus.peterslan>

Lincoln Peters wrote:
>
> Has anyone considered taking advantage of Ximian's (Novell's?) Mono
> project?

Have you?  I can think of a zillion things Xconq *could* have in it...
but I concentrate on the ones I'm fully willing to implement myself.  No
harm in asking if someone else is also interested in Mono, but my point
is you have to be the one to lead the effort for that sort of thing.

> * Allow Xconq to talk to a other application.  This may
> initially sound
> silly, but imagine how much easier it might be to play games such as
> bellum.g if you could use a spreadsheet to represent various
> aspects of
> your empire (particularly such things as supply of 'c') using charts.
> It might not be quite so bad for Xconq to behave (to some extent) like
> an office application.

What I *have* considered, is writing the Windows UI in C# and .NET.  I'm
a .NET nunce, I don't know what its GUI features are.  Maybe it has some
kind of applicable "spreadsheet form."  Thanks for reminding me that
right-click popups won't solve all UI problems, I'll need a National
Budget screen somewhere.

If I go the C# .NET route, then I'll simply leave it to others to worry
about porting it to Mono.  But one thing I've discovered, that I didn't
realize before, is that C# is not exactly a good language for interoping
with C directly.  You have to create DLLs and do all this marshalling
stuff, it's a tedious function-by-function job.  Either that or wrap
stuff up in Managed C++.  Neither would be so bad if the C was legacy
code awaiting conversion to something more modern, but I expect it will
be a live target for some time.  I have no interest in chasing the C
coders' tails with my manual labor.

So today, I'm looking at Python / C interop.  Possibly a "make this more
OO" effort needs to precede C# .NET efforts.  Once I have a higher level
construct summarizing the Xconq interactions, use that to bridge to C#.
NET.  This is like the idea of wrapping stuff up with Managed C++,
except I'm wrapping stuff up with Python.  And then accepting possibly
some more difficulty implementing the interop bridge.

Or there's Door #3: finding a Python GUI that has the right-click popup
and spreadsheet tables I need.  Another thing I'll be looking at today.
But my concern is there's probably no RAD tool at the same level of
quality as C# .NET in the Python world.  I want to bang out GUIs
quickly, not futz manually.


Cheers,                         www.indiegamedesign.com
Brandon Van Every               Seattle, WA

20% of the world is real.
80% is gobbledygook we make up inside our own heads.


  reply	other threads:[~2003-11-18 20:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-18 18:42 Lincoln Peters
2003-11-18 21:01 ` Brandon J. Van Every [this message]
2003-11-18 21:28   ` Lincoln Peters
2003-11-19  0:22     ` Eric McDonald
2003-11-18 21:22 ` Eric McDonald
2003-11-18 21:47   ` Lincoln Peters

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=OOEALCJCKEBJBIJHCNJDAEPAGLAB.vanevery@indiegamedesign.com \
    --to=vanevery@indiegamedesign.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).