tl24 / miragemud Goto Github PK

globalLists and QueryManager are static classes.  Allow construction and
setting of the default instance for testing purposes.  Lock the static
instance during initialization and throw an exception if anything else
tries to set it.

Change the login screen to allow a local repository to be set.  Once a
repository is set it is tied to a given server/port.  Once a repository is
set, it will be kept in sync when connected to the server.  

Refactor IOHandler to support this module.  Basically it will intercept
certain commands to do save/retrieval to disk.  During disconnected work it
will handle any requests.  The console will be disabled when working
disconnected and possibly hidden to prevent any extraneous commands.  Any
unrecognized commands will just respond with an error.

Sync operations will be changed to check last modified dates on area files.
 The local repository will also need to keep track of what the user
changed.  Any unchanged files will be synced up with the server when the
user connects.  If there are conflicts, i.e. the user changed a file and
someone else has committed a new version to the server, the user will be
prompted with a dialog to resolve.

When connected to the server, permissions will need to be retrieved and
stored as well so that edit checks happen appropriately.  They will be
checked anyway when committing to the server, but we don't want the case
where the user is allowed to do something while disconnected but fails when
they try to commit it because they don't have permissions.  Maybe allow
them to override their permissions on the client to support a use case
where they only work disconnected and have to mail their files to the admin
to get them posted to the game.

Refactor the "content", e.g. player, area, mobile implementations into its
own project.  This will allow the core services to be used without the
content.  The core will consist of I/O services, initialization modules,
and execution modules, and object repository, and query services.  The
globalLists object will become the "Object repository" and will probably
need to be created via a factory since the content will want to extend it
to add the stuff that it needs to store.