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
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
Max HodgesSubject: Allow Debugging with MSXML
Author: Max Hodges
Date: 23 Apr 2002 04:01 AM
Why don't you modify this product to allow runtime debugging and variable watching etc. with the MSXML parser like Xselerator allows? Then you won't have to build your own parser (which doesn't always work the same as MSXML.) Everyone is using MSXML isn prodcution, not your internal parser right? I love the interface and feature set of your product, but Xselerator has a better debugger. I hate Xselerator's editor though, so I am constantly switching back and forth. Some of the best minds in XSLT are members of the XSLTalk yahoo group. Ask these people why they don't like your product. It will be the most valuable feedback you could get.

Cheers,
Max Hodges, MCP
Web Database Administrator
Online Technology
Dell Computer Japan

Postnext
Minollo I.Subject: Re: Allow Debugging with MSXML
Author: Minollo I.
Date: 23 Apr 2002 09:42 AM
Max, we are working on supporting MSXML as debugger; unfortunately
Microsoft is not making that extremely easy on us...

I would be interested in knowing why you think Xselerator is a better
debugger than Stylus Studio; apart from MSXML support, what do you miss or
what would you like to see changed in the Stylus Studio debugging
functionality?

Thanks,
Minollo

Postnext
Max HodgesSubject: Re: Allow Debugging with MSXML
Author: Max Hodges
Date: 24 Apr 2002 03:41 AM
Honestly I am not sure exactly! Someone told me it was better, but now that I have looked closer they are pretty darn close. Xsel's debugger seems a little more intuitive for me (vague I know.) Things seem more organized in Xselerator. In your variables windows you list global parameters, variables, and context node attributes. Xselerator labels these things more distinctly. Xselerator's debugger shows where I am in both the XSLT and the XML (stylus only highlights the row in the xsl.) Also I have trouble getting the windows arranged. Maybe if I could right-click on a window's title bar (like the call stack and variables window) and check an option to make these windows float... I like how the debug toolbar is closer to the debug views in xselerator. Actually, I just realized that Xselerator doesn't show the output dynamically as I step in debugging mode! Stylus does--which is much better! Actually, now that I have focused more attention on it, I understand things better and actually think your debugger works very well. Maybe you should expand the Context node in the variables pane by default (minor point, admittedly.) Another minor point, allow double-click to autosize columns in the watch and variables windows.

Don't get me wrong, you product is excellent. I honestly feel giddy using it because it is so awesome. Biggest complaint, besides MSXML debugging is: 1) let me open the output in a browser in one click (I have to save to file first, and then open that file) because I am doing a lot of onmouseover things to mask actual URLs and I have to check these in the broswer's status bar.

Also, I have a hard time finding and checking things in the output text because I have to horizontally scroll. Maybe it would help if I could use Find to search for text in the output pane views.

Also bug in 4.0 when I clicked on Keyboard... in tools, the program terminated (all windows disappeared) happened twice. Today it is working fine (!)

I gave your guys lots on feedback for version 3 and you did an awesome job of making this a product that I love to use. I pushed for SourceSafe integration and you did a great job on that (thank you very much!) One more request, I wish I could Find and Replace paragraph marks. I would help with I cleanup pasted HTML (non-XHTML) text. I do lots of finds and replacements, and it is easier to use Word. In Word I can find and replace ">" with "^p>" ("^p" = paragraph mark) this helps me see everything easier as I am working. Hope this helps.

Postnext
Minollo I.Subject: Re: Allow Debugging with MSXML
Author: Minollo I.
Date: 24 Apr 2002 10:20 AM

>...
>Maybe if I could right-click on a window's title bar (like the call stack
>and variables window) and check an option to make these windows float...

You can drag&drop them keeping the Ctrl button pressed; that will force
them to undock; it's a standard docking window behavior.

>Maybe you should expand the Context node in the variables pane by default
>(minor point, admittedly.) Another minor point, allow double-click to
>autosize columns in the watch and variables windows.

They both make sense.

>1) let me open the output in a browser in one click (I have to save to
>file first, and then open that file) because I am doing a lot of
>onmouseover things to mask actual URLs and I have to check these in the
>broswer's status bar.

That's high in our PCR list; it should make 4.0 GA.

>...
>Also bug in 4.0 when I clicked on Keyboard... in tools, the program
>terminated (all windows disappeared) happened twice. Today it is working
>fine (!)

That's very weird. Do you have any struzzo.log as a result of those crashes?

>I gave your guys lots on feedback for version 3 and you did an awesome job
>of making this a product that I love to use. I pushed for SourceSafe
>integration and you did a great job on that (thank you very much!) One
>more request, I wish I could Find and Replace paragraph marks. I would
>help with I cleanup pasted HTML (non-XHTML) text. I do lots of finds and
>replacements, and it is easier to use Word. In Word I can find and replace
>">" with "^p>" ("^p" = paragraph mark) this helps me see everything easier
>as I am working.

I see what you are saying; I'm adding this to our PCR database.

>Hope this helps.

It surely does!
Thanks a lot,
Minollo

Posttop
Max HodgesSubject: Re: Allow Debugging with MSXML
Author: Max Hodges
Date: 26 Apr 2002 01:17 AM
Glad you like my feedback. While I have your attention then, here is a very minor request if you think it merits inclusion. I work on projects with several xsl files. Usually they all include the same library file, attribute_set file, and use the same xml file and reference xml file (document()). Often when I make a change in the xml or reference xml or library or attribute xsl files I want to run my templates one-by-one and check the results to see if I broke anything. So the request is (I know its very small) but I wish I could right-click on the xsl file in the Project windows and access the parse command (you call it "Preview XSLT Result")

 
Topic Page 1 2 3 4 5 6 7 8 9 Go to previous topicPrev TopicGo to next topicNext Topic
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.