Hi Jono,

Thanks for the super quick response.  Regarding spaces in modifiers/
verbs, I can live with that for now ~ and am looking forward to your
parser2 enhancements that will give it more flexibility.

With regard to auto-complete, what seemed to be tripping me up is an
issue surrounding parsing commands with no DOs-- ( no "takes"
clause ).  When I construct such a command, hitting tab to auto-
complete has the destructive effect of eliminating all spaces in the
command so far -- and selecting a random verb that has a DO of
noun_text_arb.  Pressing tab more times then has an even further
confusing effect of multiplying the (incorrect) verb on the line ...

But now that I seem to have figured out that DOs are required, Tab
seems to be doing the right thing.  I have it now correctly auto-
completing names of twitter followers [and soon facebook friends].
Very exciting.

Thanks, and by the way this is a really cool project, Mozlabs
friends.   I'd like to help out and contribute if possible ~

e...@mit


On May 27, 6:43 pm, Jono DiCarlo <[email protected]> wrote:
> Hi Max,
> These are not newbish questions at all, actually -- they are things
> we've been struggling with how to design.
>
> The short answer is that there's not currently any way to do exactly
> what you want.  We are working on some revisions to the core of the
> parser and the way commands are integrated which will make them
> easier.
>
> As it currently stands, spaces are Very Important To The Parser as it
> uses them to figure out how to break up the sentence, which means it's
> problematic to have them in verb names or prepositions.  (Spaces in
> argument values are always OK.)
>
> For the nonce, I recommend trying to find a way to reword your
> commands so their names and modifiers are single words:  for example,
> "alert on (event) from (source)" rather than "alert me on new (event)
> from (source)".  Not ideal, I know, but it will work
>
> Ubiquity's autocomplete feature is triggered by the Tab key.  Give
> that a try and, if its behavior isn't what you want, send another
> email to the list and let us know how it's different from what you're
> looking for.
>
> --Jono, Mozilla Labs
>
> On May 27, 1:23 pm, electronic Max <[email protected]> wrote:
>
> > Sorry for the newbish questions, I'm trying to work on a research
> > prototype on a tight deadline and am looking for answers fast.  Just
> > joined the group yesterday and am just getting into hacking commands
> > --
>
> > 1. Spaces in modifiers and verbs:
>
> > Does ubiquity currently  / Parser2 handle verbs and modifiers with
> > spaces in them?  I'm trying to implement a reminderbot/assistantbot
> > using ubquity so I can ask it to do things like:
>
> > - "alert me on new emails from aza raskin"
>
> > "alert me" is a verb with a space in it
> > "on new" is a modifier with a space in it
>
> > This ("on new") is a relatively contrived example, but in general
> > modfiiers with spaces seem to be useful. I can't seem to get it to
> > DTRT when there are spaces in modifier or verb names.  Spaces in
> > values (e.g, Aza Raskin) seem to be OK.
>
> > 2. Auto-partial completion based on suggestions
>
> > The other thing I really need is auto-complete for modifier
> > values. For example, if I type "alert me on n", and it shows me "new
> > news items", "new emails" and "new tweets" as suggestions, I want to
> > be able to hit space/right arrow to auto complete _just this modifier_
> > and move on to the next modifier.  Right now I can't seem to figure
> > out a way to do this.  Hitting enter submits the whole thing, and
> > right arrow doesn't
> > do anything.
>
> > Thanks in advance,
>
> > electronic Max
> > MIT CSAIL
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"ubiquity-firefox" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/ubiquity-firefox?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to