[Qt-interest] Reducing Qt footprint when using plugins

Tim Dewhirst tim at bugless.co.uk
Thu Jul 9 18:37:56 CEST 2009


Afternoon,

Christopher Boger wrote:
> Yeah that’s what I was afraid of. I think the current implementation 
> forces you to include pretty much all gui elements if you use plugins, 
> even if you’re doing a very simple plugin. (I was able to prune out some 
> non-gui stuff.) I don’t see why one couldn’t go through the code and 
> remove some of the larger unneeded stuff, which is what I might have to 
> do.  It would also be nice to know the approximate code sizes associated 
> with all the Qt features, so I can focus on the big ones.
> 
> Note that I’m not trying to run Designer in my app, only support a 
> simple custom widget plugin.

I'm assuming that from the previous discussion that you're using 
QFormBuilder to load your .ui file. Would QUiLoader perhaps be better 
(not being part of the QtDesigner module)? This should support loading 
from designer plugins. If not, then you could compile the custom widget 
code into your main app. and override createWidget().

Tim




More information about the Qt-interest-old mailing list