 next
|
  Subject: Stylus Studio X15 stuck on processing XSL 2.0 transform...even after restart and reboot
Author: HereGear HereGear
Date: 05 May 2014 08:17 PM
|
OK - I finally figured out what is going on here:
Assigning the Output URL in a scenario to a file is somehow tied to the Preview Window's memory consumption. When I deleted the code that SS generates into the XSL file - i.e. the code that defines the scenario metadata - then ran it without setting that file-based URL output - SS tried to dump 464k lines of txt output to the Preview Window, which locked up the app.
I went back and setup the scenario as I originally had it - i.e. the output to a file and, voila - worky worky.
Now - Altova does this automagically without meta info in the file and by running some type of algorithm beforehand and, if it senses the output will be big, it'll turn off "autosense" in the output window (maybe it senses that the output won't necessarily be XML).
So, in conclusion, I think there's some fixes that should be affected:
-The biggee: Preview, plain-and-simple: insure that the output options are visible and configurable upon first startup of SS. This is a must-have - it's a big, bad, bug.
-Preview can lock up the app if you don't have a file set for the output for txt-based XSL conversion (and know that many developers are doing lots of txt-based XSL > JSON conversions these days - know it, love it, learn it, please respond accordingly within your application's logic sooner rather than later)
-Preview vs. Output: bad idea. Lose Preview, just use one output window. Too confusing.
-Get the app to try and sense what the output is going to be and - if it can't definitively sense that it'll be XML, AND the scenario has no output file configured - pop up a warning, fairly straightforward.
I just bought this tool - I would like a fix for this stuff soon so that it's in my upgrade contract. Don't look at my feedback as a negative: take it as a positive, you just got a high-paid developer to effectively debug a nasty problem with your app that I'm sure others have been frustrated with as well. (I should get paid!)
Last little rant I'm going to make (maybe): please modify the app so that I can run java from any location without having to update windows itself. I should be able to pop into SS, go to a config screen, change java's location, run it - and 5 seconds later do the same thing without leaving SS. Go look at Eclipse: it's the standard.
Thanks.
|
|
SStudioConsoleOutOptionsBug.jpg
TEMP(1).ZIP
top