Kent Tong <freemant2000 <at> yahoo.com> writes: > > 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?
Done. Just changed to use a map of "in-app invocation" objects. The Element API is restored. Please take a look to see if it's OK. Thanks! -- Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
