Talk:Incremental search: Difference between revisions
m Signing comment by 173.13.229.185 - "→Origins: " |
No edit summary |
||
| Line 55: | Line 55: | ||
The term "incremental search" seems far more common than "incremental find": Google ["incremental search" -wikipedia] 90,500 vs. ["incremental find" -wikipedia] 34,900. In Google Books: 671/40. Though there are admittedly other meanings for "incremental search", scanning the results seems to show that "incremental search" is still more common in this sense than "incremental find" is; moreover, it is the name in Emacs, which originated it and is still in wide use. I suggest the article be moved. --[[User:Macrakis|macrakis]] ([[User talk:Macrakis|talk]]) 21:44, 20 December 2009 (UTC) |
The term "incremental search" seems far more common than "incremental find": Google ["incremental search" -wikipedia] 90,500 vs. ["incremental find" -wikipedia] 34,900. In Google Books: 671/40. Though there are admittedly other meanings for "incremental search", scanning the results seems to show that "incremental search" is still more common in this sense than "incremental find" is; moreover, it is the name in Emacs, which originated it and is still in wide use. I suggest the article be moved. --[[User:Macrakis|macrakis]] ([[User talk:Macrakis|talk]]) 21:44, 20 December 2009 (UTC) |
||
== Incremental search - needs section on significance of incremental search on Web == |
|||
My notes - that described (briefly) the fact that web based searches used non-local resources as opposed to local resources - have been edited out by Macrakis. The casual observer will now be left wondering why web searches use more resources. It is a very important point and has been covered in numerous blogs and criticisms of Google Instant for example. |
|||
This is what I had added:- |
|||
---------------------------- |
|||
=== local scope v. internet scope === |
|||
While offline (or private network) incremental searches utilize mainly "local" resources (such as a single [[personal computer]]'s processor and its attached peripherals such as [[hard disk]]s), an incremental web searches represents a [[paradigm shift]] in the [[Scope (computer science)|scope]] of such a search. |
|||
An incremental search on the "Google web space" involves enlisting a global network of resources (including worldwide communications, online databases etc) and consumes bandwidth even during the time a user is entering individual keystrokes. The implications for [[algorithmic efficiency|efficiency]] are significant since, at the level of keystrokes (as opposed to whole words or phrases), the number of [[false positive]]s is intrinsically quite high until more of the entire search key is eventually entered or selected. This will inevitably consume more resources (and use more energy) than would have occured on a full search key <ref>http://bizdharma.com/blog/never-use-google-instant/</ref><ref>http://www.google.com/support/forum/p/Web+Search/thread?tid=4d9dab8ab0f64ca8&hl=en</ref> |
|||
A further disadvantage to web based incremental searches is the insurmountable problem of varying response times in relation to a users latent [[typing speed]] and, to some extent at least, [[reaction time|"thinking" speed]] (since searches are often typed "[[on-the-fly]]"). If the response time is slowed (due to poor connection or other delays), the user may experience some [[Disorientation#Disorientation_in_hypermedia|disorientation]] effecting the overall "[[User experience|user experience]]" of the interface. |
|||
------------------------------------------- |
|||
I believe my changes should be put back in. |
|||
Revision as of 13:15, 16 September 2011
 | Computing: Software Stub‑class  | |||||||||||||||
| ||||||||||||||||
Excremental
The link to "Excremental" redirects to "Feces." Can it be removed, or is there a better article to link to? Hac13 (talk) 05:49, 15 November 2008 (UTC)
Page rename
I disagree with calling this feature "Non-modal incremental find". It's quite modal, and the biggest drawback is that it's modal without being a dialog, leading to mode error. --User:Jesse Ruderman
- I removed the "non-modal" bits as the name is too lengthy. --minghong 09:03, 20 Apr 2005 (UTC)
Origins
What are the origins of this type of feature? I remember hearing once that Emacsen pioneered this, but I'm not at all sure. --maru (talk) contribs 04:47, 3 April 2006 (UTC)
- I'm flabbergasted that WordPerfect gets the credit for this. GNU Emacs has AFAIK always had this, although a quick search only confirms it was present in Emacs 15 (the NEWS for Emacs 16 lists an enhancement for low baud usage), which was released in 1985. I do not know if this was new with GNU Emacs or if Gosling Emacs had this as well. Kjetilho (talk) 12:41, 10 June 2009 (UTC)
- I did some research and added some earlier history. I think the WordPerfect story could be less chatty and more encyclopedic, but I'll leave that for others to edit. Kjetilho (talk) 08:32, 11 June 2009 (UTC)
EMACS had this in the 1970s; it was called "incremental search". It was modal: you type ctrl-S to begin, the prompt says "I-Search:" and you start typing. As you type (or delete), it scrolls through the buffer to the matching string; you exit by typing ESC or any editing command. This version of EMACS was written in TECO on the PDP-10, not sure who created this particular feature. The (much fancier) version of emacs on the Lisp Machine also had this, about 1977. I think EMACS may have coined the term "incremental search", by the way. —Preceding unsigned comment added by 173.13.229.185 (talk) 19:10, 8 September 2010 (UTC)
less?
The article claims that incremental find is available in less, but it doesn't seem to be available in version 406 of less. Does anyone know if there exists a version of less that supports incremental find?
word wheeling
A similar article called word wheeling exists. I would like you guys to have a look at it. --Kushalt 19:47, 26 October 2007 (UTC)
Fair use rationale for Image:Faytie7.jpg
Image:Faytie7.jpg is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.
Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.
If there is other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images uploaded after 4 May, 2006, and lacking such an explanation will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.
BetacommandBot 11:09, 27 October 2007 (UTC)
Linux
Non-modal incremental find is found in:
Modern operating systems:
- Apple Computer's Spotlight (which searches the entire computer);
- Microsoft's Windows Vista;
Is Linux just omitted is does it really not have it? ʄ!•¿talk? 17:25, 20 June 2008 (UTC)
- All or most of the applications listed run on linux, so technically linux has this. The more detailed question is whether and where this feature appears in KDE, gnome and the like. Surely it's there; just a matter of identifying specific examples. dr.ef.tymac (talk) 23:57, 20 June 2008 (UTC)
Incremental search vs. incremental find
The term "incremental search" seems far more common than "incremental find": Google ["incremental search" -wikipedia] 90,500 vs. ["incremental find" -wikipedia] 34,900. In Google Books: 671/40. Though there are admittedly other meanings for "incremental search", scanning the results seems to show that "incremental search" is still more common in this sense than "incremental find" is; moreover, it is the name in Emacs, which originated it and is still in wide use. I suggest the article be moved. --macrakis (talk) 21:44, 20 December 2009 (UTC)
Incremental search - needs section on significance of incremental search on Web
My notes - that described (briefly) the fact that web based searches used non-local resources as opposed to local resources - have been edited out by Macrakis. The casual observer will now be left wondering why web searches use more resources. It is a very important point and has been covered in numerous blogs and criticisms of Google Instant for example.
This is what I had added:-
local scope v. internet scope
While offline (or private network) incremental searches utilize mainly "local" resources (such as a single personal computer's processor and its attached peripherals such as hard disks), an incremental web searches represents a paradigm shift in the scope of such a search.
An incremental search on the "Google web space" involves enlisting a global network of resources (including worldwide communications, online databases etc) and consumes bandwidth even during the time a user is entering individual keystrokes. The implications for efficiency are significant since, at the level of keystrokes (as opposed to whole words or phrases), the number of false positives is intrinsically quite high until more of the entire search key is eventually entered or selected. This will inevitably consume more resources (and use more energy) than would have occured on a full search key [1][2]
A further disadvantage to web based incremental searches is the insurmountable problem of varying response times in relation to a users latent typing speed and, to some extent at least, "thinking" speed (since searches are often typed "on-the-fly"). If the response time is slowed (due to poor connection or other delays), the user may experience some disorientation effecting the overall "user experience" of the interface.
I believe my changes should be put back in.