FreeOrion

The IDS calls for a CreateSitrepUpdate() and HandleSitRepUpdate() interface in the EmpireManager hierarchy in order to send and receive the sitrep for a new turn.

For a couple of reasons, I'd like to include this information in the Empire updates and dispense with having seperate empire and sitrep updates. If nobody has any objections, I'm going to get rid of those methods.

At some point we need to maintain/rewrite the IDS to account for the changes we're making.

JB

_________________
Empire Team Lead

If you're aying that you want one update sent to each client, then that change is already relfected in the way the Networking code handles things. I made a similar note about the IDS when I posted the code, but as you know that posting is now lost to history.

I don't see any problem with that.

And updating our designs has been on my todo list for about a couple months now . But it's been prioritized behind getting the code done, so nothings been happening there. I think once we hit the point where we have a functioning galaxy map I'll leave off coding for a while to get our documentation up to date.

_________________
Programming Lead

I think we can screw updating the IDS for v0.1; its so simple, and I think we more or less know what needs to be changed.

I think we should do a re-write of it sometime. Perhaps after 0.1, definitely after 0.2. Let's at least wait till 0.1 is finished, because the interface changes will probably have stabilized by then.

JB

_________________
Empire Team Lead

The only reason I say screw it is that, like you, I think we should wait until the interface is more stable, but at that point who cares about v0.1? At that point it'll be time for v0.2.

I think at some point we'll want to do one for 0.1 or 0.2 or whatever the last completed version is, because we're going to want one for the current state of the code.

Maybe we should hand this one off to the documentation team?

JB

_________________
Empire Team Lead