Resources Configuration File

Description

A simple, JSON based configuration file for specifying one or more path prefixes, for automatically resolving into a full resource path -- absolute directory path. This path can then be used for things like establishing a relative filesystem root (vaguely similar to Apple's Application Bundle format).

Why

This was developed to help create a consistent packaging (distribution) directory layout between not only development and release builds but across platforms as well (OSX, POSIX, Windows). An emphasis is made on development builds, where the installation paths are often the project's own build directory (always considered temporary), and are subject to being moved around as development progresses. Furthermore, in order to help ease support of features like reloading a file(s) at run-time, it often makes sense to not use an installation or (temporary) build path, and rather prefer use of a stable path -- i.e.: nomlib.git/Resources directory.

...if only Apple's app and library bundling ways ruled the world -- I'd happily settle for apt-get, though!

Configuration File Syntax

// v1
{
  "resources":
  {
    "search_prefix":
    [
      "./",
      "../../",
      "../../../"
    ],

     // This relative path will try to be resolved to each of the search 
     // prefixes specified above, stopping at the first fully resolved path.
    "path": "Resources/tests/gui/librocket/nomlibTest/"
  }
}