Re: [DQSD-Devel] Re: [DQSD-Announce] ANN: DQSD 3.1.9.1

[Monty Scroggins]

FWIW - Personally I think all the special handling should be removed unless it is needed for the toolbar to function properly.  Most of the special handling is left over from when the toolbar only had a few builtin searches with no searches directory full of search xml files. Why would a DNS lookup be a hardcoded process when there searches to perform the same function?  The same applies for currency conversion, language translations, phone number lookups etc... my $.02 Monty Shawn K. Hall wrote: Hi John, I have disabled and deleted ARIN... However I have left DNS (DNSStuff.com). The ip autohandler currently checks for the existence of the function before attempting to use it. This is the way all the auto-handlers work, though the process could be improved. Can/should there be a preference for the default handler for DNS? Maybe I'm missing it here since I so rarely use any DNS lookup stuff anyhow. If I enter an IP in DQSD, I'm usually hoping to launch it in my default browser. Maybe that could/should be a preference too? Feel free to correct me if I have my head in the sand. We've discussed solutions for this type of thing for the next release, sorta. What I think we're going to do is rework the "auto" handlers so they're appended to a new array of functions that is enumerated when a new search is processed. This would effectively allow each search to 'turn on' it's own auto-handling during the initial loading of the script, so if/when you delete/disable the search it kills the auto-handler for that search, as well. As autohandlers are being detected during processing they are compared against a "disable" variable of a similar name, so you could have two handlers for ip-detection and disable one or both of them. Throughout your use of DQSD you could programmatically change the values of the disable variables and effectively toggle the state of the auto-handler instructions. I'd also like to eventually provide alternative handlings for other events, and be able to toggle state within a search. For example, I use a home-made search for url parsing all the time, in order to add domains to my censor list ( www.commoncensor.com ). Unfortunately, right now DQSD only provides a simple "window.open" type handler for URL's, but this would allow me to just copy and paste urls into DQSD and not have to prefix them with a search function name. So I could write an alias that toggles the default url processing instruction from "window.open" to "mysearch" and vice versa. Likewise, the user could toggle the IP-autodetection script, as well, or any other handlers, like "default," "phoneautodetect," and the 'drag+drop' event. Regards, Shawn K. Hall http://12PointDesign.com/ http://ReliableAnswers.com/