The printed data was using instead of spaces when printing out all
extensions found. This resulted in the browser not being able to properly
separate rows.
In practice, this means that the tables are initially collapsed and hide
all authors with a workload below one percent. The user can expand a
table in order to show all authors found during statistical analysis.
In practice, this means that whenever an author is not part of a
collection of periods he will not be printed out.
This cleans up the output and also speeds up analysis.
The output was simply wrong and was outputting extra "<authors>" tags all
over the place. Also, whenever there was very little work, this was not
included in the timeline.
Multi-line POD comments in Perl are not supported for now; they are a
little hairy and probably require a little extra work in order to be
parsed correctly.
This can now be done by supplying one (or both) of the "--since" and
"--until" parameters to the gitinspector executable. These parameters
work in the same manner as they do in git and accept the same values.
Statistics will only be generated from data between the given interval.
The call to git log included "'" characters to "stringify" input to the
git command. On unix systems, this functions the same way as the
citation (") character. On Windows however, it does not.
This bug occurred because whenever the "git blame" command detects
international character it outputs a string escaped character string in
the form "\ddd\ddd". Gitinspector didn't properly handle this. Python
offers a way to decode this using the decode function together with the
"string_escape" encoding.
The Outputable class is now the base class of all the classes that want to
output formatted text. This is more object oriented and cleaner solution
compared to the previous implementation.
Instead of directly supporting the version module, XML and HTML output will
instead always output a version string somewhere to indicate with what
version of gitinspector the output was generated.
This output is a good start and should work fine as a first template that
can be used when implementing HTML output in all other modules.
Once this is done we can work on adding some interactivity. However; it
might be a good idea to just release a version with some simple HTML
output before adding more complex stuff.
