Pedro Abelleira Seco wrote: > > I also have noticed this. In fact, I think we are going to quit using > the date picker if the performance problems have to do exclusively with > it. Any experiences about how to speed things up? > > BTW, I noticed that is works faster in Firefox than in IE. >
Reviving this topic from the dead... I've had my own set of problems with the Tap4/4.1 DatePicker and decided to look at the code. Wow. So, first off... the DatePicker is being generated using DOM create/attachElement methods, which is http://www.quirksmode.org/dom/innerhtml.html dog-slow compared to innerHTML . For those suffering under older versions of IE, you're looking at an order of magnitude drop in performance. But there's a bigger issue: Why you doesn't the component render its own body? It's just crazy. You know, every time I hack a work-around to some Tapestry limitation I'm admonished about doing things "The Tapestry Way," and yet here's a core component that's being generated in Javascript, and in the slowest way possible. At least it was easy enough to rewrite. -- View this message in context: http://www.nabble.com/performace-issues-with-many-date-pickers-in-a-page-tp1308506p14359676.html Sent from the Tapestry - User mailing list archive at Nabble.com.
