Re: [Rails-devel] autosave files

[Stefan F. <ste...@we...>]

I agree, but currently none of the config/properties options can be adjusted 
by the GUI (as far as I know at least), thus I follow good practice here ;-)

Serveral ways to improve the mechanism:

1) Create a UI to edit the configuration options
2) Store user adjustments
3) Provide ftf/pbem defaults properties

2) and 3) are easy to code as they are directly supported by the properties 
class. For 1) the tedious part is to enforce restrictions and provide help 
text.

Stefan


>
> As a general rule, we should try to most options that affect loading,
> saving, and gameplay into the GUI.
>
> Properties file options are great for development and "sensible"
> defaults that few people will want to change.
>
> We can then have the GUI update the properties file with the updated
> settings (if it doesn't already).
>
> > A possible solution for the conflicting "defaults" are predefined
> > configuration files for ftf and pbem plays.
> >
> > Maybe even asking for the preferred configuration on the first startup?
> >
> > Stefan
>
> ---Brett.
>
> ---------------------------------------------------------------------------
>--- This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel