Hi Bruno, 2009/10/9 Bruno Postle <br...@postle.net>: > > On Thu 08-Oct-2009 at 10:04 +0200, Lukáš Jirkovský wrote: >> >>> I know I'm not great at this stuff, but in the panostart tool there >>> is a perl module that abstacts all the business of writing and >>> escaping Makefile rules, i.e. you declare your intent with a list of >>> input files, a list of output files, and the command(s) needed to >>> generate those output files: > >>Yep, it's much cleaner. But I think this would be much more easy to >>implement with XML or other markup language (eg YAML). > > Hugin needs to programatically define all the files it knows how to > create and the commands for creating them somewhere. > > If you abandon 'make' then you need to find some way of recreating > its functionality: > > Currently Hugin doesn't need to worry about ordering of commands, it > just writes rules and then specifies the end target(s) it wants, you > will need to write a dependency solver.
May be fun. I never did that :-D > > You would need to find some way to run commands in parallel as we > can now with -j. > > Currently intermediate files are shared between targets, e.g. if you > specify both kinds of Exposure Fused output, 'make' only remaps the > images once with nona and reuses the files with the two different > enblend/enfuse strategies. I didn't think about that. AFAIK it only looks at the timestamps. The question how difficult is to do it really multiplatform. > > Currently I can stop and restart stitching simply by killing the > process, you will need to find some way of doing the same thing. I > can edit the alpha channel of one of the intermediate files then > restart 'make' and it will pick up at the right point and only > create the files that are effected by my changes. > >>I'd keep .pto format at least for storing image positions etc. But >>with XML it would be much easier to store more informations to store. >>I can think of storing informations about positions, stacks, it would >>be possible to store informations about exposure > > We already store all this stuff in the .pto. I admit that it wasn't a good example. Especially the one about exposure. What I meant about positions was not "absolute" positions like the ones in stored pto but instead something like "pictures a,b and c are in stack" or "this picture is nadir". > > -- > Bruno > > > > It is said that every programmer tried to write his OS in his life. I'm not that experienced (yet ;-) ) so this may be nice start. I've just got an idea that I may reuse it in some school subject. This term they allowed me to try to implement simple denoising algorithm which I invented when I was drunk instead of the boring "standard" task. Lukas --~--~---------~--~----~------------~-------~--~----~ 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
