Hi Brent, > Some of my friends who I've converted to DQSD when I > tell them how to define an alias - their eyes glaze > over and they can't do it.
I see a small little form with a text field (for alias name) then a drop-down that lists the search names. When a search is selected in the search listing it generates a second dropdown that includes the available extensions for a given search (from column one of the @class=helpboxDesc table with a description next to it (or on float-over) of column 3 (if 3 columns) or column 2 if the table is only 2 columns. Additional text fields would function as the rest of the options for the alias (name, section, description). Next to the search-alias builder would be a couple options for 'simple' and 'advanced' view, where the advanced view would effectively display just a long text field beside it with whatever they've built within the simple view up to that point. > 1) move to a Windows deskbar (which Kim's got a good > start on - I've been using for quite a while) Yep. > 2) move the auto-search specification hardcoded-ness > out of search.htm Yep. > 3) make ui for setting up aliases and setting variable > values - even if it's something as simple as mozilla > firefox's about:config page Yep. > 4) make disabled searches not take up memory - need an > easy way to enable/disable searches other than > renaming or deleting the searches you don't want Yep. > 5) make ui for finding/adding/removing searches Yep. > 6) support Google Deskbar extensions - this is > something I've been rolling around in my head as > something that might be cool. You know that there are > going to be more and more extensions (searches) > written for Google and it'd be nice to be able to use > those out of the box. It would involve finding those > and starting the .NET runtime if available - which > would be a fun technological problem as well :) Yep. Google Deskbar doesn't provide a very simple way to extend itself, so this would be some work. http://deskbar.google.com/help/api/index.html It also looks like the plugins are expected to be redistributed as dll's, so they won't work with the same object model without adding more complexity to the DQSD engine. Regards, Shawn K. Hall http://12PointDesign.com/ http://ReliableAnswers.com/ '// ======================================================== If at first you don't succeed, skydiving isn't for you ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Archive: https://lists.sourceforge.net/lists/listinfo/dqsd-devel
