[Freeciv-Dev] Re: CMA 3.0

[Raimar Falke <hawk@xxxxxxxxxxxxxxxxxxxxxxx>]

On Wed, Dec 19, 2001 at 10:41:55PM -0600, Mike Kaufman wrote:
> here comes some more bloat!
> there's a (largish) patch for CMA 3.0 in incoming/ on the ftp site
> 
> please try it out and try to break it.
> 
> a short synopsis of what's done:
> 
> rename taxmans -> taxmen

> renamed some files whose names were obscenely long (sorry Raimar ;)

We will speak about this latter ;)

> integrated into new city_dialog
> ability to add/delete presets
> ability to save/load presets
> predefined presets are in README.cma
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> notice this! you no longer get free presets 
> (you need to make a bit of effort)
> 
> still needs to be done: (not too critical, though in order of importance)
> 
> CMA messages need to have an option for where they go to.
> lot's o' documentation on CMA --> helpfile
> still more comments in function headers.
> delete preset needs better focus
> use data/freeciv.rc for keyboard
> 
> if you are reading this, you just might be interested enough to create
> a patch to do what still needs to be done. Send me a patch!
> 
> sketchy:
> 
> add asserts?
> flush additional attribute to the server?
> more keyboard shortcuts?
> xaw port: not that this is sketchy -- it should be another patch
> 
> opinion on these?

I haven't looked at the patch and will have no time before new year.

> Please note that this patch required my previous 
> save_options patch (PR #1097) which saves the client's options using
> secfile_* (see how useful it is? :) It's in there so you don't have to 
> go find it to apply this one.

This should be solved by attributes. There should be an extra
attribute flag which is either: SAVE_ON_SERVER, SAVE_ON_CLIENT,
SAVE_ON_BOTH. Note that you also have to specify from which source you
want to load attributes because this will lead to clashes
otherwise. The client attributes could be saved in a simple binary
file ".civclient.attributes". Yes this isn't nicely editable but the
other option would be to have two interfaces: the attribute one and
another one for the textual client side.

        Raimar
-- 
 email: rf13@xxxxxxxxxxxxxxxxx
  One nuclear bomb can ruin your whole day.