Hey Monty,
> IMO if any of this special handling is in place, the embedded
> search code should be split into a standalone xml file and
> placed with the core searches bundle.. This might really
> make sense since the creation of the core searches directory.
In one way, yes, but then there's the overhead of loading and parsing an XML
file for each core function...
Here's the relevant portion of search.htm:
// detect special commands
if (!special(t))
{
// detect translations
if (translate(t)) return false;
// detect URLs, filenames, etc to open directly
if (direct(t)) return false;
// detect strings that look like phone numbers
if ((typeof autodetect_phone) == 'function' && autodetect_phone(t))
return false;
// detect strings that look like currency conversions
if ((typeof autodetect_currency) == 'function' &&
autodetect_currency(t)) return false;
// detect math expressions
if (mathexp(t)) return false;
}
// try to execute a shortcut - this should perform the default search
if (shortcut(t)) return false;
I think most if not all of those are valid hard-coded shortcuts. The phone
number auto-detection may be the exception, since it's not globally
applicable, but it's convenient enough for US people, so I don't mind - it's
never gotten in my way so far.
But maybe this is not what you meant...? I guess none of the above can be
implemented as standard searches, since they don't have a given prefix.
As for aliases, the ".", "+" and the "#" bite me every time with ".NET",
"C++" and "C#" - I'd love to get rid of those.
Kim
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
DQSD-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dqsd-devel
