Thank you so much for looking into these two timing issues.
We look forward to XXE version 8.3 with the fix for the top-level
attribute issue.
I will examine ways to try and deal with our CSS challenge. So I'll
know, was a main part of the problem with the label(xpath()) items the
time it takes to process the xpath statements and that every time such
an element was rendered, it had to process the xpath command again?
--Andy
On 11/17/2018 4:38 AM, Hussein Shafie wrote:
We have investigated this issue. It is caused by this excerpt of your
CSS stylesheet:
---
@property-group contentType()
{
display:concatenate(xpath("if(not((/xlingpaper/styledPaper/lingPaper|/lingPaper)/contentControl/@showOnlyChosenItemsInEditor)
or
(/xlingpaper/styledPaper/lingPaper|/lingPaper)/contentControl/@showOnlyChosenItemsInEditor='no','block',contains((/xlingpaper/styledPaper/lingPaper|/lingPaper)/contentControl/contentControlChoices/contentControlChoice[@active='yes']/@exclude,@contentType),'none','block')"));
}
---
When a "display:" is dynamically computed as above, XXE v8.2 considers
that the subject element depends on ALL its attributes. When this is
the case, changing any attribute causes XXE to rebuild the view of the
element.
We have optimized this. In the above case, XXE now considers that the
elements to which "property-group contentType()" is applied depend
only on the @showOnlyChosenItemsInEditor, @active, @exclude,
@contentType attributes. This is not 100% optimal, however this is
clearly an improvement over the old behavior.
So in practice, the issue you have reported is solved in XXE v8.3 (not
yet released).
=================================================================
--> Now about the extreme slowness of XXE when rebuilding the view of
the <lingPaper> element of your SeriGrammarXML_2017.xml file. <--
In fact, at first, I was not able to open your SeriGrammarXML_2017.xml
file in XXE on my Linux box.
After waiting for several minutes, I just got several "Out of memory"
errors.
In order to open your SeriGrammarXML_2017.xml file, I had to increase
the memory limit of XXE (to 3Gb of RAM) as explained in this FAQ:
http://www.xmlmind.com/xmleditor/faq.html#outofmemory
I eventually managed to open your SeriGrammarXML_2017.xml file but
when using Java 11, it took me 2mn to open this file and, more
surprisingly, 4mn to close it!
Your SeriGrammarXML_2017.xml file is just 7Mb long, but when styled
using your 10000+ lines XLingPap.css CSS stylesheet, it eats about
700Mb of Java memory.
In comparison, when you open SeriGrammarXML_2017.xml without a CSS
stylesheet (tree view), it eats "just 100Mb" of Java memory and it
opens the file in about 3s, closes it in less that 1s.
My conclusion is that XXE is not adapted to editing large XLingPap
documents styled your current XLingPap.css CSS stylesheet.
-->Please consider simplifying your XLingPap.css CSS stylesheet.<--
Please note that we spent several hours analyzing why XXE is so low
when your XLingPap.css CSS stylesheet is used
We came to the conclusion that this is caused by your excessive use
(10000+) of label(xpath()) CSS pseudo-function
(http://www.xmlmind.com/xmleditor/_distrib/doc/csssupport/label.html).
We tried to optimize our "label() manager" implementation and with
this new, experimental implementation, we managed to open
SeriGrammarXML_2017.xml in about 55s and to close it in about 40s,
which is, in our opinion, still unusable.
As a consequence, we are not sure to keep this experimental "label()
manager" implementation in XXE v8.3.
=================================================================
On 10/24/2018 08:19 PM, Andy Black wrote:
We have a custom configuration we've developed and have noticed that
with large documents, when we edit an attribute of a high-level element,
XXE can take an exceedingly long time to respond. This is not the case
if we edit PCDATA in another element that is at the beginning of the
document.
For one case, editing text in the title element is almost instantaneous
(as one would like). Inserting a new element at the beginning of that
title element may take 3-5 seconds, but that is livable. But if we use
the Attributes Editor to change an attribute on an element that is two
elements up it can take over an hour before the Attributes Editor
responds.
To be a bit more specific, in:
<lingPaper
automaticallywrapinterlinears="yes"
chapterlabel="chapter "
figureRefDefault="singular"
sectionRefCapitalizedPluralLabel="§§"
sectionRefCapitalizedSingularLabel="§"
sectionRefDefault="singular"
sectionRefPluralLabel="§§"
sectionRefSingularLabel="§"
tablenumberedLabel="Table"
tablenumberedRefDefault="singular"
version="2.10.0"
<frontMatter
<title
<langData
lang="sei"
Cmiique Iitom:</langData
the Seri language</title
...
Typing before "Cmiique" is instantaneous. Inserting text before the
langData element takes a few seconds to respond. But inserting a new
attribute or editing an existing attribute in the lingPaper element
takes an exceedingly long time.
Is there something we can do with our configuration to speed this
process up? I can get you a sample document off-list.
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
