Re: Info Center

just to add, a google search of "cwbRC_RunCmd" returns 3 meaningless hits.
adding "site:ibm.com" or "site:publib.boulder.ibm.com" returns nothing.

in contrast, a google search on the CreateProcess win32 api at site
microsoft.com returns many relevant hits.

So I dont think a google search is a good solution. Not until Boulder opens
its pages to google indexing.

Steve Richter

----- Original Message -----
From: "Steve Richter" <srichter@AutoCoder.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, May 07, 2002 8:08 AM
Subject: Re: Info Center


> Here is a way to fix info center.
>
> The problem is the search results.
>
> First, the order of the search results seems to be completely random.  But
> once you find the best search result link, the presentation of information
> can be pretty good.  For an example, search on a CAE API "cwbRC_RunCmd".
> The top 2 results are useless. The next few, if you are looking for api
> reference info, will get you to a some well ordered and complete info on
> this api.
>
> Second, using the cwbRC_RunCmd api as an example again, the actual api
> reference page for cwbRC_RunCmd is not  in the search results list.
>
> Keep an internal table.
>     Search keyword
>     Search result page
>     Count of times this page linked to via this search keyword
>
> When showing the search results, order the results by link count
descending.
>
> When the search word is an API or command, always show its reference
manual
> page as the top search result. The reference manual page for the API
should
> then not only describe the API but also be the link point for more info on
> the API.
>
> Steve Richter
> AutoCoder, LLC
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>