View Single Post
Old 10-18-2010, 04:37 PM   #11
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,447
Karma: 8012886
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
I should say that in a measurable percentage of cases, I don't bother with the designer. I build the dialog in code. For example, the new check_library is done that way. My reason: it is more of a bother to build the .ui file and then interface to it than it is to build the dialog directly. More examples: the custom column tabs in metadata edit are also built by code, because they depend on the DB and can't be known in advance. The test fields in search/replace are built by code.

On the other hand, the plugboard UI and the various 'manage X' dialogs were done with designer.
chaley is offline   Reply With Quote