Comments on: Solving the “It” Problem http://www.azarask.in/blog/post/solving-the-it-problem/ -- aza | ɐzɐ -- Tue, 07 Feb 2012 20:21:16 +0000 hourly 1 http://wordpress.org/?v=3.1 By: top wind energy companies http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-15906 top wind energy companies Thu, 22 Dec 2011 02:45:36 +0000 http://www.azarask.in/blog/?p=354#comment-15906 Hi, great website, I m from Australia, so our growing times conditions are obviously different. Although this summer has been a fantastic growing year, our main problem is white fly Trialeurodes vaporariorum which eat all the leaves and damage the fruit. I don t use any pesticides and I ve found tha Hi, great website, I m from Australia, so our growing times conditions are obviously different. Although this summer has been a fantastic growing year, our main problem is white fly Trialeurodes vaporariorum which eat all the leaves and damage the fruit. I don t use any pesticides and I ve found tha

]]> By: Teri Kriebel http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-15232 Teri Kriebel Tue, 18 Oct 2011 23:18:04 +0000 http://www.azarask.in/blog/?p=354#comment-15232 Foremost, let me commend your lucidness on this subject. I am not a trained on this topic, but after analyzing your article, my expertise has bettered well. Please allow me to snatch up your rss feed to stay in touch with any forthcoming updates. Complete business and will fall out it on to admirers and my web site followers. Foremost, let me commend your lucidness on this subject. I am not a trained on this topic, but after analyzing your article, my expertise has bettered well. Please allow me to snatch up your rss feed to stay in touch with any forthcoming updates. Complete business and will fall out it on to admirers and my web site followers.

]]> By: Drew F http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3953 Drew F Mon, 16 Feb 2009 01:55:53 +0000 http://www.azarask.in/blog/?p=354#comment-3953 I don't really have anything new to offer (although I am trying to think of something). I have opinions about the already mentioned concepts. I am against the quotation system. I agree with Aza it doesn't feel natural. I think a main point of the natural language command architecture is to impose far less semantics. Having specific key words has both a positive and negative effects. The positive being that this seems like a more frequently used word than image or url so the probability of errors occurring are less likely. But by making more keywords if the problems do occur now conflicts arise from each of those keywords. I like Gerv's idea of ths and hm but I am more favored to thiss and himm. I have gotten used to this on the iPhone, and although not very discoverable, it is very memorable (as I use it for getting we'll instead of well). This seems like a solution for a more technically savvy user though as I also use it in things like textExpander. Although I feel that this should be the demographic ubiquity targets, if these features will eventually be added to the awesome bar then I feel that Aza's recommendation fits a more general audience. I don’t really have anything new to offer (although I am trying to think of something). I have opinions about the already mentioned concepts.
I am against the quotation system. I agree with Aza it doesn’t feel natural. I think a main point of the natural language command architecture is to impose far less semantics.

Having specific key words has both a positive and negative effects. The positive being that this seems like a more frequently used word than image or url so the probability of errors occurring are less likely. But by making more keywords if the problems do occur now conflicts arise from each of those keywords.

I like Gerv’s idea of ths and hm but I am more favored to thiss and himm. I have gotten used to this on the iPhone, and although not very discoverable, it is very memorable (as I use it for getting we’ll instead of well). This seems like a solution for a more technically savvy user though as I also use it in things like textExpander. Although I feel that this should be the demographic ubiquity targets, if these features will eventually be added to the awesome bar then I feel that Aza’s recommendation fits a more general audience.

]]> By: Gerv http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3940 Gerv Fri, 13 Feb 2009 17:42:31 +0000 http://www.azarask.in/blog/?p=354#comment-3940 Here's an idea: embrace the txt speak. It's like the "thisselection" idea but much less clunky. Make it so the vowelless form of the word triggers the substitution. So "ths" is this, substituted, "t" is "it", "hm" is him and so on. I think people would get the hang of this fairly quickly, and the rule for converting a pronoun to the substitutable form is simple. Here’s an idea: embrace the txt speak. It’s like the “thisselection” idea but much less clunky. Make it so the vowelless form of the word triggers the substitution. So “ths” is this, substituted, “t” is “it”, “hm” is him and so on. I think people would get the hang of this fairly quickly, and the rule for converting a pronoun to the substitutable form is simple.

]]> By: Kevin Cannon http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3938 Kevin Cannon Fri, 13 Feb 2009 10:40:03 +0000 http://www.azarask.in/blog/?p=354#comment-3938 Why not simply use quotation marks if there is ambiguity. That's a fairly common method of solving this problem. So, highlight Ubuiquities keywords in a different way to show they're 'special' - or do best guesses if possible, but ultimately let the user over ride it themselves. It's something that is easily learned. email "I think this website alot" to john That's quite a simple solution. Also, natural language interpretation is always going to be difficult, so maybe you need to set a grammar for Ubiquity, that keywords aren't allowed in the middle of random strings. You can add rules to the language to be used. If someone tries one form and it doesn't work, then they're smart enough to rephrase it. Why not simply use quotation marks if there is ambiguity. That’s a fairly common method of solving this problem. So, highlight Ubuiquities keywords in a different way to show they’re ‘special’ – or do best guesses if possible, but ultimately let the user over ride it themselves. It’s something that is easily learned.

email “I think this website alot” to john

That’s quite a simple solution.
Also, natural language interpretation is always going to be difficult, so maybe you need to set a grammar for Ubiquity, that keywords aren’t allowed in the middle of random strings. You can add rules to the language to be used. If someone tries one form and it doesn’t work, then they’re smart enough to rephrase it.

]]> By: Sam Hasler http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3936 Sam Hasler Thu, 12 Feb 2009 15:09:09 +0000 http://www.azarask.in/blog/?p=354#comment-3936 Looking at this mockup: http://www.flickr.com/photos/azaraskin/3272673947/ that makes the modifiers discoverable, but what about having to press the right arrow key to see the suggestions, that's not discoverable. Why not show an image of the right arrow key above the first modifier, then the more the user uses the right arrow key the fainter it gets until it doesn't appear at all. Could the right arrow key be pressed again to select the "from" modifier instead of "to", swapping them over? What happens if there are three or more modifiers, how do you know which will be brought across next? what if you select past the modifier you want, can you select the previous one? I'm assuming the left-arrow key would just move the cursor, maybe ctrl+z, or would they cycle so you have to go full circle. How about if the cursor is at the far right but not after whitespace pressing the right-arrow selects the first modifier that the preceeding word fragment matches the start of. So if you your example the user typed "f" and hit the right arrow it would bring from across. As the user is type if the start of a modifier matches the word fragment before the cursor that word fragment could be highlighted in bold so the user knows which modifier pressing the right-arrow will select. Looking at this mockup: http://www.flickr.com/photos/azaraskin/3272673947/

that makes the modifiers discoverable, but what about having to press the right arrow key to see the suggestions, that’s not discoverable. Why not show an image of the right arrow key above the first modifier, then the more the user uses the right arrow key the fainter it gets until it doesn’t appear at all.

Could the right arrow key be pressed again to select the “from” modifier instead of “to”, swapping them over? What happens if there are three or more modifiers, how do you know which will be brought across next? what if you select past the modifier you want, can you select the previous one? I’m assuming the left-arrow key would just move the cursor, maybe ctrl+z, or would they cycle so you have to go full circle.

How about if the cursor is at the far right but not after whitespace pressing the right-arrow selects the first modifier that the preceeding word fragment matches the start of. So if you your example the user typed “f” and hit the right arrow it would bring from across. As the user is type if the start of a modifier matches the word fragment before the cursor that word fragment could be highlighted in bold so the user knows which modifier pressing the right-arrow will select.

]]> By: Sam Hasler http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3935 Sam Hasler Thu, 12 Feb 2009 14:51:29 +0000 http://www.azarask.in/blog/?p=354#comment-3935 when it's possible to press a key to activate some functionallity the interface should show an image of the key. The more the user uses the key the fainter the image gets until it doesn't appear at all. when it’s possible to press a key to activate some functionallity the interface should show an image of the key. The more the user uses the key the fainter the image gets until it doesn’t appear at all.

]]> By: David http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3930 David Thu, 12 Feb 2009 00:32:37 +0000 http://www.azarask.in/blog/?p=354#comment-3930 Whatever you do, don't make people take their hands off of home row to make Ubiquity selections. That defeats the whole purpose. (So, obviously, clicking or up-arrow-ing the 'this' wouldn't cut it. Clicking should be an option, of course, but the keyboard equivalent should leave your hands be.) Whatever you do, don’t make people take their hands off of home row to make Ubiquity selections. That defeats the whole purpose. (So, obviously, clicking or up-arrow-ing the ‘this’ wouldn’t cut it. Clicking should be an option, of course, but the keyboard equivalent should leave your hands be.)

]]> By: Dan Cardin http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3929 Dan Cardin Thu, 12 Feb 2009 00:23:17 +0000 http://www.azarask.in/blog/?p=354#comment-3929 I agree with Robby. having more specific nouns makes mroe sense. As i understood it, Ubiquity was to feel natural and flowing. Taking the time to take your fingers away from the typing position isnt very natural, nor would it save time. While having to type the whole thing over again might be slightly annoying or slower i think it would flow well and would give many more meanings to each general keyword. As said above this could relate to url, selection, image, etc I agree with Robby. having more specific nouns makes mroe sense. As i understood it, Ubiquity was to feel natural and flowing. Taking the time to take your fingers away from the typing position isnt very natural, nor would it save time. While having to type the whole thing over again might be slightly annoying or slower i think it would flow well and would give many more meanings to each general keyword.

As said above this could relate to url, selection, image, etc

]]> By: alex.r. http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3925 alex.r. Wed, 11 Feb 2009 20:29:15 +0000 http://www.azarask.in/blog/?p=354#comment-3925 A suggestion: You let the user chose as they type but the default changes as you collect the responses. It could be done based on the probability of choice given context p(c|magic word, preceding words). An HMM could be used to estimate that. Obviously this would only help when users repeat the same actions. I don't know if it's generally the case. A suggestion:

You let the user chose as they type but the default changes as you collect the responses.

It could be done based on the probability of choice given context p(c|magic word, preceding words).

An HMM could be used to estimate that.

Obviously this would only help when users repeat the same actions. I don’t know if it’s generally the case.

]]>