Didn't I just say something about some documentation being a bit ...
sparse?
Please, all you programmers out there:
Take an additional hour or so, after you are "done" with the Real
Work, and expand the "help" and man files.
Then take yet another hour, go back over your code and add some
comments. (Well, really, you should be commenting as you go.
Shouldn't you?)
Coolness isn't cool if nobody but yourself and three buddies can use
it / make sense of it.
Come on now, everybody reach for the next level TOGETHER. ;)
Thanks,
eo
On Nov 21, 2010, at 10:18 AM, kfj wrote (in part):
.... I looked at likely candidates among the scripts that handle pto
files, but all I
found was extremely meagre documentation. It made me really angry.
Like there is 'hugin_stich_project'. It is a command line tool to
stitch a hugin project. It states
Verwendung: hugin_stitch_project [-h] [-o <str>] [-t <num>] [-d]
[<project> <images>...]
-h, --help show this help message
-o, --output=<str> output prefix
-t, --threads=<num> number of threads
-d, --delete delete pto file after stitching
... and that's it. (there is a man page which says the same in
slightly more words).
. . .
I lost patience.
with clenched jaw from grinding my teeth
Kay
--
--
You received this message because you are subscribed to the Google Groups "Hugin and
other free panoramic software" group.
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
