Dude, parsed-xml-dev is where you're likely to get help about this. Dennis Allison <allison@sumeru.stanford.EDU> writes:
The problem I have is that to get it all to work I needed to do it by brain surgery, actually modify the Product sources. None of the usual mechanisms has the right namespaces, or so it appears. This has the disadvantage that it effects everything that uses the tree widget on the DOM, including the management screens. I've not checked yet as to what I did there. :-|
The change is pretty simple -- in ManageableDOM.py:
def tpValues(self): [...]
How about grabbing the wrapped DOM node, aquiring this and whatever other methods the tree widget needs, and wrapping the node that gets returned when the user is done with the widget? -- Karl Anderson kra@monkey.org http://www.monkey.org/~kra/
Yup, but there is zero traffic there or so it appears from the archive. Sorry to bother. -d On 18 Apr 2002, Karl Anderson wrote:
Dude, parsed-xml-dev is where you're likely to get help about this.
Dennis Allison <allison@sumeru.stanford.EDU> writes:
The problem I have is that to get it all to work I needed to do it by brain surgery, actually modify the Product sources. None of the usual mechanisms has the right namespaces, or so it appears. This has the disadvantage that it effects everything that uses the tree widget on the DOM, including the management screens. I've not checked yet as to what I did there. :-|
The change is pretty simple -- in ManageableDOM.py:
def tpValues(self): [...]
How about grabbing the wrapped DOM node, aquiring this and whatever other methods the tree widget needs, and wrapping the node that gets returned when the user is done with the widget?
-- Karl Anderson kra@monkey.org http://www.monkey.org/~kra/
My ParsedXML system is beginning to function. It would be nice to be able to use the system mechanism for converting a DOM-URL to an object reference, but I've been unable to find it in the code. Any hints? :-) -dra
Dennis Allison writes:
My ParsedXML system is beginning to function. It would be nice to be able to use the system mechanism for converting a DOM-URL to an object reference, but I've been unable to find it in the code. Any hints? :-) What's a DOM-URL?
If it's an URL inside the Zope hierarchy, you can use "restrictedTraverse" (--> Zope Help --> API reference --> ObjectManagerItem). Dieter
Actually I found the routine... Turns out to be called resolveNodePath() and takes a DOM Url and returns the object it references.
Just wanted to follow up on the ParsedXML queries that were posted earlier. My problem was getting the dtml-tree widget to not show all the nodes in the DOM-tree. I ended up with a brain surgery solution which hacked tpValues so it wouldn't consider non-XML-ish nodes as acceptable children. (and there was also an associated namespace problem...) Well, it looks like that was the wrong solution. Apparently, the various nodes in the DOM have a nodeType and the nodes I wanted to display have a nodeType on 1. :-( It would have been helpful had there been some documentation separate from the implemenation on the storage model, what aspects were maintained, and how XML is mapped onto the DOM tree.
participants (3)
-
Dennis Allison -
Dieter Maurer -
Karl Anderson