r3 - 07 Jul 2005 - 14:18:01 - LisaDusseaultYou are here: OSAF >  Journal Web  > NamespaceCompletion20030116
From Jon Udell's Radio Blog

application namespace
Epsilon (emacs) file/directory
Epsilon (emacs) commands
Outlook contacts
QuickBooks account names
MSIE urls
MSIE per-site forms input
ActiveWords active words

"Sadly, each of these per-app completion mechanisms works in a different way, and each is available only within the context of the app...

Here's my nirvana. Every app that manages one or more namespaces -- and it's hard to think of an app that doesn't -- would offer namespace completion as a service. Let's make it a web service, while we're at it, so it's available locally or remotely in the same way.

Can't we please support this at the OS level, across operating systems? I know that completion isn't only a geek thing, because I've seen QuickBooks users utterly depend on it. We haven't managed to generalize the idea, though, so people don't expect it to work everywhere and polymorphically. They should. ... the reason I don't depend as heavily on bookmarks and tabs as I might is that namespace completion mines the browser history very effectively for me."

-- SocinianClarke - 16 Jan 2003


It seems to me that the completion solution you're looking for should be directly tied to the 'context' of the data entry field that the user is editing: "email address, subject, date, message, etc" I suspect that Chandler's developers could devise a completion engine that is 'fed' by a context-specific database of commonly entered information. Ex. Email data entry field could feed the NamespaceCompletion? routine with a database of email addresses, email message could be fed with a dictionary, etc.

-- JimMcCusker - 17 Jan 2003

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r3 < r2 < r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.