Atom Configurations

Atom Configurations provide facilities for do configurations and profiles for enviroments, Games of course instead of just normal Java applications.

The past

First let’s take a look into the past of years and see how Java developers do configurations for their applications:

  • The config files for application in desktop enviroments may loaded from user’s home, or the app’s folder. The config files can be plain text, XML, JSON, binary or something else.

  • The config can also be received from external sources like from network services, database. The protocol for them can be object base (POJO), relational structure based (resultset) or else …

  • The config can also be intelligently procedure based in the stats and infos of the device or deployed enviroment…

So there is not a single way to do configurations. Is there an unified way now? The answer is still NO. Configurations is the aspect of gamedev SHOULD be kept flexible the most. Tricks and smart stuffs can involve in this progress a lot: optimizations, per device & per user configuration, policies… In another hand, it keep you busy with tricky parts and complexibilities of underlying datastructure and extra progress.

Some other libraries and game engine tend to hide the detail from developer and provide a premade solutions for configurations in supported enviroment.

Ex: LibGDX with Prefs, Unity with Metadata, XNA with Properties…

The more configurations apart from Data and Code, the more it getting complex. In the other hand, getting closer, it mixed and tangled with Data and Code. So how can we make it the right way?

The solutions

The Solution is actually very practical as it should. It’s the corporation of existed techniques but with a fine-tuned and industrial approaches. The “Fine tuning are predefined or customized by the user them self (if they know how to do it). Isn’t it what is configurations is all about. Think about a ridiculous control panel which have only one button, and the other complex and also not very useful with 300 of them… This framework is your control panel, tailored by you! What it help:

  1. There are “fine-tuned configurations for enviroments , devices, users, or aspects… and custom configurations for arbitrary scope and context.

  2. Abstract out the data structure of configurations and its lower level of persist, load and communications.

  3. Revolution in the publish, deloy enviroment and progress: to make the configuration actually is data (and code…), not something else.

Technologies

  1. AtomEx’s Universe provide a repository of configuration profiles. Concepts and mechanisms of Atom’s Universe is the similar to Maven repository. So Java dev can use Maven or Gradle to include them at development time (or even runtime). In runtime, an IOC mechanism is provide for configurations initialization similar to Spring system.

  2. Apache Commons & Archaius to abstract out the data structure of configurations. Under them are Utils that consider appliance of configurations as watchable Tasks.

  3. Gradle and Go is employed in the deploy progress make it very flexible and watchable. Configuration publishing is supported by tailored GUI Editors in JMP. Generic configuration editors for Text, Properties, XML, JSON… are also provided.

Toolset

Documentation