searchbar plugin

This plugin adds a search bar to K-Meleon.


Changes in v0.0.3:

* Fixed focus bug (Dorian).
* Fixed: cannot type more than editbox width (Dorian).
* Added "kmeleon.plugins.searchbar.title" pref (Dorian).
* Added Unicode support (Dorian).
* Renamed SetFocus to Focus.

thx You guys.

btw. I a not sure, but this might be one of the dll that can use (like bookmark) mark307s patch for input abbility of special (Chinese & Japanese) characters?

This patch? It only affects the Bookmarks plugin....

I am not very familiar with non-Latin character inputs, but all I know is that I can type and search using these characters (under WinXP English, K-Meleon 0.9, standard US keyboard): Traditional Chinese (Taiwan), Simplified Chinese (using pinyin), Japanese, and Korean.

Just don't ask me what I typed in....

This searchbar works fine. I can input Japanese charactors through IME to the searchbar.

As I understand, a cause of that IME problem is keyboard hook. Bookmarks plugin uses hook, this plugin doesn't.
Thanks.

It seems the 0.0.3 version doesn't works with w98se, I ought to test 0.0.2 , but unfortunately, if the link text on your page indicate 0.0.2, it's in fact 0.0.3

A+

Alain,

I can confirm that this 0.0.3 version doesn't play well with W98se on my laptop.

N

I've corrected the link to version 0.0.2.

Is there any more information about the problem, e.g. an error message?

K-Meleon Crash when starting, just after having checked the plugin, I'm on this computer under XP, but with 0.9.12

After having deleted searchbar from kplugins, it stats ok

I'm going to test with 0.0.2

A+

0.0.2 works with 0.9.12
0.0.3 crashes 0.9.12

A+

> K-Meleon Crash when starting, just after having checked the plugin, I'm on this computer under XP, but with 0.9.12

1. So it crashes under 98SE and XP?

2. I need to know what the error message says; otherwise I can't do much. Output from the crash plugin would probably help as well.

The OS seems not important here, just the KM version.

I'll post the crashlog to-morrow.

An idea (I think it's not too difficult, but I really don't knows) is to read the pref kmeleon.general.searchEngine to choose the engine instead of having it hard-coded in the kplugins.

A+

> The OS seems not important here, just the KM version.

There's a possibility that I uploaded the wrong build. The one built against K-Meleon CVS does crash 0.9....

> An idea (I think it's not too difficult, but I really don't knows) is to read the pref kmeleon.general.searchEngine to choose the engine instead of having it hard-coded in the kplugins.

It uses keyword.URL (I just forgot to document it), but I'll change it to kmeleon.general.searchEngine.

Sorry, but it's the same with the last version (I use 0.9.12 Fr4)

K-Meleon Crash Information

Application exception occurred:
Date: 2006-04-20 @ 18:40 +1, Paris, Madrid (heure d'‚t‚)
Exception: C0000005 (ACCESS VIOLATION, Reading Address: 6547202A)
Process: C:\PROGRAM FILES\K-MELEON\K-MELEON.EXE
Exception Addr: 6547202A

*----> System Information <----*
Number of processors: 1
Processor Type: x86 Family 6 Model 8 Stepping 10
Windows 98 Version: 4.10 A
Current Build: 2222

*----> Stack Back Trace <----*
ReturnAddr Param#1 Param#2 Param#3 Param#4 Param#5


I'm going to try with Plus 8

A+

The same with Fred's Plus 8.

A+

OK, I have uploaded the one that should work with 0.9. Can you try again?

rmn,

Your latest 0.0.3 searchbar.dll works now on my W98se system running KM 0.9, GRE 1.7.12 (Brian's patch).

<g>

N

Ok, now it's ok with 0.9

Just two improvements I hope, if possible:

-Take the pref 'kmeleon.general.searchEngine' to choose the engine
-Take the pref 'kmeleon.general.searchOpen' to choose the window open mode

-searchEngine = 0 >> current window
-searchEngine = 1 >> new window
-searchEngine = 2 >> Background

A+

-Take the pref 'kmeleon.general.searchEngine' to choose the engine

Yep, I've changed it for the next version.


-Take the pref 'kmeleon.general.searchOpen' to choose the window open mode

I have to investigate further to make it consistent with other similar operations (ID_NAV_GO, ID_NAV_SEARCH, macros(Search)), because we have 5 places to open a page in (current, FG window, BG window, FG layer, BG layer) and I don't want to simply assign 5 arbitrary numbers for each of them.

I think I'll see how ID_NAV_SEARCH behaves and copy it.

You can put the action to do directly in the pref instead of a number.

And yes, plugin compiled for 1.0 will only work with 1.0