Complete.Org: Mailing Lists: Archives: freeciv-dev: July 1999:
[Freeciv-Dev] Client X
Home

[Freeciv-Dev] Client X

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Freeciv List <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Client X
From: Daniel Sjolie <deepone@xxxxxxxxxx>
Date: Mon, 12 Jul 1999 15:38:32 +0200

Sorry about the stupid name... :)
I'm beginning to feel that I have a good idea how the restructure the
client... There are still a few questionmarks though...
It would be real nice if someone familiar with the client code could
join me in #freeciv some day soon..

Until then I figured I'd post this piece here and see what comes back at
me... :)

[03:10pm] <deepone> I can't figure out the best way to structure my
client model from the player to the gui...
[03:11pm] <deepone> have You read my client ai page?
[03:11pm] <deepone> could You? :)
[03:11pm] <deepone> http://www.shaolie.dhs.org/~freeciv/
[03:12pm] <deepone> I placed a <hr> down by the player where I start to
get into trouble... :)
[03:13pm] <deepone> the stuff after that is old and possily doesn't make
a lot of sense anymore...
[03:14pm] <deepone> I have a good idea in my head how to do this...
[03:14pm] <deepone> the problem is how to do it well... :)
[03:14pm] <deepone> If I was to simply have one ai and one gui then I
would have no problem...
[03:15pm] <deepone> But at this time we have 2 clients and I want to
make it possible to add more and possibly more than one ai...
[03:16pm] <deepone> Coming up with A solition is no problem...
[03:16pm] <deepone> but I want THE solution... Hehehehe... :p
[03:19pm] <deepone> one way would be to have a 'ui' and a 'ai' directory
in the 'player' directory...
[03:19pm] <deepone> but then we should have a 'gui' directory in the
'ui' directory and a 'gtk' direktory in that one...
[03:20pm] <deepone> ...client/player/ui/gui/gtk/
[03:20pm] <deepone> lots of directories!
[03:20pm] <deepone> But it would be a LOT clearer what is what...
[03:21pm] <deepone> Another approach is to go for a shallow structure...
[03:22pm] <deepone> That would mean having 'gui' and 'ai_player' in
'player' and if You want a non-gui ui later You'll have to add another
directory to 'player'...

I think sound would be well handeled in this model...
I certainly think sounds should be all client just like graphics...

One issue is that when You have the ai in the client You loose quite
some stuff if the client craches...
One idea would be to implement a simpel and general package thingy
for sending information to the server for 'safe-keeping'...
I certainly think it would be better than keep adding new packages
for every feature that could be implemented in the client...

/Daniel

-- 
Now take a deep breath, smile and don't take life so seriously... :)

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