Hello, I've got a quite sound idea. Just "to put a bug in your head" (czech saying) – to make you think about it. There are numerous bug reports which are caused by using some "forbidden" characters inside makefile (and some strange bugs too). Sometimes they can be escaped but sometimes it doesn't help or it breaks something.
I can imagine using something different instead of makefile. My first thoughts were about using some dynamic language like python or perl but I rejected these thoughts immediately. They would brink need to distribute python/perl/whatever with hugin. So this is no way. They're too big. What I think may be quite nice way to store necessary data is the XML. Although I'm not a huge XML fan (in fact I think it's overused) it could bring some improvements to the current workflow. I've two ideas how it could help. First it wouldn't break just because someone used = (or so) in file name. Second it would allow to create better structured files which would be more readable especially when working with stacks. However it has it's culprits eg someone would have to write some parser which would process this kind of files. The other problem is backward-compatibility. Let the discussion begin. regards, Lukáš --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
