Subject:Some requests from a power user Author:K. e.T. Date:17 Jan 2013 04:37 AM
Hi everybody!
I'm using StylusStudio each day for nearly 3 years now and I finally found the time to give you some feedback on features I would love to see in the next release (or let me know If they are already implemented and I didn't see them!):
*Visualize fields in the input which got transformed
For example, we have input i1,output o1 and mapping m1.
i1 has 5 fields: f1,f2,f3,f4 and f5.
m1 transforms information from field f1,f2 and f5 to o1.
Missing information: f3 and f4 should be highlighted in the input
I know that the "Mapper" is doing something similar, but this might get confusing when using huge input-data.
*Sort tabs
You should be able to sort the tabs (move left/right).
*Memorize the last folder I've used when opening a scenario
Subject:Some requests from a power user Author:Ivan Pedruzzi Date:17 Jan 2013 11:28 AM
Thanks khaled,
We are always honored when a customer takes the time to share his/her feedback with us.
I added your suggestion about re-arranging tabs to the database.
We have debating internally on when highlighting un-mapped fields.
In most of the mappings not all fields need to be transformed to the target schema. Based on which criteria Stylus Studio should highlight fields f3 and f4?
The Open File Dialog starts from the folder in which you have open the last document, this is Stylus Studio wise. If you open document c:\temp\a.xml using File->Open,then you open a scenario and start browsing for the input document, the open dialog should star in c:\temp
Does it work for you?
Subject:Some requests from a power user Author:K. e.T. Date:21 Jan 2013 09:11 AM Originally Posted: 21 Jan 2013 05:36 AM
Hi Ivan!
Incredible, you guys are fast!!
1)
>We have debating internally on when highlighting un-mapped fields.
>In most of the mappings not all fields need to be transformed to the >target schema. Based on which criteria Stylus Studio should highlight >fields f3 and f4
There are two (related to this request) possible scenarios we are dealing with very often:
a) Map all fields from a specific input (sample given) into an output (schema given)
b) Fill all fields of the output (sample given) from an input (schema given)
We are re-using XSLTs very often so it would be nice to see which untouched fields we have to map manually.
It's the same idea as "Mapper" in SS, but with a better visualization.
I don't know if this request is too specific for our company needs, but It would be very useful because for now we are either manually checking each field or use a script (which shows the xpaths, no integrated visualization).
2)
>The Open File Dialog starts from the folder in which you have open the >last document, this is Stylus Studio wise. If you open document
>c:\temp\a.xml using File->Open,then you open a scenario and start >browsing for the input document, the open dialog should star in c:\temp
>Does it work for you?
I am opening scenarios out of Windows Explorer, I don't use the "File -> Open" functionality. I'll try this, thanks :)
EDIT: Suggestion: If I'm editing a scenario and try open another Source and/or Output URL, the already pre-entered XML URL should be taken as navigation-path, if existing.
Regarding scenarios: Would be great to have a project-related scenario which allows the usage of more than one input, one mapping and one output.
I am using Stylus Studio's project functionality to simulate the message flow in our middleware.
There might be a flow like:
input -> XSLT -> output -> XSLT2 -> output2
For now I have to split it in two scenarios and execute each one separately.
3)[NEW REQUEST] Use schemas for XSLT-development
When creating/editing XSLTs it would be nice to know If my syntax is correct. This is already implemented when validating an output with a schema: You'll be able to modify the input and SS gives you suggestions based on the XSD, wonderful!
Anyhow, this would be very handy while creating/editing the XSLT itself: Am I allowed to put nested elements here? Is an attribute needed?
For now It is more or less try and error or I have to study the output very well.
Subject:Some requests from a power user Author:Ivan Pedruzzi Date:21 Jan 2013 10:15 AM
1) Understood.
2) Have you look at the XML Pipeline editor?
3) This is already partially possible. If you associate the output document schema to the project folder of your XSLT you can get the SenseX and syntax coloring for the output types, see screenshot.
Subject:Some requests from a power user Author:Ivan Pedruzzi Date:22 Jan 2013 12:09 AM
We have prepared a preliminary package for build 1910f which implements a a new feature for locating nodes which have not been mapped.
If you select any node in the content model, then hit F4 (or click the context menu item "Find Node without link") the tree control will highlight the next node which has not been mapped.
If you have time to try, let us know if this new feature mitigates issues 1