Loading Profile...
using escapes (\) for "it", "this"
using escapes (\) for "it", "this" if you want it as natural language. (twitter \this icecream is delicious)
I’m excited
5
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The best point from the company
-
I'm opposed to adding an escape mechanism. I don't want this interface to turn into writing regexps. Ubiquity produces parsings both with and without pronoun interpolation and presents both in the suggestion list, so you can always down-arrow-key to the one you want.
However, anecdotal evidence suggestions that people are annoyed by pronoun interpolation happening when they don't want it. A case can certainly be made that the relative position of the variant parsings in the suggestion list should be different, and that it should be sorted more intelligently. In 0.2 I'm going to be adding some memory to the suggestion list so that completions you've chosen before are ranked higher, which ought to help a bit. We can also do some analysis -- if the argument is a whole sentence with "it" in the middle, the user is less likely to want pronoun interpolation than if the argument is just a single word "it".
I’m undecided
4 people think
this is one of the best points
-
Inappropriate?I think the solution to figuring out the right "this" must be found using a different approach. IMHO, adding escapes would make it unnatural.
I’m undecided
1 person thinks
this is one of the best points
-
Inappropriate?Agreed that escape sequence would be unnatural, but what other ways be used to decide which "right" should be used? I think making it context sensitive would be hard..
I’m undecided
-
Inappropriate?Yeah, I agree. I mentioned it as more of a stopgap for while the context sensitivity is refined. I suppose it is also made redundant by the menu presented with available options.
I’m undecided
-
Inappropriate?I'm opposed to adding an escape mechanism. I don't want this interface to turn into writing regexps. Ubiquity produces parsings both with and without pronoun interpolation and presents both in the suggestion list, so you can always down-arrow-key to the one you want.
However, anecdotal evidence suggestions that people are annoyed by pronoun interpolation happening when they don't want it. A case can certainly be made that the relative position of the variant parsings in the suggestion list should be different, and that it should be sorted more intelligently. In 0.2 I'm going to be adding some memory to the suggestion list so that completions you've chosen before are ranked higher, which ought to help a bit. We can also do some analysis -- if the argument is a whole sentence with "it" in the middle, the user is less likely to want pronoun interpolation than if the argument is just a single word "it".
I’m undecided
4 people think
this is one of the best points
-
Inappropriate?How about an escape but instead of using them to escape text, use them to escape those reserved words, sumthing like $this (on a php inspiration). where '$' will try escape something only if the following word is a right next to it without any spaces, tabs, etc. That way writting for instance, 'hey man when are you gonna pay me back my $ it sucks to have to remind you about it every day!', wouldn't trigger the escape.
I’m unsure
-
Inappropriate?Escaping is not going to work if the goal is to have a natural language for interaction, however finding a way to effectively escape "this" and "it". Two quick possible solutions come to mind.
The first is using how humans and computers differ in "reading" a sentence. for instance. having a sentence that read :
email esc this is really a good idea
will email "this is a really good idea" using the email verb.
The command system will read any word after the "escape words" as normal and not execute. Humans can still use normal language.
A second option is to use duplication in verbs to archive the same result.
twitter I love to twitter twitter, follow me at tinyurl http://twitter.com/unixel
This will execute the twitter verb and detect since a verb was given twice to use it as a normal word instead. In this example I'm also showing that two verbs can be used in one command.
comments etc welcome :)
I’m undecided
-
Inappropriate?I agree with Jono. Adding memory to remember the options we choose is the best way. But the memory should remember that if we chose that option while starting with a command as twitter, we might not want to chose it while starting with a command as map.
I’m confident
-
Inappropriate?Agreed with Jono. Escapes are un-natural to folks not experienced with programming. Instead, how about some combination of:
- An intelligent parser that detects contextually whether keywords make sense and re-orders autocomplete suggestions as such
- Primitive syntax highlighting to make it obvious to users how Ubiquity plans to interpret their commands
I'm all for some amount of learning, but keep in mind the danger of re-arranging menu items, as this has the potential to break user expectations.
Looking forward to hearing more about the new parser!
I’m excited
2 people think
this is one of the best points
EMPLOYEE
EMPLOYEE
