Not entirely Ext related, but jquery... - Ext JS

# 2 03-08-2007, 06:25 PM

If you have Ext, did you try DomQuery? It should work fine with either query and will be slightly faster anyway.

# 3 03-08-2007, 08:15 PM

I thought that DomQuery was now leveraging/wrapping JQuery?

Anyway, my test shows that node-list predicate selectors aren't working in DomQuery either. These are the cases where I need Xpath over css. Take this example:

XML Document:

<XMLResponse>
  <Errors/>
  <Warnings/>
  <Messages/>
  <Response>
    <NinestarStyle>
  <Sid>S44c14b83172b03.48738167</Sid>
  <Name>Another Original Cap</Name>
  <Properties/>
  <ProductTypeId>5</ProductTypeId>
  <VendorItemId>35011077Y</VendorItemId>
  <VendorId>DWIND</VendorId>
  <BrandId>DWIND</BrandId>
  <Price>19.99</Price>
  <Margin/>
  <DefaultCost/>
  <Taxable>1</Taxable>
  <Persisted>1</Persisted>
  <Instock/>
  <ItemPropertyGroups/>
  <ProductType>
    <Id>5</Id>
    <Name>Hats</Name>
    <ProductGroup>Fashion</ProductGroup>
    <Margin/>
    <Properties>
      <PropertyTemplate>
        <Sid>44c0ade005d75</Sid>
        <ProductTypeId>5</ProductTypeId>
        <PropertyTypeId>8</PropertyTypeId>
        <PropertyType>
          <Id>8</Id>
          <Name>Hats Size</Name>
          <DataType>1</DataType>
          <Units/>
          <VendorSpecific>0</VendorSpecific>
        </PropertyType>
        <Required>1</Required>
        <Name>Size</Name>
        <Type>0</Type>
      </PropertyTemplate>
      <PropertyTemplate>
        <Sid>44c0ade0078cc</Sid>
        <ProductTypeId>5</ProductTypeId>
        <PropertyTypeId>2</PropertyTypeId>
        <PropertyType>
          <Id>2</Id>
          <Name>Color</Name>
          <DataType>1</DataType>
          <Units/>
          <VendorSpecific>1</VendorSpecific>
        </PropertyType>
        <Required>0</Required>
        <Name>Color</Name>
        <Type>0</Type>
      </PropertyTemplate>
    </Properties>
  </ProductType>
  <_propertiesLoaded>1</_propertiesLoaded>
  <_categoriesLoaded>1</_categoriesLoaded>
  <_deep>1</_deep>
</NinestarStyle>
  </Response>
</XMLResponse>

This xpath selector works with DomQuery (but not with jquery):

//NinestarStyle/ProductType/Properties/PropertyTemplate

Selects 2 nodes.

This selector, however, returns no nodes:

//NinestarStyle/ProductType/Properties/PropertyTemplate[Type='0']

# 4 03-08-2007, 10:53 PM

jQuery will be offering an option to use DomQuery as it is faster (but also larger).

//NinestarStyle/ProductType/Properties/PropertyTemplate[Type='0']

This is where CSS selectors take precedence over XPath. In CSS selectors that is an attribute query, not a "nodeValue" query.

Adding it is easy though, and I have a added a pseudo to DomQuery ("nodeValue") that will in the next release. In the mean time, you can add this code anywhere after Ext and it will be available now:

Ext.DomQuery.pseudos.nodeValue = function(c, v){
    var r = [];
    for(var i = 0, ci; ci = c[i]; i++){
        if(ci.firstChild && ci.firstChild.nodeValue == v){
            r[r.length] = ci;
        }
    }
    return r;
}

Plugging in custom pseudos is pretty easy as you can see and you can always add your own if something you need is missing.

Your query would be:

//NinestarStyle/ProductType/Properties/PropertyTemplate:nodeValue(0)

# 5 03-08-2007, 11:28 PM

Quote:

//NinestarStyle/ProductType/Properties/PropertyTemplate:nodeValue(0)

Since I was looking for the PropertyTemplate with child node Type=0, wouldn't it be:

//NinestarStyle/ProductType/Properties/PropertyTemplate/Type:nodeValue(0)/../

I think, haven't tried yet but it doesn't quite look right.

Since support for these should be easy (it's just a recursion), how about a DomQuery mode switch CSS or XPath type predicates? The only change would be if an @ is required to signify an attribute.

# 6 03-08-2007, 11:47 PM

Yes it would have Type.

The switch you suggested requires some changes to the parser and internal logic. I'm not sure how difficult they would be but it won't be changed in this release. That code is stable and there are other things which need to get finished.

# 7 03-08-2007, 11:51 PM

Thanks for the help Jack. I think I'll be able to develop a suitable workaround.

# 8 03-12-2007, 09:01 PM

Quote:

Originally Posted by jacksloc

Yes it would have Type.

The switch you suggested requires some changes to the parser and internal logic. I'm not sure how difficult they would be but it won't be changed in this release. That code is stable and there are other things which need to get finished.

Hi Jack,

Still having problems... what would the correct syntax be? For example, if I want to retrieve the _value node for the property with Sid 44c0e4bee03cf from the XML snipppet below:

  <Properties>
    <Property>
      <Sid>44c0e4bee03cf</Sid>
      <ValueSid>44c0e4bee03cf</ValueSid>
      <VendorId>DWIND</VendorId>
      <_value>YOUTH</_value> 
...

This is the xpath style selector, but using your nodeValue pseudo:

Properties/Property[Sid:nodeValue("+sid+")]/_value

But it's not working. Just bails.

Properties/Property/Sid:nodeValue("+sid+")

Gets the right Sid node, but then trying to navigate to the _value node fails:

Properties/Property/Sid:nodeValue("+sid+")/../_value

Just bails. I tried creating a parent() pseudo to select the parent nodes, but it's not working:

Properties/Property/Sid:nodeValue("+sid+"):parent()/_value

With this parent def:

Ext.DomQuery.pseudos.parent = function(c){ 
    var r = []; 
    for(var i = 0, ci; ci = c[i]; i++)
		if(ci.parentNode)
			r[r.length] = ci.parentNode; 
    return r; 
}

I'm beat. I've also tried using a node that's not _value (in case the underscore isn't liked by the xml processor, with no change)

# 9 03-12-2007, 09:09 PM

Quote:

Originally Posted by jacksloc

This is where CSS selectors take precedence over XPath. In CSS selectors that is an attribute query, not a "nodeValue" query.

Wouldn't the css attribute selector require an @?

# 10 03-12-2007, 09:14 PM

Jack,

I wrote a custom pseudo selector to do exactly what I want, but it's a disappointing hack. This functionality should be part of the Xpath library.

Ext.DomQuery.pseudos.nodeValueParent = function(c, v){ 
    var r = []; 
    for(var i = 0, ci; ci = c[i]; i++){ 
        if(ci.firstChild && ci.firstChild.nodeValue == v){ 
            r[r.length] = ci.parentNode; 
        } 
    } 
    return r; 
}