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 (1146)
+ Stylus Studio Technical Forum (14176)
+ Website Feedback (244)
- XSLT Help and Discussion (7514)
-> + XSL-FO question (2)
-> + EDI 997 creation. (7)
-> + Line break within a tag in XML... (2)
-> + Contact Help Needed (2)
-> + ACK 997 (2)
-> + XSLT to output XML( which conf... (11)
-> + Retrieving all nodes where a c... (6)
-> + Verifying XML and XSD within X... (4)
-> + How to validate date format in... (3)
-> + XSLT question (2)
-> + Muenchian grouping (2)
-> + How to remove specific text en... (8)
-> + If Else Condition along with L... (2)
-> + SAXON Problem (2)
-> + comapring global variable valu... (2)
-> + copying the value of xsl in va... (2)
-> + Urgent:XSLT element value sel... (2)
-> + Ignoring first element using f... (2)
-> + EDI X12 to XML (4)
-> + XSLT FOR-EACH HELP (2)
-> + Sorting Help Needed (3)
-> + XSLT help with linking (2)
-> + selecting data into node set b... (2)
-> + Watch and Variable in Debug no... (4)
-> + Transforming XML to XML - grou... (2)
-> + Saxon 9.0 B support in debug m... (2)
-> + Repeating element question (2)
-> + Newly Purchased Version Not La... (2)
-> + xsl:include not finding file (5)
-> + JAXP and XSLT 2.0 / XPATH 2.0 (2)
-> + ASP:DropDownList trigger in Xs... (2)
-> + Auto-Skip empty values (2)
-> + retrieving a javascript functi... (2)
-> + need help (2)
-> + html tag ignored (2)
-> + Quick reply needed (8)
-> + xslt to remove namespaces but ... (2)
-> - Using a WSDL definition in an ... (1)
-> + XSL logic issue for simple inp... (6)
-> + Regarding XML namespace prefix... (4)
-> + Mapper reoganizes itself. (8)
-> + XSL Substring Removal (2)
-> + Regarding XSLT logic for a sim... (3)
-> + XSLT Transform documentation (2)
-> + XSLT stack trace in case of er... (3)
-> + No New Line (2)
-> - No New Line (1)
-> + howto loop through a sequence (2)
-> + xml and xsl and whitespace in... (2)
-> + XSL Date formatting (4)
-> + XSL to XSL Mapping using custo... (4)
-> + flat xml to nested xml comvers... (4)
-> + Including schema in scenario (2)
-> + DTDs and traversing (2)
-> + Help with transformation (2)
-> + Problem running XSLT against X... (2)
-> + Carriage return in the output (5)
-> + Generating XSLT to match a sch... (3)
-> + WYSIWYG editor (2)
-> + Grouping without For-Each (3)
-> + output XML using XSLT (8)
-> + Help configuring Xalan-j proce... (8)
-> + Convert Existing HTML pages to... (2)
-> + Generating Transformation - XS... (4)
-> + DOCTYPE public and system info... (2)
-> + Using EXSLT str:tokenize funct... (5)
-> + Where can I get a special char... (3)
-> + XSLT vs XQuery (2)
-> + Using Variables. How to use a ... (4)
-> + XSL incremental count - (5)
-> + thought I was being clever but... (2)
-> - Need help with FO:Table-row (1)
-> + Need help with FO:Table-row (3)
-> + Create mapping based on destin... (5)
-> + Finding a missing parameter (2)
-> + looping an element (5)
-> + Generate an XSLT from an XML f... (2)
-> + Easiest way to split many docu... (7)
-> + how to get xsl:copy-of to appe... (5)
-> + Recursive XSLT Templates (7)
-> + Selecting nodes (help please) (2)
-> + if string = null stop it from... (2)
-> + Display top n items from categ... (3)
-> + Retain input values (2)
-> + XML data import with XSL Style... (4)
-> + Entities with the stylesheet (3)
-> + How can I make a subset Schema... (5)
-> + How to map XML to XML with a m... (2)
-> + displaying specific html when ... (3)
-> + table and cell borders (8)
-> + Grouping Problem (3)
-> + Error while running an XSL wit... (4)
-> + images in XSL Reports. (2)
-> + XSLT Preview on syntax error l... (6)
-> + Mapping Alternatives (2)
-> + how to load image in xsl (2)
-> + XSLT page breaks (2)
-> + Need help on Processing two xm... (7)
-> + Parse text from XML, remember ... (10)
-> + Grouping on lookup values. (3)
-- Previous [661-680] [681-700] [701-720] Next
+ XQuery Help and Discussion (1892)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (361)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Adam Van den HovenSubject: Yet another Feature request
Author: Adam Van den Hoven
Date: 14 Sep 2001 02:31 PM
Hey guys, I've had some more inspiration today.

When creating a select or a match attribute, SenseX is polite enough to prompt you with possible nodes and attributes. Add such functions as node() text(), comment(), etc to that list. Also the variables and parameters that are currently in scope would also be nice. I would also appreciate a similar feature for the name attribute in call-template and with-param. Perhaps mode could similarly be prompted.

I tend to have quite a few named templates either locally or more likely in libraries. I'm always cutting from the library and pasting into my code, adding call- before template and with- before param. A little help would be useful. If it could make suggestions for regular templates with params that too would be useful.

Adam

Postnext
Minollo I.Subject: Re: Yet another Feature request
Author: Minollo I.
Date: 14 Sep 2001 02:44 PM
At 02:38 PM 9/14/2001 -0400, you wrote:
>From: "Adam Van den Hoven"
>
>Hey guys, I've had some more inspiration today.
>
>When creating a select or a match attribute, SenseX is polite enough to
>prompt you with possible nodes and attributes. Add such functions as
>node() text(), comment(), etc to that list. Also the variables and
>parameters that are currently in scope would also be nice.

This time you are not the first one to ask for this... ;)
It's in our PCR list, including axes.

>I would also appreciate a similar feature for the name attribute in
>call-template and with-param. Perhaps mode could similarly be prompted.
>
>
>I tend to have quite a few named templates either locally or more likely
>in libraries. I'm always cutting from the library and pasting into my
>code, adding call- before template and with- before param. A little help
>would be useful. If it could make suggestions for regular templates with
>params that too would be useful.

I see what you are saying; we'll keep that in mind.

Thanks,
Minollo

Postnext
Adam Van den HovenSubject: Re: Yet another Feature request
Author: Adam Van den Hoven
Date: 14 Sep 2001 04:24 PM
Well, I refuse to be thwarted in my quest to add to your work load ;)

In the variables window, the option to take a variable that has a nodeset and expand it into a tree (or somehow make it more readable). It isn't clear (at this point) what is a nodeset and what's a result tree either in the variables (another useful bit of information to have).

Postnext
Minollo I.Subject: Re: Yet another Feature request
Author: Minollo I.
Date: 14 Sep 2001 04:29 PM

>...
>In the variables window, the option to take a variable that has a nodeset
>and expand it into a tree (or somehow make it more readable).
>It isn't clear (at this point) what is a nodeset and what's a result tree
>either in the variables (another useful bit of information to have).

Sorry... we are already working on that... :)

thanks,
Minollo

Postnext
Adam Van den HovenSubject: Re: Yet another Feature request
Author: Adam Van den Hoven
Date: 14 Sep 2001 06:00 PM
Now you're just trying to egg me on. ;)

How about opening multiple files from the dialog?

You already open XML docs from the current scenario, how about the import/included xsl files?

Now that you've added support for msxsl:script (does that include the rest of that namespace including node-set()?) how about adding support for some of the other extension namespaces such as Saxon.

Even better support the proposed EXSLT functions from http://www.jenitennison.com/xslt/exslt/common

Most of the members of the XSLT mailing list would probably agree that this would be a useful (although I'm not sure that any stand alone parser yet support them).

Adam

Postnext
Minollo I.Subject: Re: Yet another Feature request
Author: Minollo I.
Date: 14 Sep 2001 06:21 PM

>...
>How about opening multiple files from the dialog?

Yup, it's in our todo list; you can already "kind-of" make it if you select
multiple files from Explorer or any other file system/URL browser and
drag&drop the selection on Stylus Studio.

>You already open XML docs from the current scenario, how about the
>import/included xsl files?

You can already do that right-clicking on the imported/included file name
href attribute.

>Now that you've added support for msxsl:script (does that include the rest
>of that namespace including node-set()?)

....what else other than node-set()? All the other ones I can think of are
old XSL stuff. Yes, node-set() is supported.

>how about adding support for some of the other extension namespaces such
>as Saxon.
>
>Even better support the proposed EXSLT functions from
>http://www.jenitennison.com/xslt/exslt/common
>
>Most of the members of the XSLT mailing list would probably agree that
>this would be a useful (although I'm not sure that any stand alone parser
>yet support them).

We don't want to go there.
Stylus Studio 3.0 supports XSLT 1.0 with the addition of a sub-set of the
Java extension function grammar also supported by Xalan.
Microsoft is widely adopted enough (and close enough to the aborted XSLT
1.1 WD) to justify work in 3.1 to support their extensions; but we cannot
chase all the various dialects that are coming out in the XSLT area.
Hopefully XSLT 2.0 will clean-up things a bit. In the meanwhile, if you
need support for extensions unsupported by the internal processor, you can
still set-up scenarios to use an external processor (I know, that's not
what you would like to do).

Minollo

Postnext
Govindaraj KadambiSubject: Re: Yet another Feature request
Author: Govindaraj Kadambi
Date: 15 Jul 2004 04:53 PM
>At 02:38 PM 9/14/2001 -0400, you
>wrote:
>From: "Adam Van den Hoven"
>
>
>Hey guys, I've had some more
>inspiration today.
>
>When creating a
>select or a match attribute, SenseX is
>polite enough to
>prompt you with
>possible nodes and attributes. Add such
>functions as
>node() text(), comment(),
>etc to that list. Also the variables and
>
>parameters that are currently in scope
>would also be nice.

This time you are
>not the first one to ask for this...
>;)
It's in our PCR list, including
>axes.

>I would also appreciate a
>similar feature for the name attribute
>in
>call-template and with-param.
>Perhaps mode could similarly be
>prompted.
>
>
>I tend to have quite a
>few named templates either locally or
>more likely
>in libraries. I'm always
>cutting from the library and pasting
>into my
>code, adding call- before
>template and with- before param. A
>little help
>would be useful. If it
>could make suggestions for regular
>templates with
>params that too would
>be useful.

I see what you are saying;
>we'll keep that in
>mind.

Thanks,
Minollo

Is this feature available ? It does not seem like. It will be very helpful since I have a lot of templates spread in a number of include files. I have seen this feature in a product called Xselerator and found it very handy.

Posttop
Minollo I.Subject: Re: Yet another Feature request
Author: Minollo I.
Date: 15 Jul 2004 05:13 PM
>Is this feature available ? It does not seem like. It will be very helpful
>since I have a lot of templates spread in a number of include files. I have
>seen this feature in a product called Xselerator and found it very handy.

You are right, that feature is not available yet.
We'll bump up its priority.

Thanks,
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-2011 All Rights Reserved.