* GUI problem
@ 2003-11-19 14:15 Brandon J. Van Every
0 siblings, 0 replies; only message in thread
From: Brandon J. Van Every @ 2003-11-19 14:15 UTC (permalink / raw)
To: xconq
Ok, I see a problem with writing new GUIs for Xconq.
I'm looking at the libtkui code. I am counting ~250 global C functions.
It's all rather monolithic. I simply can't write to that kind of
interface. I don't think many people can, unless they're being paid for
it day in, day out.
As far as I can tell, the level of complexity of reusing Xconq code for
new GUIs is untenable. One would be better off writing a completely
generic OO GUI for hex-based TBS games "from scratch," and let someone
who actually understands all that Xconq code worry about trying to hook
into it. The knowledge investment is simply not worth it to any
newcomer. This, I think, is the unfortunate legacy of a "flat" rather
than OO development model.
Do people who know the codebase see some great clarifying principle that
I am missing? This looks like weeks and weeks and weeks of work.
Cheers, www.indiegamedesign.com
Brandon Van Every Seattle, WA
Taking risk where others will not.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-11-19 12:28 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-11-19 14:15 GUI problem Brandon J. Van Every
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).