THanks for the Firebug tip. When I have the Autocomplete anywhere in the page (not in the PageBar, for example), I get an error: "this.children[i].setTheme is not a function" that I don't get if I remove the Autocomplete. I didn't see anyway to get a backtrace in firebug, so I don't know exactly why that is getting called. I am setting a theme for the turbowidget, but the autocomplete component isn't anywhere near the turbowidget.
That said, I just removed my call to turbo.themes.setTheme() and the error went away, but the autocomplete widget is still causing my TurboPageBar widget to disappear. Looking at the structure of the page, however, there is something funny going on. THe div that defines the TurboPageBank is in the page. However, the div that contains the TurboNotebook, which contains the divs that are switched between by the PageBank are completely missing from the structure of the page. Something must have manipulated the DOM and removed those divs. Or more likely, something prevented the TurboPageBar widget from rewriting the divs as pages in the PageBar, as removing the Autocomplete does cause the missing divs to appear. So there are absolutely no errors caused by the Autocomplete, but it does prevent the PageBank from doing its thing. I don't know enough about using dojo to hypothesize very well, but my guess is that both components are setting some kind of callback or handler, but one is overwriting the other. --sam On 4/6/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > Do you not get any javascript errors in your JS console when this happens? > You might try installing the FireBug extension for firefox. It's extremely > good at debugging almost anything you'll need to figure out. > > > On 4/6/06, Sam Gendler <[EMAIL PROTECTED]> wrote: > > > I am using a TurboWidgets TurboPageBar to provide a tab pane, but if I > include an Autocomplete field anywhere on the same page as the > TurboPageBar, the entire TurboPageBar disappears entirely. I assume > this is a name conflict of some kind. I am hoping someone with more > knowledge can look into this, and maybe talk about a workaround. I'd > really like to be able to use both. In fact, I'd like to be able to > include an autocomplete within a tab on the TurboPageBar. > > I've attached an html page which you can use, although you'll have to > download TurboWidgets from http://www.turboajax.com/ and then stick > the page in Tapestry to add an autocomplete. Both TurboWidgets and > Tacos rely on dojo, so I've included the syntax for using turbo with > an external dojo library, rather than using the built in one. > > --sam > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642 > _______________________________________________ > Tacos-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/tacos-devel > > > > -- > Jesse Kuhnert > Tacos/Tapestry, team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://opennotion.com ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Tacos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tacos-devel
