[Chandler-dev] Natural language parsing in Chandler

[Heikki Toivonen]

Philippe Bossut wrote:
> On step 2, when we discussed CLI (Command Language Interface) UI long
> time ago, Lisa suggested to use the same field as the search field for
> this. i.e.:
> - type "whatever": searches for "whatever" in the repo items
> - type "/command x y z": launches "command" with the parameters "x y z"

I think there is a relatively easy way to distinguish between these in
the UI. Think about the Firefox search box in the upper right. It has a
drop down where you can select the search engine to use.

I think we could have the Chandler "search" box be a multifunction box.
By default the search context would be selected (use magnifying glass
icon or something). It would work exactly as Philippe described above.

If one were to change the context to "new event", then typing in text
and hitting enter would create a new event, parsing date etc. info from
the text. If you wanted to search instead you'd have to begin with /search.

This could work if there were just a handful of different commands or
contexts. Ideally just two: search context and command context.

-- 
  Heikki Toivonen


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 251 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20060612/dc329daf/signature.pgp