[Qt-interest] Reducing Qt footprint when using plugins

[Christopher Boger]

I am QUiLoader to load a ui file. My understanding is that QUiLoader
uses QFormBuilder.

Yeah, I wish I could avoid this ui and custom plugin stuff because of
the footprint issue, but it does allow me to support lots of different
GUIs using the same code base, which is a requirement for my app. 


-----Original Message-----
From: qt-interest-bounces at trolltech.com
[mailto:qt-interest-bounces at trolltech.com] On Behalf Of Tim Dewhirst
Sent: Thursday, July 09, 2009 9:38 AM
To: qt-interest at trolltech.com
Subject: Re: [Qt-interest] Reducing Qt footprint when using plugins

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

_______________________________________________
Qt-interest mailing list
Qt-interest at trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-interest