Complete.Org: Mailing Lists: Archives: freeciv: July 2002:
[Freeciv] Re: RTS version of Freeciv; need to change my email address
Home

[Freeciv] Re: RTS version of Freeciv; need to change my email address

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: rf13@xxxxxxxxxxxxxxxxx
Cc: freeciv@xxxxxxxxxxx
Subject: [Freeciv] Re: RTS version of Freeciv; need to change my email address
From: "C Ratchet" <zratchet@xxxxxxxxxxx>
Date: Mon, 15 Jul 2002 23:18:45 +0000

OK - so server might not be rewritten, but I do think it would be useful to 
create a web-based interface to the server with checkboxes and spinners. 
That could be implemented using PHP or Perl, right?

Thanks
Ratchet


>From: Raimar Falke <rf13@xxxxxxxxxxxxxxxxx>
>To: Marco Colombo <marco@xxxxxx>
>CC: C Ratchet <zratchet@xxxxxxxxxxx>, freeciv@xxxxxxxxxxx
>Subject: Re: [Freeciv] Re: RTS version of Freeciv; need to change my email 
>address
>Date: Fri, 12 Jul 2002 14:32:25 +0200
>
>On Fri, Jul 12, 2002 at 10:47:51AM +0200, Marco Colombo wrote:
> > On Thu, 11 Jul 2002, C Ratchet wrote:
> >
> > >
> > >
> > > We are currently working on getting more members (majorly needed!) We 
>have
> > > 10 members currently but most seem to be busy, so that is why I asked 
>if
> > > anyone would be interested in helping. Hopefully we can get at least 
>an
> > > alpha out by August, and have a more complete version by end of year. 
>Our
> > > main needs are Java and XML people, and also I'm thinking of redoing 
>the
> > > server in either Java, PHP or Perl (with collaboration with other 
>members,
> >
> > Why redoing the server? I see no big reasons.
> >
> > The only advantage (I can think of) using Java, PHP, Perl o Python
> > is portability for free. Yet I think the server has few system 
>dependencies
> > compared to client code (all clients do have a commom part, to talk to
> > the server, and a very platform specific part, to do graphics and GUI).
> > (Re)writing the client in Java could be a win, it'd be great to run the
> > same client on both Win and Linux/unix. I like Gtk look&feel, but
> > having one "standard" multiplatform client sounds a "Really Good Thing".
> >
> > If you choose to rewrite the server, maybe you should use a language
> > that lets you *easily* use modules written in C. That way, you could 
>gain
> > access to most of the current codebase by just wrapping it in some glue
> > so that you can call C functions from your language. You can later 
>extend
> > some parts by rewriting them in your native language, if you need to.
> >
> > Check out SWIG, http://www.swig.org/, I think it might help.
> >
> > If anybody is thinking of re-designing the server, it should be 
>considered
> > to make it as friendly to SWIG as possible.
>
> > Have most of the code isolated as in a library (which is a step
> > little further than just a "modular design"), so that you can write
> > a high-level driver as the core of your application.
>
>Both the common and the server parts are available as a library. But
>this doesn't buy you anything because you have to share state. A lot
>of state.
>
> > Either you write it in C, or in a high-level language
> > like Python or Perl, you can choose anytime (you can have more than one
> > implementation around, to let people hack with their favorite language).
> >
> > This is a major task, indeed. But it may be interesting even if the
> > driver is written in C like it is now.
>
>       Raimar
>
>--
>  email: rf13@xxxxxxxxxxxxxxxxx
>  "Many of my assistants were fans of Tolkien, who wrote 'Lord of the 
>Rings'
>   and a number of other children's stories for adults.  The first 
>character
>   alphabet that was programmed for my plotter was Elvish rather than 
>Latin."
>     -- from SAIs "life as a computer for a quarter of a century"





---

Check out Age of Freedom - http://ageofreedom.sf.net



_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx



[Prev in Thread] Current Thread [Next in Thread]