|
next
|
 Subject: SenseX Author: Darren Hayduk Date: 05 Sep 2001 01:49 PM
|
> When editing an XML document associated to
> a schema (DTD or XML Schema), the SenseX
> functionality which helps in the creation
> of new tags is now context sensitive.
I have a schema that uses the same tag name, but the tag has different attributes depending upon context. SenseX appears to match by name, and therefore produces the Union of possible items.
Example:
{Table}
{Field A="1" B="2"/}
{/Table}
{View}
{Field C="1" D="2"/}
{/View}
when I'm in a Field tag, the SenseX shows attributes A,B,C, and D. In my schema, I have a TableField type and a ViewField type (each with 2 attributes). So, if I'm in Table/Field, I would want SenseX to list A&B, while in View/Field it should be C&D.
Otherwise, the behavior is much improved! Thanks for this feature (FYI, XMLSpy doesn't do context-sensitive parsing in text view - only tree/grid). This is appreciated!!
Darren
|
top
|
 Subject: RE: SenseX Author: (Deleted User) Date: 05 Sep 2001 02:02 PM
|
Hi, Darren
We understand the problem and did think about the soltuion you suggested at
beginning. but there is some limitation in text view to do a 'perfect'
context sensitive auto complete.
the solution you suggested require the editor to know the exact full path of
a particular position. this is hard in text view because the text you are
editing could be very large and not necessarily well formed.
our solution detect only one level of the tag. this solution is a compromise
and will work fine in most cases.
song
> -----Original Message-----
> From: stylus-studio-tech Listmanager [mailto:listmanager]
> Sent: Wednesday, September 05, 2001 1:56 PM
> To: Recipients of 'stylus-studio-tech' suppressed
> Subject: SenseX
>
>
> From: "Darren Hayduk"
>
> > When editing an XML document associated to
> > a schema (DTD or XML Schema), the SenseX
> > functionality which helps in the creation
> > of new tags is now context sensitive.
>
> I have a schema that uses the same tag name, but the tag has
> different attributes depending upon context. SenseX appears
> to match by name, and therefore produces the Union of possible items.
>
> Example:
> {Table}
> {Field A="1" B="2"/}
> {/Table}
> {View}
> {Field C="1" D="2"/}
> {/View}
> when I'm in a Field tag, the SenseX shows attributes A,B,C,
> and D. In my schema, I have a TableField type and a ViewField
> type (each with 2 attributes). So, if I'm in Table/Field, I
> would want SenseX to list A&B, while in View/Field it should be C&D.
>
> Otherwise, the behavior is much improved! Thanks for this
> feature (FYI, XMLSpy doesn't do context-sensitive parsing in
> text view - only tree/grid). This is appreciated!!
>
> Darren
>
>
>
> To reply: mailto:stylus-studio-tech.3601@edn.exceloncorp.com
> To start a new topic: mailto:stylus-studio-tech@edn.exceloncorp.com
> To login: http://edn.exceloncorp.com/~SSDN
>
>
|
|
|
|