Hi Brent, > I think we need to have the ability to enable/disable > in the DQSD app not just the installation program.
I agree 100%. I think the 'installer' should function similar to the current "?" functionality - in that it allows you to check boxes in what amounts to an HTML page. A well-written script should be able to do all that I described, though I've not had to read or write files in the ./searches directory - I'm pretty sure other searches do it now. > Also I like having the search configuration > information (language, category, enabled status, etc) > in xml so it's explicitly all there... I agree. The index I suggested would be an xml-formatted file that simply served as a single physical cache location for the important (to DQSD) information so that not every resource within every search (enabled and disabled alike) had to be cached in memory. It would provide the best of all worlds - smaller memory footprint, faster cache retrieval, direct recovery of uncached information from referenced files, and the ability to edit each record individually as a separate XML file to ease broad contribution. Regards, Shawn K. Hall http://ReliableAnswers.com/ '// ======================================================== "There's not a lot of money in revenge." -- 'Inigo', The Princess Bride ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ DQSD-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-devel
