On 10/17/07, Terry Brown <terry_n_brown@...12...> wrote:
It's currently very slow because it uses --query-height etc. many times per slide. I filed a RFE
https://sourceforge.net/tracker/index.php?func=detail&aid=1811901&gr...
but I think I could code this into main.cpp well enough myself... if I do that and submit a patch will it probably make it in, or would it be better for someone more familiar with the code base to do it in a way that's more in keeping with other code - assuming that anyone thinks it's worthwhile, and also assuming my patch might be greeted with "why on earth would you do it that way!?" ;-)
Yes, I think such a patch will be welcome. I just think we need to spend some more time designing the output format of such an option, so that it:
1 is easy to understand for a human even without reading documentation
2 is easy to parse by scripts
3 is easy to extend in the future, to provide more info about objects, without breaking backwards compatibility
Your suggestion in the RFE is good on 2, but worse on 1, and I'm not sure about 3. What do you think?