<br><br><div><span class="gmail_quote">2007/6/7, Angelo Naselli <<a href="mailto:anaselli@linux.it">anaselli@linux.it</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Alle gioved¨¬ 7 giugno 2007, Krasu ha scritto:<br>> Wed, 6 Jun 2007 22:58:39 +0200, Angelo Naselli <<a href="mailto:anaselli@linux.it">anaselli@linux.it</a>><br>> §á§Ú§ã§Ñ§Ý(§Ñ):<br>><br>> > ImageViewer : initial import of new OpenGL based image
<br>> > viewer.<br>><br>> Hmmm.. Now image viewers will have two ways to open images ? KSquirrel,<br>> for example, will have two OpenGL image viwers :( If this plugin will have<br>> delayed init, it's ok. But if it will initialize itself on load, it will
<br>> eat CPU time and memory.<br>Ksquirrel is a viewer, not the only one of course ;)<br><br>Anyway you should be able to disable the plugins that your host application<br>doesn't need.<br>Gilles can you point him how to do that? thanks.
</blockquote><div><br>You want mean how to disable a plugin in a host ? If yes, look in digiKam source code, KameraKlient plugin is disable for ex. Look in digikam/digikam/digikamapp.cpp in DigikamApp::loadPlugins() method.
<br><br>Gilles</div></div><br>