From: Pablo d'A. <pab...@we...> - 2006-10-26 19:34:48
|
Hi all, Daniel M. German schrieb: > This is my plan for release 3.0.0. I'd like to hear comments and > possible things I have missed. > > > MAIN GOAL IN THE SHORT FUTURE: > > * Create callbacks that hugin can use (and add them to pano13), for > all the processing done in panotools, so it does not to run the > programs. While in general, this is a good idea, the question is what functionality needs to be available in hugin? Do we need a complete, real life preview with the effect of color correction etc? Maybe the main question is if hugin should call the external programs for final rendering, or should it use the routines in libpano13 directly. I still don't have a real feeling for what should be better. Most end-users would probably like don't care how its done, if it only works, while some experts will probably remap the panos or just write out a panotools script and then use the commandline or their own scripts for further processing. Also, on the hugin side, some work is needed, because I do not use the sometimes strange libpano12 internal data structures for storing the panorama state and images (Instead hugin uses own classes, which also have become bloated over time..). I have a function to fill the data structures so far that I can create the coordinate transforms, but currently, thats it. > SHORT TERM: Release 3.0.0 > > ---------------------------------------------------------------------- > PTmender: > > > DESIRABLE FEATURES: > > - Insert script into the TIFF comment field. > > - Cleanup command line options, and add a -h option > > - Process fisheye lenses. > > - If somebody wants full compatibility with PTstitcher, a new program > can be added that does all the work. It will be a "superset" of many > of the current pano tools. Hmm, as Max has noticed, changing the interface of the tools extensively has to be well thought out. While I personally don't have a problem with a bare bones PTmender, some people might be surprised. Hmm, maybe renaming the stripped down PTmender to PTremap, and providing some shell script/frontend application with a superset of PTmenders and PTStitchers functionality, if possible? > ---------------------------------------------------------------------- > > PTblender: > > DESIRABLE: > > - (PTblender) Create photoshop curves and maps for HSV colour > corrections For people without photoshop or if somebody wants to run enblend on them, it might be a good idea to provide an option to write out the recolored images. > - (PTroller) Add the ability to stack and add composing images. I assume this will then just apply the curves file created by PTblender, right? > DESIRABLE new tools: > > PTcrop: > > - Two options: crop to bounding rectangle, and crop to inner rectangle > (I think that were the names Pablo gave them). I'm not sure if inner rectangle was a good description. ;-) Some of that functionality would be a good thing to have. > ---------------------------------------------------------------------- > LONGER TERM: > > * Allow tools to read their parameters from the PTstitcher script. Actually I think the PTstitcher scripts are a bit messy to parse, and especially they are hard to extend nicely. Switching to some better formated alternative, like an windows .ini file, or maybe even an xml document might also be something that should be considered for the future. > * Add support to all the tools for 16 bit, and 32 bit images (it is > kind of mixed at this point) I assume with 32 bit you mean float? That might be a bit tricky for PTblender. ciao Pablo |