This post about a little and trivial thing (already reported to HMG developers).
Mmm… little and trivial?… deserves it a post?… YES!!!… I’ll explain why… lets go!
Again… I’m thinking (specially) in new HMG users and their experience.
Being new to HMG, one of the first things that you’ll gonna do, is to review the documentation.
It includes a nice text-input along with a button labeled ‘Search’.
As you could imagine its purpose is to search the documentation… YOU ARE WRONG!… IT DOES NOTHING! 🙂
This search ‘feature’, resulted to be problematic for many users, reporting incompatibility with some anti-virus software, slowness and other problems that could even to impede them to use the help docs.
So, it was decided to disable it… GOOD DECISION!.
The problem is that the text-input and the search button still being here… driving us to… ‘The Problem’ 🙂
Mmm… (again)… IMHO (I could be wrong!) this ‘feature’ should be reconsidered from the scratch, since, because its design, it could be very very difficult to solve the problems reported by the users.
Besides that, it is not a real full-text search, but an indexed search based on some few keywords, ‘hard-coded’ on a JS function, meaning that its utility is very limited.
I’m a little obsessive and I get easily disturbed by non-working things and this is a very notorious non-working thing 🙂 .
So, I’ve simply removed the text-input and the non-working search button from documentation.
Despite my obsessive neurosis, think again in ‘The Problem’: A new user trying to search something on documentation, repeatedly clicking the search button with no results… NOT GOOD!
WANT TO REMOVE THIS ‘FEATURE’?:
You must replace ‘navigator.html’ file, located at \doc\data sub-folder of your HMG3.4.3 installation.
You can get the fixed file (Navigator.htm.7z) from here
WANT TO TALK ABOUT THIS?
If you want to discuss about this (even to disagree with me ) you ca do it here (you need a SourceForge account to be able to post).
IMPORTANT NOTE (Déjà vu):
The problem described here, was already posted to HMG developers and it will be fixed in the next versions (at the time of this writing version is 3.4.3).