This kind of sucks. I hoped there was an easy way to include large pre-formatted portions in a kid template.
I have another: are there any examples on implementing caching of XHTML fragments with Kid? Thanks, nyenyec On 2/17/06, Martina Oefelein <[EMAIL PROTECTED]> wrote: > > Hi Nyenyec, > > > In my application I have relatively large (20k-100k) XHTML files in > > the DB. I'd like to show a number of these to the user based based on > > some filtering criteria using a single page. > > > > I didn't find any efficient way in kid to include large XML documents. > > Using the XML() function makes it very slow and the page takes more > > than 2 seconds to generate. > > > > In the context of TurboGears are there any efficient solutions to do > > this? > > One option would be to serve the XHTML files separately from the > templated page. In the templated page, use either iframes to include > the xhtml files, or use a bit of javascript to load them via > XmlHttpRequest. > > Another option would be to put placeholders for the xhtml files in > the template, and postprocess the kid-generated html to replace these > placeholders with the real xhtml data. > > ciao > Martina > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
