Address #133 (examples broken due to transform creation changes)

By default, when Transform::fromAlgorithm is used, attach a stream transform
as the root of whatever transform is created (can be disabled with a flag).

Actually implement stream project(template), give a warning if only returning
one of N templates.
Warn on Expand::project(template), qFatal is excessive here
Added ReadLandmarks
Fixed some documentation on ReadLandmarks
Merge pull request #134 from biometrics/template_updates

Address #133
Added coordinate output in draw, moved some landmark related transforms to landmark.cpp
Merge branch 'master' of https://github.com/biometrics/openbr
Bug fix for case when no face is detected
Merge branch 'master' of https://github.com/biometrics/openbr
Add a script running FaceRecognition using the LFW protocol

Rscript will actually crash partway through writing the output pdf, presumably
because the recognition curves are degeenrate in this case.
Add option to crop ROI from a metadata field
Add option to enroll TemplateList from C API
generalized evalGenderRecognition script
Add br_img_is_empty to C API in case imdecode fails
In train, use the parallelized transform when projecting
Fix br -objects
Fix a periodic crash when running br -objects without -useGui 0

Fix a crash periodically manifested in br -objects which was caused by
ShowTrainingTransform's transform * creating and deleting a ShowTransform so
quickly that its associated window still had incoming messages when it was
deleted in ShowTransform's destructor.

By using the deleteLater slot instead of calling delete directly we can be sure
that incoming events are processed before the window is deleted.
Don't use ! as a shortcut for +Expand+
Merge pull request #136 from biometrics/calm_down

Remove the '!' abbreviation
Rework smartCopy

If we are doing nonsense like composing algorithms in memory, checking for
a NULL parent is not a viable way to detect when smartCopy has returned a
loose transform. This is because root transforms created through
algorithmCore or whatever also have NULL parents, but actually they will
be deleted via QSharedPointers, so adding them to a parent chain is
dangerous, and they can show up as child transforms if we say attach them
as children of a stream or distribute transform as part of a
parallelization scheme.

So, instead we add an output parameter to smartCopy indicating if the
returned pointer is a newly allocated transform, that is not already set
up to be deleted.