thanks for your detailed response.
I would like to implement most of your suggestions.
Unfortunately, it seems that my bosses have decided
against keeping our OpenOffice solution. This could
very well be a failure on my part to write optimal
code, I don't know.
But while I am on my soapbox, I
Kent Gibson wrote:
thanks for your detailed response.
I would like to implement most of your suggestions.
Unfortunately, it seems that my bosses have decided
against keeping our OpenOffice solution. This could
very well be a failure on my part to write optimal
code, I don't know.
But while I
There is no loading, we render each document from
scratch and always keep the result in memory. It is
hard to pinpoint our bottlenecks. There is not one
particular place. However for example, inserting into
the document and stlying each cell of a table are
pretty costly operations.
Just last week
We render documents using the api. For the most part
everything is great but performance.
Are there any ways I can tweak a bit more peformance?
For example we do not use the database, calc or
presenation components. Is there any way I can make
sure these components are not slowing things
Hi kent
did you have a oook at lockControllers and unlockControllers ?
http://api.openoffice.org/docs/common/ref/com/sun/star/frame/XModel.html#lockControllers
Laurent
--
Laurent Godard [EMAIL PROTECTED] - Ingénierie OpenOffice.org -
http://www.indesko.com
Nuxeo Enterprise Content Management
thanks. I have tried that. But 1) I noticed no
difference (should there a big gain?) and 2) sometimes
even though I render in a read only document the
results are not the same. I can remember that x,y
results from my view cursor sometimes looked odd. I
should probably test this again, before I has
Kent Gibson wrote:
We render documents using the api. For the most part
everything is great but performance.
Are there any ways I can tweak a bit more peformance?
Hard to give a specific answer for such a general question. :-)
For example we do not use the database, calc or
