Hi Heikki,

> 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.

I've been thinking along similar lines, although I'd imagined that for
discoverability all commands would be in the drop down.

My picture has been of a drop-down menu with not just icons, but also
listing the command you'd use if you didn't want to do the currently
selected action.  It could look something like:

/search [*icon*]
/event  [*icon*]
/task   [*icon*]
/note   [*icon*]

Switching context to /task mode would make it possible to do what a
participant asked for recently on the design list
(http://lists.osafoundation.org/pipermail/design/2006-June/004836.html),
create a series of tasks by just typing the titles and hitting enter.

I imagine many people would stay in /search mode all the time, so they'd
have to type /task by hand if they wanted to make a new task.

It would be really cool if we got language parsing to the point that my
workflow to create a task could be:
1. command+K to get to search bar (that's what Mozilla uses, might as
well follow suit)
2. type /task book hotel reservations by Thursday

and I'd have a task with appropriate due date.

Sincerely,
Jeffrey
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to