TODO

TODO
====

Commands
--------

ninjecto render -> Default behavior, render a template

ninjecto run
ninjecto new

Fixes
-----

- Fix namespaces.
- Inconsistent loading behavior:

  - Load ninjeconf.py from another directory? i.e when ninjeconf.py is in CWD
    but source is not.
    - Currently, ninjeconf.py is loaded from source directory.
  - Load .ninjerc.xxx from source directory? i.e when source is not in CWD.
    - .ninjerc.xx is not loaded from source, gitroot and CWD are the latest too
      resolution paths.

  Could all this be fixed with the following changes?:

 - Do not load ninjeconf.py from source relative, do it from PWD.
 - Add --cd-to-src so the behavior is the same?

Documentation
-------------

- Input and output.
- Values.
- Libraries.
- ninjeconf.py
- Configuration and .ninjerc.xxx

Features
--------

- Nice progression: maybe a progress bar, or at least nice logging about what
  Ninjecto is currently processing.
- ninjecto --create, or ninjecto create <name> (vs ninjecto render): render a
  start template with name <name>.
- Command file to execute render? How to execute it? ninjecto render-project ?
- Add support for ninjecto projects in remote git repositories:
  Allow to specify: protocol, user, (password?), repository, revision, tag or
  branch and subdirectory.
- Change directory to source file? Maybe this could help some people with their
  project setup.

Checking
--------

- Avoid overriding the source: is this mandatory? The cases are at least:
  - If source is a directory:
    - Output in and output is source directory: FAIL
    - Output and output is source directory: FAIL
  - If source is a file:
    - Output in and output is source file: FAIL, that makes no sense,
      output_in must be always a directory.
    - Output and output is source path: MAYBE?! Override the file? Why not?
      Ugly?
- Avoid breaking when system configuration files (non-explicit) are broken.
- What about binary files in the template?