On Mon, 30 Aug 2004 19:58:04 +0200, Kim Gr�sman wrote > - Parsing of disabledsearches.txt - is this still the way to disable > searches? I though you were to rename them to .xml_disabled or something...?
Well the renaming of the search files was a kludgy workaround in lieu of a real method to disable searches... The toolbar loads all searches it finds into memory... With over 310 searches in the package, this is really wasteful... > - localsearch.xml - there's some interesting code which looks for > localsearch in the document, loads an XML document by that name, and > adds the local searches mentioned therein. Surely the localsearches directory > covers this stuff now? Yeah originally *all* the searches were contained in a single xml file!. (ugh) I think a mechanism was implemented to allow for local searches that weren't part of the standard delivered xml file, and later the individual searches were split out into standalone xml files.. And of course now we have a localsearches subdir... All that old processing of a single xml file containing multiple searches is not needed anymore... > > To be honest, it doesn't take much time to execute, but it bothers > my eye. > > Are you all OK with me removing this functionality, or should I > leave it for backwards compatibility? I say yank it like you're starting a mower! ;-) > > FYI, I have found an optimization worth mentioning: document.write > calls are EXPENSIVE, so I shaved off something like 30% of the > source-emit time by building a string and writing it in one go. ooh thats a nice tip.. thanks! monty ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_idP47&alloc_id808&op=click _______________________________________________ DQSD-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-devel
