|
|
 top
|
  Subject: Re: USING SCENARIOS
Author: Minollo I.
Date: 01 Jul 2002 05:46 PM
|
At 05:51 PM 7/1/2002 -0400, you wrote:
>From: "Al Ogrodski"
>
>Could someone explain how/when Stylus Studio handles the data for a
>Scenario that points to a large set of data?
>
>I've noticed performance issues when setting large documents up in a
>Scenario. Stylus Studio appears to load the entire document, which takes
>several minutes every time I open the stylesheet. Also, it appears to
>reload the data every time I leave the Stylus Studio application window
>and then return back to it.
When you assign an XML document to a (active) scenario, that XML document
is loaded entirely in memory because it will be used by the XSLT processor
to preview your XSLT source, and it will be used to populate the XML
structure tree on the right of your source.
The feeling of the document being reloaded every time when you leave Stylus
and return to it, should just be a feeling; but what Stylus actually does
in that moment is checking if the open documents have been changes; if
these documents sit on a remote server, that can require some time. You can
turn off this check on modified documents in Tools|Options|Application
Settings, "Automatically check for externally modified files".
>It also seems to hit a limit and not load anymore data because my XSLT
>previews don't include all the data. If I run the transformation directly
>on the file outside of Stylus Studio, I'll get the correct results.
That shouldn't happen; that's more likely a difference in the behavior of
the external processor you are using compared to the Stylus Studio one.
To be more precise on this last point, we need a testcase, so that we can
see the same behavior you are seeing.
Thanks,
Minollo
|
|
|
|
next