Here's for you who prefer a separate search bar. This plugin is just an update of Romanito's version, adding a few bells and whistles (and bugs):
* Get search engine from pref "keyword.URL".
* Escape some chars.
* Added experimental SetFocus command. (I know it barely works, don't tell me about it.)
Aha. Sorry, forgot to put the instructions. Since Geocities does not like 7z files, I had to rename them to zip. Just remove the ".zip" part of the filename and open it using 7-Zip (I heard that WinRAR also works).
No need to go for kill code. On this verson of KM (0.9, GRE 1.7.5 updated to Brian's latest 1.7.13 patch), Edit/Preferences/Plugins enable/disable works just fine with your searchbar plugin.
Kill code what? I don't understand.... If you are talking about the dll-only download then, yes, please remove it. It contains Romanito's code released under GPL, so theoretically we can't distribute it without the GPL text.
well compiled rmn - i use with 1.0 - ndbord with 0.9! great.
I will remove. did upload that only - so that nothing can interfere.
can not kill from here - may take some time.
alternately i could add usage conditions to my post?
Like: download is under GNU - do not download if You do not accept condition.
p.s. i would have posted kill code but the last time i did - some joker killed the file before the recepient had downloaded.
I'm with you, rmn... having one bar makes things a little less complicated and leaves more real estate for the actual webpage. I like it that way. I have trimmed down my toolbars to only have the bare minimum, as you can see here: http://tinypic.com/view/?pic=sy9vg5
I leave lots of space for what I use a lot and little space for what I rarely use. That's the way it should be, after all- much more effecient that way.
I like the searchbar, but I too have a small screen (12.1) and right now I have edited KM's look down to 2 bars, the Main and the icon line (with privacy bar edited down to fit on that bar). I use too use search from the URL dialog box instead, but from time to time, I enable this search plugin and it is useful, even though it takes up real estate.
By the way, I've just found a strange bug with this plugin. You can't type exceeding the textbox size. I'll look at it, but I don't think I'll be able to fix it.
I really want to know how to fix the focus problem, since I don't know how to associate the textbox to each window/layer so the SetFocus() function works on that window's searchbar. I was thinking of storing them + their parent window handle in a linked list and searching through the list for "current window", but that seems overkill, plus introducing O(n) list-searching.
Another thing: the code to escape characters is horrible (and will not work well with Unicode); I wonder if there is a URL encoder function in the plugin API?
OK, I got rid of the size bug by adding ES_AUTOHSCROLL to dwStyle.
But I just found a major bug similar to the SetFocus bug (I don't understand how I missed this before): the search text is always taken from the last created editbox.
And another one (also related to the problem with SetFocus): I think it's leaking. There are no code to destroy the editbox when a window is closed.