This is the mail archive of the xconq7@sources.redhat.com mailing list for the Xconq project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: JConq


At 07:17 PM 2/8/2002 +0100, Bruno Boettcher wrote:
>On Fri, Feb 08, 2002 at 07:51:58AM -0500, lduperval@microcelli5.com wrote:
> > > So if you want to port xconq to java, I would encourage you to give it a
> > > try. I doubt the result would be much better than existing versions, 
> but I
>uhm i gave it a try.....
>2-3 years ago, maybe you remember...
>i wasn't able to come up with a scema to draw the hexes and all the
>layers above them with reasonable CPU and memory consumption....

Yeah, I remember talking with you when you started out and while I am not a 
UI person I could see that memory was going to be a real killer for the 
code you had at the time.  I didn't have any answers for a better approach 
and I'm still scratching my head on this one.


> > > could be wrong, and the proof is in the pudding. However, changing 
> the grid
> > > seems to me like an unnecessary complication. It is not this part of 
> xconq
> > > that needs to be fixed, it is the network code.
>yeah....
>a true server client design is needed....
>
> > So what exactlky *is* the problem with the net code. Is it the code itself?
> > Is it the design? Is it something else? Is it so incomprehensible that it
> > should be rewritten from scratch?
>design IMHO....
>the server part should be completely extracted from the client...

As Martin Fowler would say, it's time for refactoring :-)  My problem is 
that I'm not willing to do that in 'C'.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]