On August 22, 2011 09:51:37 AM Jeffrey Martin wrote:
> Is the usage of QT by
> Autopano Pro (and Autopano Giga) the reason that those programs work
> exactly the same way (i.e. really well, no obvious errors in UI, etc.) on
> mac, windows, and linux? I can't say the same for Hugin. I don't know if
> this is something to do with wxwidgets or not.

Not so simple, but to answer it in simple terms, yes in many cases and no in 
some others.

Selecting/editing a table cell is a basic functionality provided by the GUI 
toolkit (Qt or wxWidgets).  The app developer merely calls that 
functionality, and if the toolkit is slick so is the app.  The chances that 
the toolkit is slick are bigger because the more apps rely on it, the more 
eyeballs reports bugs and contributed fixes.

On the other hand, displaying and editing control points is specific 
functionality provided by Hugin.  The code still uses primitives from the 
GUI toolkit but has a significant custom layer that does not get as much 
attention as the basic functionalities provided by the toolkit.

Qt definitely covers more ground than wxWidgets and provides a more complete 
app framework, enabling developers to write apps with less code (= less 
bugs).

Another source of rough edges is when the app is written and built against 
earlier version of the toolkit and not taking full advantage of the 
improvements to the toolkit over time.  This can be backward compatibility 
by design or, more often, simply lack of resources to bring the app up to 
date and ditch backward compatibility.  AFAIK Hugin is still compatible with 
wxWidgets 2.6.  Fixing this is not rocket science, but tedious and 
unthankful Sisyphean task.

So bottom line: yes Qt would help, but it is not the only factor.

Yuv

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to