From: Eric McDonald <mcdonald@phy.cmich.edu>
To: bboett@adlp.org
Cc: xconq7@sources.redhat.com
Subject: Re: UI proposal
Date: Wed, 19 Nov 2003 17:25:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0311191158160.31399-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <20031119151651.GK387@adlp.org>
Hi Bruno,
On Wed, 19 Nov 2003, Bruno Boettcher wrote:
> but i thought that adding other interfaces was hard due to the deep
> interwindling of xconq game machine and UI, the stuff that prevented a
> clean client server design IIRC?
I am no authority on adding interfaces to Xconq as I haven't spent
much time with the UI code, but the kernel is essentially
abstracted from the interfaces. I also believe that Stan(?)
pointed this out recently, and he said that the ability to add
new interfaces was the primary motivator for this. From a kernel
hacker's perspective, I can tell you that I don't see alot of
evidence of deep intertwining.
However, I will agree that a client-server model would be nice. I
currently don't feel ambitious enough to attempt the separation,
and dropping in the clisrv communication layer in between. I don't
plan on doing this in the 7.6 release cycle either. But perhaps
others are more ambitious....
The reason I have thought about a clisrv architecture in the past
was not for the GUI's, but for the AI's.
Regards,
Eric
next prev parent reply other threads:[~2003-11-19 17:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 8:22 Lincoln Peters
2003-11-19 12:15 ` Brandon J. Van Every
2003-11-19 19:02 ` Lincoln Peters
2003-11-19 14:51 ` Peter Garrone
2003-11-19 14:51 ` Erik Jessen
2003-11-19 15:24 ` Bruno Boettcher
2003-11-19 17:25 ` Eric McDonald [this message]
2003-11-20 0:35 ` Brandon J. Van Every
2003-11-19 17:09 ` Eric McDonald
2003-11-19 19:07 ` Lincoln Peters
2003-11-19 18:37 Elijah Meeks
2003-11-19 19:01 ` Hans Ronne
2003-11-19 19:49 ` Lincoln Peters
2003-11-19 20:04 ` Eric McDonald
2003-11-19 20:36 ` Elijah Meeks
2003-11-20 9:33 ` Andreas Bringedal
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=Pine.LNX.4.44.0311191158160.31399-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=bboett@adlp.org \
--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).