Document loading in kdevelop4
amantia at kde.org
Sun Jul 23 06:47:44 UTC 2006
On Sunday 23 July 2006 01:26, Adam Treat wrote:
> Then the document loading on project startup would be limited only by
> the speed of the background parser.
Good idea, with possible the following enhancement: construct the KParts
in the background if the application is idle. If this is too hard to
detect due to the plugin architecture, you might try how it works out
by constructing a KPart each X ms with a timer.
This would make switching to a document in some cases faster, with the
drawback of higher memory footprint. But not higher as today. Also make
sure if the tab is closed with the close button or from the context
menu of the tab, the KPart is not created and destroyed. ;-)
A question though about the document parser: does it operate on the
files on the disk or on the loaded documents (via KTextEditor)?
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the KDevelop-devel