>From Jesse Kuhnert <[EMAIL PROTECTED]>: > P.S., Since we can basically do whatever we want there'd be nothing wrong > with releasing a beta-2 as soon as Bug35 is fixed.
To sum up on the bugs: Bug11, i dont think this can be really fixed any time soon (even for tacos4 final). I had to do a few tapestry patches in order just to be able to see something in portlets (though it may be Jetspeeds fault and not Tapestrys - i guess there are many ways to interpret the JSR). And many many things used by AjaxService are unsupported in PortletRequest & PortletResponse, i.e. addHeader. Maybe for tacos4 we could just make tacos components work as if javascript was disabled. It s not that bad a solution. Bug13 i really want to investigate a bit - at least for Konqueror. I dont think we ll get to 100% support, but we can make it better than it is now. Bug18 is not IMO critical, and it doesnt affect users at all. Bug35. I can live with it as it is now. Dont know about users though. So, i ll be working on 13 from Monday (maybe even test on Safari) + waiting for suggestions for 11 and 35 + hopefully we can release beta-2 during this coming week. > > On 2/4/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > > > Eh, I have to be honest that I didn't spend a very large portion of time > > on that one. We can always re-open Bug35 and re-address it in beta-2. ? > > > > > > > > On 2/4/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > > Just saw how bug35 was fixed, and wanted to note that someone might run > > > into > > > problems > > > even now. > > > > > > Tapestry AbstractEngine handles PageRedirectException a bit differently. > > > > > > It checks to see if a second PageRedirectException is thrown while > > > activating > > > the new page (for instance in the page validate method) and then > > > activates that > > > second > > > page - until no PageRedirectExceptions occur. > > > So, it is possible that we can end up in the page we started. > > > > > > Tacos implementation will also end up (through a javascript redirect) to > > > the > > > same page > > > but there will be a slight difference. State (private page fields > > > mostly) will > > > have been lost. > > > > > > So, it is probable that in the near future we will get another bug > > > report on > > > this, saying that he > > > is seeing different things when moving from @Form to @AjaxForm. > > > > > > BTW, i actually thought that this would be resolved by doing exactly > > > what > > > Tapestry does and then > > > returning a special ajax response code along with the complete html > > > page. Then > > > tacos.js would replace > > > the whole page instead of the given portion. But ofcourse, thats easier > > > said > > > than done :) > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > > > files > > > for problems? Stop! Download the new AJAX search engine that makes > > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > > > _______________________________________________ > > > Tacos-devel mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/tacos-devel > > > > > > > > -- ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Tacos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tacos-devel
