Hello,

one of the few features missing from KM is the autocomplete feature for each form field, like FF does.

I found a JS examples site (http://www.javascript-examples.com/autocomplete-demo/) which offers JS autocomplete examples incl. sources,
but I don't know how to tell KM to use one of these scripts.
Maybe someone with more knowledge about the inner workings of KM could
shed some light on this?

And there's another site which offers a jQuery plugin: Autocomplete (http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/).
The latter seems to be rather targeted at web developers,
but I'd like to have the autocomplete feature on every web page,
as normal user.


Thanks for your help:-)


The other missing features:
An easier way to update NoScript and ABP, be it a simple general script

No one interested in a real solution for this missing but important (IMHO) feature?

I'm sure there are _users_ who would like to have this feature implemented in KM,
but also don't know how to make it work.

FF has it, IE has it, and maybe other Browsers have it,
or at least support usage of external tools, like Roboform.

The older FF mechanism using a file (formhistory.dat) would be sufficient,
no need for the SQLite version using formhistory.sqlite .

However I'd prefer to use KM, but the autocomplete feature is _really_ missing,
so maybe I'll switch back to FF.


OT:
For me, one of the reasons to switch from FF to KM, was the increasing slowliness
of FF after some time of usage, which can be hours.
Since I often work with several open tabs, response times grew fast,
rendering FF to a unusable state.

However, KM also tends to slow down after some usage time and open tabs,
but doesn't speed up again after having most of the tabs closed.
I have to end the application and restart KM again.
This behaviour is similar to FF, and maybe it's due to the slow
JS engine, so there's not much gained.

Still hoping for some serious responses - Thanks:-)

Ray

Yes You are interested! We are all users & volunteers that do the work.

I pressed Roboform plugin to serve my needs years ago.

IMHO it is Your turn now.



Edited 1 time(s). Last edit at 11/30/2009 05:02AM by guenter.

Thanks for your reply.

I took a look into the sources of FF 2.0.0.2 for occurences related to formhistory.
Since I'm not too deep (actually not at all) into web browser development,
I realized that adapting the autocomplete service from FF to KM
would be a task for someone much more experienced in that area.

The external solutions, like Roboform or lastpass (in the CCF version),
look like firing cannon balls towards sparrows,
and propably need more PC energy than the FF internal solution ported to KM...


I appreciate the great work of many enthusiasts for making KM a real nice browser.

However regarding web browsers, I'm a user and I don't want to dig into
the inner workings too much (Except maybe "Open selected links in tabs";-) ,
since my own free-of-charge projects (like SpeedUI for HP-48)
consume much of my spare time...

Ray

Ok, then You know that all takes three times as long as expected - so some things are never done.

Firefox has Toolkit backend - so some things are impossible.

SeaMonkey "wallet" service activated in --enable-extensions during compilation will not be available anymore after the change to GRE 1.9.

p.s. ich habe mal versucht mehr von dem Dienst zu aktiviren, wusste aber nicht genug. Jetzt müssen wir warten, was uns bei 1.9 erwartet.



Edited 1 time(s). Last edit at 12/01/2009 12:13PM by guenter.