At 10:44 AM 01/28/02 +0800, Stas Bekman wrote: >Of course, silly me :) > >But that's easy. We just prepare a special template during the >rendering, which will be an html with everything inside + a placeholder >for search results. Piece of cake. Right? We should need only one static >page for this as all the hits will have their links from /.
That's fine. If DocSet can build me a page with just a [% content %] section where you want the results, that will be easy. My existing template is designed to use with WRAPPER, so that will make things simple. We could always hard code the layout for the search script. Would be a little faster than loading TT for each search. But it would be nice to use the script. So with docset, if I modify one page and run /bin/build, it knows to only build that one page. But what if a change in a page modifies how the sidebar menu will look will DocSet go and re-build everything? Maybe when you can't sleep some night think about separating DocSet from the HTML generation. It might be nice. DocSet -> ttree -> html output. DocSet might write a tt config file, or provide a plugin to read the cache. You might end up with a more powerful solution where DocSet, CGI, and mod_perl could be used together in a site. DocSet should also be able to read a config. For example, if you wanted "Search" to be a menu item, but Search is not part of "src" then it might be nice to have a way to tell DocSet to include that. >so you say that it didn't copy the dot files from the search directory, >right? Right. But odd. I did a cvs update and bin/build and now the .htaccess you added was copied. Also: .../dst_html/.htaccess: Redirect to non-URL >BTW, update your cvs, I've added an .htaccess file at the root dir already. I thought I just updated a few hours ago. ... Oh, now there's the update. > >>> <!-- SwishCommand index --> > >>> [% content %] > >>> <!-- SwishCommand noindex --> > >I'll commit it immediately. Yep, that's it. Add libxml2 to swish-e was a very nice thing. The old html and xml parsers in swish really sucked. But then I get "bug" reports where javascript was being indexed: <script> <!-- hide from old clients some javascript here // end of hide --> </script> The old swish HTML parser would ignore the java script inside the "comment", but libxml2 (correctly) seems that as CDATA and it was indexed. Libxml2 makes it easy to add IgnoreTags script style And fixed. One more bug to fix before I sign off. Let me know when you can generate a template for the search script to use. -- Bill Moseley mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
