XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> - Stylus Studio - Registrar en o... (1)
-> + Stylus Studio - Registrar en o... (2)
-> + Can a pipeline send a file by ... (2)
-> + After Updateing WIN10 to WIN11... (12)
-> + Where do I add the custom java... (3)
-> + Where is the Diagram tab? (5)
-> + Applying XSLT to Word DOCX/XML (2)
-> - CSV conversion via ConvertToXM... (1)
-> + Text symbols in SS not same as... (4)
-> + Exposing xquery as webservice ... (6)
-> + Syntax Identifier (2)
-> + Saving a Converted XML as an X... (5)
-> + Output document cannot be pars... (4)
-> - Archiving output from conversi... (1)
-> + EDIFACT guideline from Stylus ... (3)
-> + CSV file putting all the data ... (5)
-> + Can't install Home version 64b... (5)
-> + presale - Can I covers this sc... (5)
-> + Problem with UNB (5)
-> + Splitting EDIFACT files pipeli... (4)
-- [1-20] [21-40] [41-60] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Bruce JohnsonSubject: General praise and feedback
Author: Bruce Johnson
Date: 30 Jul 2002 10:11 AM
To the support & development team:

I have been using an evaluation version of Stylus Studio to try some fairly complex XML-to-XML mappings, and it’s going very well. Tell your development team they have built a fantastic product – eXcelon is definitely in the lead in the area of automatic XSLT generation. We were truly amazed that the mapping GUI is non-destructive to manual changes made to the XSLT source. You made a wise choice to allow this, because 80% of what we need can be handled by the drag-and-drop method, but some manual XSLT is required as well. Please continue to allow manual XSLT editing along with the drag-and-drop mapping functionality.

You’ve done all the hard parts beautifully, but I have a few usability suggestions that would be icing on the cake:

- It should be easier to search for elements in the XML-to-XML mapping view. It can be tough to “eyeball” it for big documents.
- The source XML tree (the left side) in an XML-to-XML mapping does not seem to correctly support a mouse wheel for scrolling. Although it might be an MFC bug, it would be worth trying to fix. It would be very helpful, because there’s often a lot of looking around in the document, yet the scroll bar is on the left side, which is unusual (but understandable in this context). Mouse wheel support would be the perfect thing.
- When you edit a property of a mapping relationship (e.g. “Passes Value” or “Does For Each”), there is no need to show a message box when the value doesn’t change. I sometimes accidentally click on “Passes Value” instead of “Does For Each”. But when I click on the correct one, the “Passes Value” edit box loses focus without changing its value, causing a message box reading “The destination already has a value link!” I think you could safely suppress this and similar dialogs in all cases. Consider the VB forms designer as a model, which always does its work silently.

- Bruce

Posttop
Minollo I.Subject: Re: General praise and feedback
Author: Minollo I.
Date: 30 Jul 2002 10:17 AM

>...
>Tell your development team they have built a fantastic product...

Thanks Bruce; we ARE the development team, so thanks for your words!

>- It should be easier to search for elements in the XML-to-XML mapping
>view. It can be tough to "eyeball" it for big documents.

Noted.

>- The source XML tree (the left side) in an XML-to-XML mapping does not
>seem to correctly support a mouse wheel for scrolling. Although it might
>be an MFC bug, it would be worth trying to fix. It would be very helpful,
>because there's often a lot of looking around in the document, yet the
>scroll bar is on the left side, which is unusual (but understandable in
>this context). Mouse wheel support would be the perfect thing.

It is a bug of ours; we know about that. It's filed and we'll get to it as
soon as possible.

>- When you edit a property of a mapping relationship (e.g. "Passes Value"
>or "Does For Each"), there is no need to show a message box when the value
>doesn't change. I sometimes accidentally click on "Passes Value" instead
>of "Does For Each". But when I click on the correct one, the "Passes
>Value" edit box loses focus without changing its value, causing a message
>box reading "The destination already has a value link!" I think you could
>safely suppress this and similar dialogs in all cases. Consider the VB
>forms designer as a model, which always does its work silently.

Noted.

Thanks; we'll address the requests as soon as possible (which basically
means as soon as work on XML-to-HTML gives us a break).

Minollo

   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.