> > Simple searches would gain access to these abilities without having to > > be coded as an addon. Don't get me wrong - though I love that addons > > *can* be done, and have more abilities than simple, or complex even, > > searches, I'm not fond of relying on addons for what I believe should > > be basic functionality. > > You know, I feel the exact opposite way. I think search.htm is already > overloaded with functionality, and that stuff like this should be separately > installable. A 31 KB .htm file consisting of mostly javascript is not my > idea of maintainable software. As far as I'm concerned, the basic > functionality of Dave's Quick Search Deskbar is all in its name; a *quick* > *search* *deskbar*. That's really all I need. >
I feel strongly about this... Bloat and scope creep are the enemies of any application. The whole reason the add-on capabilities were added was to allow the core toolbar functionality to be lean and mean, and to allow extra funtionality to be added to those who wanted it, without affecting every single user running the toolbar. There are still parts of the toolbar that an argument could be made to move to an addon, or at least to standalone functionality that could be disabled. This all became an issue when the problem of losing tray icons on windows startup surfaced.. > The fact that it can do lots of other stuff for me is mostly cool, but I > rarely use any of the features, so I'd rather have that I could install them > when/if I need them. > > But this is getting to be a tired argument :) My vote is for an add-on. > +1 FWIW, Monty ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ DQSD-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-devel
