On 3/22/06, Leonardo Quijano Vincenzi <[EMAIL PROTECTED]> wrote: > Ahh right. > > Yes, this is a problem I found out some time ago when using some Tacos > components. I use a lot of Component-in-Component in my application, so > those bugs tend to surface there. But I haven't used the autocompleter. =================== 99% of the stuff I do is component in component because I strongly believe an Ajax app is an application that runs from a SINGLE page .
> As for the demo, actually, a better solution is to showcase a full - > working app for that. =================== yea that's what I mean > But for automated tests simpler pages are actually > better. For example, for this Autocompleter problem, we could use a > simple page with a JWC and a Autocompleter inside. The simplest way to > reproduce the bug is always the best. =================== Well yes , it's simple to have automated testts on simple pages , but as you can see , simple pages won't find all the bugs a component might have . I'm thinking back to the 2 - 3 months i've been complaining that there is a comment bug in tacos . Everyone was telling me it's fixed , and then Andy realised that the bug is still there IF you also have <script> tags in your response . > > Did you register a bug report for this? A test page - like the one I > said above - would help us a lot, too. Checkout the bugs/ directory in > the demo for examples of test pages. =================== I have provided example code , I have provided details , didn't register the bug as Andy told me he has good leads on the problem . > -- > Ing. Leonardo Quijano Vincenzi > DTQ Software > > > Cosmin Bucur wrote: > > Leonardo , please check my post regarding the autocompleter as an example . > > > > In the dedmo the autocompleter is the ony component in a .page ... I > > tried using it , and i needed to have it in a jwc that would be inside > > a page . This was as far as I could go because the autocompleter was > > made to work only inside a page and doesn't seem to work if it's > > within a jwc that's within a page ... > > > > Similar problems i've found with other components , and while > > automated testing is done for the demo , the demo simply has one page > > especially for each component , meanwhile the framework has problems > > when combining all the components in a real life scenario ... > > > > all i'm suggesting is that it woul be better to have a demo that DOES > > something and combines the components rather than just have a special > > page for each in part , where they are guaranteed to have no problems > > if they work fine by themselves > > > > On 3/22/06, Leonardo Quijano Vincenzi <[EMAIL PROTECTED]> wrote: > > > >> I'm sure this can be fixed in a workstation independent way ;). > >> > >> I'll catch up later if I get a chance. > >> > >> -- > >> Ing. Leonardo Quijano Vincenzi > >> DTQ Software > >> > >> > > > > > ------------------------------------------------------- > 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&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Tacos-devel mailing list > Tacos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tacos-devel > ------------------------------------------------------- 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 Tacos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tacos-devel
