> I'm finding the changes to Element to be a little strange. > setSrcObject() / getSrc() ... is it intentional that the names are > different?
Sorry, a mistaken. It should be setSrc() and getSrc(). > Why "src" ... that's not mneumonic or descriptive. Is > this even necessary ... it seems like you could maintain a Map > inside the page tester from element to Object and not clutter the > Element API with this. The Page Tester would like to work in a higher level of abstraction than a browser. For example, instead of dealing a link URL, the Page Tester would like to know whether it's a page link or an action link, and for the former, the page name, the context (Object[]) and etc. All this info has to be passed back from the Tapestry app to the client (Page Tester). One way is to store this structured data source into the DOM element itself. Of course, one could also use a Map as you suggested. I am calling the "source" for the element because that's the best name I can come up with. Any suggestion? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
