Skip to content

Simplify configuration after install #41

@Fxhnd

Description

@Fxhnd

Installation has become easier because of the wheel, but Macleod still doesn't, "Just Work" immediately after install. This could be simplified by setting some safe cross-platform defaults in the configuration and then adopting a setup where a user-supplied config file overrides the default behaviour if needed.

  1. Change how Macleod searches for and uses the provers
    • Search for the application name on the PATH environment variable
    • If the name is found then assume it is active by default
    • Default some values, using minimal system resources, for each application
  2. Change how Macleod resolves imports relative to other files
    1. Standard search paths
      * Documented standard search order people can reference (e.g. cmake) and build their workflow around
      * Begin search for imports relative to current file or current working directory
      * Continually search folders higher in filesystem until some stopping point (e.g. marker file, max_limit, etc)
      * Configuration values accept HINTS of directories to search first prior to the tiered search upwards
      * Add COLORE (https://github.com/gruninger/colore), OntoHub (https://ontohub.org/) well known URIs
      * Configuration accepts additional URIs for import parsing
  3. Allow users to manually override each setting via their own config file given by some file following some standard location (maybe ~/.macleod, %APPDATA%, XDG standard, etc)
  4. Both CLI entrypoints and the GUI should accept a config file as an optional argument and/or support overriding individual parameters via the command line.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions