Subject: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.
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.
Subject: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).
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).
Subject: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.
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).
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).
>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.
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.