Jean-Marc Lasgouttes wrote:
[EMAIL PROTECTED] writes:
On Mon, 13 Aug 2007, Abdelrazak Younes wrote:
Look at loadChildDocuments(). It's all in the commit logs.
Being somewhat lazy and ignorant, is there a link to the commit logs?
And you will learn they say
* Buffer: load all child documents in one go where it makes sense.
This has the advantage to call updateLabels() only once for the
master buffer and to get rid of the LyXView dependency. We can think
of maintaining a child document list in the future.
Now it is up to you to guess where it makes sense. Is the intent that
all child buffers are always loaded?
Yes. And this has always been like this. The difference is that we load
all the child documents at the same time instead of waiting that the
loading is asked by some insets.
Was the impact on really large
files been evaluated?
As I said, the loading happens anyway. Loading them preably make the
loading actually make the overall parsing _faster_.
Are previews computed on such un-shown child
documents?
If you mean BufferView and Workarea initialisation. No, they aren't.
These files are loaded in the background. They are accessible in the
Document menu but not in the TabBar. This, by the way, is very helpful
when you have a lot of of child documents: you don't want all of them to
have a tab button.
Why have the documents to be scanned once more instead of
doing recursive loading directly in Buffer::read?
Because it's faster and because we won't have to update the Labels each
time a child document is found.
Abdel.
