I guess I'm looking for a way to tell the MarkupWriter (or other responsible DOM generators) to also output the t namespace in the generated html. In particulair, I'm after having the t:id added. Would this be hard to add, and what would be my entrypoint to start on a patch.
The idea comes from wicket which has a getTagByWicketId which I think is quite powerful. Cheers, Joost On Wed, May 27, 2009 at 12:22 AM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > On Mon, May 25, 2009 at 6:14 PM, Joost Schouten (mailing lists) > <joost...@jsportal.com> wrote: >> First off, I love the new xpath project. Unit testing components and >> pages is a lot easier because of it. > > It can be used to write mixins too. :) > >> One thing that would make life even better is if I have a way to tell >> tapestry to print out all t: namespace params in the output xhtml (for >> testing purposes). Targeting specific components on a page will be >> made a lot easier. Does such a setting exist? > > I guess it doesn't, as the DOM XPaths works on is the generated HTML > output, not the template. > > -- > Thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
