Luca, I just followed your advice and moved the Processing.initialize()
call to initGUI().
I did not test, however, to check that startup time has improved. The
change is already in master, so you can test it.
Let me know if you have more suggestions
Thanks!
2014-09-19 14:02 GMT+02:00 Luca
Hi all,
moving Processing initialization to initGui() does not change situation.
I played with this about week or two ago. The problem is in another
place and I plan to work on this with Victor at hackfest
2014-09-24 12:10 GMT+03:00 Victor Olaya vola...@gmail.com:
Luca, I just followed your
Great. Thanks for the work Alex.
Looking forward to being at the HackFest!
2014-09-24 11:15 GMT+02:00 Alexander Bruy alexander.b...@gmail.com:
Hi all,
moving Processing initialization to initGui() does not change situation.
I played with this about week or two ago. The problem is in another
On Thu, Aug 28, 2014 at 5:31 PM, Victor Olaya vola...@gmail.com wrote:
I am away until Sept 5th, but will work on that once i am back. Didn't know
about the init() and initGUI() separation, so thanks for the info.
A large part of the time it takes to start Processing is probably spent in
I am away until Sept 5th, but will work on that once i am back. Didn't know
about the init() and initGUI() separation, so thanks for the info.
A large part of the time it takes to start Processing is probably spent in
reading the description files for SAGA, GRASS and OTB algorithms, so i will
try
On Wed, Aug 27, 2014 at 7:43 AM, Martin Dobias wonder...@gmail.com wrote:
Actually since the adoption of metadata.txt for plugin metadata it is
not necessary for QGIS to load all python plugins on start up. I have
a suspicion that it is the plugin installer component which tries to
load them
Hi.
Perhaps this is due to the plugin onstaller serring alway update at
startup ?
Il 27/ago/2014 06:35 Nathan Woodrow madman...@gmail.com ha scritto:
It should also be possible to add some timing stats to the plugin loading
code from the QGIS side to log which plugins are taking time to load.
Il 27/08/2014 08:36, Luca Manganelli ha scritto:
On Wed, Aug 27, 2014 at 7:43 AM, Martin Dobias wonder...@gmail.com wrote:
Actually since the adoption of metadata.txt for plugin metadata it is
not necessary for QGIS to load all python plugins on start up. I have
a suspicion that it is the
On Wed, Aug 27, 2014 at 9:23 AM, Paolo Cavallini cavall...@faunalia.it wrote:
I have seen plugins occasionally getting broken: are you suggesting to do the
check
only on activating them (+ at install time of course)?
All the best.
No. As Martin Dobian suggested, when QGIS is loading, only
When and how will the creation of menu items and push buttons for the
plugins be done?
Regards
Bo Victor Thomsen
Aestas-GIS
Denmark
Den 27-08-2014 09:37, Luca Manganelli skrev:
On Wed, Aug 27, 2014 at 9:23 AM, Paolo Cavallini cavall...@faunalia.it wrote:
I have seen plugins occasionally
On Wed, Aug 27, 2014 at 10:24 AM, Bo Victor Thomsen
bo.victor.thom...@gmail.com wrote:
When and how will the creation of menu items and push buttons for the
plugins be done?
It can be done inside initGUI() function.
___
Qgis-developer mailing list
Hi,
in our organization with over 1,000 windows machines, we install QGIS
on a windows samba share so it can be launched via a desktop shortcut.
We discovered that the processing python plugin is the slowest plugin
to load. The QGIS base install contains 5 python plugins (fTools,
metaSearch,
Hi,
interesting issue.
More generaly, startup speed starts to be an issue here, and plugins take
more than half the time of global startup.
Do we have tips for plugin authors to speed up python loading?
Do we have already investigate all startup bottlenecks ?
Cheers
Régis
--
View this
On Tue, Aug 26, 2014 at 5:36 PM, Régis Haubourg
regis.haubo...@eau-adour-garonne.fr wrote:
Hi,
interesting issue.
More generaly, startup speed starts to be an issue here, and plugins take
more than half the time of global startup.
Right. If we remove all of those plugin, QGIS is much faster
It should also be possible to add some timing stats to the plugin loading
code from the QGIS side to log which plugins are taking time to load.
- Nathan
On Wed, Aug 27, 2014 at 2:29 PM, Luca Manganelli luc...@gmail.com wrote:
On Tue, Aug 26, 2014 at 5:36 PM, Régis Haubourg
On Wed, Aug 27, 2014 at 11:29 AM, Luca Manganelli luc...@gmail.com wrote:
Do we have tips for plugin authors to speed up python loading?
Yes, they should move the big code from init() to initGUI().
They should remember that the code in init() is ALWAYS executed, even
with that plugin
16 matches
Mail list logo
