<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_10_14_138207</id>
	<title>10/GUI &mdash; an Interface For Multi-Touch Input</title>
	<author>Soulskill</author>
	<datestamp>1255528320000</datestamp>
	<htmltext>Naznarreb writes <i>"<a href="http://rclayton.net/">R. Clayton Miller</a> has <a href="http://10gui.com/video/">an extremely impressive GUI concept he's calling 10/GUI</a> (video; <a href="http://www.gizmag.com/10gui-multi-touch-interface/13104/">written description here</a>). Essentially, it combines the high-bandwidth input possibilities of multi-touch interfaces with the ease and immediacy of a mouse. The video is quite interesting, and, for me at least, pretty jaw dropping. This is a dramatic re-imagining of the current mouse/screen schema, one that I think has significant potential."</i></htmltext>
<tokenext>Naznarreb writes " R. Clayton Miller has an extremely impressive GUI concept he 's calling 10/GUI ( video ; written description here ) .
Essentially , it combines the high-bandwidth input possibilities of multi-touch interfaces with the ease and immediacy of a mouse .
The video is quite interesting , and , for me at least , pretty jaw dropping .
This is a dramatic re-imagining of the current mouse/screen schema , one that I think has significant potential .
"</tokentext>
<sentencetext>Naznarreb writes "R. Clayton Miller has an extremely impressive GUI concept he's calling 10/GUI (video; written description here).
Essentially, it combines the high-bandwidth input possibilities of multi-touch interfaces with the ease and immediacy of a mouse.
The video is quite interesting, and, for me at least, pretty jaw dropping.
This is a dramatic re-imagining of the current mouse/screen schema, one that I think has significant potential.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29751285</id>
	<title>Nix the window manager and use one hand.</title>
	<author>Stebalien</author>
	<datestamp>1255522380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>1. I hate the window manager; it is an interesting idea but a horrible implementation.<br>2. Two hands is a problem. Think Twister (the game).</p><p>In my opinion, it would be better to keep a normal window manager and have one touch pad on the right (or left) for one hand.</p></htmltext>
<tokenext>1 .
I hate the window manager ; it is an interesting idea but a horrible implementation.2 .
Two hands is a problem .
Think Twister ( the game ) .In my opinion , it would be better to keep a normal window manager and have one touch pad on the right ( or left ) for one hand .</tokentext>
<sentencetext>1.
I hate the window manager; it is an interesting idea but a horrible implementation.2.
Two hands is a problem.
Think Twister (the game).In my opinion, it would be better to keep a normal window manager and have one touch pad on the right (or left) for one hand.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744659</id>
	<title>Not quite....</title>
	<author>neuromountain</author>
	<datestamp>1255534860000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>little behind these guys:

<a href="http://www.perceptivepixel.com/" title="perceptivepixel.com" rel="nofollow">http://www.perceptivepixel.com/</a> [perceptivepixel.com]

Doncha think?</htmltext>
<tokenext>little behind these guys : http : //www.perceptivepixel.com/ [ perceptivepixel.com ] Doncha think ?</tokentext>
<sentencetext>little behind these guys:

http://www.perceptivepixel.com/ [perceptivepixel.com]

Doncha think?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745223</id>
	<title>A few issues with an otherwise great idea.</title>
	<author>Anonymous</author>
	<datestamp>1255537140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>While the demo was very cool and full of eye-candy-tastic animations, there is one thing that stands in the way of this idea. Tactile response. You have this mat in front of you that can track all 10 fingers when you place them on the surface, and then to click with a finger, you press it into the mat.</p><p>Well first off, you're going to need to feel that as a click, if this is to be the Next Big Thing. The other issue is how hard do you have to press to get it to register a click? If you think about your mouse, the "click" motion is very very tiny and light and yet there is a definite clicking sound and feel. On a trackpad, you're moving your finger around and then (assuming you don't use the button) you have to lift your finger, tap it, and lift it again to register a click. That won't do either. Its going to be a challenge to "tune" this to not be clicking all the time or take too much pressure before it "clicks." If its too sensitive, you'll have people unconsciously straining their arms slightly to reduce the weight of their hands on the mat.</p><p>Another thing thing I'm concerned about is how a mouse feels in your hand. I rather like the feel of griping a mouse in my hand, and I'm not sure I can get the same feeling from resting my hands on the desk all the time.</p><p>We shall see. I doubt Cindy from accounting will be very gung-ho about this, unfortunately.</p></htmltext>
<tokenext>While the demo was very cool and full of eye-candy-tastic animations , there is one thing that stands in the way of this idea .
Tactile response .
You have this mat in front of you that can track all 10 fingers when you place them on the surface , and then to click with a finger , you press it into the mat.Well first off , you 're going to need to feel that as a click , if this is to be the Next Big Thing .
The other issue is how hard do you have to press to get it to register a click ?
If you think about your mouse , the " click " motion is very very tiny and light and yet there is a definite clicking sound and feel .
On a trackpad , you 're moving your finger around and then ( assuming you do n't use the button ) you have to lift your finger , tap it , and lift it again to register a click .
That wo n't do either .
Its going to be a challenge to " tune " this to not be clicking all the time or take too much pressure before it " clicks .
" If its too sensitive , you 'll have people unconsciously straining their arms slightly to reduce the weight of their hands on the mat.Another thing thing I 'm concerned about is how a mouse feels in your hand .
I rather like the feel of griping a mouse in my hand , and I 'm not sure I can get the same feeling from resting my hands on the desk all the time.We shall see .
I doubt Cindy from accounting will be very gung-ho about this , unfortunately .</tokentext>
<sentencetext>While the demo was very cool and full of eye-candy-tastic animations, there is one thing that stands in the way of this idea.
Tactile response.
You have this mat in front of you that can track all 10 fingers when you place them on the surface, and then to click with a finger, you press it into the mat.Well first off, you're going to need to feel that as a click, if this is to be the Next Big Thing.
The other issue is how hard do you have to press to get it to register a click?
If you think about your mouse, the "click" motion is very very tiny and light and yet there is a definite clicking sound and feel.
On a trackpad, you're moving your finger around and then (assuming you don't use the button) you have to lift your finger, tap it, and lift it again to register a click.
That won't do either.
Its going to be a challenge to "tune" this to not be clicking all the time or take too much pressure before it "clicks.
" If its too sensitive, you'll have people unconsciously straining their arms slightly to reduce the weight of their hands on the mat.Another thing thing I'm concerned about is how a mouse feels in your hand.
I rather like the feel of griping a mouse in my hand, and I'm not sure I can get the same feeling from resting my hands on the desk all the time.We shall see.
I doubt Cindy from accounting will be very gung-ho about this, unfortunately.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744281</id>
	<title>Multitouch?</title>
	<author>Anonymous</author>
	<datestamp>1255533360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I've GOT multitouch.</p><p>It's called a keyboard in conjunction with a tiling window manager.</p></htmltext>
<tokenext>I 've GOT multitouch.It 's called a keyboard in conjunction with a tiling window manager .</tokentext>
<sentencetext>I've GOT multitouch.It's called a keyboard in conjunction with a tiling window manager.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747383</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>KnownIssues</author>
	<datestamp>1255546560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Other problem is that now your both hands lay on the wide touch area and you dont have a keyboard.</p></div><p>I can imagine three ways to address this. First way: Touch areas on each side of the keyboard. Second way: Touch area below the keyboard. Third way: Touch area both on each side and below the keyboard.</p><p>I can see this being as natural as using a mouse. Regarding precision, I think this could be at least adequately addressed by having the application adjust it's "precision scale" for the activity involved.</p></div>
	</htmltext>
<tokenext>Other problem is that now your both hands lay on the wide touch area and you dont have a keyboard.I can imagine three ways to address this .
First way : Touch areas on each side of the keyboard .
Second way : Touch area below the keyboard .
Third way : Touch area both on each side and below the keyboard.I can see this being as natural as using a mouse .
Regarding precision , I think this could be at least adequately addressed by having the application adjust it 's " precision scale " for the activity involved .</tokentext>
<sentencetext>Other problem is that now your both hands lay on the wide touch area and you dont have a keyboard.I can imagine three ways to address this.
First way: Touch areas on each side of the keyboard.
Second way: Touch area below the keyboard.
Third way: Touch area both on each side and below the keyboard.I can see this being as natural as using a mouse.
Regarding precision, I think this could be at least adequately addressed by having the application adjust it's "precision scale" for the activity involved.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744459</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>thah0ppa</author>
	<datestamp>1255534020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>With respect, I disagree.

Will this replace current software interfaces, no.

It will require the sw that is setup for this type of interface, but all games could be made to support this.

These would shine, as you can manipulate many variable interfaces at once.

Existing sw and games could take gaming to new places.</htmltext>
<tokenext>With respect , I disagree .
Will this replace current software interfaces , no .
It will require the sw that is setup for this type of interface , but all games could be made to support this .
These would shine , as you can manipulate many variable interfaces at once .
Existing sw and games could take gaming to new places .</tokentext>
<sentencetext>With respect, I disagree.
Will this replace current software interfaces, no.
It will require the sw that is setup for this type of interface, but all games could be made to support this.
These would shine, as you can manipulate many variable interfaces at once.
Existing sw and games could take gaming to new places.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744905</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>muffen</author>
	<datestamp>1255535820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>However, I would love to have this kind of system in my living room (either just for the tv, or the computer thats connected to tv screen).</p></div></blockquote><p>
<a href="http://www.logitech.com/index.cfm/keyboards/keyboard/devices/3848&amp;cl=us,en" title="logitech.com">You can try something like this.</a> [logitech.com]
<br> <br>
I use that with my Media PC and it works well.</p></div>
	</htmltext>
<tokenext>However , I would love to have this kind of system in my living room ( either just for the tv , or the computer thats connected to tv screen ) .
You can try something like this .
[ logitech.com ] I use that with my Media PC and it works well .</tokentext>
<sentencetext>However, I would love to have this kind of system in my living room (either just for the tv, or the computer thats connected to tv screen).
You can try something like this.
[logitech.com]
 
I use that with my Media PC and it works well.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29750613</id>
	<title>Re:A few problems and some solutions</title>
	<author>Frogg</author>
	<datestamp>1255518300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>2) Try pinching with four fingers.  It's not very comfortable, at all (the only practical way is to lift up the pinky).</p></div><p>...it's just as easy/comfortable to lift up the first finger instead of the pinky (possibly moreso) - my macbook touchpad has two-finger scrolling (it's an older model, and doesn't have the same multi-touch support as their newer models), and i generally use the second+third finger to scroll (and rest my pinky down when reading/not scrolling) - i find it more comfortable than using the first+second finger</p><p>that said, i imagine a four finger pinch (using thumb movement to pinch) is still not particularly accurate - but the proof of the pudding is in the eating as they say (ie. i would have to try it out to know for sure)</p></div>
	</htmltext>
<tokenext>2 ) Try pinching with four fingers .
It 's not very comfortable , at all ( the only practical way is to lift up the pinky ) ....it 's just as easy/comfortable to lift up the first finger instead of the pinky ( possibly moreso ) - my macbook touchpad has two-finger scrolling ( it 's an older model , and does n't have the same multi-touch support as their newer models ) , and i generally use the second + third finger to scroll ( and rest my pinky down when reading/not scrolling ) - i find it more comfortable than using the first + second fingerthat said , i imagine a four finger pinch ( using thumb movement to pinch ) is still not particularly accurate - but the proof of the pudding is in the eating as they say ( ie .
i would have to try it out to know for sure )</tokentext>
<sentencetext>2) Try pinching with four fingers.
It's not very comfortable, at all (the only practical way is to lift up the pinky)....it's just as easy/comfortable to lift up the first finger instead of the pinky (possibly moreso) - my macbook touchpad has two-finger scrolling (it's an older model, and doesn't have the same multi-touch support as their newer models), and i generally use the second+third finger to scroll (and rest my pinky down when reading/not scrolling) - i find it more comfortable than using the first+second fingerthat said, i imagine a four finger pinch (using thumb movement to pinch) is still not particularly accurate - but the proof of the pudding is in the eating as they say (ie.
i would have to try it out to know for sure)
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744967</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748179</id>
	<title>Accessibility</title>
	<author>jemenake</author>
	<datestamp>1255549920000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>From watching the video, it looks like they presuppose quite a high degree of dexterity on the part of the user. To resize an app window in the video, they touched three fingers to the pad, held <i>two</i> of them still while pinch-zooming with the third. Now, you probably don't have to hold two of the fingers still relative to each other, but this still sets the bar quite high in its requirements for independent control of your digits.
<br> <br>
This would exclude a lot of users, and not just those who are missing a few fingers. About 10 years ago, I helped set up some web-browsing PC's in a community-college library. One of the things I hadn't anticipated was that some of the older users were lacking in coordination to the extent that it made it difficult for them to use the PC effectively. Even the task of trying to double-click fast enough to get it to <i>register</i> as a double-click would cause these users to twitch some of their arm muscles, causing the mouse to scoot a couple of inches in the middle of the double-click. They'd try several times to get it right, but the mouse always ended up moving off of the targeted icon before the double-click was complete.
<br> <br>
What we eventually had to do was to provide trackballs, so that the user could move the mouse pointer to where they wanted it and then, taking their hand off of the <i>ball</i> part of the trackball, double-click the buttons. So, <i>that</i> is the level of dexterity that some users are at. So, this three-finger-pinch-zooming idea... I could see this being extremely frustrating for them.</htmltext>
<tokenext>From watching the video , it looks like they presuppose quite a high degree of dexterity on the part of the user .
To resize an app window in the video , they touched three fingers to the pad , held two of them still while pinch-zooming with the third .
Now , you probably do n't have to hold two of the fingers still relative to each other , but this still sets the bar quite high in its requirements for independent control of your digits .
This would exclude a lot of users , and not just those who are missing a few fingers .
About 10 years ago , I helped set up some web-browsing PC 's in a community-college library .
One of the things I had n't anticipated was that some of the older users were lacking in coordination to the extent that it made it difficult for them to use the PC effectively .
Even the task of trying to double-click fast enough to get it to register as a double-click would cause these users to twitch some of their arm muscles , causing the mouse to scoot a couple of inches in the middle of the double-click .
They 'd try several times to get it right , but the mouse always ended up moving off of the targeted icon before the double-click was complete .
What we eventually had to do was to provide trackballs , so that the user could move the mouse pointer to where they wanted it and then , taking their hand off of the ball part of the trackball , double-click the buttons .
So , that is the level of dexterity that some users are at .
So , this three-finger-pinch-zooming idea... I could see this being extremely frustrating for them .</tokentext>
<sentencetext>From watching the video, it looks like they presuppose quite a high degree of dexterity on the part of the user.
To resize an app window in the video, they touched three fingers to the pad, held two of them still while pinch-zooming with the third.
Now, you probably don't have to hold two of the fingers still relative to each other, but this still sets the bar quite high in its requirements for independent control of your digits.
This would exclude a lot of users, and not just those who are missing a few fingers.
About 10 years ago, I helped set up some web-browsing PC's in a community-college library.
One of the things I hadn't anticipated was that some of the older users were lacking in coordination to the extent that it made it difficult for them to use the PC effectively.
Even the task of trying to double-click fast enough to get it to register as a double-click would cause these users to twitch some of their arm muscles, causing the mouse to scoot a couple of inches in the middle of the double-click.
They'd try several times to get it right, but the mouse always ended up moving off of the targeted icon before the double-click was complete.
What we eventually had to do was to provide trackballs, so that the user could move the mouse pointer to where they wanted it and then, taking their hand off of the ball part of the trackball, double-click the buttons.
So, that is the level of dexterity that some users are at.
So, this three-finger-pinch-zooming idea... I could see this being extremely frustrating for them.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29749673</id>
	<title>Re:All 10 fingers</title>
	<author>kitsch</author>
	<datestamp>1255513260000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p>It's not the number of fingers that makes playing piano hard.  It's the combinations.   The chords are the hard part.  Also the independent use of each finger.  An interface like this and most other multi-touch interfaces use simple clenching or releasing motions.  These are movements that anyone with fully functional hands will have already mastered.  They are baby movements.</p><p>As for FPS games I don't see the issues I'd say my finger tip is roughly the size of a baddies head.  Panning would be a breeze.  Group selection in RTS games would be much nicer.  If you combined this with a pen for drawing then I could easily see a mouse becoming obsolete.</p><p>As for palm interference I doubt that is a hard thing to treat as noise in the input.</p><p>The biggest problem is replacing a keyboard.  That wont happen any time soon. Though for many tasks (like Gimp/Photoshop, or 3D animation) you could replace the small key combos with larger key areas. Replace 3D mice with circular panning areas and such. I would prefer that the touch screen to display an abstraction of the interface  -- window outlines, key areas.  Nothing too detailed and distracting -- maybe an e-ink level display.</p></htmltext>
<tokenext>It 's not the number of fingers that makes playing piano hard .
It 's the combinations .
The chords are the hard part .
Also the independent use of each finger .
An interface like this and most other multi-touch interfaces use simple clenching or releasing motions .
These are movements that anyone with fully functional hands will have already mastered .
They are baby movements.As for FPS games I do n't see the issues I 'd say my finger tip is roughly the size of a baddies head .
Panning would be a breeze .
Group selection in RTS games would be much nicer .
If you combined this with a pen for drawing then I could easily see a mouse becoming obsolete.As for palm interference I doubt that is a hard thing to treat as noise in the input.The biggest problem is replacing a keyboard .
That wont happen any time soon .
Though for many tasks ( like Gimp/Photoshop , or 3D animation ) you could replace the small key combos with larger key areas .
Replace 3D mice with circular panning areas and such .
I would prefer that the touch screen to display an abstraction of the interface -- window outlines , key areas .
Nothing too detailed and distracting -- maybe an e-ink level display .</tokentext>
<sentencetext>It's not the number of fingers that makes playing piano hard.
It's the combinations.
The chords are the hard part.
Also the independent use of each finger.
An interface like this and most other multi-touch interfaces use simple clenching or releasing motions.
These are movements that anyone with fully functional hands will have already mastered.
They are baby movements.As for FPS games I don't see the issues I'd say my finger tip is roughly the size of a baddies head.
Panning would be a breeze.
Group selection in RTS games would be much nicer.
If you combined this with a pen for drawing then I could easily see a mouse becoming obsolete.As for palm interference I doubt that is a hard thing to treat as noise in the input.The biggest problem is replacing a keyboard.
That wont happen any time soon.
Though for many tasks (like Gimp/Photoshop, or 3D animation) you could replace the small key combos with larger key areas.
Replace 3D mice with circular panning areas and such.
I would prefer that the touch screen to display an abstraction of the interface  -- window outlines, key areas.
Nothing too detailed and distracting -- maybe an e-ink level display.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745705</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744511</id>
	<title>3 fingers to move an application?  Read between th</title>
	<author>mastahYee</author>
	<datestamp>1255534260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>IMHO, an interface's success is directly proportionate to the amount of effort required to use it.</htmltext>
<tokenext>IMHO , an interface 's success is directly proportionate to the amount of effort required to use it .</tokentext>
<sentencetext>IMHO, an interface's success is directly proportionate to the amount of effort required to use it.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29767271</id>
	<title>Re:going in circles</title>
	<author>me-g33k</author>
	<datestamp>1255697880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I agree with you on the perspective of "before its time". I also have a couple of Touchstreams and I use them extensively. I only use the tactile units when I game as the driver response time on the touchstreams are not optimal for gaming.</p></htmltext>
<tokenext>I agree with you on the perspective of " before its time " .
I also have a couple of Touchstreams and I use them extensively .
I only use the tactile units when I game as the driver response time on the touchstreams are not optimal for gaming .</tokentext>
<sentencetext>I agree with you on the perspective of "before its time".
I also have a couple of Touchstreams and I use them extensively.
I only use the tactile units when I game as the driver response time on the touchstreams are not optimal for gaming.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745723</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747927</id>
	<title>Re:This problem has been solved on my desktop</title>
	<author>corychristison</author>
	<datestamp>1255548840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Or I use virtual desktops basically for the same thing</p></div><p>I think you hit my soft spot right there.</p><p>I've been using Linux for a few years (since 2002-ish) and I really like XFCE. It's virtual desktop support is great. My favorite part is the mouse resistance on the edge of the screen to switch to the next screen.</p><p>All you need to do is drag the mouse to the edge of the screen, and give it a nice push. Depending on how you have your virtual desktops arranged, I have two rows of 4, so a total of 8 virtual desktops, so they are arranged in a grid like so:<br>[1][2][3][4]<br>[5][6][7][8]</p><p>1: Work Stuff (usually a web browser, file browser and text editor)<br>2: Usually a terminal and sometimes graphics stuff.<br>3&amp;4: "Extra Work Stuff", VirtualBox and a terminal usually sit somewhere on these two.<br>5: Music and Media<br>6: "General Stuff" (on #6 right now) Usually a web browser(firefox), aMSN and E-mail (Thunderbird)<br>7&amp;8: "Extra General Stuff" When I'm compiling things they usually sit on one of these two. Sometimes I use 7 to find a document quick when I need to show it to someone (easier to switch to 7 than to minimize stuff and open a folder)</p><p>And to top it off, here's a <a href="http://img62.imageshack.us/img62/6271/screenshotnd.png" title="imageshack.us">screenshot</a> [imageshack.us]!</p></div>
	</htmltext>
<tokenext>Or I use virtual desktops basically for the same thingI think you hit my soft spot right there.I 've been using Linux for a few years ( since 2002-ish ) and I really like XFCE .
It 's virtual desktop support is great .
My favorite part is the mouse resistance on the edge of the screen to switch to the next screen.All you need to do is drag the mouse to the edge of the screen , and give it a nice push .
Depending on how you have your virtual desktops arranged , I have two rows of 4 , so a total of 8 virtual desktops , so they are arranged in a grid like so : [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ 7 ] [ 8 ] 1 : Work Stuff ( usually a web browser , file browser and text editor ) 2 : Usually a terminal and sometimes graphics stuff.3&amp;4 : " Extra Work Stuff " , VirtualBox and a terminal usually sit somewhere on these two.5 : Music and Media6 : " General Stuff " ( on # 6 right now ) Usually a web browser ( firefox ) , aMSN and E-mail ( Thunderbird ) 7&amp;8 : " Extra General Stuff " When I 'm compiling things they usually sit on one of these two .
Sometimes I use 7 to find a document quick when I need to show it to someone ( easier to switch to 7 than to minimize stuff and open a folder ) And to top it off , here 's a screenshot [ imageshack.us ] !</tokentext>
<sentencetext>Or I use virtual desktops basically for the same thingI think you hit my soft spot right there.I've been using Linux for a few years (since 2002-ish) and I really like XFCE.
It's virtual desktop support is great.
My favorite part is the mouse resistance on the edge of the screen to switch to the next screen.All you need to do is drag the mouse to the edge of the screen, and give it a nice push.
Depending on how you have your virtual desktops arranged, I have two rows of 4, so a total of 8 virtual desktops, so they are arranged in a grid like so:[1][2][3][4][5][6][7][8]1: Work Stuff (usually a web browser, file browser and text editor)2: Usually a terminal and sometimes graphics stuff.3&amp;4: "Extra Work Stuff", VirtualBox and a terminal usually sit somewhere on these two.5: Music and Media6: "General Stuff" (on #6 right now) Usually a web browser(firefox), aMSN and E-mail (Thunderbird)7&amp;8: "Extra General Stuff" When I'm compiling things they usually sit on one of these two.
Sometimes I use 7 to find a document quick when I need to show it to someone (easier to switch to 7 than to minimize stuff and open a folder)And to top it off, here's a screenshot [imageshack.us]!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744643</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744953</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>elh\_inny</author>
	<datestamp>1255536000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>It would also be quite impossible to play FPS or other kinds of games with this type of setup.</p></div><p>I think Quake 3 engine has been open-sourced a while ago.</p><p>I wonder if it'd be possible to use that game (and maybe other games, apps) as a benchmark to test the efficiency of various input methods.</p><p>If you can win on Nightmare on q3dm17, it's good/quick enough for me at least.</p></div>
	</htmltext>
<tokenext>It would also be quite impossible to play FPS or other kinds of games with this type of setup.I think Quake 3 engine has been open-sourced a while ago.I wonder if it 'd be possible to use that game ( and maybe other games , apps ) as a benchmark to test the efficiency of various input methods.If you can win on Nightmare on q3dm17 , it 's good/quick enough for me at least .</tokentext>
<sentencetext>It would also be quite impossible to play FPS or other kinds of games with this type of setup.I think Quake 3 engine has been open-sourced a while ago.I wonder if it'd be possible to use that game (and maybe other games, apps) as a benchmark to test the efficiency of various input methods.If you can win on Nightmare on q3dm17, it's good/quick enough for me at least.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745025</id>
	<title>Linux?</title>
	<author>mcnazar</author>
	<datestamp>1255536300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Yes Yes! But does it run on Linux?</p></htmltext>
<tokenext>Yes Yes !
But does it run on Linux ?</tokentext>
<sentencetext>Yes Yes!
But does it run on Linux?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745511</id>
	<title>Re:going in circles</title>
	<author>Laxori666</author>
	<datestamp>1255538340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Not always true. If you see the beginning of the video, there's a case where you have to adjust 4 scrollbars at the same time. We certainly have the mental capacity to do that - it's just the mouse that prevents us from doing it quickly. I can see this technology being useful anytime you have to simultaneously adjust 2 or more values.</htmltext>
<tokenext>Not always true .
If you see the beginning of the video , there 's a case where you have to adjust 4 scrollbars at the same time .
We certainly have the mental capacity to do that - it 's just the mouse that prevents us from doing it quickly .
I can see this technology being useful anytime you have to simultaneously adjust 2 or more values .</tokentext>
<sentencetext>Not always true.
If you see the beginning of the video, there's a case where you have to adjust 4 scrollbars at the same time.
We certainly have the mental capacity to do that - it's just the mouse that prevents us from doing it quickly.
I can see this technology being useful anytime you have to simultaneously adjust 2 or more values.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744657</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29755213</id>
	<title>Re:some subtle hints in that presentation</title>
	<author>Anonymous</author>
	<datestamp>1255609500000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Was thinking the same thing.  Look at the current mac book pro - It's proportioned almost perfectly for a larger touchpad area that would allow them to implement this.</p></htmltext>
<tokenext>Was thinking the same thing .
Look at the current mac book pro - It 's proportioned almost perfectly for a larger touchpad area that would allow them to implement this .</tokentext>
<sentencetext>Was thinking the same thing.
Look at the current mac book pro - It's proportioned almost perfectly for a larger touchpad area that would allow them to implement this.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744325</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745197</id>
	<title>some problems...</title>
	<author>master\_p</author>
	<datestamp>1255537020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>1) tiring to move hands from/to keyboard/touch surface all the time.</p><p>2) the easy selection of another window from the task bar becomes a very time consuming operation of zooming out, select window, zoom in.</p><p>3) redundant visual effects like scrolling and zooming.</p><p>4) where is the equivalent of the task bar icon tray? where is the current language and time, for example?</p><p>5) since I can't stack one window below the other, how do I put a media player, chat program, web browser and text editor on the same screen?</p><p>6) how do I know the widget my fingers are on? given a menu bar, with 3 items next to each other (File, Edit, Help), how do I know which of my fingers is on File, on Edit and on Help?</p><p>7) what about information conveyed by mouse over? with ten cursors instead of one, the screen will literally burst with information at each movement of my hand.</p><p>8) how do I work with maximized windows?</p><p>I don't think this is ever going to go somewhere. There are lots of usability issues.</p></htmltext>
<tokenext>1 ) tiring to move hands from/to keyboard/touch surface all the time.2 ) the easy selection of another window from the task bar becomes a very time consuming operation of zooming out , select window , zoom in.3 ) redundant visual effects like scrolling and zooming.4 ) where is the equivalent of the task bar icon tray ?
where is the current language and time , for example ? 5 ) since I ca n't stack one window below the other , how do I put a media player , chat program , web browser and text editor on the same screen ? 6 ) how do I know the widget my fingers are on ?
given a menu bar , with 3 items next to each other ( File , Edit , Help ) , how do I know which of my fingers is on File , on Edit and on Help ? 7 ) what about information conveyed by mouse over ?
with ten cursors instead of one , the screen will literally burst with information at each movement of my hand.8 ) how do I work with maximized windows ? I do n't think this is ever going to go somewhere .
There are lots of usability issues .</tokentext>
<sentencetext>1) tiring to move hands from/to keyboard/touch surface all the time.2) the easy selection of another window from the task bar becomes a very time consuming operation of zooming out, select window, zoom in.3) redundant visual effects like scrolling and zooming.4) where is the equivalent of the task bar icon tray?
where is the current language and time, for example?5) since I can't stack one window below the other, how do I put a media player, chat program, web browser and text editor on the same screen?6) how do I know the widget my fingers are on?
given a menu bar, with 3 items next to each other (File, Edit, Help), how do I know which of my fingers is on File, on Edit and on Help?7) what about information conveyed by mouse over?
with ten cursors instead of one, the screen will literally burst with information at each movement of my hand.8) how do I work with maximized windows?I don't think this is ever going to go somewhere.
There are lots of usability issues.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747199</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>26199</author>
	<datestamp>1255545720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I can offer direct insight into your questions courtesy of years of experience using the Fingerworks TouchStream:</p><p>
<a href="http://www.fingerworks.com/ST\_product.html" title="fingerworks.com">http://www.fingerworks.com/ST\_product.html</a> [fingerworks.com] <br>
<a href="http://www.youtube.com/watch?v=FDW5zyjhCbc" title="youtube.com">http://www.youtube.com/watch?v=FDW5zyjhCbc</a> [youtube.com] </p><p>MultiTouch devices are very precise. In fact, moreso than a mouse for fine movements, because they take an average over the whole contact area so subpixel movements are possible.</p><p>You can have a keyboard. See the TouchStream. It works really well and is more efficient than a mouse+keyboard combo. Use of MultiTouch makes the keyboard itself vastly more efficient: gestures and chords are all available without leaving the keyboard.</p><p>I've played Doom 3 using the TouchStream. It's not as good as a keyboard+mouse combo but I'll bet it beats gamepad.</p></htmltext>
<tokenext>I can offer direct insight into your questions courtesy of years of experience using the Fingerworks TouchStream : http : //www.fingerworks.com/ST \ _product.html [ fingerworks.com ] http : //www.youtube.com/watch ? v = FDW5zyjhCbc [ youtube.com ] MultiTouch devices are very precise .
In fact , moreso than a mouse for fine movements , because they take an average over the whole contact area so subpixel movements are possible.You can have a keyboard .
See the TouchStream .
It works really well and is more efficient than a mouse + keyboard combo .
Use of MultiTouch makes the keyboard itself vastly more efficient : gestures and chords are all available without leaving the keyboard.I 've played Doom 3 using the TouchStream .
It 's not as good as a keyboard + mouse combo but I 'll bet it beats gamepad .</tokentext>
<sentencetext>I can offer direct insight into your questions courtesy of years of experience using the Fingerworks TouchStream:
http://www.fingerworks.com/ST\_product.html [fingerworks.com] 
http://www.youtube.com/watch?v=FDW5zyjhCbc [youtube.com] MultiTouch devices are very precise.
In fact, moreso than a mouse for fine movements, because they take an average over the whole contact area so subpixel movements are possible.You can have a keyboard.
See the TouchStream.
It works really well and is more efficient than a mouse+keyboard combo.
Use of MultiTouch makes the keyboard itself vastly more efficient: gestures and chords are all available without leaving the keyboard.I've played Doom 3 using the TouchStream.
It's not as good as a keyboard+mouse combo but I'll bet it beats gamepad.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744337</id>
	<title>Not optimizing what I spend most of my time doing</title>
	<author>faffod</author>
	<datestamp>1255533600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Right now this comes across as an interesting thought exercise. I think that FPS style games should be possible (where there's a will...) but I think that things like typing will be more less efficient than on a keyboard, which provides tactile feedback. And I spend more time typing than I do mousing and reorganizing windows. This isn't optimizing the 80\% case. Since all the tech is available, they should be able to provide a real demo as opposed to animation mockups; then we'll see how typing and other real world problems fit in. Until proven wrong about slowing down the things that I do on a PC, I agree that this isn't for a desktop PC. The other question is, where else could this be used?</htmltext>
<tokenext>Right now this comes across as an interesting thought exercise .
I think that FPS style games should be possible ( where there 's a will... ) but I think that things like typing will be more less efficient than on a keyboard , which provides tactile feedback .
And I spend more time typing than I do mousing and reorganizing windows .
This is n't optimizing the 80 \ % case .
Since all the tech is available , they should be able to provide a real demo as opposed to animation mockups ; then we 'll see how typing and other real world problems fit in .
Until proven wrong about slowing down the things that I do on a PC , I agree that this is n't for a desktop PC .
The other question is , where else could this be used ?</tokentext>
<sentencetext>Right now this comes across as an interesting thought exercise.
I think that FPS style games should be possible (where there's a will...) but I think that things like typing will be more less efficient than on a keyboard, which provides tactile feedback.
And I spend more time typing than I do mousing and reorganizing windows.
This isn't optimizing the 80\% case.
Since all the tech is available, they should be able to provide a real demo as opposed to animation mockups; then we'll see how typing and other real world problems fit in.
Until proven wrong about slowing down the things that I do on a PC, I agree that this isn't for a desktop PC.
The other question is, where else could this be used?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746655</id>
	<title>Re:Virtuoso Users only!</title>
	<author>zippthorne</author>
	<datestamp>1255543200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I would also enjoy an ePaper satellite for notes, documents, help files, quick-references, etc.</p></htmltext>
<tokenext>I would also enjoy an ePaper satellite for notes , documents , help files , quick-references , etc .</tokentext>
<sentencetext>I would also enjoy an ePaper satellite for notes, documents, help files, quick-references, etc.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744653</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748135</id>
	<title>But... my overlapping windows!</title>
	<author>Roogna</author>
	<datestamp>1255549740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Seriously... something like that would probably work fine for say, my grandmother.  Who tended to only have her e-mail app open, or her card game of the day, or whatever.<br>But god, I can't begin to imagine the suffering of trying to write code on an interface like that.  I'm all for multi-touch, but sheesh.  Why is it every 2-bit designer who comes along thinks that to progress UI's they have to toss out everything that's managed to stick over the past 30 years.</p><p>I have a lovely 30" screen... plus another smaller screen.  When I'm coding it's not uncommon to have the project open, multiple source and header files, plus other windows open for reference, testing, source control, server connections, and others.  This is hardly cluttered either, I -want- absolute control over where each of these windows is on the screen and what size they are.  I don't want some OS trying to organize them for me off the screen.  Because especially with client/server coding, when I say, run the app on one screen, I don't -want- it hiding all the windows that are tracking log files on the server too.  I'm watching those for immediate feedback.</p><p>So while I think multi-touch is great and certainly has a place on the desktop of the future, please won't someone come up with a way of using it effectively amongst the UI's we already have!</p></htmltext>
<tokenext>Seriously... something like that would probably work fine for say , my grandmother .
Who tended to only have her e-mail app open , or her card game of the day , or whatever.But god , I ca n't begin to imagine the suffering of trying to write code on an interface like that .
I 'm all for multi-touch , but sheesh .
Why is it every 2-bit designer who comes along thinks that to progress UI 's they have to toss out everything that 's managed to stick over the past 30 years.I have a lovely 30 " screen... plus another smaller screen .
When I 'm coding it 's not uncommon to have the project open , multiple source and header files , plus other windows open for reference , testing , source control , server connections , and others .
This is hardly cluttered either , I -want- absolute control over where each of these windows is on the screen and what size they are .
I do n't want some OS trying to organize them for me off the screen .
Because especially with client/server coding , when I say , run the app on one screen , I do n't -want- it hiding all the windows that are tracking log files on the server too .
I 'm watching those for immediate feedback.So while I think multi-touch is great and certainly has a place on the desktop of the future , please wo n't someone come up with a way of using it effectively amongst the UI 's we already have !</tokentext>
<sentencetext>Seriously... something like that would probably work fine for say, my grandmother.
Who tended to only have her e-mail app open, or her card game of the day, or whatever.But god, I can't begin to imagine the suffering of trying to write code on an interface like that.
I'm all for multi-touch, but sheesh.
Why is it every 2-bit designer who comes along thinks that to progress UI's they have to toss out everything that's managed to stick over the past 30 years.I have a lovely 30" screen... plus another smaller screen.
When I'm coding it's not uncommon to have the project open, multiple source and header files, plus other windows open for reference, testing, source control, server connections, and others.
This is hardly cluttered either, I -want- absolute control over where each of these windows is on the screen and what size they are.
I don't want some OS trying to organize them for me off the screen.
Because especially with client/server coding, when I say, run the app on one screen, I don't -want- it hiding all the windows that are tracking log files on the server too.
I'm watching those for immediate feedback.So while I think multi-touch is great and certainly has a place on the desktop of the future, please won't someone come up with a way of using it effectively amongst the UI's we already have!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748515</id>
	<title>Is 10/GUI a step BACKWARDS?</title>
	<author>uslurper</author>
	<datestamp>1255551300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Before GUI's there was the command line.<br>The command line is great in that you can initiate an unlimited variety of tasks. These tasks are powerful because the interface is based on your imagination.<br>For example: \rename *.csv *.txt<br>You cannot see the files in the directory you are in, but you know in your mind that you are selecting all files with the<nobr> <wbr></nobr>.csv extention in your current location, and no files in other places. You have instructed to change only the last 3 letters of these filename, no matter how long they are. You dont have this kind of single-command power with a GUI.<br>The downside of a command-line of course is that you have learn the commands before you can use them.<br>That leads us to the GUI. All of the controls of the objects are presented on the screen. The idea is that how to manipulate the objects is self-evident (somewhat). Users learn by interacting in real-time.</p><p>i've never liked gesture-style screen commands because they have all of the drawbacks of a command-line but very limited power. perhaps some general commands like on the ipod interface, but it will never be a replacement for menus or text commands.</p><p>Regarding the "problem" of organizing windows as shown in the video..I contend that that is not a real issue.  The only problem is the current window managers drop stuff 'wherever'. I work perfectly fine on a small monitor with all my apps maximized. My coworkers have twice the screen real-estate I do but still only use one app at a time becasue the foreground application is hogging  most of the space and the others are splattered around behind it.<br>At home I have a nicely organized side toolbar with all my frequently used stuff, and I have ZERO desktop icons.</p></htmltext>
<tokenext>Before GUI 's there was the command line.The command line is great in that you can initiate an unlimited variety of tasks .
These tasks are powerful because the interface is based on your imagination.For example : \ rename * .csv * .txtYou can not see the files in the directory you are in , but you know in your mind that you are selecting all files with the .csv extention in your current location , and no files in other places .
You have instructed to change only the last 3 letters of these filename , no matter how long they are .
You dont have this kind of single-command power with a GUI.The downside of a command-line of course is that you have learn the commands before you can use them.That leads us to the GUI .
All of the controls of the objects are presented on the screen .
The idea is that how to manipulate the objects is self-evident ( somewhat ) .
Users learn by interacting in real-time.i 've never liked gesture-style screen commands because they have all of the drawbacks of a command-line but very limited power .
perhaps some general commands like on the ipod interface , but it will never be a replacement for menus or text commands.Regarding the " problem " of organizing windows as shown in the video..I contend that that is not a real issue .
The only problem is the current window managers drop stuff 'wherever' .
I work perfectly fine on a small monitor with all my apps maximized .
My coworkers have twice the screen real-estate I do but still only use one app at a time becasue the foreground application is hogging most of the space and the others are splattered around behind it.At home I have a nicely organized side toolbar with all my frequently used stuff , and I have ZERO desktop icons .</tokentext>
<sentencetext>Before GUI's there was the command line.The command line is great in that you can initiate an unlimited variety of tasks.
These tasks are powerful because the interface is based on your imagination.For example: \rename *.csv *.txtYou cannot see the files in the directory you are in, but you know in your mind that you are selecting all files with the .csv extention in your current location, and no files in other places.
You have instructed to change only the last 3 letters of these filename, no matter how long they are.
You dont have this kind of single-command power with a GUI.The downside of a command-line of course is that you have learn the commands before you can use them.That leads us to the GUI.
All of the controls of the objects are presented on the screen.
The idea is that how to manipulate the objects is self-evident (somewhat).
Users learn by interacting in real-time.i've never liked gesture-style screen commands because they have all of the drawbacks of a command-line but very limited power.
perhaps some general commands like on the ipod interface, but it will never be a replacement for menus or text commands.Regarding the "problem" of organizing windows as shown in the video..I contend that that is not a real issue.
The only problem is the current window managers drop stuff 'wherever'.
I work perfectly fine on a small monitor with all my apps maximized.
My coworkers have twice the screen real-estate I do but still only use one app at a time becasue the foreground application is hogging  most of the space and the others are splattered around behind it.At home I have a nicely organized side toolbar with all my frequently used stuff, and I have ZERO desktop icons.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748483</id>
	<title>Re:Virtuoso Users only!</title>
	<author>nine-times</author>
	<datestamp>1255551180000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>I see this as stratifying feature... the have's and have not, the able and the un-able.</p></div><p>I think you're right in a lot of what you're saying, except for this.  The problem is that if most people don't feel comfortable, then it won't become a ubiquitous control scheme.  Most computers won't come with the appropriate hardware and software support, so it won't be available for most computers you sit down at.  That means most people won't get the opportunity to practice it and become comfortable with it.
</p><p>So there may be some occasional people who have it set up on their own computer and use it themselves, but it'll probably be quite a rarity.  Because of this, it probably won't be well supported even on systems where it's supported.  Whenever you have some niche thing in computers, you always end up with bugs.  The hardware drivers will conflict with some other drivers, or some particular piece of software will render something in a whacky way breaking your nice little unified UI.  Part of the reason things like this don't catch on is that, if you want your computer to work well, it's best to stick to well-worn roads.
</p><p>I like the idea and I'm always interested in new UI ideas, but they always seem to be too complicated and subtle.  There's something nice about having a button that you push, and having that button do a clear and expected thing.  I always turn off the multitouch stuff on my trackpad, or else it gets activated accidentally at random times, and my browser fonts change size because it interpreted something I did as a "pinch" move.
</p><p>Here's what I could see as a new mouse alternative: put a small touchpad next to your keyboard with an LCD screen behind it.  Most of the time it can work as a normal touchpad like we have in laptops today, even allowing for configurable multi-touch controls.  However, you could have it change its display under certain contexts to allow for specialty-functions.  Like let's say you press a certain key combination to control your computer's volume, and the pad turns into a graphic equalizer.  It could be cool, useful, and not-too-confusing to your grandma.</p></div>
	</htmltext>
<tokenext>I see this as stratifying feature... the have 's and have not , the able and the un-able.I think you 're right in a lot of what you 're saying , except for this .
The problem is that if most people do n't feel comfortable , then it wo n't become a ubiquitous control scheme .
Most computers wo n't come with the appropriate hardware and software support , so it wo n't be available for most computers you sit down at .
That means most people wo n't get the opportunity to practice it and become comfortable with it .
So there may be some occasional people who have it set up on their own computer and use it themselves , but it 'll probably be quite a rarity .
Because of this , it probably wo n't be well supported even on systems where it 's supported .
Whenever you have some niche thing in computers , you always end up with bugs .
The hardware drivers will conflict with some other drivers , or some particular piece of software will render something in a whacky way breaking your nice little unified UI .
Part of the reason things like this do n't catch on is that , if you want your computer to work well , it 's best to stick to well-worn roads .
I like the idea and I 'm always interested in new UI ideas , but they always seem to be too complicated and subtle .
There 's something nice about having a button that you push , and having that button do a clear and expected thing .
I always turn off the multitouch stuff on my trackpad , or else it gets activated accidentally at random times , and my browser fonts change size because it interpreted something I did as a " pinch " move .
Here 's what I could see as a new mouse alternative : put a small touchpad next to your keyboard with an LCD screen behind it .
Most of the time it can work as a normal touchpad like we have in laptops today , even allowing for configurable multi-touch controls .
However , you could have it change its display under certain contexts to allow for specialty-functions .
Like let 's say you press a certain key combination to control your computer 's volume , and the pad turns into a graphic equalizer .
It could be cool , useful , and not-too-confusing to your grandma .</tokentext>
<sentencetext>I see this as stratifying feature... the have's and have not, the able and the un-able.I think you're right in a lot of what you're saying, except for this.
The problem is that if most people don't feel comfortable, then it won't become a ubiquitous control scheme.
Most computers won't come with the appropriate hardware and software support, so it won't be available for most computers you sit down at.
That means most people won't get the opportunity to practice it and become comfortable with it.
So there may be some occasional people who have it set up on their own computer and use it themselves, but it'll probably be quite a rarity.
Because of this, it probably won't be well supported even on systems where it's supported.
Whenever you have some niche thing in computers, you always end up with bugs.
The hardware drivers will conflict with some other drivers, or some particular piece of software will render something in a whacky way breaking your nice little unified UI.
Part of the reason things like this don't catch on is that, if you want your computer to work well, it's best to stick to well-worn roads.
I like the idea and I'm always interested in new UI ideas, but they always seem to be too complicated and subtle.
There's something nice about having a button that you push, and having that button do a clear and expected thing.
I always turn off the multitouch stuff on my trackpad, or else it gets activated accidentally at random times, and my browser fonts change size because it interpreted something I did as a "pinch" move.
Here's what I could see as a new mouse alternative: put a small touchpad next to your keyboard with an LCD screen behind it.
Most of the time it can work as a normal touchpad like we have in laptops today, even allowing for configurable multi-touch controls.
However, you could have it change its display under certain contexts to allow for specialty-functions.
Like let's say you press a certain key combination to control your computer's volume, and the pad turns into a graphic equalizer.
It could be cool, useful, and not-too-confusing to your grandma.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744653</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745993</id>
	<title>Re:Not quite....</title>
	<author>kLaNk</author>
	<datestamp>1255540200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>little behind these guys:</p><p><a href="http://www.perceptivepixel.com/" title="perceptivepixel.com" rel="nofollow">http://www.perceptivepixel.com/</a> [perceptivepixel.com]</p><p>Doncha think?</p></div><p>Their multi-touch wall and multi-touch workstation are in exactly the configurations that the 10/GUI video puts forth as being unusable.</p></div>
	</htmltext>
<tokenext>little behind these guys : http : //www.perceptivepixel.com/ [ perceptivepixel.com ] Doncha think ? Their multi-touch wall and multi-touch workstation are in exactly the configurations that the 10/GUI video puts forth as being unusable .</tokentext>
<sentencetext>little behind these guys:http://www.perceptivepixel.com/ [perceptivepixel.com]Doncha think?Their multi-touch wall and multi-touch workstation are in exactly the configurations that the 10/GUI video puts forth as being unusable.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744659</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746391</id>
	<title>Bits Not Decimals</title>
	<author>PerfectionLost</author>
	<datestamp>1255541940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Computing got revolutionized by using base 2, not base 10.  This is be cause on/off (click/no click) is easy to understand.  Imagine explaining to your parents or grand parents how to pan between applications.  Touch/Pinch is doable, but once you get into 2/3/4 finger pinch, things get confusing.

What really blows my mind is that there is no hand-mash predefined function.</htmltext>
<tokenext>Computing got revolutionized by using base 2 , not base 10 .
This is be cause on/off ( click/no click ) is easy to understand .
Imagine explaining to your parents or grand parents how to pan between applications .
Touch/Pinch is doable , but once you get into 2/3/4 finger pinch , things get confusing .
What really blows my mind is that there is no hand-mash predefined function .</tokentext>
<sentencetext>Computing got revolutionized by using base 2, not base 10.
This is be cause on/off (click/no click) is easy to understand.
Imagine explaining to your parents or grand parents how to pan between applications.
Touch/Pinch is doable, but once you get into 2/3/4 finger pinch, things get confusing.
What really blows my mind is that there is no hand-mash predefined function.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29752455</id>
	<title>Some comments</title>
	<author>johncch</author>
	<datestamp>1255531260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I actually watched the video yesterday before the<nobr> <wbr></nobr>/. post came up and sat through my thoughts for a day and this is what i feel.

Multi touch interfaces are overhyped.

Point being, 1) I think one thing that the mouse works really well is that it basically is a amplification and translation of human motion. This is my main criticism of this interface design. I can understand why touch works for the iPhone, but say for the computer, simply put, for zooming in and out, most photo managing programs (hello picasa) uses the mouse scroll button to zoom. And it really translates and require far less effort on my part to perform this task as to if i were to keep pinching my fingers. And reset and pinch again. Basically the mouse wheel allows me to zoom to theoretically infinity. Thus that is a reason why I don't think I would want something like this. The effort to use this device is basically presented in the concept itself - It has a surface that is wide, and it needs ten fingers to operate. To what benefit does it bring? Interestingly, I'm more of a fan of the new Wacom Bamboo Touch. I think while the concept is similar, the execution is different and the device itself would have more potential in a still windows based environment.

2) I don't see the point of tiling windows in a long strip. It may be good for some applications but not for others. What about applications that have inherently small windows? Like Instant messengers. Are all my conversation windows going to be tiled full screen over my big monitor? The other thing that I'm thinking is what if I'm referencing something. I've done this a few times, say if I'm writing code or essay and I keep a webpage or something maximised in the background while my current window occupies a smaller window on the front? And basically the zoom all the way out fees like expose, or compiz on linux where you can line all windows up. And scrolling the windows tile is simply.. alt tabbing? But with touch gestures? Imagine if you have a capacitative touch pad, and you can say use a 2 finger gesture to alt-tab (+ auto maximise if you so desire). Does it work the same way?

I love the idea of reimagining interfaces. And I really laud the video poster for his good work. But I don't think it works for me and I'd like to post this as some constructive feedback.</htmltext>
<tokenext>I actually watched the video yesterday before the / .
post came up and sat through my thoughts for a day and this is what i feel .
Multi touch interfaces are overhyped .
Point being , 1 ) I think one thing that the mouse works really well is that it basically is a amplification and translation of human motion .
This is my main criticism of this interface design .
I can understand why touch works for the iPhone , but say for the computer , simply put , for zooming in and out , most photo managing programs ( hello picasa ) uses the mouse scroll button to zoom .
And it really translates and require far less effort on my part to perform this task as to if i were to keep pinching my fingers .
And reset and pinch again .
Basically the mouse wheel allows me to zoom to theoretically infinity .
Thus that is a reason why I do n't think I would want something like this .
The effort to use this device is basically presented in the concept itself - It has a surface that is wide , and it needs ten fingers to operate .
To what benefit does it bring ?
Interestingly , I 'm more of a fan of the new Wacom Bamboo Touch .
I think while the concept is similar , the execution is different and the device itself would have more potential in a still windows based environment .
2 ) I do n't see the point of tiling windows in a long strip .
It may be good for some applications but not for others .
What about applications that have inherently small windows ?
Like Instant messengers .
Are all my conversation windows going to be tiled full screen over my big monitor ?
The other thing that I 'm thinking is what if I 'm referencing something .
I 've done this a few times , say if I 'm writing code or essay and I keep a webpage or something maximised in the background while my current window occupies a smaller window on the front ?
And basically the zoom all the way out fees like expose , or compiz on linux where you can line all windows up .
And scrolling the windows tile is simply.. alt tabbing ?
But with touch gestures ?
Imagine if you have a capacitative touch pad , and you can say use a 2 finger gesture to alt-tab ( + auto maximise if you so desire ) .
Does it work the same way ?
I love the idea of reimagining interfaces .
And I really laud the video poster for his good work .
But I do n't think it works for me and I 'd like to post this as some constructive feedback .</tokentext>
<sentencetext>I actually watched the video yesterday before the /.
post came up and sat through my thoughts for a day and this is what i feel.
Multi touch interfaces are overhyped.
Point being, 1) I think one thing that the mouse works really well is that it basically is a amplification and translation of human motion.
This is my main criticism of this interface design.
I can understand why touch works for the iPhone, but say for the computer, simply put, for zooming in and out, most photo managing programs (hello picasa) uses the mouse scroll button to zoom.
And it really translates and require far less effort on my part to perform this task as to if i were to keep pinching my fingers.
And reset and pinch again.
Basically the mouse wheel allows me to zoom to theoretically infinity.
Thus that is a reason why I don't think I would want something like this.
The effort to use this device is basically presented in the concept itself - It has a surface that is wide, and it needs ten fingers to operate.
To what benefit does it bring?
Interestingly, I'm more of a fan of the new Wacom Bamboo Touch.
I think while the concept is similar, the execution is different and the device itself would have more potential in a still windows based environment.
2) I don't see the point of tiling windows in a long strip.
It may be good for some applications but not for others.
What about applications that have inherently small windows?
Like Instant messengers.
Are all my conversation windows going to be tiled full screen over my big monitor?
The other thing that I'm thinking is what if I'm referencing something.
I've done this a few times, say if I'm writing code or essay and I keep a webpage or something maximised in the background while my current window occupies a smaller window on the front?
And basically the zoom all the way out fees like expose, or compiz on linux where you can line all windows up.
And scrolling the windows tile is simply.. alt tabbing?
But with touch gestures?
Imagine if you have a capacitative touch pad, and you can say use a 2 finger gesture to alt-tab (+ auto maximise if you so desire).
Does it work the same way?
I love the idea of reimagining interfaces.
And I really laud the video poster for his good work.
But I don't think it works for me and I'd like to post this as some constructive feedback.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745723</id>
	<title>Re:going in circles</title>
	<author>Anonymous</author>
	<datestamp>1255539120000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>As an owner of the FingerWorks TouchStream (the keyboard/mousepad multitouch combo product), I disagree with your assessment. The reasons the keyboard failed are many. One of the most important ones, I think, was that it was too early. Yes, it had multi-touch, but no application supported multi-touch. So the only thing you could use it for is a virtual keyboard. The keyboard was good, but lacked haptic feedback, thus making touch-typing very difficult.</p><p>If applications would support multi-touch, a product like the TouchStream could be a success, because now it gives you an advantage over a conventional keyboard.</p></htmltext>
<tokenext>As an owner of the FingerWorks TouchStream ( the keyboard/mousepad multitouch combo product ) , I disagree with your assessment .
The reasons the keyboard failed are many .
One of the most important ones , I think , was that it was too early .
Yes , it had multi-touch , but no application supported multi-touch .
So the only thing you could use it for is a virtual keyboard .
The keyboard was good , but lacked haptic feedback , thus making touch-typing very difficult.If applications would support multi-touch , a product like the TouchStream could be a success , because now it gives you an advantage over a conventional keyboard .</tokentext>
<sentencetext>As an owner of the FingerWorks TouchStream (the keyboard/mousepad multitouch combo product), I disagree with your assessment.
The reasons the keyboard failed are many.
One of the most important ones, I think, was that it was too early.
Yes, it had multi-touch, but no application supported multi-touch.
So the only thing you could use it for is a virtual keyboard.
The keyboard was good, but lacked haptic feedback, thus making touch-typing very difficult.If applications would support multi-touch, a product like the TouchStream could be a success, because now it gives you an advantage over a conventional keyboard.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744657</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744767</id>
	<title>Application-centric workflow is a problem</title>
	<author>argent</author>
	<datestamp>1255535280000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>Application centric user interfaces are already a problem. On both Windows and Mac these days there's an increasing level of application-centric organization, and that breaks the task-centric workflow badly. I normally have a separate workspace for each task, with windows from each application all visible simultaneously. I can surround each primary document with windows of all sizes, to the sides, above, and below. The 10/GUI control model looks very very good, and would work well for a multi-desktop window-oriented workflow, but the Con10uum user interface would be a huge obstacle multi-document workflow.</p></htmltext>
<tokenext>Application centric user interfaces are already a problem .
On both Windows and Mac these days there 's an increasing level of application-centric organization , and that breaks the task-centric workflow badly .
I normally have a separate workspace for each task , with windows from each application all visible simultaneously .
I can surround each primary document with windows of all sizes , to the sides , above , and below .
The 10/GUI control model looks very very good , and would work well for a multi-desktop window-oriented workflow , but the Con10uum user interface would be a huge obstacle multi-document workflow .</tokentext>
<sentencetext>Application centric user interfaces are already a problem.
On both Windows and Mac these days there's an increasing level of application-centric organization, and that breaks the task-centric workflow badly.
I normally have a separate workspace for each task, with windows from each application all visible simultaneously.
I can surround each primary document with windows of all sizes, to the sides, above, and below.
The 10/GUI control model looks very very good, and would work well for a multi-desktop window-oriented workflow, but the Con10uum user interface would be a huge obstacle multi-document workflow.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746173</id>
	<title>Re:going in circles</title>
	<author>Anonymous</author>
	<datestamp>1255541040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I'm not sure most would agree that they their hands are always faster than they think. How many of us can type out the sentences as fast as we talk, let alone think? Switching between windows or adjusting window position/size always slows me down.</p><p>I thought FingerWorks closed because Apple wanted it to?</p><p>Adaption may be slow but is definitely impossible. I remember double click used to be a hard concept for many.</p></htmltext>
<tokenext>I 'm not sure most would agree that they their hands are always faster than they think .
How many of us can type out the sentences as fast as we talk , let alone think ?
Switching between windows or adjusting window position/size always slows me down.I thought FingerWorks closed because Apple wanted it to ? Adaption may be slow but is definitely impossible .
I remember double click used to be a hard concept for many .</tokentext>
<sentencetext>I'm not sure most would agree that they their hands are always faster than they think.
How many of us can type out the sentences as fast as we talk, let alone think?
Switching between windows or adjusting window position/size always slows me down.I thought FingerWorks closed because Apple wanted it to?Adaption may be slow but is definitely impossible.
I remember double click used to be a hard concept for many.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744657</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746919</id>
	<title>Re:Replacing current business work interface</title>
	<author>Elbowgeek</author>
	<datestamp>1255544520000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>In the current key/mouse interface, there's a big difference between the mental processes in pressing a physical key and operating a mouse.  With a keyboard your fingers reach to press a button which stays stationary, but with a mouse and other free-range positioning device or interface much greater mental activity is necessary.  You have to move the on-screen pointer to the position desired and then click on it - the positioning mechanism is that much different from simply keying that a certain amount of stress and inaccuracy results.  I personally dislike having to take my hands away from the keyboard to do any kind of interface function as I lose a certain amount of mental flow owing to the disparity in brain processing which results.</p><p>In light of this, a keyboard-based system of moving and manipulating windows seems preferable.  I would posit that a great many functions for doing one's daily work on a windowed system are quite do-able without taking one's hand off the keyboard with a properly thought-out set of commands assigned to the existing standard input device, with a few additions.  Indeed one can almost do that today, but the keyboard-centric paradigm will need to be adopted as standard for the majority of applications for it to truly increase productivity.</p></htmltext>
<tokenext>In the current key/mouse interface , there 's a big difference between the mental processes in pressing a physical key and operating a mouse .
With a keyboard your fingers reach to press a button which stays stationary , but with a mouse and other free-range positioning device or interface much greater mental activity is necessary .
You have to move the on-screen pointer to the position desired and then click on it - the positioning mechanism is that much different from simply keying that a certain amount of stress and inaccuracy results .
I personally dislike having to take my hands away from the keyboard to do any kind of interface function as I lose a certain amount of mental flow owing to the disparity in brain processing which results.In light of this , a keyboard-based system of moving and manipulating windows seems preferable .
I would posit that a great many functions for doing one 's daily work on a windowed system are quite do-able without taking one 's hand off the keyboard with a properly thought-out set of commands assigned to the existing standard input device , with a few additions .
Indeed one can almost do that today , but the keyboard-centric paradigm will need to be adopted as standard for the majority of applications for it to truly increase productivity .</tokentext>
<sentencetext>In the current key/mouse interface, there's a big difference between the mental processes in pressing a physical key and operating a mouse.
With a keyboard your fingers reach to press a button which stays stationary, but with a mouse and other free-range positioning device or interface much greater mental activity is necessary.
You have to move the on-screen pointer to the position desired and then click on it - the positioning mechanism is that much different from simply keying that a certain amount of stress and inaccuracy results.
I personally dislike having to take my hands away from the keyboard to do any kind of interface function as I lose a certain amount of mental flow owing to the disparity in brain processing which results.In light of this, a keyboard-based system of moving and manipulating windows seems preferable.
I would posit that a great many functions for doing one's daily work on a windowed system are quite do-able without taking one's hand off the keyboard with a properly thought-out set of commands assigned to the existing standard input device, with a few additions.
Indeed one can almost do that today, but the keyboard-centric paradigm will need to be adopted as standard for the majority of applications for it to truly increase productivity.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744371</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745497</id>
	<title>Virtual keyboard</title>
	<author>wolfguru</author>
	<datestamp>1255538280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>There's no reason a virtual keyboard could not be integrated into the surface being used as the interface. Add a third 'edge' surface to activate the keyboard, perhaps the edge closest to the user, so a palm touch would convert the surface to act as the keyboard; with a kb displayed as the surface, there would be little difficulty in using a virtual; the system is already sensitized to pressure response so typing a key vs resting on it would be an easy transition.  The touch surface could even be slightly textured to represent the divisions between keys, which is one of the common issues with virtual keyboards now. The laser-projected keyboard that is available as a blue-tooth peripheral is another approach; display a kb over the surface with the projection; activated by the 'bottom edge' touch perhaps.

This looks like a first pass concept at a real interface, and will take refining, but it covers a significant portion of the needs of the interactions with a quite simple but thorough approach.

Where can I get one to start trying this out<nobr> <wbr></nobr>:)</htmltext>
<tokenext>There 's no reason a virtual keyboard could not be integrated into the surface being used as the interface .
Add a third 'edge ' surface to activate the keyboard , perhaps the edge closest to the user , so a palm touch would convert the surface to act as the keyboard ; with a kb displayed as the surface , there would be little difficulty in using a virtual ; the system is already sensitized to pressure response so typing a key vs resting on it would be an easy transition .
The touch surface could even be slightly textured to represent the divisions between keys , which is one of the common issues with virtual keyboards now .
The laser-projected keyboard that is available as a blue-tooth peripheral is another approach ; display a kb over the surface with the projection ; activated by the 'bottom edge ' touch perhaps .
This looks like a first pass concept at a real interface , and will take refining , but it covers a significant portion of the needs of the interactions with a quite simple but thorough approach .
Where can I get one to start trying this out : )</tokentext>
<sentencetext>There's no reason a virtual keyboard could not be integrated into the surface being used as the interface.
Add a third 'edge' surface to activate the keyboard, perhaps the edge closest to the user, so a palm touch would convert the surface to act as the keyboard; with a kb displayed as the surface, there would be little difficulty in using a virtual; the system is already sensitized to pressure response so typing a key vs resting on it would be an easy transition.
The touch surface could even be slightly textured to represent the divisions between keys, which is one of the common issues with virtual keyboards now.
The laser-projected keyboard that is available as a blue-tooth peripheral is another approach; display a kb over the surface with the projection; activated by the 'bottom edge' touch perhaps.
This looks like a first pass concept at a real interface, and will take refining, but it covers a significant portion of the needs of the interactions with a quite simple but thorough approach.
Where can I get one to start trying this out :)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745533</id>
	<title>Mouse, Keyboard, FPS</title>
	<author>RivenAleem</author>
	<datestamp>1255538400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>On a touch sensitive pad you could take an object, like a Hemisphere or Starfish-shape, and the software could interpret that as "The Mouse". By using it on the touch surface, you have a cordless mouse that requires no batteries and can be taken off, or moved to a specific location when not in use.<br><br>I have in my workplace a perspex stand that sits between my keyboard and screen for resting documents. I don't see why you can't mount a touch pad on it so that you can change the angle it rests at for a more ergonomic typing position.<br><br>With these modifications, or others, you can easily replace keyboard and mouse with a large touch sensitive pad. Without making any more modifications you could use it as is to play games. But, you are not taking the idea and using it's full potential. You are still only considering the hardware. It would be easy to create a mod for , or design a game around, the use of a touch pad for interaction with abilities.<br><br>Create an area where movement is controlled by sliding finger from middle to edge to signal movement in that direction (holding it at the edge to keep moving) while having another area designed for triggering abilities, changing view, selecting chat options. ATM we use a keyboard to control characters in game because that is the input device we have to other applications in the computer. I consider it to be a woefully inadequate input device for almost all games I play, and a hand-held console controller to be much better for most. In WoW for example the keyboard acts as a control and command input device for 90+\% of the time and only become a text input device when I hit the / key. There is no reason for the same to happen to a dynamic input device like a touch pad. The advantage is that when it is not being a keyboard, it can be optimized to be a far greater command input device.<br><br>If you imagine where the future (and much science fiction) is going (has gone), the idea of VR goggles + gloves is going to be a much more common reality. When this happens you can expect that game input will be in the form of a virtual device, an orb, a disc or any other shape you wish. It is very unlikely that game input in a VR setting will be a keyboard + mouse.</htmltext>
<tokenext>On a touch sensitive pad you could take an object , like a Hemisphere or Starfish-shape , and the software could interpret that as " The Mouse " .
By using it on the touch surface , you have a cordless mouse that requires no batteries and can be taken off , or moved to a specific location when not in use.I have in my workplace a perspex stand that sits between my keyboard and screen for resting documents .
I do n't see why you ca n't mount a touch pad on it so that you can change the angle it rests at for a more ergonomic typing position.With these modifications , or others , you can easily replace keyboard and mouse with a large touch sensitive pad .
Without making any more modifications you could use it as is to play games .
But , you are not taking the idea and using it 's full potential .
You are still only considering the hardware .
It would be easy to create a mod for , or design a game around , the use of a touch pad for interaction with abilities.Create an area where movement is controlled by sliding finger from middle to edge to signal movement in that direction ( holding it at the edge to keep moving ) while having another area designed for triggering abilities , changing view , selecting chat options .
ATM we use a keyboard to control characters in game because that is the input device we have to other applications in the computer .
I consider it to be a woefully inadequate input device for almost all games I play , and a hand-held console controller to be much better for most .
In WoW for example the keyboard acts as a control and command input device for 90 + \ % of the time and only become a text input device when I hit the / key .
There is no reason for the same to happen to a dynamic input device like a touch pad .
The advantage is that when it is not being a keyboard , it can be optimized to be a far greater command input device.If you imagine where the future ( and much science fiction ) is going ( has gone ) , the idea of VR goggles + gloves is going to be a much more common reality .
When this happens you can expect that game input will be in the form of a virtual device , an orb , a disc or any other shape you wish .
It is very unlikely that game input in a VR setting will be a keyboard + mouse .</tokentext>
<sentencetext>On a touch sensitive pad you could take an object, like a Hemisphere or Starfish-shape, and the software could interpret that as "The Mouse".
By using it on the touch surface, you have a cordless mouse that requires no batteries and can be taken off, or moved to a specific location when not in use.I have in my workplace a perspex stand that sits between my keyboard and screen for resting documents.
I don't see why you can't mount a touch pad on it so that you can change the angle it rests at for a more ergonomic typing position.With these modifications, or others, you can easily replace keyboard and mouse with a large touch sensitive pad.
Without making any more modifications you could use it as is to play games.
But, you are not taking the idea and using it's full potential.
You are still only considering the hardware.
It would be easy to create a mod for , or design a game around, the use of a touch pad for interaction with abilities.Create an area where movement is controlled by sliding finger from middle to edge to signal movement in that direction (holding it at the edge to keep moving) while having another area designed for triggering abilities, changing view, selecting chat options.
ATM we use a keyboard to control characters in game because that is the input device we have to other applications in the computer.
I consider it to be a woefully inadequate input device for almost all games I play, and a hand-held console controller to be much better for most.
In WoW for example the keyboard acts as a control and command input device for 90+\% of the time and only become a text input device when I hit the / key.
There is no reason for the same to happen to a dynamic input device like a touch pad.
The advantage is that when it is not being a keyboard, it can be optimized to be a far greater command input device.If you imagine where the future (and much science fiction) is going (has gone), the idea of VR goggles + gloves is going to be a much more common reality.
When this happens you can expect that game input will be in the form of a virtual device, an orb, a disc or any other shape you wish.
It is very unlikely that game input in a VR setting will be a keyboard + mouse.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747395</id>
	<title>Re:going in circles</title>
	<author>26199</author>
	<datestamp>1255546560000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>I disagree: the keyboard and mouse do not work really well. What they are is really easy to start using, and <i>good enough</i>.</p><p>The TouchStream takes at least a month or two to get used to. Most people spent that long getting started with a keyboard, and aren't willing to invest the time again learning a new device. Nor is there any pressing need except for power users.</p><p>For those power users, though, the TouchStream presents a potentially big[1] boost to productivity and comfort. At least, that's what I found.</p><p>

[1] Where "big" is ~20\%. That's only big if you're working 8 hours a day...</p></htmltext>
<tokenext>I disagree : the keyboard and mouse do not work really well .
What they are is really easy to start using , and good enough.The TouchStream takes at least a month or two to get used to .
Most people spent that long getting started with a keyboard , and are n't willing to invest the time again learning a new device .
Nor is there any pressing need except for power users.For those power users , though , the TouchStream presents a potentially big [ 1 ] boost to productivity and comfort .
At least , that 's what I found .
[ 1 ] Where " big " is ~ 20 \ % .
That 's only big if you 're working 8 hours a day.. .</tokentext>
<sentencetext>I disagree: the keyboard and mouse do not work really well.
What they are is really easy to start using, and good enough.The TouchStream takes at least a month or two to get used to.
Most people spent that long getting started with a keyboard, and aren't willing to invest the time again learning a new device.
Nor is there any pressing need except for power users.For those power users, though, the TouchStream presents a potentially big[1] boost to productivity and comfort.
At least, that's what I found.
[1] Where "big" is ~20\%.
That's only big if you're working 8 hours a day...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744657</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744591</id>
	<title>Another "expert" interface that will fail</title>
	<author>drsmack1</author>
	<datestamp>1255534620000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>It seems that every time an "improved" interface to your computer is invented, they get more complicated whilst simultaneously looking simpler.
<br> <br>
This particular interface perhaps has potential for the expert user (like most slashdot folks), but I don't see your average housewife or Grandpa wanting to remember how many fingers to use for what.<br> <br>

And just what are you supposed to be doing with the fingers not touching the screen?  Hold them in the air?<br> <br>

How about your left hand?  Keep it in your pocket until you need a context menu?<br> <br>

I'm guessing you will still need a keyboard; where is that supposed to fit on your desk?<br> <br>

Apple got it right with the iPhone - by restricting the buttons and losing the stylus they have greatly simplified the interface.<br> <br>*I* personally miss the hardware buttons from my Windows phone and taskbar - but those things were sacrificed for the greater good.</htmltext>
<tokenext>It seems that every time an " improved " interface to your computer is invented , they get more complicated whilst simultaneously looking simpler .
This particular interface perhaps has potential for the expert user ( like most slashdot folks ) , but I do n't see your average housewife or Grandpa wanting to remember how many fingers to use for what .
And just what are you supposed to be doing with the fingers not touching the screen ?
Hold them in the air ?
How about your left hand ?
Keep it in your pocket until you need a context menu ?
I 'm guessing you will still need a keyboard ; where is that supposed to fit on your desk ?
Apple got it right with the iPhone - by restricting the buttons and losing the stylus they have greatly simplified the interface .
* I * personally miss the hardware buttons from my Windows phone and taskbar - but those things were sacrificed for the greater good .</tokentext>
<sentencetext>It seems that every time an "improved" interface to your computer is invented, they get more complicated whilst simultaneously looking simpler.
This particular interface perhaps has potential for the expert user (like most slashdot folks), but I don't see your average housewife or Grandpa wanting to remember how many fingers to use for what.
And just what are you supposed to be doing with the fingers not touching the screen?
Hold them in the air?
How about your left hand?
Keep it in your pocket until you need a context menu?
I'm guessing you will still need a keyboard; where is that supposed to fit on your desk?
Apple got it right with the iPhone - by restricting the buttons and losing the stylus they have greatly simplified the interface.
*I* personally miss the hardware buttons from my Windows phone and taskbar - but those things were sacrificed for the greater good.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29750397</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>oceanicicefloe</author>
	<datestamp>1255516860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I could definitely see myself using this. I don't think I would even particularly need a real keyboard - a virtual one using the touch interface would be fine. Come on people, use your imagination! Don't you want to at least try it as a replacement for all that ugly input hardware?<nobr> <wbr></nobr>:-)</htmltext>
<tokenext>I could definitely see myself using this .
I do n't think I would even particularly need a real keyboard - a virtual one using the touch interface would be fine .
Come on people , use your imagination !
Do n't you want to at least try it as a replacement for all that ugly input hardware ?
: - )</tokentext>
<sentencetext>I could definitely see myself using this.
I don't think I would even particularly need a real keyboard - a virtual one using the touch interface would be fine.
Come on people, use your imagination!
Don't you want to at least try it as a replacement for all that ugly input hardware?
:-)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744155</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745875</id>
	<title>Guys..</title>
	<author>Anonymous</author>
	<datestamp>1255539720000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Guys, you are missing one incredibly important aspect of this -&gt; Porn browsing.</p><p>Everyone knows it's impossible to browse various websites while you're favourite hand is in use. This changes everything.</p></htmltext>
<tokenext>Guys , you are missing one incredibly important aspect of this - &gt; Porn browsing.Everyone knows it 's impossible to browse various websites while you 're favourite hand is in use .
This changes everything .</tokentext>
<sentencetext>Guys, you are missing one incredibly important aspect of this -&gt; Porn browsing.Everyone knows it's impossible to browse various websites while you're favourite hand is in use.
This changes everything.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746653</id>
	<title>Interesting, but developed from a flawed premise</title>
	<author>Dudeman\_Jones</author>
	<datestamp>1255543200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The idea is interesting, the execution is intriguing, but the problem it solves isn't necessarily a problem.  The video goes to great lengths to say that current window management systems are arbitrary and messy, but this is the problem.  Alot of people arrange those windows intentionally to specific positions to better enable multi-tasking.  Additionally, the concept seems to completely forget about the existence of task bars and minimizing in current windowed GUIs.  Furthermore this solution isn't even all that superior anyway what with all open programs being oriented horizontally.  It sounds like a good idea at first as it allows you to simply flip through your programs, but this is an example of an interface being built around an intended feature instead of the other way around.  Any more than a few programs open at once and I can see it becoming very easy to lose track of where the program you were just using is, at which point you have to shrink the entire application space until you bring up their own version of alt-tab, at which point you've pretty much used a more cumbersome method to perform the exact same window management technique that the the video initially comdemns.  The final issue that I have with it is that it nearly eliminates the desktop and all it's utility, opting instead to hide it most of the time behind every program you are working with.  You can't use it as a quick workspace for file management, or a temporary destination for works in progress, all it's good for is widgets that you can't even see unless you hide everything you are doing at the moment.</p></htmltext>
<tokenext>The idea is interesting , the execution is intriguing , but the problem it solves is n't necessarily a problem .
The video goes to great lengths to say that current window management systems are arbitrary and messy , but this is the problem .
Alot of people arrange those windows intentionally to specific positions to better enable multi-tasking .
Additionally , the concept seems to completely forget about the existence of task bars and minimizing in current windowed GUIs .
Furthermore this solution is n't even all that superior anyway what with all open programs being oriented horizontally .
It sounds like a good idea at first as it allows you to simply flip through your programs , but this is an example of an interface being built around an intended feature instead of the other way around .
Any more than a few programs open at once and I can see it becoming very easy to lose track of where the program you were just using is , at which point you have to shrink the entire application space until you bring up their own version of alt-tab , at which point you 've pretty much used a more cumbersome method to perform the exact same window management technique that the the video initially comdemns .
The final issue that I have with it is that it nearly eliminates the desktop and all it 's utility , opting instead to hide it most of the time behind every program you are working with .
You ca n't use it as a quick workspace for file management , or a temporary destination for works in progress , all it 's good for is widgets that you ca n't even see unless you hide everything you are doing at the moment .</tokentext>
<sentencetext>The idea is interesting, the execution is intriguing, but the problem it solves isn't necessarily a problem.
The video goes to great lengths to say that current window management systems are arbitrary and messy, but this is the problem.
Alot of people arrange those windows intentionally to specific positions to better enable multi-tasking.
Additionally, the concept seems to completely forget about the existence of task bars and minimizing in current windowed GUIs.
Furthermore this solution isn't even all that superior anyway what with all open programs being oriented horizontally.
It sounds like a good idea at first as it allows you to simply flip through your programs, but this is an example of an interface being built around an intended feature instead of the other way around.
Any more than a few programs open at once and I can see it becoming very easy to lose track of where the program you were just using is, at which point you have to shrink the entire application space until you bring up their own version of alt-tab, at which point you've pretty much used a more cumbersome method to perform the exact same window management technique that the the video initially comdemns.
The final issue that I have with it is that it nearly eliminates the desktop and all it's utility, opting instead to hide it most of the time behind every program you are working with.
You can't use it as a quick workspace for file management, or a temporary destination for works in progress, all it's good for is widgets that you can't even see unless you hide everything you are doing at the moment.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29754897</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>Simon Brooke</author>
	<datestamp>1255605780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I was thinking the same thing. I thought one way to handle this more elegantly would be to have two separate touch pads, one on each side of the keyboard:</p><p>[TP][ KB ][TP]</p><p>Of course, you may lose some manipulation space for your hands, but this would take up considerably less vertical space, which is the more "expensive" dimension, in my opinion.</p></div><p>Or have the keyboard mounted on a powered slide or folding mechanism) over the touchpad. so that at a touch, the keyboard slides over the touchpad allowing you to type on real keys (for composing a document or an email, for example) and then another touch moves or folds the keyboard out of the way, revealing the touchpad again. With this set up I imagine you'd use a 'soft' keyboard for typing short texts, and might retain a conventional mouse or trackball for use when the touchpad was covered.</p><p>But your keyboard and touchpad would both be in the same (ergonomically optimal) position when in use, and, depending on how the keyboard moved/slid/retracted/folded out of the way, the composite touchpad/keyboard arrangement would not need to take up more desk space.</p></div>
	</htmltext>
<tokenext>I was thinking the same thing .
I thought one way to handle this more elegantly would be to have two separate touch pads , one on each side of the keyboard : [ TP ] [ KB ] [ TP ] Of course , you may lose some manipulation space for your hands , but this would take up considerably less vertical space , which is the more " expensive " dimension , in my opinion.Or have the keyboard mounted on a powered slide or folding mechanism ) over the touchpad .
so that at a touch , the keyboard slides over the touchpad allowing you to type on real keys ( for composing a document or an email , for example ) and then another touch moves or folds the keyboard out of the way , revealing the touchpad again .
With this set up I imagine you 'd use a 'soft ' keyboard for typing short texts , and might retain a conventional mouse or trackball for use when the touchpad was covered.But your keyboard and touchpad would both be in the same ( ergonomically optimal ) position when in use , and , depending on how the keyboard moved/slid/retracted/folded out of the way , the composite touchpad/keyboard arrangement would not need to take up more desk space .</tokentext>
<sentencetext>I was thinking the same thing.
I thought one way to handle this more elegantly would be to have two separate touch pads, one on each side of the keyboard:[TP][ KB ][TP]Of course, you may lose some manipulation space for your hands, but this would take up considerably less vertical space, which is the more "expensive" dimension, in my opinion.Or have the keyboard mounted on a powered slide or folding mechanism) over the touchpad.
so that at a touch, the keyboard slides over the touchpad allowing you to type on real keys (for composing a document or an email, for example) and then another touch moves or folds the keyboard out of the way, revealing the touchpad again.
With this set up I imagine you'd use a 'soft' keyboard for typing short texts, and might retain a conventional mouse or trackball for use when the touchpad was covered.But your keyboard and touchpad would both be in the same (ergonomically optimal) position when in use, and, depending on how the keyboard moved/slid/retracted/folded out of the way, the composite touchpad/keyboard arrangement would not need to take up more desk space.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745491</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745889</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>Carbaholic</author>
	<datestamp>1255539780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Another problem with this system is that he's tied the input device to the Software, those global and local bars are lame. The menu controls should be in the OS and should be independent from the input device.</p><p>Also, his con10uum idea is lame, that kind of system is already being used in coverflow and it's fine for looking through a few albums, but not for managing my windows.</p><p>Wait, wait, I'm having a brain storm, you know that thumbnail view he showed if you zoom out, we could take a thumbnail view like that and show it all the time. We could put it at the bottom of the screen. If you hover over the thumbnail it gives you a preview of the window, and if you click on the thumbnail that window pops up. Amazing idea huh</p><p>Oh yeah, and then there's the fact that there are products similar to this that <a href="http://www.wacom.com/bamboo/bamboo\_touch.php" title="wacom.com" rel="nofollow">already exist</a> [wacom.com] and are compatible with existing systems.</p></htmltext>
<tokenext>Another problem with this system is that he 's tied the input device to the Software , those global and local bars are lame .
The menu controls should be in the OS and should be independent from the input device.Also , his con10uum idea is lame , that kind of system is already being used in coverflow and it 's fine for looking through a few albums , but not for managing my windows.Wait , wait , I 'm having a brain storm , you know that thumbnail view he showed if you zoom out , we could take a thumbnail view like that and show it all the time .
We could put it at the bottom of the screen .
If you hover over the thumbnail it gives you a preview of the window , and if you click on the thumbnail that window pops up .
Amazing idea huhOh yeah , and then there 's the fact that there are products similar to this that already exist [ wacom.com ] and are compatible with existing systems .</tokentext>
<sentencetext>Another problem with this system is that he's tied the input device to the Software, those global and local bars are lame.
The menu controls should be in the OS and should be independent from the input device.Also, his con10uum idea is lame, that kind of system is already being used in coverflow and it's fine for looking through a few albums, but not for managing my windows.Wait, wait, I'm having a brain storm, you know that thumbnail view he showed if you zoom out, we could take a thumbnail view like that and show it all the time.
We could put it at the bottom of the screen.
If you hover over the thumbnail it gives you a preview of the window, and if you click on the thumbnail that window pops up.
Amazing idea huhOh yeah, and then there's the fact that there are products similar to this that already exist [wacom.com] and are compatible with existing systems.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744311</id>
	<title>simple != good</title>
	<author>loony</author>
	<datestamp>1255533420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I like the touch surface but that "simple" window manager is just that. Simple. Too bad that there is a difference between simple and better. Just like a skateboard is simpler than a car doesn't make it more suitable to go to the grocery store with.... After all that talk of "lets increase interactivity because you can't reduce 10 fingers to one x/y coordinate" I think its a little strange that they then go to  "lets reduce x/y window layouts to just x"...</p><p>In the end it just looks like an effort in changing things just for the sake of change.</p><p>Peter.</p></htmltext>
<tokenext>I like the touch surface but that " simple " window manager is just that .
Simple. Too bad that there is a difference between simple and better .
Just like a skateboard is simpler than a car does n't make it more suitable to go to the grocery store with.... After all that talk of " lets increase interactivity because you ca n't reduce 10 fingers to one x/y coordinate " I think its a little strange that they then go to " lets reduce x/y window layouts to just x " ...In the end it just looks like an effort in changing things just for the sake of change.Peter .</tokentext>
<sentencetext>I like the touch surface but that "simple" window manager is just that.
Simple. Too bad that there is a difference between simple and better.
Just like a skateboard is simpler than a car doesn't make it more suitable to go to the grocery store with.... After all that talk of "lets increase interactivity because you can't reduce 10 fingers to one x/y coordinate" I think its a little strange that they then go to  "lets reduce x/y window layouts to just x"...In the end it just looks like an effort in changing things just for the sake of change.Peter.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745957</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>Anonymous</author>
	<datestamp>1255540080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Under your logic, the monitor does not work because blind people exist.</p></htmltext>
<tokenext>Under your logic , the monitor does not work because blind people exist .</tokentext>
<sentencetext>Under your logic, the monitor does not work because blind people exist.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744181</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744653</id>
	<title>Virtuoso Users only!</title>
	<author>Anonymous</author>
	<datestamp>1255534860000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>Yes, this is slick. Yes, it's an improvement. Yes, this will happen. But...<br> <br>
Having seen people have trouble with pressing control and clicking at the same time (to deselect a single item), I foresee a chilly reception, user frustration and a training issue. 10GUI is like playing Mozart among people only able to manage Chop Sticks.<br> <br>

I see this as stratifying feature... the have's and have not, the able and the un-able. I would request this for my workflow, but the run of the mill admins would be stuck with the keyboard. Aside from the social aspect, there is the difficult task of convincing the boss that "you need this, even if the others don't". Good luck with that.<br> <br>
I have grown to hate the windowing paradigm for all the reasons cited. I'm not convinced that the linear arrangement is an improvement. I'm more in favor of multiple monitors, the main screen for the primary task and satellites with multiple windows for ancillary tasks. 10GUI doesn't address this.</htmltext>
<tokenext>Yes , this is slick .
Yes , it 's an improvement .
Yes , this will happen .
But.. . Having seen people have trouble with pressing control and clicking at the same time ( to deselect a single item ) , I foresee a chilly reception , user frustration and a training issue .
10GUI is like playing Mozart among people only able to manage Chop Sticks .
I see this as stratifying feature... the have 's and have not , the able and the un-able .
I would request this for my workflow , but the run of the mill admins would be stuck with the keyboard .
Aside from the social aspect , there is the difficult task of convincing the boss that " you need this , even if the others do n't " .
Good luck with that .
I have grown to hate the windowing paradigm for all the reasons cited .
I 'm not convinced that the linear arrangement is an improvement .
I 'm more in favor of multiple monitors , the main screen for the primary task and satellites with multiple windows for ancillary tasks .
10GUI does n't address this .</tokentext>
<sentencetext>Yes, this is slick.
Yes, it's an improvement.
Yes, this will happen.
But... 
Having seen people have trouble with pressing control and clicking at the same time (to deselect a single item), I foresee a chilly reception, user frustration and a training issue.
10GUI is like playing Mozart among people only able to manage Chop Sticks.
I see this as stratifying feature... the have's and have not, the able and the un-able.
I would request this for my workflow, but the run of the mill admins would be stuck with the keyboard.
Aside from the social aspect, there is the difficult task of convincing the boss that "you need this, even if the others don't".
Good luck with that.
I have grown to hate the windowing paradigm for all the reasons cited.
I'm not convinced that the linear arrangement is an improvement.
I'm more in favor of multiple monitors, the main screen for the primary task and satellites with multiple windows for ancillary tasks.
10GUI doesn't address this.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744325</id>
	<title>some subtle hints in that presentation</title>
	<author>Anonymous</author>
	<datestamp>1255533480000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>- iphone<br>- window button position<br>- dashboard<br>- expose<br>- dock<br>- cinema display</p><p>wonder what platform they're going to market to first eh?</p></htmltext>
<tokenext>- iphone- window button position- dashboard- expose- dock- cinema displaywonder what platform they 're going to market to first eh ?</tokentext>
<sentencetext>- iphone- window button position- dashboard- expose- dock- cinema displaywonder what platform they're going to market to first eh?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746455</id>
	<title>both hands?</title>
	<author>Anonymous</author>
	<datestamp>1255542300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>if i need two hands to navigate, surfing porn will get much tougher</p></htmltext>
<tokenext>if i need two hands to navigate , surfing porn will get much tougher</tokentext>
<sentencetext>if i need two hands to navigate, surfing porn will get much tougher</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29753813</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>craagz</author>
	<datestamp>1255547100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>That's exactly what I thought too. Taking it further, maybe the game developers can work with this Interface and design proper shooting and FPS movements. How exciting would that be?</htmltext>
<tokenext>That 's exactly what I thought too .
Taking it further , maybe the game developers can work with this Interface and design proper shooting and FPS movements .
How exciting would that be ?</tokentext>
<sentencetext>That's exactly what I thought too.
Taking it further, maybe the game developers can work with this Interface and design proper shooting and FPS movements.
How exciting would that be?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744417</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747663</id>
	<title>Re:Virtuoso Users only!</title>
	<author>KnownIssues</author>
	<datestamp>1255547760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>If you watch videos (product demos, interviews, training, etc) at the time the mouse first came out, you'll laugh at the detail they go into to explain what a mouse is and how to use it. We take it for granted that it's so intuitive that a two year old can figure it out. There was a time this wasn't the case. This multitouch concept can be just as powerful, useful and usable as the mouse, and I will not be surprised when it seems just as obvious as the mouse.</htmltext>
<tokenext>If you watch videos ( product demos , interviews , training , etc ) at the time the mouse first came out , you 'll laugh at the detail they go into to explain what a mouse is and how to use it .
We take it for granted that it 's so intuitive that a two year old can figure it out .
There was a time this was n't the case .
This multitouch concept can be just as powerful , useful and usable as the mouse , and I will not be surprised when it seems just as obvious as the mouse .</tokentext>
<sentencetext>If you watch videos (product demos, interviews, training, etc) at the time the mouse first came out, you'll laugh at the detail they go into to explain what a mouse is and how to use it.
We take it for granted that it's so intuitive that a two year old can figure it out.
There was a time this wasn't the case.
This multitouch concept can be just as powerful, useful and usable as the mouse, and I will not be surprised when it seems just as obvious as the mouse.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744653</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744949</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>Anonymous</author>
	<datestamp>1255536000000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>or get it precisely to a specific pixel. It's hard to do that with your fingers because the area they touch is a large one, it's not easy to just move your finger by one pixel and your hand tend to shake a little bit too</p></div><p>You are just not imaginative enough.  This isn't a laptop touchpad, so there is a lot more space to work with.  You could possibly go into a "detail" or "zoom" mode where the amount of space traversed when moving across the pad is less.</p></div>
	</htmltext>
<tokenext>or get it precisely to a specific pixel .
It 's hard to do that with your fingers because the area they touch is a large one , it 's not easy to just move your finger by one pixel and your hand tend to shake a little bit tooYou are just not imaginative enough .
This is n't a laptop touchpad , so there is a lot more space to work with .
You could possibly go into a " detail " or " zoom " mode where the amount of space traversed when moving across the pad is less .</tokentext>
<sentencetext>or get it precisely to a specific pixel.
It's hard to do that with your fingers because the area they touch is a large one, it's not easy to just move your finger by one pixel and your hand tend to shake a little bit tooYou are just not imaginative enough.
This isn't a laptop touchpad, so there is a lot more space to work with.
You could possibly go into a "detail" or "zoom" mode where the amount of space traversed when moving across the pad is less.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744479</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>techiemikey</author>
	<datestamp>1255534080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>No, it would not be impossible to play FPS with this kind of setup.  It would require a different type of setup than we are currently used to, but that doesn't mean it would be a bad setup.</htmltext>
<tokenext>No , it would not be impossible to play FPS with this kind of setup .
It would require a different type of setup than we are currently used to , but that does n't mean it would be a bad setup .</tokentext>
<sentencetext>No, it would not be impossible to play FPS with this kind of setup.
It would require a different type of setup than we are currently used to, but that doesn't mean it would be a bad setup.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747313</id>
	<title>gesture recognition (Minority report)</title>
	<author>peter303</author>
	<datestamp>1255546140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Why settle for just 10 finger tips? Go for the whole hand, arm or body like in deaf-language.  There are people working on this.</htmltext>
<tokenext>Why settle for just 10 finger tips ?
Go for the whole hand , arm or body like in deaf-language .
There are people working on this .</tokentext>
<sentencetext>Why settle for just 10 finger tips?
Go for the whole hand, arm or body like in deaf-language.
There are people working on this.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744279</id>
	<title>Looks like Apple's tablet-like input interface</title>
	<author>dfxm</author>
	<datestamp>1255533360000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>When I saw this video, I immediately thought of this article: <a href="http://www.appleinsider.com/articles/09/10/01/evidence\_of\_apples\_tablet\_like\_input\_interface\_reappears.html" title="appleinsider.com" rel="nofollow">http://www.appleinsider.com/articles/09/10/01/evidence\_of\_apples\_tablet\_like\_input\_interface\_reappears.html</a> [appleinsider.com]</htmltext>
<tokenext>When I saw this video , I immediately thought of this article : http : //www.appleinsider.com/articles/09/10/01/evidence \ _of \ _apples \ _tablet \ _like \ _input \ _interface \ _reappears.html [ appleinsider.com ]</tokentext>
<sentencetext>When I saw this video, I immediately thought of this article: http://www.appleinsider.com/articles/09/10/01/evidence\_of\_apples\_tablet\_like\_input\_interface\_reappears.html [appleinsider.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745379</id>
	<title>cool looking, but whats the point?</title>
	<author>PalmKiller</author>
	<datestamp>1255537800000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>He was still single clicking from a single point of interest, though he had several points he could choose from, he just had 5 mouse pointers on the screen slid around using the basic inaccurate touch pad finger method.  But then again, I for one hate touch pads in general (prefer intellipoint like devices on business class laptops), so I guess maybe I am biased.  Seemed to me to be more chaotic than graceful.</htmltext>
<tokenext>He was still single clicking from a single point of interest , though he had several points he could choose from , he just had 5 mouse pointers on the screen slid around using the basic inaccurate touch pad finger method .
But then again , I for one hate touch pads in general ( prefer intellipoint like devices on business class laptops ) , so I guess maybe I am biased .
Seemed to me to be more chaotic than graceful .</tokentext>
<sentencetext>He was still single clicking from a single point of interest, though he had several points he could choose from, he just had 5 mouse pointers on the screen slid around using the basic inaccurate touch pad finger method.
But then again, I for one hate touch pads in general (prefer intellipoint like devices on business class laptops), so I guess maybe I am biased.
Seemed to me to be more chaotic than graceful.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745387</id>
	<title>Mousing is easy</title>
	<author>Anonymous</author>
	<datestamp>1255537800000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The mouse and keyboard aren't going anywhere until our computers have a direct link with our brains. The mouse is probably one of the simplest tools humans have ever created. How is the 10/GUI system going to work for people with dexterity problems? Watching the demo cartoon character move windows around by sliding with the right hand and grabbing an application with the left hand using three or four fingers requires too much from the user. Reminds me of the string game kids play.</p></htmltext>
<tokenext>The mouse and keyboard are n't going anywhere until our computers have a direct link with our brains .
The mouse is probably one of the simplest tools humans have ever created .
How is the 10/GUI system going to work for people with dexterity problems ?
Watching the demo cartoon character move windows around by sliding with the right hand and grabbing an application with the left hand using three or four fingers requires too much from the user .
Reminds me of the string game kids play .</tokentext>
<sentencetext>The mouse and keyboard aren't going anywhere until our computers have a direct link with our brains.
The mouse is probably one of the simplest tools humans have ever created.
How is the 10/GUI system going to work for people with dexterity problems?
Watching the demo cartoon character move windows around by sliding with the right hand and grabbing an application with the left hand using three or four fingers requires too much from the user.
Reminds me of the string game kids play.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29750769</id>
	<title>An incremental hardware update putting on airs</title>
	<author>SpaceToast</author>
	<datestamp>1255519200000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>I blogged this last night.  Short version: fail.</p><p>Problems:</p><p>1. You just doubled the amount of space I need between myself and the monitor.</p><p>2. Multitouch allows for more kinds of interaction: true! However, this interface steals ALL of them away from use by the applications.</p><p>3. Left and right sides of the screen aren't discoverable. Might as well be top and bottom -- i.e. bottom of the screen for application launching (call it a "dock") and top of the screen for context-specific options (a sort of "bar" of "menus").</p><p>4. Linear spatial overload of windows is no better than two-dimensional spatial overload of windows. Labelled zoom-all-the-way-out cheat no better than Expose and application switcher.</p><p>5. Where does file management fit into this scheme?</p><p>Lukas Mathis calls 10/GUI "one of the most dramatic reimaginations of the desktop user interface I've seen in a long time" but on examination it's an incremental hardware update with no real interface breakthroughs. Keyboard + mouse has gone on for far too long, as has the W.I.M.P. interface. A better direction would be a tactile multitouch surface which can be anything it needs to be, including a keyboard (for any language), coupled with a GUI that represents tasks and actors rather than objects in a space. 10/GUI does nothing about window and document clutter, squinting, scanning large lists, or making the computer's workings and status an organic part of its presentation. The video may be a slick investors' reel, but shows no real progress.</p></htmltext>
<tokenext>I blogged this last night .
Short version : fail.Problems : 1 .
You just doubled the amount of space I need between myself and the monitor.2 .
Multitouch allows for more kinds of interaction : true !
However , this interface steals ALL of them away from use by the applications.3 .
Left and right sides of the screen are n't discoverable .
Might as well be top and bottom -- i.e .
bottom of the screen for application launching ( call it a " dock " ) and top of the screen for context-specific options ( a sort of " bar " of " menus " ) .4 .
Linear spatial overload of windows is no better than two-dimensional spatial overload of windows .
Labelled zoom-all-the-way-out cheat no better than Expose and application switcher.5 .
Where does file management fit into this scheme ? Lukas Mathis calls 10/GUI " one of the most dramatic reimaginations of the desktop user interface I 've seen in a long time " but on examination it 's an incremental hardware update with no real interface breakthroughs .
Keyboard + mouse has gone on for far too long , as has the W.I.M.P .
interface. A better direction would be a tactile multitouch surface which can be anything it needs to be , including a keyboard ( for any language ) , coupled with a GUI that represents tasks and actors rather than objects in a space .
10/GUI does nothing about window and document clutter , squinting , scanning large lists , or making the computer 's workings and status an organic part of its presentation .
The video may be a slick investors ' reel , but shows no real progress .</tokentext>
<sentencetext>I blogged this last night.
Short version: fail.Problems:1.
You just doubled the amount of space I need between myself and the monitor.2.
Multitouch allows for more kinds of interaction: true!
However, this interface steals ALL of them away from use by the applications.3.
Left and right sides of the screen aren't discoverable.
Might as well be top and bottom -- i.e.
bottom of the screen for application launching (call it a "dock") and top of the screen for context-specific options (a sort of "bar" of "menus").4.
Linear spatial overload of windows is no better than two-dimensional spatial overload of windows.
Labelled zoom-all-the-way-out cheat no better than Expose and application switcher.5.
Where does file management fit into this scheme?Lukas Mathis calls 10/GUI "one of the most dramatic reimaginations of the desktop user interface I've seen in a long time" but on examination it's an incremental hardware update with no real interface breakthroughs.
Keyboard + mouse has gone on for far too long, as has the W.I.M.P.
interface. A better direction would be a tactile multitouch surface which can be anything it needs to be, including a keyboard (for any language), coupled with a GUI that represents tasks and actors rather than objects in a space.
10/GUI does nothing about window and document clutter, squinting, scanning large lists, or making the computer's workings and status an organic part of its presentation.
The video may be a slick investors' reel, but shows no real progress.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745143</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>Chris Pimlott</author>
	<datestamp>1255536840000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>You could easily replace the multi-finger gestures with single-feature gestures (or a traditional mouse) plus modifier keys.  This system doesn't really let you do anything new you couldn't do before, it just takes advantage of all you fingers to let you do them quickly and more efficiently.</p></htmltext>
<tokenext>You could easily replace the multi-finger gestures with single-feature gestures ( or a traditional mouse ) plus modifier keys .
This system does n't really let you do anything new you could n't do before , it just takes advantage of all you fingers to let you do them quickly and more efficiently .</tokentext>
<sentencetext>You could easily replace the multi-finger gestures with single-feature gestures (or a traditional mouse) plus modifier keys.
This system doesn't really let you do anything new you couldn't do before, it just takes advantage of all you fingers to let you do them quickly and more efficiently.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744181</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748779</id>
	<title>Re:All 10 fingers</title>
	<author>Anonymous</author>
	<datestamp>1255552380000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>You know what else uses 10 fingers?  Typing.</p><p>MANY MANY MANY people learn how to do it.  Some use 1 finger some use all ten.  Takes a bit of training but it works.  It looks like this is a few gestures (5?) which people can learn.  It is not like remembering where all 26 letters and 10 numbers are, or remembering that part of the music is one half step down.  See the difference?  I do see your point as many people can not even master drag and drop.</p><p>I see a small trackpad with multi touch being useful.  It sure removes the 2 button limitation of the mouse that is for sure.</p></htmltext>
<tokenext>You know what else uses 10 fingers ?
Typing.MANY MANY MANY people learn how to do it .
Some use 1 finger some use all ten .
Takes a bit of training but it works .
It looks like this is a few gestures ( 5 ?
) which people can learn .
It is not like remembering where all 26 letters and 10 numbers are , or remembering that part of the music is one half step down .
See the difference ?
I do see your point as many people can not even master drag and drop.I see a small trackpad with multi touch being useful .
It sure removes the 2 button limitation of the mouse that is for sure .</tokentext>
<sentencetext>You know what else uses 10 fingers?
Typing.MANY MANY MANY people learn how to do it.
Some use 1 finger some use all ten.
Takes a bit of training but it works.
It looks like this is a few gestures (5?
) which people can learn.
It is not like remembering where all 26 letters and 10 numbers are, or remembering that part of the music is one half step down.
See the difference?
I do see your point as many people can not even master drag and drop.I see a small trackpad with multi touch being useful.
It sure removes the 2 button limitation of the mouse that is for sure.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745705</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744567</id>
	<title>Similar to gestures on latest Apple MacBook Pro</title>
	<author>Anonymous</author>
	<datestamp>1255534500000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>In the end it looks like Apple is not far with the buttonless large touchpad featured on the latest MacBook pro, which permit gestures with up to 4 fingers that trigger expose, switch from applications, scroll documents and more.</htmltext>
<tokenext>In the end it looks like Apple is not far with the buttonless large touchpad featured on the latest MacBook pro , which permit gestures with up to 4 fingers that trigger expose , switch from applications , scroll documents and more .</tokentext>
<sentencetext>In the end it looks like Apple is not far with the buttonless large touchpad featured on the latest MacBook pro, which permit gestures with up to 4 fingers that trigger expose, switch from applications, scroll documents and more.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745111</id>
	<title>I can has?</title>
	<author>dorque\_wrench</author>
	<datestamp>1255536660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I like it. I want it. I just wish the keyboard was part of the touch interface, rather than a separate peripheral.</htmltext>
<tokenext>I like it .
I want it .
I just wish the keyboard was part of the touch interface , rather than a separate peripheral .</tokentext>
<sentencetext>I like it.
I want it.
I just wish the keyboard was part of the touch interface, rather than a separate peripheral.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744181</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>smitty777</author>
	<datestamp>1255532880000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>Another problem is the assumption of 10 digits.  For example, this might be more difficult for someone that is missing a digit or is paralyzed in an arm.  In that case, the mouse would have a definite advantage.</p></htmltext>
<tokenext>Another problem is the assumption of 10 digits .
For example , this might be more difficult for someone that is missing a digit or is paralyzed in an arm .
In that case , the mouse would have a definite advantage .</tokentext>
<sentencetext>Another problem is the assumption of 10 digits.
For example, this might be more difficult for someone that is missing a digit or is paralyzed in an arm.
In that case, the mouse would have a definite advantage.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748395</id>
	<title>Metaphor infinity</title>
	<author>ElitistWhiner</author>
	<datestamp>1255550700000</datestamp>
	<modclass>None</modclass>
	<modscore>2</modscore>
	<htmltext><p>Metaphors are held to the laws of physics, aging and death.  Witness crop of new gestures creeping up on desktop files and apps.</p><p>Transitional schemes bridge us to the next heuristic interface which hasn't evolved yet to mass market technology.</p><p>Voice<nobr> <wbr></nobr>.vs. touch will define the future as technology obviates the necessity to command<nobr> <wbr></nobr>.vs. control.</p></htmltext>
<tokenext>Metaphors are held to the laws of physics , aging and death .
Witness crop of new gestures creeping up on desktop files and apps.Transitional schemes bridge us to the next heuristic interface which has n't evolved yet to mass market technology.Voice .vs .
touch will define the future as technology obviates the necessity to command .vs .
control .</tokentext>
<sentencetext>Metaphors are held to the laws of physics, aging and death.
Witness crop of new gestures creeping up on desktop files and apps.Transitional schemes bridge us to the next heuristic interface which hasn't evolved yet to mass market technology.Voice .vs.
touch will define the future as technology obviates the necessity to command .vs.
control.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745239</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>Anonymous</author>
	<datestamp>1255537200000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>you could also possibly the multi-touch 'zoom' and 'pinch' actions like on the iPhone -- just zoom in if you need to get at small buttons / specific pixel placements</p></htmltext>
<tokenext>you could also possibly the multi-touch 'zoom ' and 'pinch ' actions like on the iPhone -- just zoom in if you need to get at small buttons / specific pixel placements</tokentext>
<sentencetext>you could also possibly the multi-touch 'zoom' and 'pinch' actions like on the iPhone -- just zoom in if you need to get at small buttons / specific pixel placements</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745963</id>
	<title>Not extremely impressive</title>
	<author>Anonymous</author>
	<datestamp>1255540080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It seems pretty conventional to me.  Nothing here that hasn't been talked about since the 80's.</p></htmltext>
<tokenext>It seems pretty conventional to me .
Nothing here that has n't been talked about since the 80 's .</tokentext>
<sentencetext>It seems pretty conventional to me.
Nothing here that hasn't been talked about since the 80's.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745583</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>Interoperable</author>
	<datestamp>1255538580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It seems to me that this type of technology, coupled with existing technology and much more customizable window mangers supporting multi-touch is the way to go. It's not a keyboard or a multi-touch, or a mouse or a multi-touch.</p><p>Why not have it all! You could have a mouse on a multi-touch pad and another pad below the keyboard that's however large you want it to be. You could have a standard cursor associated with the mouse and record finger presses beside the mouse. I can easily control the mouse with my palm and index finger and still have a thumb and three finger to accurately touch the mousepad for pinch zoom and application scrolling. Just bind the interface to do what you want for any given window management task or application task. In an FPS you could use the mouse for aim and hits on the multi-touch for leaning out from corners or weapon selection or whatever else you want.</p><p>More possibilities are never bad! I can't wait to use the full information bandwidth of my digits, I have dexterity to spare! I think that concepts like that are gonna make the future *awesome*, bring on the bandwidth!</p></htmltext>
<tokenext>It seems to me that this type of technology , coupled with existing technology and much more customizable window mangers supporting multi-touch is the way to go .
It 's not a keyboard or a multi-touch , or a mouse or a multi-touch.Why not have it all !
You could have a mouse on a multi-touch pad and another pad below the keyboard that 's however large you want it to be .
You could have a standard cursor associated with the mouse and record finger presses beside the mouse .
I can easily control the mouse with my palm and index finger and still have a thumb and three finger to accurately touch the mousepad for pinch zoom and application scrolling .
Just bind the interface to do what you want for any given window management task or application task .
In an FPS you could use the mouse for aim and hits on the multi-touch for leaning out from corners or weapon selection or whatever else you want.More possibilities are never bad !
I ca n't wait to use the full information bandwidth of my digits , I have dexterity to spare !
I think that concepts like that are gon na make the future * awesome * , bring on the bandwidth !</tokentext>
<sentencetext>It seems to me that this type of technology, coupled with existing technology and much more customizable window mangers supporting multi-touch is the way to go.
It's not a keyboard or a multi-touch, or a mouse or a multi-touch.Why not have it all!
You could have a mouse on a multi-touch pad and another pad below the keyboard that's however large you want it to be.
You could have a standard cursor associated with the mouse and record finger presses beside the mouse.
I can easily control the mouse with my palm and index finger and still have a thumb and three finger to accurately touch the mousepad for pinch zoom and application scrolling.
Just bind the interface to do what you want for any given window management task or application task.
In an FPS you could use the mouse for aim and hits on the multi-touch for leaning out from corners or weapon selection or whatever else you want.More possibilities are never bad!
I can't wait to use the full information bandwidth of my digits, I have dexterity to spare!
I think that concepts like that are gonna make the future *awesome*, bring on the bandwidth!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747603</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>lewiscr</author>
	<datestamp>1255547460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>It would also be quite impossible to play FPS or other kinds of games with this type of setup.</p></div><p>I said that about a mouse.  The serial mice of the time were utterly useless in a FPS.  Now look what happened.</p></div>
	</htmltext>
<tokenext>It would also be quite impossible to play FPS or other kinds of games with this type of setup.I said that about a mouse .
The serial mice of the time were utterly useless in a FPS .
Now look what happened .</tokentext>
<sentencetext>It would also be quite impossible to play FPS or other kinds of games with this type of setup.I said that about a mouse.
The serial mice of the time were utterly useless in a FPS.
Now look what happened.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746141</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>mofag</author>
	<datestamp>1255540800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I saw that too and immediately thought they need to split the touch pad - one half on each side of the keyboard. Also I'm not sure how thise would make best use of multiple monitors. I don't think I know anyone who uses just one monitor anymore.</p></htmltext>
<tokenext>I saw that too and immediately thought they need to split the touch pad - one half on each side of the keyboard .
Also I 'm not sure how thise would make best use of multiple monitors .
I do n't think I know anyone who uses just one monitor anymore .</tokentext>
<sentencetext>I saw that too and immediately thought they need to split the touch pad - one half on each side of the keyboard.
Also I'm not sure how thise would make best use of multiple monitors.
I don't think I know anyone who uses just one monitor anymore.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744727</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746127</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>Anonymous</author>
	<datestamp>1255540800000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I feel like your criticisms are short sighted:</p><p><div class="quote"><p> It's hard to do that with your fingers because the area they touch is a large one, it's not easy to just move your finger by one pixel</p> </div><p>Just off of the top of my head, I can imagine a 2 hand setup where one hand/finger selects the approximate area, and the other makes broad strokes which register and small movements on the screen.</p><p><div class="quote"><p>Other problem is that now your both hands lay on the wide touch area and you dont have a keyboard.<nobr> <wbr></nobr>... Typing on the touch area gives no feedback and again takes your hands of the "mouse"</p></div><p>Use 2 devices (keyboard &amp; mouse), use 1 with some sort of feedback (blackberry storm-esc).  Place a screen on the touchpad and see what you are typing.... it really doesn't matter.  The technology is already available to make this not only work, but work well (it does need to get cheaper on the other hand) - it is the software that really needs to catch up.</p><p>Don't dismiss this yet</p></div>
	</htmltext>
<tokenext>I feel like your criticisms are short sighted : It 's hard to do that with your fingers because the area they touch is a large one , it 's not easy to just move your finger by one pixel Just off of the top of my head , I can imagine a 2 hand setup where one hand/finger selects the approximate area , and the other makes broad strokes which register and small movements on the screen.Other problem is that now your both hands lay on the wide touch area and you dont have a keyboard .
... Typing on the touch area gives no feedback and again takes your hands of the " mouse " Use 2 devices ( keyboard &amp; mouse ) , use 1 with some sort of feedback ( blackberry storm-esc ) .
Place a screen on the touchpad and see what you are typing.... it really does n't matter .
The technology is already available to make this not only work , but work well ( it does need to get cheaper on the other hand ) - it is the software that really needs to catch up.Do n't dismiss this yet</tokentext>
<sentencetext>I feel like your criticisms are short sighted: It's hard to do that with your fingers because the area they touch is a large one, it's not easy to just move your finger by one pixel Just off of the top of my head, I can imagine a 2 hand setup where one hand/finger selects the approximate area, and the other makes broad strokes which register and small movements on the screen.Other problem is that now your both hands lay on the wide touch area and you dont have a keyboard.
... Typing on the touch area gives no feedback and again takes your hands of the "mouse"Use 2 devices (keyboard &amp; mouse), use 1 with some sort of feedback (blackberry storm-esc).
Place a screen on the touchpad and see what you are typing.... it really doesn't matter.
The technology is already available to make this not only work, but work well (it does need to get cheaper on the other hand) - it is the software that really needs to catch up.Don't dismiss this yet
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747685</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>physburn</author>
	<datestamp>1255547820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>If you need precise input on a touch surface, use a stylus or point pen,
but apart from art work, you won't need this.<p>
I like this GUI system, because you have multiple separate fingers you
can teach the system gesture short cuts which will let you navigate much
more quickly around you system. There's no reason why touch panels
shouldn't become even cheaper than mice. The only thing I didn't like
about the system in the video, was attaching the keyboard to the touch
panel, i'd much prefer them separate, and spaced at and angle around
the desktop.
</p><p>
Not only would it not be "impossible" to play FPS on such a system, it
would be easier and more fun. Turn you hand to turn your character,
flick a finger forward to shoot a gun. Walk two fingers along the pad
to walk/run. Finger combos to change weapons, or activate special
abilities. It would soon be more obvious than using a mouse.
</p><p>
An improvement to the system I like to see, would be to have another
screen on the touch panel, as well the screen above, to show
basic control patterns, this would make it more obvious what the
interactions with the pad would be like.
</p><p>
So having established this is a good idea. We need a standard
interface for multi-touch in Linux (and other OSs), and gesture library
that interoperates with standard GUI components. Probably most
GUI apps would have to be rewritten to get the most out of multi-touch
and gestures. But its a start.
</p><p>
---
</p><p>
<a href="http://www.feeddistiller.com/blogs/GUI\%20Design\%20and\%20Programming/feed.html" title="feeddistiller.com"> GUI Design and Programming</a> [feeddistiller.com] Feed @ <a href="http://www.feeddistiller.com/" title="feeddistiller.com">Feed Distiller</a> [feeddistiller.com]</p></htmltext>
<tokenext>If you need precise input on a touch surface , use a stylus or point pen , but apart from art work , you wo n't need this .
I like this GUI system , because you have multiple separate fingers you can teach the system gesture short cuts which will let you navigate much more quickly around you system .
There 's no reason why touch panels should n't become even cheaper than mice .
The only thing I did n't like about the system in the video , was attaching the keyboard to the touch panel , i 'd much prefer them separate , and spaced at and angle around the desktop .
Not only would it not be " impossible " to play FPS on such a system , it would be easier and more fun .
Turn you hand to turn your character , flick a finger forward to shoot a gun .
Walk two fingers along the pad to walk/run .
Finger combos to change weapons , or activate special abilities .
It would soon be more obvious than using a mouse .
An improvement to the system I like to see , would be to have another screen on the touch panel , as well the screen above , to show basic control patterns , this would make it more obvious what the interactions with the pad would be like .
So having established this is a good idea .
We need a standard interface for multi-touch in Linux ( and other OSs ) , and gesture library that interoperates with standard GUI components .
Probably most GUI apps would have to be rewritten to get the most out of multi-touch and gestures .
But its a start .
--- GUI Design and Programming [ feeddistiller.com ] Feed @ Feed Distiller [ feeddistiller.com ]</tokentext>
<sentencetext>If you need precise input on a touch surface, use a stylus or point pen,
but apart from art work, you won't need this.
I like this GUI system, because you have multiple separate fingers you
can teach the system gesture short cuts which will let you navigate much
more quickly around you system.
There's no reason why touch panels
shouldn't become even cheaper than mice.
The only thing I didn't like
about the system in the video, was attaching the keyboard to the touch
panel, i'd much prefer them separate, and spaced at and angle around
the desktop.
Not only would it not be "impossible" to play FPS on such a system, it
would be easier and more fun.
Turn you hand to turn your character,
flick a finger forward to shoot a gun.
Walk two fingers along the pad
to walk/run.
Finger combos to change weapons, or activate special
abilities.
It would soon be more obvious than using a mouse.
An improvement to the system I like to see, would be to have another
screen on the touch panel, as well the screen above, to show
basic control patterns, this would make it more obvious what the
interactions with the pad would be like.
So having established this is a good idea.
We need a standard
interface for multi-touch in Linux (and other OSs), and gesture library
that interoperates with standard GUI components.
Probably most
GUI apps would have to be rewritten to get the most out of multi-touch
and gestures.
But its a start.
---

 GUI Design and Programming [feeddistiller.com] Feed @ Feed Distiller [feeddistiller.com]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744933</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>naasking</author>
	<datestamp>1255535940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>For one, mouse is an incredibly precise input device - you can pretty easily move it along same pixel axis, or get it precisely to a specific pixel.</i></p><p>I think the existence of touchpads that have already replaced mice on all portable computers demonstrates that a touch surface can be almost as precise as a mouse. Certainly there are some input activities that require even more control, but there are simple solutions: a) these activities require a more precise pointing device, or b) use the zoom gesture to zoom into an area where you need to exert finer control.</p><p>There are similar solutions to you other concerns.</p></htmltext>
<tokenext>For one , mouse is an incredibly precise input device - you can pretty easily move it along same pixel axis , or get it precisely to a specific pixel.I think the existence of touchpads that have already replaced mice on all portable computers demonstrates that a touch surface can be almost as precise as a mouse .
Certainly there are some input activities that require even more control , but there are simple solutions : a ) these activities require a more precise pointing device , or b ) use the zoom gesture to zoom into an area where you need to exert finer control.There are similar solutions to you other concerns .</tokentext>
<sentencetext>For one, mouse is an incredibly precise input device - you can pretty easily move it along same pixel axis, or get it precisely to a specific pixel.I think the existence of touchpads that have already replaced mice on all portable computers demonstrates that a touch surface can be almost as precise as a mouse.
Certainly there are some input activities that require even more control, but there are simple solutions: a) these activities require a more precise pointing device, or b) use the zoom gesture to zoom into an area where you need to exert finer control.There are similar solutions to you other concerns.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744983</id>
	<title>Palm Pre</title>
	<author>Anonymous</author>
	<datestamp>1255536180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Looking through the examples it looks as though most of this interface has been accomplished with the Palm Pre already.  Sliding windows multitasking, check.  Multitouch input... check.  Gesture area for system menus outside of the screen... check.</p></htmltext>
<tokenext>Looking through the examples it looks as though most of this interface has been accomplished with the Palm Pre already .
Sliding windows multitasking , check .
Multitouch input... check. Gesture area for system menus outside of the screen... check .</tokentext>
<sentencetext>Looking through the examples it looks as though most of this interface has been accomplished with the Palm Pre already.
Sliding windows multitasking, check.
Multitouch input... check.  Gesture area for system menus outside of the screen... check.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744715</id>
	<title>Keyboard</title>
	<author>bWareiWare.co.uk</author>
	<datestamp>1255535040000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>1</modscore>
	<htmltext><p>Next they will introduce a non-Cartesian grid of ridges with hybrid haptic and aural feedback, featuring standardized cartographic symbols.</p><p>Unfortunately IBM may have some prior-art with their model-M.</p></htmltext>
<tokenext>Next they will introduce a non-Cartesian grid of ridges with hybrid haptic and aural feedback , featuring standardized cartographic symbols.Unfortunately IBM may have some prior-art with their model-M .</tokentext>
<sentencetext>Next they will introduce a non-Cartesian grid of ridges with hybrid haptic and aural feedback, featuring standardized cartographic symbols.Unfortunately IBM may have some prior-art with their model-M.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744155</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>LBt1st</author>
	<datestamp>1255532760000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p>At the very end of the video they show a keyboard positioned over the touchpad. So I don't think they're trying to eliminate the keyboard entirely.</p><p>Still you've got many valid points. The mouse is still a much needed tool for many tasks.</p></htmltext>
<tokenext>At the very end of the video they show a keyboard positioned over the touchpad .
So I do n't think they 're trying to eliminate the keyboard entirely.Still you 've got many valid points .
The mouse is still a much needed tool for many tasks .</tokentext>
<sentencetext>At the very end of the video they show a keyboard positioned over the touchpad.
So I don't think they're trying to eliminate the keyboard entirely.Still you've got many valid points.
The mouse is still a much needed tool for many tasks.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29751695</id>
	<title>Re:Replacing current business work interface</title>
	<author>leftie</author>
	<datestamp>1255526040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>What can be done to create an input device with natural rest position of hands. Thumbs up. Palms facing together. Fingers curved. ??</p><p>With all the new materials, doesn't seem that tough to make.</p></htmltext>
<tokenext>What can be done to create an input device with natural rest position of hands .
Thumbs up .
Palms facing together .
Fingers curved .
? ? With all the new materials , does n't seem that tough to make .</tokentext>
<sentencetext>What can be done to create an input device with natural rest position of hands.
Thumbs up.
Palms facing together.
Fingers curved.
??With all the new materials, doesn't seem that tough to make.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744371</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745943</id>
	<title>Re:going in circles</title>
	<author>kLaNk</author>
	<datestamp>1255540020000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>FingerWorks' primary product was just like what 10/GUI describes: a multitouch surface that could either replace they keyboard or the mouse(pad). It largely failed in the market.</p></div><p>Personally, I feel that it largely failed because it attempted to replace a keyboard with a device that had no tactile feedback. Despite my best efforts I could never get anywhere close in typing speed (and my error rate went WAY up).</p><p>However, the actual multi-touch navigation improvements were awesome. Part of the reason I tried so damn hard to learn to type well on it (and I never could) was because of all the other benefits it offered.</p></div>
	</htmltext>
<tokenext>FingerWorks ' primary product was just like what 10/GUI describes : a multitouch surface that could either replace they keyboard or the mouse ( pad ) .
It largely failed in the market.Personally , I feel that it largely failed because it attempted to replace a keyboard with a device that had no tactile feedback .
Despite my best efforts I could never get anywhere close in typing speed ( and my error rate went WAY up ) .However , the actual multi-touch navigation improvements were awesome .
Part of the reason I tried so damn hard to learn to type well on it ( and I never could ) was because of all the other benefits it offered .</tokentext>
<sentencetext>FingerWorks' primary product was just like what 10/GUI describes: a multitouch surface that could either replace they keyboard or the mouse(pad).
It largely failed in the market.Personally, I feel that it largely failed because it attempted to replace a keyboard with a device that had no tactile feedback.
Despite my best efforts I could never get anywhere close in typing speed (and my error rate went WAY up).However, the actual multi-touch navigation improvements were awesome.
Part of the reason I tried so damn hard to learn to type well on it (and I never could) was because of all the other benefits it offered.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744657</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748447</id>
	<title>Re:some subtle hints in that presentation</title>
	<author>Anonymous</author>
	<datestamp>1255550940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Considering as it looked a lot like KDE with a touchpad....</p></htmltext>
<tokenext>Considering as it looked a lot like KDE with a touchpad... .</tokentext>
<sentencetext>Considering as it looked a lot like KDE with a touchpad....</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744325</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746355</id>
	<title>Do Not Touch</title>
	<author>e2d2</author>
	<datestamp>1255541760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I've said it before and I'll say it again - get your greasy stinky corn chip covered fingers off my screen. Now get out of here and do not cross my lawn!</htmltext>
<tokenext>I 've said it before and I 'll say it again - get your greasy stinky corn chip covered fingers off my screen .
Now get out of here and do not cross my lawn !</tokentext>
<sentencetext>I've said it before and I'll say it again - get your greasy stinky corn chip covered fingers off my screen.
Now get out of here and do not cross my lawn!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29759883</id>
	<title>Can this techincally work?</title>
	<author>radiorental</author>
	<datestamp>1255632420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I have a question about the feasibility of the design.  As I understand the video a user rests their hands on the 10gui input device and the capacitive sensor detects the positions of those ten fingers.  Pretty normal multitouch so far.  Where the 10gui design is innovative is the combination of the resistive layer to detect 'clicks'.  If you watch the video at 5 minutes you'll see what I'm talking about and where I'd like to understand how this is being done.

The problem is, you cannot detect multiple presses with a resistive layer - that's a basic limitation of that tech and no way around it afaik.

My initial reaction to this was to think 'hey, this is just a concept for now, lets look in to the boring details later' so I went back and did some research on the other multiple touch sensor technologies and found a very interesting problem.  A very fundamental problem too!

Take a look at this video <a href="http://cs.nyu.edu/~jhan/ftirsense/" title="nyu.edu" rel="nofollow">http://cs.nyu.edu/~jhan/ftirsense/</a> [nyu.edu]

So, all the other multitouch sensors are optical - That I've found, and I would dearly love to be corrected! - are optical.  So the fundamental problem is how do you 'see' the difference between a user resting their fingers on a surface and the user pressing down on the surface.  You need to use two very different technologies - as 10gui proposes.  But, all the other technologies are single touch only.

I use a multitouch sensor for my desktop (wacom bamboo 8x5) and it is tiring as hell to hover your hands above the input device.  The only way these device will work is as demoed in the video.  However, I dont think its technically possible.</htmltext>
<tokenext>I have a question about the feasibility of the design .
As I understand the video a user rests their hands on the 10gui input device and the capacitive sensor detects the positions of those ten fingers .
Pretty normal multitouch so far .
Where the 10gui design is innovative is the combination of the resistive layer to detect 'clicks' .
If you watch the video at 5 minutes you 'll see what I 'm talking about and where I 'd like to understand how this is being done .
The problem is , you can not detect multiple presses with a resistive layer - that 's a basic limitation of that tech and no way around it afaik .
My initial reaction to this was to think 'hey , this is just a concept for now , lets look in to the boring details later ' so I went back and did some research on the other multiple touch sensor technologies and found a very interesting problem .
A very fundamental problem too !
Take a look at this video http : //cs.nyu.edu/ ~ jhan/ftirsense/ [ nyu.edu ] So , all the other multitouch sensors are optical - That I 've found , and I would dearly love to be corrected !
- are optical .
So the fundamental problem is how do you 'see ' the difference between a user resting their fingers on a surface and the user pressing down on the surface .
You need to use two very different technologies - as 10gui proposes .
But , all the other technologies are single touch only .
I use a multitouch sensor for my desktop ( wacom bamboo 8x5 ) and it is tiring as hell to hover your hands above the input device .
The only way these device will work is as demoed in the video .
However , I dont think its technically possible .</tokentext>
<sentencetext>I have a question about the feasibility of the design.
As I understand the video a user rests their hands on the 10gui input device and the capacitive sensor detects the positions of those ten fingers.
Pretty normal multitouch so far.
Where the 10gui design is innovative is the combination of the resistive layer to detect 'clicks'.
If you watch the video at 5 minutes you'll see what I'm talking about and where I'd like to understand how this is being done.
The problem is, you cannot detect multiple presses with a resistive layer - that's a basic limitation of that tech and no way around it afaik.
My initial reaction to this was to think 'hey, this is just a concept for now, lets look in to the boring details later' so I went back and did some research on the other multiple touch sensor technologies and found a very interesting problem.
A very fundamental problem too!
Take a look at this video http://cs.nyu.edu/~jhan/ftirsense/ [nyu.edu]

So, all the other multitouch sensors are optical - That I've found, and I would dearly love to be corrected!
- are optical.
So the fundamental problem is how do you 'see' the difference between a user resting their fingers on a surface and the user pressing down on the surface.
You need to use two very different technologies - as 10gui proposes.
But, all the other technologies are single touch only.
I use a multitouch sensor for my desktop (wacom bamboo 8x5) and it is tiring as hell to hover your hands above the input device.
The only way these device will work is as demoed in the video.
However, I dont think its technically possible.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748227</id>
	<title>Re:Virtuoso Users only!</title>
	<author>Anonymous</author>
	<datestamp>1255550100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><blockquote><div><p>I'm more in favor of multiple monitors</p></div></blockquote><p>Use a <a href="http://en.wikipedia.org/wiki/Tiling\_window\_manager" title="wikipedia.org" rel="nofollow">tiling window manager</a> [wikipedia.org] and save yourself some money, electricity, desk space, neck strain,<nobr> <wbr></nobr>...</p></div>
	</htmltext>
<tokenext>I 'm more in favor of multiple monitorsUse a tiling window manager [ wikipedia.org ] and save yourself some money , electricity , desk space , neck strain , .. .</tokentext>
<sentencetext>I'm more in favor of multiple monitorsUse a tiling window manager [wikipedia.org] and save yourself some money, electricity, desk space, neck strain, ...
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744653</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29751325</id>
	<title>Sounds like DasKeyboard to me</title>
	<author>Anonymous</author>
	<datestamp>1255522680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I don't agree at all with their conception that the control surface and the display should be separated.  I'd argue that the display should continue on to the touch surface, allowing both to be used.  After all, you don't see many people using keyboards without key caps, or light boards without captioned buttons, or audio mixers without labels, even if they are as simple as colors on the knobs.</p><p>Removing any sense of context whatsoever, and therefore having to devote more of the vertical display surface to controls such as a virtual keyboard (sans physical feedback), or a virtual palette of actions, is a waste of valuable space and would also serve to dramatically reduce input accuracy.</p><p>Give me a keyboard and a screen on the desk with a context sensitive multitouch interface and I think it would be significantly more usable than this video concept.</p></htmltext>
<tokenext>I do n't agree at all with their conception that the control surface and the display should be separated .
I 'd argue that the display should continue on to the touch surface , allowing both to be used .
After all , you do n't see many people using keyboards without key caps , or light boards without captioned buttons , or audio mixers without labels , even if they are as simple as colors on the knobs.Removing any sense of context whatsoever , and therefore having to devote more of the vertical display surface to controls such as a virtual keyboard ( sans physical feedback ) , or a virtual palette of actions , is a waste of valuable space and would also serve to dramatically reduce input accuracy.Give me a keyboard and a screen on the desk with a context sensitive multitouch interface and I think it would be significantly more usable than this video concept .</tokentext>
<sentencetext>I don't agree at all with their conception that the control surface and the display should be separated.
I'd argue that the display should continue on to the touch surface, allowing both to be used.
After all, you don't see many people using keyboards without key caps, or light boards without captioned buttons, or audio mixers without labels, even if they are as simple as colors on the knobs.Removing any sense of context whatsoever, and therefore having to devote more of the vertical display surface to controls such as a virtual keyboard (sans physical feedback), or a virtual palette of actions, is a waste of valuable space and would also serve to dramatically reduce input accuracy.Give me a keyboard and a screen on the desk with a context sensitive multitouch interface and I think it would be significantly more usable than this video concept.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746929</id>
	<title>Could do this with a Touchco sensor</title>
	<author>Anonymous</author>
	<datestamp>1255544580000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>This could actually work if you used a Touchco multi-touch resistive sensor (http://www.touchco.com/tech.html) because they have precise tracking resolution plus true pressure sensitivity.</p></htmltext>
<tokenext>This could actually work if you used a Touchco multi-touch resistive sensor ( http : //www.touchco.com/tech.html ) because they have precise tracking resolution plus true pressure sensitivity .</tokentext>
<sentencetext>This could actually work if you used a Touchco multi-touch resistive sensor (http://www.touchco.com/tech.html) because they have precise tracking resolution plus true pressure sensitivity.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29751679</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>FelixNZ</author>
	<datestamp>1255525920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>How on earth did you miss "Playing the drums with only one arm"?!</htmltext>
<tokenext>How on earth did you miss " Playing the drums with only one arm " ?
!</tokentext>
<sentencetext>How on earth did you miss "Playing the drums with only one arm"?
!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744809</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745633</id>
	<title>Doesn't work for windows of different scale....</title>
	<author>hrpatton</author>
	<datestamp>1255538760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The linear one-axis window presentation doesn't deal with windows that need to be spatially arranged in other ways.  This is problematic for windows of different scale in simultaneous use.
<p>
Real example:  I recently edited a photograph portrait to fix some glitches around the subject's eyes.  I had a 1:1 view of the photo in a window at the top of my screen, and a zoomed-in version of just the eyes in another window at the bottom.  This enabled me to make fine edits to the eyes and see what they looked like in the original scale.  The zoomed window needed to span the entire width of the screen because<nobr> <wbr></nobr>... well, eyes are wider than they are tall.  Had the windows been organized side-by-side, I'd have had to scale down the view of the eyes to fit the narrower window.  The window manager would thus be dictating the scale at which I can work in a way that a more flexible manager would not.
</p><p>
This would be a problem in 3D apps, too, in which users often need multiple views of the same object simultaneously.  If I want to see a model of a head, let's say, from front, back, top, and side views, I need to arrange the windows accordingly.  I'd go insane trying to look at them all in tall, side-by-side windows.
</p><p>
And what about apps with tool palettes or timelines?  Where do those go?  Spacial arrangement is key for these UI elements.  Does each window get its own?
</p><p>
The interface as proposed is fine for regular desktop use, but it just doesn't work for windows that need different (x,y) sizing while appearing on the same screen.
</p><p>
Now, if we could have a window mosaic instead of a strip, we'd be getting somewhere.</p></htmltext>
<tokenext>The linear one-axis window presentation does n't deal with windows that need to be spatially arranged in other ways .
This is problematic for windows of different scale in simultaneous use .
Real example : I recently edited a photograph portrait to fix some glitches around the subject 's eyes .
I had a 1 : 1 view of the photo in a window at the top of my screen , and a zoomed-in version of just the eyes in another window at the bottom .
This enabled me to make fine edits to the eyes and see what they looked like in the original scale .
The zoomed window needed to span the entire width of the screen because ... well , eyes are wider than they are tall .
Had the windows been organized side-by-side , I 'd have had to scale down the view of the eyes to fit the narrower window .
The window manager would thus be dictating the scale at which I can work in a way that a more flexible manager would not .
This would be a problem in 3D apps , too , in which users often need multiple views of the same object simultaneously .
If I want to see a model of a head , let 's say , from front , back , top , and side views , I need to arrange the windows accordingly .
I 'd go insane trying to look at them all in tall , side-by-side windows .
And what about apps with tool palettes or timelines ?
Where do those go ?
Spacial arrangement is key for these UI elements .
Does each window get its own ?
The interface as proposed is fine for regular desktop use , but it just does n't work for windows that need different ( x,y ) sizing while appearing on the same screen .
Now , if we could have a window mosaic instead of a strip , we 'd be getting somewhere .</tokentext>
<sentencetext>The linear one-axis window presentation doesn't deal with windows that need to be spatially arranged in other ways.
This is problematic for windows of different scale in simultaneous use.
Real example:  I recently edited a photograph portrait to fix some glitches around the subject's eyes.
I had a 1:1 view of the photo in a window at the top of my screen, and a zoomed-in version of just the eyes in another window at the bottom.
This enabled me to make fine edits to the eyes and see what they looked like in the original scale.
The zoomed window needed to span the entire width of the screen because ... well, eyes are wider than they are tall.
Had the windows been organized side-by-side, I'd have had to scale down the view of the eyes to fit the narrower window.
The window manager would thus be dictating the scale at which I can work in a way that a more flexible manager would not.
This would be a problem in 3D apps, too, in which users often need multiple views of the same object simultaneously.
If I want to see a model of a head, let's say, from front, back, top, and side views, I need to arrange the windows accordingly.
I'd go insane trying to look at them all in tall, side-by-side windows.
And what about apps with tool palettes or timelines?
Where do those go?
Spacial arrangement is key for these UI elements.
Does each window get its own?
The interface as proposed is fine for regular desktop use, but it just doesn't work for windows that need different (x,y) sizing while appearing on the same screen.
Now, if we could have a window mosaic instead of a strip, we'd be getting somewhere.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29750929</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>thethibs</author>
	<datestamp>1255520040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Different strokes...The keyboard in the video is where my keyboard is (elbows on the desk means no CTS). The difference is I have bare wood where they have the touch pad.</p><p>For me the configuration is ideal. Using the pad just requires leaning back in my chair, just as I do when all I need is the mouse.</p></htmltext>
<tokenext>Different strokes...The keyboard in the video is where my keyboard is ( elbows on the desk means no CTS ) .
The difference is I have bare wood where they have the touch pad.For me the configuration is ideal .
Using the pad just requires leaning back in my chair , just as I do when all I need is the mouse .</tokentext>
<sentencetext>Different strokes...The keyboard in the video is where my keyboard is (elbows on the desk means no CTS).
The difference is I have bare wood where they have the touch pad.For me the configuration is ideal.
Using the pad just requires leaning back in my chair, just as I do when all I need is the mouse.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744727</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744801</id>
	<title>carpal tunnel?</title>
	<author>poetmatt</author>
	<datestamp>1255535400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This thing has RSI and carpal tunnel written all over it, even though it's a creative idea.</p></htmltext>
<tokenext>This thing has RSI and carpal tunnel written all over it , even though it 's a creative idea .</tokentext>
<sentencetext>This thing has RSI and carpal tunnel written all over it, even though it's a creative idea.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29753807</id>
	<title>Re:Virtuoso Users only!</title>
	<author>Anonymous</author>
	<datestamp>1255547100000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>Not sure I totally agree.  Look and how quickly people took to the iPhone and iTouch gestures.  This is just another set of rather simple gestures with a new paradigm on window manipulation.</p></htmltext>
<tokenext>Not sure I totally agree .
Look and how quickly people took to the iPhone and iTouch gestures .
This is just another set of rather simple gestures with a new paradigm on window manipulation .</tokentext>
<sentencetext>Not sure I totally agree.
Look and how quickly people took to the iPhone and iTouch gestures.
This is just another set of rather simple gestures with a new paradigm on window manipulation.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744653</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29758153</id>
	<title>Solution: Touch-sensitive keyboard + mouse</title>
	<author>Dalzhim</author>
	<datestamp>1255624920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Why would we need to place both hands on such a pad? I can easily imagine myself using a single hand on such a pad while still having my other hand on the mouse for finer control. I think the idea is to have the choice between the keyboard and the pad in order to better adapt to various situations.<br>
<br>
In order to prevent having to switch from keyboard to pad as we already do with the mouse, we could even make a keyboard that has touch-sensitive keys. When you just drag your hand over the keys without pressing them, you could use the keyboard just as one would use the pad, and when you press the keys you get normal keyboard usage.</htmltext>
<tokenext>Why would we need to place both hands on such a pad ?
I can easily imagine myself using a single hand on such a pad while still having my other hand on the mouse for finer control .
I think the idea is to have the choice between the keyboard and the pad in order to better adapt to various situations .
In order to prevent having to switch from keyboard to pad as we already do with the mouse , we could even make a keyboard that has touch-sensitive keys .
When you just drag your hand over the keys without pressing them , you could use the keyboard just as one would use the pad , and when you press the keys you get normal keyboard usage .</tokentext>
<sentencetext>Why would we need to place both hands on such a pad?
I can easily imagine myself using a single hand on such a pad while still having my other hand on the mouse for finer control.
I think the idea is to have the choice between the keyboard and the pad in order to better adapt to various situations.
In order to prevent having to switch from keyboard to pad as we already do with the mouse, we could even make a keyboard that has touch-sensitive keys.
When you just drag your hand over the keys without pressing them, you could use the keyboard just as one would use the pad, and when you press the keys you get normal keyboard usage.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747115</id>
	<title>George Orwell teaches 10GUI to his mother</title>
	<author>greyhueofdoubt</author>
	<datestamp>1255545360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>George Orwell teaches 10GUI to his mother:</p><p>"Four fingers good, two fingers bad!"</p><p>No but seriously, if my mom ever asked me about this, I'd have to tell her to stay away from it. If people can't remember the commands for copy and paste, there is no way they can keep track of 8-10 fingers all at once.</p><p>-b</p></htmltext>
<tokenext>George Orwell teaches 10GUI to his mother : " Four fingers good , two fingers bad !
" No but seriously , if my mom ever asked me about this , I 'd have to tell her to stay away from it .
If people ca n't remember the commands for copy and paste , there is no way they can keep track of 8-10 fingers all at once.-b</tokentext>
<sentencetext>George Orwell teaches 10GUI to his mother:"Four fingers good, two fingers bad!
"No but seriously, if my mom ever asked me about this, I'd have to tell her to stay away from it.
If people can't remember the commands for copy and paste, there is no way they can keep track of 8-10 fingers all at once.-b</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744177</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>Canazza</author>
	<datestamp>1255532820000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>the final few seconds of the vid shows it as a suppliment to a keyboard (below it)<br>so while you're using WASD for movement you can still use the pad like a mouse</p><p>OR you can use the left hand for movement on the pad (splitting the left side into Forward/back/left/right sections) totally ignoring the keyboard. Combine it with it's own thin screen below it to display custom click areas, and boom! FPS.<br>Could even replace the keyboard in that case</p></htmltext>
<tokenext>the final few seconds of the vid shows it as a suppliment to a keyboard ( below it ) so while you 're using WASD for movement you can still use the pad like a mouseOR you can use the left hand for movement on the pad ( splitting the left side into Forward/back/left/right sections ) totally ignoring the keyboard .
Combine it with it 's own thin screen below it to display custom click areas , and boom !
FPS.Could even replace the keyboard in that case</tokentext>
<sentencetext>the final few seconds of the vid shows it as a suppliment to a keyboard (below it)so while you're using WASD for movement you can still use the pad like a mouseOR you can use the left hand for movement on the pad (splitting the left side into Forward/back/left/right sections) totally ignoring the keyboard.
Combine it with it's own thin screen below it to display custom click areas, and boom!
FPS.Could even replace the keyboard in that case</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744517</id>
	<title>Three observations.</title>
	<author>wadam</author>
	<datestamp>1255534260000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>I really like the idea, but not so much the implementation.  Two observations, and one theoretical quibble:
<br> <br>
1) On the hardware side, turning the multitouch interface into a second touch screen that could work as a mouse-like input device (like the video shows), or bring up a keyboard (like the lower half of the iphone, only taking up the whole space) would be preferable.  A keyboard without physical feedback would be awkward at first, but after getting used to it, you could do away with a physical keyboard entirely.  You could also stick meta-materials from the UI down there.  You could have something like a system dock with quick links to open programs and switch windows.  And you could have, say, the clock, wireless indicator, battery indicator, etc. down there.  It would cut down on clutter on the main screen.
<br> <br>
2)  On the software side, I'm not sure that I see the advantage of their version of a linear window manager the way they have it set up.  Instead, it seems more useful to fan applications in and out, turning the name bars on the side into tabs.  Window one opens and slips into place with its name bar on the left side of the screen.  Window two opens from the right, partially obscuring window one.  Window three moves window two all the way to the left, leaving window one entirely obscured, except for a tab.  And so on.  That way, you have a visual representation of every window on the screen at all times.  Much simpler to track than having to zoom out.
<br> <br>
And my theoretical quibble:  I know, it's odd coming from a longtime mac user, but I dislike the concept of a physical UI so closely tied to a particular software system that you have no alternative but to use them together.  I look at this, and I fear "The Windows Computer of the Future."  You buy a multi-touch computer that has Microsoft's future OS on it, and the hardware interface is so specific that you couldn't, if you wanted, chuck the software and install Linux.  I can imagine a Linux-like alternative being written for this interface.  But I can also imagine a set of patents that would encumber alternate OSes, such that you end up with a One Computer One OS system.  Which is far, far too restrictive, and invites vertical monopolistic practices.</htmltext>
<tokenext>I really like the idea , but not so much the implementation .
Two observations , and one theoretical quibble : 1 ) On the hardware side , turning the multitouch interface into a second touch screen that could work as a mouse-like input device ( like the video shows ) , or bring up a keyboard ( like the lower half of the iphone , only taking up the whole space ) would be preferable .
A keyboard without physical feedback would be awkward at first , but after getting used to it , you could do away with a physical keyboard entirely .
You could also stick meta-materials from the UI down there .
You could have something like a system dock with quick links to open programs and switch windows .
And you could have , say , the clock , wireless indicator , battery indicator , etc .
down there .
It would cut down on clutter on the main screen .
2 ) On the software side , I 'm not sure that I see the advantage of their version of a linear window manager the way they have it set up .
Instead , it seems more useful to fan applications in and out , turning the name bars on the side into tabs .
Window one opens and slips into place with its name bar on the left side of the screen .
Window two opens from the right , partially obscuring window one .
Window three moves window two all the way to the left , leaving window one entirely obscured , except for a tab .
And so on .
That way , you have a visual representation of every window on the screen at all times .
Much simpler to track than having to zoom out .
And my theoretical quibble : I know , it 's odd coming from a longtime mac user , but I dislike the concept of a physical UI so closely tied to a particular software system that you have no alternative but to use them together .
I look at this , and I fear " The Windows Computer of the Future .
" You buy a multi-touch computer that has Microsoft 's future OS on it , and the hardware interface is so specific that you could n't , if you wanted , chuck the software and install Linux .
I can imagine a Linux-like alternative being written for this interface .
But I can also imagine a set of patents that would encumber alternate OSes , such that you end up with a One Computer One OS system .
Which is far , far too restrictive , and invites vertical monopolistic practices .</tokentext>
<sentencetext>I really like the idea, but not so much the implementation.
Two observations, and one theoretical quibble:
 
1) On the hardware side, turning the multitouch interface into a second touch screen that could work as a mouse-like input device (like the video shows), or bring up a keyboard (like the lower half of the iphone, only taking up the whole space) would be preferable.
A keyboard without physical feedback would be awkward at first, but after getting used to it, you could do away with a physical keyboard entirely.
You could also stick meta-materials from the UI down there.
You could have something like a system dock with quick links to open programs and switch windows.
And you could have, say, the clock, wireless indicator, battery indicator, etc.
down there.
It would cut down on clutter on the main screen.
2)  On the software side, I'm not sure that I see the advantage of their version of a linear window manager the way they have it set up.
Instead, it seems more useful to fan applications in and out, turning the name bars on the side into tabs.
Window one opens and slips into place with its name bar on the left side of the screen.
Window two opens from the right, partially obscuring window one.
Window three moves window two all the way to the left, leaving window one entirely obscured, except for a tab.
And so on.
That way, you have a visual representation of every window on the screen at all times.
Much simpler to track than having to zoom out.
And my theoretical quibble:  I know, it's odd coming from a longtime mac user, but I dislike the concept of a physical UI so closely tied to a particular software system that you have no alternative but to use them together.
I look at this, and I fear "The Windows Computer of the Future.
"  You buy a multi-touch computer that has Microsoft's future OS on it, and the hardware interface is so specific that you couldn't, if you wanted, chuck the software and install Linux.
I can imagine a Linux-like alternative being written for this interface.
But I can also imagine a set of patents that would encumber alternate OSes, such that you end up with a One Computer One OS system.
Which is far, far too restrictive, and invites vertical monopolistic practices.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745227</id>
	<title>Put it on both sides of the keyboard</title>
	<author>MadLad</author>
	<datestamp>1255537140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This looks really great. But for me, a mistake is that the touchpad is in front of the keyboard. You have to move your arms forward and back when you want to switch; using one hand on each is tricky if the touchpad registers your dangling sleeve or your wrist.<br> <br>

I think it would be much better if the total area of the touchpad was split between the two side of the keyboard. Then you could have both hands on the touchpad or one on the touchpad and one on the keyboard, and you wouldn't have to do the forward-back thing with your arms.</htmltext>
<tokenext>This looks really great .
But for me , a mistake is that the touchpad is in front of the keyboard .
You have to move your arms forward and back when you want to switch ; using one hand on each is tricky if the touchpad registers your dangling sleeve or your wrist .
I think it would be much better if the total area of the touchpad was split between the two side of the keyboard .
Then you could have both hands on the touchpad or one on the touchpad and one on the keyboard , and you would n't have to do the forward-back thing with your arms .</tokentext>
<sentencetext>This looks really great.
But for me, a mistake is that the touchpad is in front of the keyboard.
You have to move your arms forward and back when you want to switch; using one hand on each is tricky if the touchpad registers your dangling sleeve or your wrist.
I think it would be much better if the total area of the touchpad was split between the two side of the keyboard.
Then you could have both hands on the touchpad or one on the touchpad and one on the keyboard, and you wouldn't have to do the forward-back thing with your arms.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744321</id>
	<title>VT100</title>
	<author>thomasdz</author>
	<datestamp>1255533480000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p>I like my GUI text-only, 80 characters wide by 25 lines long.  The way Ghod intended.<br>oh yeah and 7-bit ASCII only... none of this fancy schmancy 8-bit extended code-page goop.<br>and GET OFF MY LAWN!  Damn kids with their game boys.</p></htmltext>
<tokenext>I like my GUI text-only , 80 characters wide by 25 lines long .
The way Ghod intended.oh yeah and 7-bit ASCII only... none of this fancy schmancy 8-bit extended code-page goop.and GET OFF MY LAWN !
Damn kids with their game boys .</tokentext>
<sentencetext>I like my GUI text-only, 80 characters wide by 25 lines long.
The way Ghod intended.oh yeah and 7-bit ASCII only... none of this fancy schmancy 8-bit extended code-page goop.and GET OFF MY LAWN!
Damn kids with their game boys.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29767181</id>
	<title>Early adopters already have multi-touch</title>
	<author>me-g33k</author>
	<datestamp>1255696620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This is a nice revisit to the technology but even now I am using a multi-touch interface to type this comment. I was luck enough to be an early adopter and have a few of the now defunct FingerWorks LLP products. Notably my two TouchStream LPs and an iGesture pad.  Unlike the displayed product my keyboard/mouse has two pads and is arranged in an ergonomic arrangement (see image: <a href="http://pcworld.in/uploads/images/pcworld/4915355\_15.jpg" title="pcworld.in" rel="nofollow">http://pcworld.in/uploads/images/pcworld/4915355\_15.jpg</a> [pcworld.in]).</p><p>There are some finger markers to let you find the home row by touch. I move the mouse with two fingers on the right side of the screen and control the cursor in applications with two fingers on the right. There are a number of programmed gestures that allow for a great deal of task automation in stead of multiple click and drags.</p><p>I love the device but it does have limitations. Response time is not so great for gaming as you have the Gesture interpreter layer to contend with. There is a game mode for the device but I've rarely used it. I still mis-type a lot but then the driver also helps and makes a lot of corrections automatically based on what word I am typing. In my case it's usually about 90\% correct when it fixes my typos.</p><p>I loved the GUI interaction metaphors that the video describes. I hope that older versions of devices like the one I have will get grandfathered in to design considerations or even further development!</p></htmltext>
<tokenext>This is a nice revisit to the technology but even now I am using a multi-touch interface to type this comment .
I was luck enough to be an early adopter and have a few of the now defunct FingerWorks LLP products .
Notably my two TouchStream LPs and an iGesture pad .
Unlike the displayed product my keyboard/mouse has two pads and is arranged in an ergonomic arrangement ( see image : http : //pcworld.in/uploads/images/pcworld/4915355 \ _15.jpg [ pcworld.in ] ) .There are some finger markers to let you find the home row by touch .
I move the mouse with two fingers on the right side of the screen and control the cursor in applications with two fingers on the right .
There are a number of programmed gestures that allow for a great deal of task automation in stead of multiple click and drags.I love the device but it does have limitations .
Response time is not so great for gaming as you have the Gesture interpreter layer to contend with .
There is a game mode for the device but I 've rarely used it .
I still mis-type a lot but then the driver also helps and makes a lot of corrections automatically based on what word I am typing .
In my case it 's usually about 90 \ % correct when it fixes my typos.I loved the GUI interaction metaphors that the video describes .
I hope that older versions of devices like the one I have will get grandfathered in to design considerations or even further development !</tokentext>
<sentencetext>This is a nice revisit to the technology but even now I am using a multi-touch interface to type this comment.
I was luck enough to be an early adopter and have a few of the now defunct FingerWorks LLP products.
Notably my two TouchStream LPs and an iGesture pad.
Unlike the displayed product my keyboard/mouse has two pads and is arranged in an ergonomic arrangement (see image: http://pcworld.in/uploads/images/pcworld/4915355\_15.jpg [pcworld.in]).There are some finger markers to let you find the home row by touch.
I move the mouse with two fingers on the right side of the screen and control the cursor in applications with two fingers on the right.
There are a number of programmed gestures that allow for a great deal of task automation in stead of multiple click and drags.I love the device but it does have limitations.
Response time is not so great for gaming as you have the Gesture interpreter layer to contend with.
There is a game mode for the device but I've rarely used it.
I still mis-type a lot but then the driver also helps and makes a lot of corrections automatically based on what word I am typing.
In my case it's usually about 90\% correct when it fixes my typos.I loved the GUI interaction metaphors that the video describes.
I hope that older versions of devices like the one I have will get grandfathered in to design considerations or even further development!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747781</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>dissy</author>
	<datestamp>1255548180000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>Theres still a few problems though. For one, mouse is an incredibly precise input device</p> </div><p>Where in the article, or anywhere else for that matter, is it stated one must unplug the mouse from the computer before the touch interface turns on?</p><p>For a geek news site, that is a really non-intelligent assumption to make, one that has been proven repeatedly to not be true.  With every new input device out there, they run just fine with my mouse also plugged in.</p></div>
	</htmltext>
<tokenext>Theres still a few problems though .
For one , mouse is an incredibly precise input device Where in the article , or anywhere else for that matter , is it stated one must unplug the mouse from the computer before the touch interface turns on ? For a geek news site , that is a really non-intelligent assumption to make , one that has been proven repeatedly to not be true .
With every new input device out there , they run just fine with my mouse also plugged in .</tokentext>
<sentencetext>Theres still a few problems though.
For one, mouse is an incredibly precise input device Where in the article, or anywhere else for that matter, is it stated one must unplug the mouse from the computer before the touch interface turns on?For a geek news site, that is a really non-intelligent assumption to make, one that has been proven repeatedly to not be true.
With every new input device out there, they run just fine with my mouse also plugged in.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746829</id>
	<title>LCD Touchpad</title>
	<author>Calmiche</author>
	<datestamp>1255543980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You know, if thing is already a capacitive screen, you might as well make it an LCD as well.  Yes I know he demonstrated that you can't see it without your hands being in the way but I'm imagining a iPod-esque scroll wheel that can be moved around and let you roll through open windows.  Or how about audio/video controls of cover art flow.</p><p>Heck, for the people concerned about precision, make it a graphics tablet as well so you can use a stylus to draw.  With the LCD multi-touch you could drop controls and a color wheel on there.  Even setting/controls that change every time you switch to a different application.  When you put more than one finger on it, it could revert back to the basic multi-touch pad.</p></htmltext>
<tokenext>You know , if thing is already a capacitive screen , you might as well make it an LCD as well .
Yes I know he demonstrated that you ca n't see it without your hands being in the way but I 'm imagining a iPod-esque scroll wheel that can be moved around and let you roll through open windows .
Or how about audio/video controls of cover art flow.Heck , for the people concerned about precision , make it a graphics tablet as well so you can use a stylus to draw .
With the LCD multi-touch you could drop controls and a color wheel on there .
Even setting/controls that change every time you switch to a different application .
When you put more than one finger on it , it could revert back to the basic multi-touch pad .</tokentext>
<sentencetext>You know, if thing is already a capacitive screen, you might as well make it an LCD as well.
Yes I know he demonstrated that you can't see it without your hands being in the way but I'm imagining a iPod-esque scroll wheel that can be moved around and let you roll through open windows.
Or how about audio/video controls of cover art flow.Heck, for the people concerned about precision, make it a graphics tablet as well so you can use a stylus to draw.
With the LCD multi-touch you could drop controls and a color wheel on there.
Even setting/controls that change every time you switch to a different application.
When you put more than one finger on it, it could revert back to the basic multi-touch pad.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747333</id>
	<title>bunch of valid points that can easily be overcome</title>
	<author>Anonymous</author>
	<datestamp>1255546260000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>While a lot of pros and especially cons where underlined, they can all be compensated at the user level. You're missing one finger? Set the preferences accordingly. FPS? bring it on, I can't wait in fact; Developers should be able to adapt it, the same way they did for the Wii. Why don't make a virtual keyboard that you can fetch with a bottom pane? Need precision drawing? make a pen that works on this. Btw, you really think you are making straight line with a mouse? Thankfully you selected the straight line option in photoshop...</p></htmltext>
<tokenext>While a lot of pros and especially cons where underlined , they can all be compensated at the user level .
You 're missing one finger ?
Set the preferences accordingly .
FPS ? bring it on , I ca n't wait in fact ; Developers should be able to adapt it , the same way they did for the Wii .
Why do n't make a virtual keyboard that you can fetch with a bottom pane ?
Need precision drawing ?
make a pen that works on this .
Btw , you really think you are making straight line with a mouse ?
Thankfully you selected the straight line option in photoshop.. .</tokentext>
<sentencetext>While a lot of pros and especially cons where underlined, they can all be compensated at the user level.
You're missing one finger?
Set the preferences accordingly.
FPS? bring it on, I can't wait in fact; Developers should be able to adapt it, the same way they did for the Wii.
Why don't make a virtual keyboard that you can fetch with a bottom pane?
Need precision drawing?
make a pen that works on this.
Btw, you really think you are making straight line with a mouse?
Thankfully you selected the straight line option in photoshop...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744727</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>JohnFen</author>
	<datestamp>1255535100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The arrangement of the keyboard/touchpad they showed is where they lost me. Too much desk space taken up, and I'll end up resting my wrists on the touchpad, <i>and</i> I'll have to type with my hands too far forward.</p><p>This seems like a tough problem. The best solution I can think of is to use the touchpad as the keyboard as well, with soft keys. But then I won't have a real keyboard -- and I love having a real keyboard.</p></htmltext>
<tokenext>The arrangement of the keyboard/touchpad they showed is where they lost me .
Too much desk space taken up , and I 'll end up resting my wrists on the touchpad , and I 'll have to type with my hands too far forward.This seems like a tough problem .
The best solution I can think of is to use the touchpad as the keyboard as well , with soft keys .
But then I wo n't have a real keyboard -- and I love having a real keyboard .</tokentext>
<sentencetext>The arrangement of the keyboard/touchpad they showed is where they lost me.
Too much desk space taken up, and I'll end up resting my wrists on the touchpad, and I'll have to type with my hands too far forward.This seems like a tough problem.
The best solution I can think of is to use the touchpad as the keyboard as well, with soft keys.
But then I won't have a real keyboard -- and I love having a real keyboard.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744155</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745119</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>Chris Pimlott</author>
	<datestamp>1255536720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Theres still a few problems though. For one, mouse is an incredibly precise input device - you can pretty easily move it along same pixel axis, or get it precisely to a specific pixel. It's hard to do that with your fingers because the area they touch is a large one, it's not easy to just move your finger by one pixel and your hand tend to shake a little bit too. If you look at the video, you see everything in the interface is quite big and even a few small windows take lots of place.</p></div><p>Exact pixel accuracy is only necessary for a few specific applications, like editing graphics.  A modifier could be added to adjust the gain, or use something like acceleration to dynamically change the movement delta when the user is moving their fingers very slowly.  But for the vast majority of uses and users, being within a few pixels is good enough.</p><p><div class="quote"><p>Other problem is that now your both hands lay on the wide touch area and you dont have a keyboard. If you put them side to side, you'll only have one hand on the touch area and dont get the full power of it.</p></div><p>I didn't notice any two-hand gestures in the video.  Looks like everything could be done with early hand singularly.</p><p><div class="quote"><p>Moving hands between them all the time is inefficient. Typing on the touch area gives no feedback and again takes your hands of the "mouse".</p></div><p>Moving hands between keyboard and mouse in inefficient now, but we manage.</p><p><div class="quote"><p>It would also be quite impossible to play FPS or other kinds of games with this type of setup.</p></div><p>Why?</p></div>
	</htmltext>
<tokenext>Theres still a few problems though .
For one , mouse is an incredibly precise input device - you can pretty easily move it along same pixel axis , or get it precisely to a specific pixel .
It 's hard to do that with your fingers because the area they touch is a large one , it 's not easy to just move your finger by one pixel and your hand tend to shake a little bit too .
If you look at the video , you see everything in the interface is quite big and even a few small windows take lots of place.Exact pixel accuracy is only necessary for a few specific applications , like editing graphics .
A modifier could be added to adjust the gain , or use something like acceleration to dynamically change the movement delta when the user is moving their fingers very slowly .
But for the vast majority of uses and users , being within a few pixels is good enough.Other problem is that now your both hands lay on the wide touch area and you dont have a keyboard .
If you put them side to side , you 'll only have one hand on the touch area and dont get the full power of it.I did n't notice any two-hand gestures in the video .
Looks like everything could be done with early hand singularly.Moving hands between them all the time is inefficient .
Typing on the touch area gives no feedback and again takes your hands of the " mouse " .Moving hands between keyboard and mouse in inefficient now , but we manage.It would also be quite impossible to play FPS or other kinds of games with this type of setup.Why ?</tokentext>
<sentencetext>Theres still a few problems though.
For one, mouse is an incredibly precise input device - you can pretty easily move it along same pixel axis, or get it precisely to a specific pixel.
It's hard to do that with your fingers because the area they touch is a large one, it's not easy to just move your finger by one pixel and your hand tend to shake a little bit too.
If you look at the video, you see everything in the interface is quite big and even a few small windows take lots of place.Exact pixel accuracy is only necessary for a few specific applications, like editing graphics.
A modifier could be added to adjust the gain, or use something like acceleration to dynamically change the movement delta when the user is moving their fingers very slowly.
But for the vast majority of uses and users, being within a few pixels is good enough.Other problem is that now your both hands lay on the wide touch area and you dont have a keyboard.
If you put them side to side, you'll only have one hand on the touch area and dont get the full power of it.I didn't notice any two-hand gestures in the video.
Looks like everything could be done with early hand singularly.Moving hands between them all the time is inefficient.
Typing on the touch area gives no feedback and again takes your hands of the "mouse".Moving hands between keyboard and mouse in inefficient now, but we manage.It would also be quite impossible to play FPS or other kinds of games with this type of setup.Why?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29749567</id>
	<title>Close to what I want for MMORPGs</title>
	<author>harlows\_monkeys</author>
	<datestamp>1255512840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>What I've long wanted for MMORPGs is a screen in front at the normal position, and a second touch screen in the position 10GUI has the touch panel. Note I want the touch thingy to be a touch screen, not just a touch panel.</p><p>The screen in normal position would show me my view of the world, with minimal overlays (probably just health bars, damage and heal numbers, and such, and minimap, and maybe the last couple lines of chat).</p><p>The bottom screen would also show the world, but would have action bars, full chat, and so on.</p><p>It would allow casting spells and taking other actions by touching the target with a designated finger, and invoking the action by either touching the icon for that action on an action bar, or by gesture. There would be gestures that combine targeting and action.</p><p>For instance, lets say we get hit by AoE, and I need to get heal spells on everyone. I'd touch and hold on the icon for the heal spell I want to use, and then with the targeting finger tap everyone I want to heal. Similar for attacking, defending, and buffing.</p></htmltext>
<tokenext>What I 've long wanted for MMORPGs is a screen in front at the normal position , and a second touch screen in the position 10GUI has the touch panel .
Note I want the touch thingy to be a touch screen , not just a touch panel.The screen in normal position would show me my view of the world , with minimal overlays ( probably just health bars , damage and heal numbers , and such , and minimap , and maybe the last couple lines of chat ) .The bottom screen would also show the world , but would have action bars , full chat , and so on.It would allow casting spells and taking other actions by touching the target with a designated finger , and invoking the action by either touching the icon for that action on an action bar , or by gesture .
There would be gestures that combine targeting and action.For instance , lets say we get hit by AoE , and I need to get heal spells on everyone .
I 'd touch and hold on the icon for the heal spell I want to use , and then with the targeting finger tap everyone I want to heal .
Similar for attacking , defending , and buffing .</tokentext>
<sentencetext>What I've long wanted for MMORPGs is a screen in front at the normal position, and a second touch screen in the position 10GUI has the touch panel.
Note I want the touch thingy to be a touch screen, not just a touch panel.The screen in normal position would show me my view of the world, with minimal overlays (probably just health bars, damage and heal numbers, and such, and minimap, and maybe the last couple lines of chat).The bottom screen would also show the world, but would have action bars, full chat, and so on.It would allow casting spells and taking other actions by touching the target with a designated finger, and invoking the action by either touching the icon for that action on an action bar, or by gesture.
There would be gestures that combine targeting and action.For instance, lets say we get hit by AoE, and I need to get heal spells on everyone.
I'd touch and hold on the icon for the heal spell I want to use, and then with the targeting finger tap everyone I want to heal.
Similar for attacking, defending, and buffing.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</id>
	<title>Not for desktop pc's, but</title>
	<author>Anonymous</author>
	<datestamp>1255531920000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>Theres still a few problems though. For one, mouse is an incredibly precise input device - you can pretty easily move it along same pixel axis, or get it precisely to a specific pixel. It's hard to do that with your fingers because the area they touch is a large one, it's not easy to just move your finger by one pixel and your hand tend to shake a little bit too. If you look at the video, you see everything in the interface is quite big and even a few small windows take lots of place.</p><p>Other problem is that now your both hands lay on the wide touch area and you dont have a keyboard. If you put them side to side, you'll only have one hand on the touch area and dont get the full power of it. Moving hands between them all the time is inefficient. Typing on the touch area gives no feedback and again takes your hands of the "mouse".</p><p>It would also be quite impossible to play FPS or other kinds of games with this type of setup.</p><p>So no, I still dont see touch interfaces replacing the usual keyboard+mouse combo anytime soon. However, I would love to have this kind of system in my living room (either just for the tv, or the computer thats connected to tv screen). It's clumsy to have keyboard or mouse in living (at the moment I have <a href="http://www.logitech.com/index.cfm/mice\_pointers/mice/devices/3443&amp;cl=US,EN" title="logitech.com">MX Air -mouse</a> [logitech.com], which is okayish), but this would be perfect for such job. Not for a desktop pc replacement though.</p></htmltext>
<tokenext>Theres still a few problems though .
For one , mouse is an incredibly precise input device - you can pretty easily move it along same pixel axis , or get it precisely to a specific pixel .
It 's hard to do that with your fingers because the area they touch is a large one , it 's not easy to just move your finger by one pixel and your hand tend to shake a little bit too .
If you look at the video , you see everything in the interface is quite big and even a few small windows take lots of place.Other problem is that now your both hands lay on the wide touch area and you dont have a keyboard .
If you put them side to side , you 'll only have one hand on the touch area and dont get the full power of it .
Moving hands between them all the time is inefficient .
Typing on the touch area gives no feedback and again takes your hands of the " mouse " .It would also be quite impossible to play FPS or other kinds of games with this type of setup.So no , I still dont see touch interfaces replacing the usual keyboard + mouse combo anytime soon .
However , I would love to have this kind of system in my living room ( either just for the tv , or the computer thats connected to tv screen ) .
It 's clumsy to have keyboard or mouse in living ( at the moment I have MX Air -mouse [ logitech.com ] , which is okayish ) , but this would be perfect for such job .
Not for a desktop pc replacement though .</tokentext>
<sentencetext>Theres still a few problems though.
For one, mouse is an incredibly precise input device - you can pretty easily move it along same pixel axis, or get it precisely to a specific pixel.
It's hard to do that with your fingers because the area they touch is a large one, it's not easy to just move your finger by one pixel and your hand tend to shake a little bit too.
If you look at the video, you see everything in the interface is quite big and even a few small windows take lots of place.Other problem is that now your both hands lay on the wide touch area and you dont have a keyboard.
If you put them side to side, you'll only have one hand on the touch area and dont get the full power of it.
Moving hands between them all the time is inefficient.
Typing on the touch area gives no feedback and again takes your hands of the "mouse".It would also be quite impossible to play FPS or other kinds of games with this type of setup.So no, I still dont see touch interfaces replacing the usual keyboard+mouse combo anytime soon.
However, I would love to have this kind of system in my living room (either just for the tv, or the computer thats connected to tv screen).
It's clumsy to have keyboard or mouse in living (at the moment I have MX Air -mouse [logitech.com], which is okayish), but this would be perfect for such job.
Not for a desktop pc replacement though.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746969</id>
	<title>MP:H for the DS</title>
	<author>GameboyRMH</author>
	<datestamp>1255544820000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>It would also be quite impossible to play FPS or other kinds of games with this type of setup.</p></div><p>Have you ever played Metroid Prime: Hunters on the DS? It could work very well. I don't see any problems with gaming on a touchscreen.

The keyboard placement issue is the only real problem I can see.</p></div>
	</htmltext>
<tokenext>It would also be quite impossible to play FPS or other kinds of games with this type of setup.Have you ever played Metroid Prime : Hunters on the DS ?
It could work very well .
I do n't see any problems with gaming on a touchscreen .
The keyboard placement issue is the only real problem I can see .</tokentext>
<sentencetext>It would also be quite impossible to play FPS or other kinds of games with this type of setup.Have you ever played Metroid Prime: Hunters on the DS?
It could work very well.
I don't see any problems with gaming on a touchscreen.
The keyboard placement issue is the only real problem I can see.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744573</id>
	<title>A solution in search of a problem</title>
	<author>sean.peters</author>
	<datestamp>1255534500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>We've basically already solved the issues shown in the video. Problems with too many windows: get a second monitor. It's not very expensive, and doesn't require me to learn a different desktop paradigm. You can also take advantage of various taskbar/Expose/Spaces type features, which (depending on your preferences) make the problem of window management a lot easier. Need more/better input "bandwidth"? Get a Mac laptop with multi-touch trackpad (if you're not a Mac person, ok, I can't imagine Windows is very far behind with this feature). But even this is a little dicey as it requires you to learn how to use the multi-touch interface - I've had an iPhone for about a year now, and I'm still not familiar with all the multi-touch gestures the system can do (it turns out that they're not really very "discoverable", at least for me).</p><p>It turns out that there's a reason we've stuck with our standard WIMP metaphor for interacting with our computers... it works really, really well. This effort strikes me as change for the sake of change.</p></htmltext>
<tokenext>We 've basically already solved the issues shown in the video .
Problems with too many windows : get a second monitor .
It 's not very expensive , and does n't require me to learn a different desktop paradigm .
You can also take advantage of various taskbar/Expose/Spaces type features , which ( depending on your preferences ) make the problem of window management a lot easier .
Need more/better input " bandwidth " ?
Get a Mac laptop with multi-touch trackpad ( if you 're not a Mac person , ok , I ca n't imagine Windows is very far behind with this feature ) .
But even this is a little dicey as it requires you to learn how to use the multi-touch interface - I 've had an iPhone for about a year now , and I 'm still not familiar with all the multi-touch gestures the system can do ( it turns out that they 're not really very " discoverable " , at least for me ) .It turns out that there 's a reason we 've stuck with our standard WIMP metaphor for interacting with our computers... it works really , really well .
This effort strikes me as change for the sake of change .</tokentext>
<sentencetext>We've basically already solved the issues shown in the video.
Problems with too many windows: get a second monitor.
It's not very expensive, and doesn't require me to learn a different desktop paradigm.
You can also take advantage of various taskbar/Expose/Spaces type features, which (depending on your preferences) make the problem of window management a lot easier.
Need more/better input "bandwidth"?
Get a Mac laptop with multi-touch trackpad (if you're not a Mac person, ok, I can't imagine Windows is very far behind with this feature).
But even this is a little dicey as it requires you to learn how to use the multi-touch interface - I've had an iPhone for about a year now, and I'm still not familiar with all the multi-touch gestures the system can do (it turns out that they're not really very "discoverable", at least for me).It turns out that there's a reason we've stuck with our standard WIMP metaphor for interacting with our computers... it works really, really well.
This effort strikes me as change for the sake of change.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29749535</id>
	<title>Re:some subtle hints in that presentation</title>
	<author>organgtool</author>
	<datestamp>1255512660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>wonder what platform they're going to market to first <b>eh</b>?</p></div></blockquote><p>
Canadians?</p></div>
	</htmltext>
<tokenext>wonder what platform they 're going to market to first eh ?
Canadians ?</tokentext>
<sentencetext>wonder what platform they're going to market to first eh?
Canadians?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744325</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745095</id>
	<title>Keyboard should do this</title>
	<author>lymond01</author>
	<datestamp>1255536600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Seems like all this could be accomplished with just a keyboard.  Tap a key to activate "touchpad controls" and then just use certain keys to manipulate the environment -- A and D scrolls left and right.  W and S zoom in and out.  And many other combinations to mimic what this thing does, and my hands never leave the keyboard.</p></htmltext>
<tokenext>Seems like all this could be accomplished with just a keyboard .
Tap a key to activate " touchpad controls " and then just use certain keys to manipulate the environment -- A and D scrolls left and right .
W and S zoom in and out .
And many other combinations to mimic what this thing does , and my hands never leave the keyboard .</tokentext>
<sentencetext>Seems like all this could be accomplished with just a keyboard.
Tap a key to activate "touchpad controls" and then just use certain keys to manipulate the environment -- A and D scrolls left and right.
W and S zoom in and out.
And many other combinations to mimic what this thing does, and my hands never leave the keyboard.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745491</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>mafian911</author>
	<datestamp>1255538220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I was thinking the same thing. I thought one way to handle this more elegantly would be to have two separate touch pads, one on each side of the keyboard:

[TP][ KB ][TP]

Of course, you may lose some manipulation space for your hands, but this would take up considerably less vertical space, which is the more "expensive" dimension, in my opinion.</htmltext>
<tokenext>I was thinking the same thing .
I thought one way to handle this more elegantly would be to have two separate touch pads , one on each side of the keyboard : [ TP ] [ KB ] [ TP ] Of course , you may lose some manipulation space for your hands , but this would take up considerably less vertical space , which is the more " expensive " dimension , in my opinion .</tokentext>
<sentencetext>I was thinking the same thing.
I thought one way to handle this more elegantly would be to have two separate touch pads, one on each side of the keyboard:

[TP][ KB ][TP]

Of course, you may lose some manipulation space for your hands, but this would take up considerably less vertical space, which is the more "expensive" dimension, in my opinion.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744727</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29751799</id>
	<title>That doesn't solve repetitive motion injury issues</title>
	<author>leftie</author>
	<datestamp>1255526700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This Perceptive Pixel product doesn't solve repetitive motion injury issues.</p><p>Different parts of the body will get injured, but there will still be injuries.</p><p>For your input device, think hands at rest. Thumbs up. Palms together. Finger curved.</p><p>Anything else will still be causing rep. motion injuries.</p></htmltext>
<tokenext>This Perceptive Pixel product does n't solve repetitive motion injury issues.Different parts of the body will get injured , but there will still be injuries.For your input device , think hands at rest .
Thumbs up .
Palms together .
Finger curved.Anything else will still be causing rep. motion injuries .</tokentext>
<sentencetext>This Perceptive Pixel product doesn't solve repetitive motion injury issues.Different parts of the body will get injured, but there will still be injuries.For your input device, think hands at rest.
Thumbs up.
Palms together.
Finger curved.Anything else will still be causing rep. motion injuries.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744659</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746749</id>
	<title>Brutal soundtrack ...</title>
	<author>Anonymous</author>
	<datestamp>1255543560000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>OK the video is fine, the device and model are interesting but the soundtrack is awful.  Also the narrators cheesy voice acting and brutal pronunciation of words like obstacle, proxy and opposite were hard to listen to.</p><p>I know that's all petty and nothing do with the point of this discussion and the video but hey, this is Slashdot.</p></htmltext>
<tokenext>OK the video is fine , the device and model are interesting but the soundtrack is awful .
Also the narrators cheesy voice acting and brutal pronunciation of words like obstacle , proxy and opposite were hard to listen to.I know that 's all petty and nothing do with the point of this discussion and the video but hey , this is Slashdot .</tokentext>
<sentencetext>OK the video is fine, the device and model are interesting but the soundtrack is awful.
Also the narrators cheesy voice acting and brutal pronunciation of words like obstacle, proxy and opposite were hard to listen to.I know that's all petty and nothing do with the point of this discussion and the video but hey, this is Slashdot.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745153</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>theghost</author>
	<datestamp>1255536840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It looks like most of your objections are a result of being too stuck in the mouse mindset. Use a little imagination.</p><p>Precision: Each fingerprint has a dot in the center like an aiming reticle - that's your single-pixel reference. Seems like the ability to map some application-specific shortcut gesture to sensitivity changes, axis locks, or to any number of other tasks would be a given.</p><p>Keyboard/mouse switching has some of this issue right now and yet we deal with it. At about 8:10 in the video you see what this might look like in conjunction with a keyboard, but that seems a little clunky to me. I can imagine a split touch surface like having a mouse pad on either side of your keyboard that would alleviate some of this. Though you would lose some of the ease of two-hand interactions this way, i suspect you could train yourself past most of that.</p><p>I have no trouble at all imagining playing an fps or almost any other kind of game with this. See above - application-specific gesture mapping.</p><p>The speed with which this could be adopted has more to do with the rate of hardware and driver development imo. I don't see cheap mass-production happening soon.</p></htmltext>
<tokenext>It looks like most of your objections are a result of being too stuck in the mouse mindset .
Use a little imagination.Precision : Each fingerprint has a dot in the center like an aiming reticle - that 's your single-pixel reference .
Seems like the ability to map some application-specific shortcut gesture to sensitivity changes , axis locks , or to any number of other tasks would be a given.Keyboard/mouse switching has some of this issue right now and yet we deal with it .
At about 8 : 10 in the video you see what this might look like in conjunction with a keyboard , but that seems a little clunky to me .
I can imagine a split touch surface like having a mouse pad on either side of your keyboard that would alleviate some of this .
Though you would lose some of the ease of two-hand interactions this way , i suspect you could train yourself past most of that.I have no trouble at all imagining playing an fps or almost any other kind of game with this .
See above - application-specific gesture mapping.The speed with which this could be adopted has more to do with the rate of hardware and driver development imo .
I do n't see cheap mass-production happening soon .</tokentext>
<sentencetext>It looks like most of your objections are a result of being too stuck in the mouse mindset.
Use a little imagination.Precision: Each fingerprint has a dot in the center like an aiming reticle - that's your single-pixel reference.
Seems like the ability to map some application-specific shortcut gesture to sensitivity changes, axis locks, or to any number of other tasks would be a given.Keyboard/mouse switching has some of this issue right now and yet we deal with it.
At about 8:10 in the video you see what this might look like in conjunction with a keyboard, but that seems a little clunky to me.
I can imagine a split touch surface like having a mouse pad on either side of your keyboard that would alleviate some of this.
Though you would lose some of the ease of two-hand interactions this way, i suspect you could train yourself past most of that.I have no trouble at all imagining playing an fps or almost any other kind of game with this.
See above - application-specific gesture mapping.The speed with which this could be adopted has more to do with the rate of hardware and driver development imo.
I don't see cheap mass-production happening soon.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744417</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>theurge14</author>
	<datestamp>1255533900000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p><i>It would also be quite impossible to play FPS or other kinds of games with this type of setup.</i></p><p>Are we all really that stuck in our ways that this is how we judge possibly revolutionary ways to interface with our computers?  By how well it stacks up to an already poor approximation of shooting guns in a computer game?</p></htmltext>
<tokenext>It would also be quite impossible to play FPS or other kinds of games with this type of setup.Are we all really that stuck in our ways that this is how we judge possibly revolutionary ways to interface with our computers ?
By how well it stacks up to an already poor approximation of shooting guns in a computer game ?</tokentext>
<sentencetext>It would also be quite impossible to play FPS or other kinds of games with this type of setup.Are we all really that stuck in our ways that this is how we judge possibly revolutionary ways to interface with our computers?
By how well it stacks up to an already poor approximation of shooting guns in a computer game?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746811</id>
	<title>Rat Poison</title>
	<author>gnujoshua</author>
	<datestamp>1255543860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>So it's basically rat poison, but with continuous-buttons, but less powerful, and less useful.

<a href="http://www.youtube.com/watch?v=Rs0GMeL2zA0" title="youtube.com">http://www.youtube.com/watch?v=Rs0GMeL2zA0</a> [youtube.com]</htmltext>
<tokenext>So it 's basically rat poison , but with continuous-buttons , but less powerful , and less useful .
http : //www.youtube.com/watch ? v = Rs0GMeL2zA0 [ youtube.com ]</tokentext>
<sentencetext>So it's basically rat poison, but with continuous-buttons, but less powerful, and less useful.
http://www.youtube.com/watch?v=Rs0GMeL2zA0 [youtube.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745235</id>
	<title>I hope it's FOSS</title>
	<author>Anonymous</author>
	<datestamp>1255537200000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Let's keep our fingers crossed!</p></htmltext>
<tokenext>Let 's keep our fingers crossed !</tokentext>
<sentencetext>Let's keep our fingers crossed!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29755527</id>
	<title>Epic design fail.</title>
	<author>sayzero</author>
	<datestamp>1255612860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>From a psychological perspective, the "attentional spotlight" does not lend itself to having 10 points on the screen to focus on. Imagine if you wanted to sort out coins on a table. It's more natural to look at coins individually and sort them sequantially than look at them all together, place multiple fingers on different coins etc.

The gesture side of multitouch is also unconvincing. The video talks about tasks that are already extremely easy with a mouse and keyboard, and take up very little time. I'm sure it's easier to scroll a mouse wheel than move two fingers apart on a pad, and why would I want 10 fingers on the screen to swap a window when I can do it with one simple drag and drop with the mouse?</htmltext>
<tokenext>From a psychological perspective , the " attentional spotlight " does not lend itself to having 10 points on the screen to focus on .
Imagine if you wanted to sort out coins on a table .
It 's more natural to look at coins individually and sort them sequantially than look at them all together , place multiple fingers on different coins etc .
The gesture side of multitouch is also unconvincing .
The video talks about tasks that are already extremely easy with a mouse and keyboard , and take up very little time .
I 'm sure it 's easier to scroll a mouse wheel than move two fingers apart on a pad , and why would I want 10 fingers on the screen to swap a window when I can do it with one simple drag and drop with the mouse ?</tokentext>
<sentencetext>From a psychological perspective, the "attentional spotlight" does not lend itself to having 10 points on the screen to focus on.
Imagine if you wanted to sort out coins on a table.
It's more natural to look at coins individually and sort them sequantially than look at them all together, place multiple fingers on different coins etc.
The gesture side of multitouch is also unconvincing.
The video talks about tasks that are already extremely easy with a mouse and keyboard, and take up very little time.
I'm sure it's easier to scroll a mouse wheel than move two fingers apart on a pad, and why would I want 10 fingers on the screen to swap a window when I can do it with one simple drag and drop with the mouse?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29750511</id>
	<title>true</title>
	<author>CarpetShark</author>
	<datestamp>1255517520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Another problem is the assumption of 10 digits. For example, this might be more difficult for someone that is missing a digit or is paralyzed in an arm. In that case, the mouse would have a definite advantage.</p></div></blockquote><p>That's a very good point.  And even if a user cannot use a mouse, they can still find hardware that emulates it more easily, since, by 10/GUI's own definition, their system requires more "bandwidth" (input channels).</p><p>Still, while I'm as concerned about accessibility as all but its most serious champions, I'm not sure that holding back a good new GUI model for accessibility reasons would be a wise move.  Then again, I've had a few ideas myself for a new GUI model, and it, being higher-level for the machine, would be easier to translate to a audio interface, for instance.</p><p>So yeah... basically, I think it could be trouble, input-accessibility wise, but I still think it looks good enough to (rightly) gain some traction in the IT/user community.</p><p>My main concern though, is more fundamental, both from a normal user's point of view, and accessibility-wise.  That is... how many people are goint to understand an interface with 5+ "meta-levels"?  Can the average user really get that three fingers to zoom around windows is linked to using two fingers to zoom around in an app?  Or that five fingers is logically the thing to do to control all apps?  Maybe, but I don't know that I'd like to count on it just yet.</p></div>
	</htmltext>
<tokenext>Another problem is the assumption of 10 digits .
For example , this might be more difficult for someone that is missing a digit or is paralyzed in an arm .
In that case , the mouse would have a definite advantage.That 's a very good point .
And even if a user can not use a mouse , they can still find hardware that emulates it more easily , since , by 10/GUI 's own definition , their system requires more " bandwidth " ( input channels ) .Still , while I 'm as concerned about accessibility as all but its most serious champions , I 'm not sure that holding back a good new GUI model for accessibility reasons would be a wise move .
Then again , I 've had a few ideas myself for a new GUI model , and it , being higher-level for the machine , would be easier to translate to a audio interface , for instance.So yeah... basically , I think it could be trouble , input-accessibility wise , but I still think it looks good enough to ( rightly ) gain some traction in the IT/user community.My main concern though , is more fundamental , both from a normal user 's point of view , and accessibility-wise .
That is... how many people are goint to understand an interface with 5 + " meta-levels " ?
Can the average user really get that three fingers to zoom around windows is linked to using two fingers to zoom around in an app ?
Or that five fingers is logically the thing to do to control all apps ?
Maybe , but I do n't know that I 'd like to count on it just yet .</tokentext>
<sentencetext>Another problem is the assumption of 10 digits.
For example, this might be more difficult for someone that is missing a digit or is paralyzed in an arm.
In that case, the mouse would have a definite advantage.That's a very good point.
And even if a user cannot use a mouse, they can still find hardware that emulates it more easily, since, by 10/GUI's own definition, their system requires more "bandwidth" (input channels).Still, while I'm as concerned about accessibility as all but its most serious champions, I'm not sure that holding back a good new GUI model for accessibility reasons would be a wise move.
Then again, I've had a few ideas myself for a new GUI model, and it, being higher-level for the machine, would be easier to translate to a audio interface, for instance.So yeah... basically, I think it could be trouble, input-accessibility wise, but I still think it looks good enough to (rightly) gain some traction in the IT/user community.My main concern though, is more fundamental, both from a normal user's point of view, and accessibility-wise.
That is... how many people are goint to understand an interface with 5+ "meta-levels"?
Can the average user really get that three fingers to zoom around windows is linked to using two fingers to zoom around in an app?
Or that five fingers is logically the thing to do to control all apps?
Maybe, but I don't know that I'd like to count on it just yet.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744181</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29753987</id>
	<title>What a simple idea...</title>
	<author>DrSpock11</author>
	<datestamp>1255549380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Now, instead of just moving a piece of plastic around and clicking one or two buttons, we can use this much more simple solution.</p><p>You just have to remember what a one finger command does, what  a two fingers command does, what a three fingers does, what a four finger command does, and what a five finger command does and you're on your way to input SIMPLICITY.</p><p>Oh, and make sure you don't touch the pad with an extra finger or you'll end up resizing your desktop instead of scrolling through windows.</p><p>I found the most interesting part of the video to be the SIMPLE new way of organizing windows. Now, instead of all those cluttered windows all over the screen, you can have the simple and easy to use solution of having them in a line with most of them not visible off of the screen!</p><p>And you can bring up a view that will show you the names of currently running programs! That seems so innovative, but I'm sure I've seen something a little bit similar to it before. Oh, that's right, I've been looking at something that does that everyday I've used a computer since Windows 95.</p></htmltext>
<tokenext>Now , instead of just moving a piece of plastic around and clicking one or two buttons , we can use this much more simple solution.You just have to remember what a one finger command does , what a two fingers command does , what a three fingers does , what a four finger command does , and what a five finger command does and you 're on your way to input SIMPLICITY.Oh , and make sure you do n't touch the pad with an extra finger or you 'll end up resizing your desktop instead of scrolling through windows.I found the most interesting part of the video to be the SIMPLE new way of organizing windows .
Now , instead of all those cluttered windows all over the screen , you can have the simple and easy to use solution of having them in a line with most of them not visible off of the screen ! And you can bring up a view that will show you the names of currently running programs !
That seems so innovative , but I 'm sure I 've seen something a little bit similar to it before .
Oh , that 's right , I 've been looking at something that does that everyday I 've used a computer since Windows 95 .</tokentext>
<sentencetext>Now, instead of just moving a piece of plastic around and clicking one or two buttons, we can use this much more simple solution.You just have to remember what a one finger command does, what  a two fingers command does, what a three fingers does, what a four finger command does, and what a five finger command does and you're on your way to input SIMPLICITY.Oh, and make sure you don't touch the pad with an extra finger or you'll end up resizing your desktop instead of scrolling through windows.I found the most interesting part of the video to be the SIMPLE new way of organizing windows.
Now, instead of all those cluttered windows all over the screen, you can have the simple and easy to use solution of having them in a line with most of them not visible off of the screen!And you can bring up a view that will show you the names of currently running programs!
That seems so innovative, but I'm sure I've seen something a little bit similar to it before.
Oh, that's right, I've been looking at something that does that everyday I've used a computer since Windows 95.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748619</id>
	<title>Fingers become irritated</title>
	<author>aaandre</author>
	<datestamp>1255551780000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Used a multitouch pad a few years back replacing a mouse. Had multiple gestures and macros. After a while, though, my fingers became oversensitive to the surface and the touch became very uncomfortable.</p></htmltext>
<tokenext>Used a multitouch pad a few years back replacing a mouse .
Had multiple gestures and macros .
After a while , though , my fingers became oversensitive to the surface and the touch became very uncomfortable .</tokentext>
<sentencetext>Used a multitouch pad a few years back replacing a mouse.
Had multiple gestures and macros.
After a while, though, my fingers became oversensitive to the surface and the touch became very uncomfortable.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745705</id>
	<title>All 10 fingers</title>
	<author>MpVpRb</author>
	<datestamp>1255539060000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>You know what other interface uses all 10 fingers...a piano.

</p><p>Virtuoso pianists can make magic with the interface.

</p><p>Most people never really get it.

</p><p>This is the fundamental limitation of all these schemes. The mouse is easy enough that anybody can use it. The more manual dexterity that's required, the more it becomes like learning to play the piano.</p></htmltext>
<tokenext>You know what other interface uses all 10 fingers...a piano .
Virtuoso pianists can make magic with the interface .
Most people never really get it .
This is the fundamental limitation of all these schemes .
The mouse is easy enough that anybody can use it .
The more manual dexterity that 's required , the more it becomes like learning to play the piano .</tokentext>
<sentencetext>You know what other interface uses all 10 fingers...a piano.
Virtuoso pianists can make magic with the interface.
Most people never really get it.
This is the fundamental limitation of all these schemes.
The mouse is easy enough that anybody can use it.
The more manual dexterity that's required, the more it becomes like learning to play the piano.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744493</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>Kagato</author>
	<datestamp>1255534200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I see this replacing the mouse and quite useful in terms of day to day PC use.  In particular in a business setting.  I think what happen is the mouse will become a specialized tool, just like drawing tablets are specialized today.</p></htmltext>
<tokenext>I see this replacing the mouse and quite useful in terms of day to day PC use .
In particular in a business setting .
I think what happen is the mouse will become a specialized tool , just like drawing tablets are specialized today .</tokentext>
<sentencetext>I see this replacing the mouse and quite useful in terms of day to day PC use.
In particular in a business setting.
I think what happen is the mouse will become a specialized tool, just like drawing tablets are specialized today.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744967</id>
	<title>A few problems and some solutions</title>
	<author>SuperKendall</author>
	<datestamp>1255536060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I see a few issues with this approach, some of which I'll offer solutions for:</p><p>1) They can invoke an application menu, but not a context menu.  You need both (even from the start the Mac has supported context menus with only one button).  They could divide the left bar into a top and bottom half, where you could hold a finger on something and then use your pinky to activate a context menu (or perhaps just hold a finger down on anything while pressing the single bar, but that may be too easy to accidentally trigger).</p><p>2) Try pinching with four fingers.  It's not very comfortable, at all (the only practical way is to lift up the pinky).  The solution is to make that a five-finger pinch (to enlarge or shrink the bar).</p><p>3) With a lot of apps open (or a lot of app windows) the bar approach is simply not feasible - you have to zoom out multiple times to see everything and then the windows are too tiny.   Instead double tap with all five fingers to bring up the bar, but wrapped around (so it ends up kind of like expose filling the screen as much as possible).  Then click any screen to jump to it.</p><p>4) They don't show any typing going on.  Obviously since the clicks have effect, they have to have a typing "mode" you enter.  Hello VI for desktops!   People always complained that Emacs was really an OS, I guess VI got jealous.  My solution to this is that you keep the keyboard (which people want anyway for extended typing) and make the 10 surface basically a large touchpad off to the side of the keyboard (or even just below, though to be large enough to use all five fingers I don't think there's enough space below a keyboard).</p><p>Although 10Gui is pretty interesting, I think what we'll see in practical use is an evolution of the trackpad to control more and more things using gestures and multitouch.  Awesome video though.</p></htmltext>
<tokenext>I see a few issues with this approach , some of which I 'll offer solutions for : 1 ) They can invoke an application menu , but not a context menu .
You need both ( even from the start the Mac has supported context menus with only one button ) .
They could divide the left bar into a top and bottom half , where you could hold a finger on something and then use your pinky to activate a context menu ( or perhaps just hold a finger down on anything while pressing the single bar , but that may be too easy to accidentally trigger ) .2 ) Try pinching with four fingers .
It 's not very comfortable , at all ( the only practical way is to lift up the pinky ) .
The solution is to make that a five-finger pinch ( to enlarge or shrink the bar ) .3 ) With a lot of apps open ( or a lot of app windows ) the bar approach is simply not feasible - you have to zoom out multiple times to see everything and then the windows are too tiny .
Instead double tap with all five fingers to bring up the bar , but wrapped around ( so it ends up kind of like expose filling the screen as much as possible ) .
Then click any screen to jump to it.4 ) They do n't show any typing going on .
Obviously since the clicks have effect , they have to have a typing " mode " you enter .
Hello VI for desktops !
People always complained that Emacs was really an OS , I guess VI got jealous .
My solution to this is that you keep the keyboard ( which people want anyway for extended typing ) and make the 10 surface basically a large touchpad off to the side of the keyboard ( or even just below , though to be large enough to use all five fingers I do n't think there 's enough space below a keyboard ) .Although 10Gui is pretty interesting , I think what we 'll see in practical use is an evolution of the trackpad to control more and more things using gestures and multitouch .
Awesome video though .</tokentext>
<sentencetext>I see a few issues with this approach, some of which I'll offer solutions for:1) They can invoke an application menu, but not a context menu.
You need both (even from the start the Mac has supported context menus with only one button).
They could divide the left bar into a top and bottom half, where you could hold a finger on something and then use your pinky to activate a context menu (or perhaps just hold a finger down on anything while pressing the single bar, but that may be too easy to accidentally trigger).2) Try pinching with four fingers.
It's not very comfortable, at all (the only practical way is to lift up the pinky).
The solution is to make that a five-finger pinch (to enlarge or shrink the bar).3) With a lot of apps open (or a lot of app windows) the bar approach is simply not feasible - you have to zoom out multiple times to see everything and then the windows are too tiny.
Instead double tap with all five fingers to bring up the bar, but wrapped around (so it ends up kind of like expose filling the screen as much as possible).
Then click any screen to jump to it.4) They don't show any typing going on.
Obviously since the clicks have effect, they have to have a typing "mode" you enter.
Hello VI for desktops!
People always complained that Emacs was really an OS, I guess VI got jealous.
My solution to this is that you keep the keyboard (which people want anyway for extended typing) and make the 10 surface basically a large touchpad off to the side of the keyboard (or even just below, though to be large enough to use all five fingers I don't think there's enough space below a keyboard).Although 10Gui is pretty interesting, I think what we'll see in practical use is an evolution of the trackpad to control more and more things using gestures and multitouch.
Awesome video though.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29753221</id>
	<title>Not revolutionary, but I won't turn it down</title>
	<author>burndive</author>
	<datestamp>1255539000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I like that they used Linux for the demo. That means they probably have a window manager ready to go (i.e., I won't have to wait for Microsoft to adopt it). When it comes out, all I'll have to do is "emerge 10-gui" (oh, and buy the hardware) to try it out.</p><p>Speaking of which, the hardware had better not be too expensive. That would kill it.</p><p>I don't think I like their linear window management idea. I like that I can arrange windows to overlap on a 2D space, and access them with a single click, or Alt+Tab in 1-D fashion. It seems better to me than manually scrolling through all my open windows.</p><p>Oh, and attaching the touch surface to the place where I rest my wrists to type? No. Just no. That's the dumbest idea ever.</p></htmltext>
<tokenext>I like that they used Linux for the demo .
That means they probably have a window manager ready to go ( i.e. , I wo n't have to wait for Microsoft to adopt it ) .
When it comes out , all I 'll have to do is " emerge 10-gui " ( oh , and buy the hardware ) to try it out.Speaking of which , the hardware had better not be too expensive .
That would kill it.I do n't think I like their linear window management idea .
I like that I can arrange windows to overlap on a 2D space , and access them with a single click , or Alt + Tab in 1-D fashion .
It seems better to me than manually scrolling through all my open windows.Oh , and attaching the touch surface to the place where I rest my wrists to type ?
No. Just no .
That 's the dumbest idea ever .</tokentext>
<sentencetext>I like that they used Linux for the demo.
That means they probably have a window manager ready to go (i.e., I won't have to wait for Microsoft to adopt it).
When it comes out, all I'll have to do is "emerge 10-gui" (oh, and buy the hardware) to try it out.Speaking of which, the hardware had better not be too expensive.
That would kill it.I don't think I like their linear window management idea.
I like that I can arrange windows to overlap on a 2D space, and access them with a single click, or Alt+Tab in 1-D fashion.
It seems better to me than manually scrolling through all my open windows.Oh, and attaching the touch surface to the place where I rest my wrists to type?
No. Just no.
That's the dumbest idea ever.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744423</id>
	<title>Free Shopping Ecko Unltd jean,DG sweater man   Hot</title>
	<author>Anonymous</author>
	<datestamp>1255533900000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>
&nbsp; &nbsp; Professional  LEATHER OEM  exporter  manufacture<br>Over 800 bag workers<br>Over 10 years' export experiences<br>Over 20 years'experience in the bag filed<br>Handbags are our speciality<br>Our market is the export market<br>Customer service is our top priority<br>Warmly welcome foreign business<br>The exhibition we attend every year<br>1:Asian Pacific Leather Fair<br>2:China Import and Export Commodities  Fair<br>Top quality ! Competitive Price ! Prompt delivery !<br>( Wholesale</p><p>lady/fashion/women/brand/leather/designer/handbags/</p><p>handbag/bag/bags/wallet/wallets/purses/purse/luggag</p><p>e/shopping bag(OEM) )</p><p>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; OUR WEBSITE:</p><p>YAHOO:shoppertrade@yahoo.com.cn</p><p>MSN:shoppertrade@hotmail.com</p><p>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; HTTP://www.tntshoes.com</p></htmltext>
<tokenext>    Professional LEATHER OEM exporter manufactureOver 800 bag workersOver 10 years ' export experiencesOver 20 years'experience in the bag filedHandbags are our specialityOur market is the export marketCustomer service is our top priorityWarmly welcome foreign businessThe exhibition we attend every year1 : Asian Pacific Leather Fair2 : China Import and Export Commodities FairTop quality !
Competitive Price !
Prompt delivery !
( Wholesalelady/fashion/women/brand/leather/designer/handbags/handbag/bag/bags/wallet/wallets/purses/purse/luggage/shopping bag ( OEM ) )             OUR WEBSITE : YAHOO : shoppertrade @ yahoo.com.cnMSN : shoppertrade @ hotmail.com                                                                           HTTP : //www.tntshoes.com</tokentext>
<sentencetext>
    Professional  LEATHER OEM  exporter  manufactureOver 800 bag workersOver 10 years' export experiencesOver 20 years'experience in the bag filedHandbags are our specialityOur market is the export marketCustomer service is our top priorityWarmly welcome foreign businessThe exhibition we attend every year1:Asian Pacific Leather Fair2:China Import and Export Commodities  FairTop quality !
Competitive Price !
Prompt delivery !
( Wholesalelady/fashion/women/brand/leather/designer/handbags/handbag/bag/bags/wallet/wallets/purses/purse/luggage/shopping bag(OEM) )
            OUR WEBSITE:YAHOO:shoppertrade@yahoo.com.cnMSN:shoppertrade@hotmail.com
                                                                          HTTP://www.tntshoes.com</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747277</id>
	<title>keyboard build into the touch area?</title>
	<author>Anonymous</author>
	<datestamp>1255546020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>What if there was a place to touch on the pad to turn the pad into a keyboard? I'm not sure how easily we'd be able to type without feedback but I think there are keyboards today that project your keyboard and track your fingers. Seems like you could do the same sort of thing here.</p></htmltext>
<tokenext>What if there was a place to touch on the pad to turn the pad into a keyboard ?
I 'm not sure how easily we 'd be able to type without feedback but I think there are keyboards today that project your keyboard and track your fingers .
Seems like you could do the same sort of thing here .</tokentext>
<sentencetext>What if there was a place to touch on the pad to turn the pad into a keyboard?
I'm not sure how easily we'd be able to type without feedback but I think there are keyboards today that project your keyboard and track your fingers.
Seems like you could do the same sort of thing here.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745537</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>timeOday</author>
	<datestamp>1255538460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>That's like saying books are bad because they assume eyesight.  Should we all switch to Braille?</htmltext>
<tokenext>That 's like saying books are bad because they assume eyesight .
Should we all switch to Braille ?</tokentext>
<sentencetext>That's like saying books are bad because they assume eyesight.
Should we all switch to Braille?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744181</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744809</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>cwgmpls</author>
	<datestamp>1255535400000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>I understand that people with disabilities have computer input needs too.  But I don't understand why the fact that we are all differently-abled should prevent people from using their abilities to their fullest capacity.</p><p>Does the fact that some people are missing a digit or have paralysis in one arm mean that no one should propose playing a piano with ten fingers?  Does that fact that some people don't have feet mean that pianos should not have foot pedals?  Of course not.</p><p>While we should move forward with good interface designs for people with disabilities, I don't see why we should stand in the way of people using the abilities they do have in a novel, more productive way.</p></htmltext>
<tokenext>I understand that people with disabilities have computer input needs too .
But I do n't understand why the fact that we are all differently-abled should prevent people from using their abilities to their fullest capacity.Does the fact that some people are missing a digit or have paralysis in one arm mean that no one should propose playing a piano with ten fingers ?
Does that fact that some people do n't have feet mean that pianos should not have foot pedals ?
Of course not.While we should move forward with good interface designs for people with disabilities , I do n't see why we should stand in the way of people using the abilities they do have in a novel , more productive way .</tokentext>
<sentencetext>I understand that people with disabilities have computer input needs too.
But I don't understand why the fact that we are all differently-abled should prevent people from using their abilities to their fullest capacity.Does the fact that some people are missing a digit or have paralysis in one arm mean that no one should propose playing a piano with ten fingers?
Does that fact that some people don't have feet mean that pianos should not have foot pedals?
Of course not.While we should move forward with good interface designs for people with disabilities, I don't see why we should stand in the way of people using the abilities they do have in a novel, more productive way.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744181</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744449</id>
	<title>ion</title>
	<author>Anonymous</author>
	<datestamp>1255533960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Against cluttered windows, just use frames (<a href="http://www.modeemi.fi/~tuomov/ion/" title="modeemi.fi" rel="nofollow">ion</a> [modeemi.fi]). Couldn't live without.</p></htmltext>
<tokenext>Against cluttered windows , just use frames ( ion [ modeemi.fi ] ) .
Could n't live without .</tokentext>
<sentencetext>Against cluttered windows, just use frames (ion [modeemi.fi]).
Couldn't live without.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744371</id>
	<title>Replacing current business work interface</title>
	<author>Dripdry</author>
	<datestamp>1255533720000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>I disagree with an earlier poster who says this can't replace the desktop interface we know.</p><p>He points out that it is inefficient because one has to move hands between keyboard and pad.<br>It seems to me that this interface can be manipulated with just one hand. that's how the mouse works now. you take your hand off the mouse to work with the full functionality of the keyboard, why couldn't 10/GUI replace that?<br>Better still, why not have both! The pad can sense a mouse and act as a mouse pad. If you need to use it as a pad move the mouse off, or perhaps use both the mouse AND the pad at the same time (one hand each). I can see a lot of possibilities there.   It could clutter a desk, sure, but I'm sure we can solve that problem.</p><p>Second, but probably more importantly, I can easily see this for the work I do, which I imagine is similar to many other people.</p><p>I use my system (two monitors) for business. I have data on one side of the screen and sometimes excel or word on the other screen. In addition (here's where 10/GUI could be useful) I'll have a pdf open in the background which i need to quickly scroll through ("in adobe, quickly!?" you ask?). With one hand on the mouse I can quickly zip through Morningstar data, and use my free hand (on the pad) to scroll through a document, then quickly zip back and forth, scrolling and zooming as necessary. Right now that's just using a mouse and it can be tiresome to move around with just that little pointer (especially morningstar! oh it would be nice to have a touch interface for that...)</p><p>Finally, I need to have a "document scroller" or whatever it is that I can resize and move around, as I find myself with documents that sometimes need to show different parts of their data on screen. Basically I need to be able to "undock" documents so i can use them effectively (like papers on an actual desktop) and then redock them when I'm done.</p><p>That would be a beautiful interface that I do feel would save me some time and frustration. I would buy that for my business.</p></htmltext>
<tokenext>I disagree with an earlier poster who says this ca n't replace the desktop interface we know.He points out that it is inefficient because one has to move hands between keyboard and pad.It seems to me that this interface can be manipulated with just one hand .
that 's how the mouse works now .
you take your hand off the mouse to work with the full functionality of the keyboard , why could n't 10/GUI replace that ? Better still , why not have both !
The pad can sense a mouse and act as a mouse pad .
If you need to use it as a pad move the mouse off , or perhaps use both the mouse AND the pad at the same time ( one hand each ) .
I can see a lot of possibilities there .
It could clutter a desk , sure , but I 'm sure we can solve that problem.Second , but probably more importantly , I can easily see this for the work I do , which I imagine is similar to many other people.I use my system ( two monitors ) for business .
I have data on one side of the screen and sometimes excel or word on the other screen .
In addition ( here 's where 10/GUI could be useful ) I 'll have a pdf open in the background which i need to quickly scroll through ( " in adobe , quickly ! ?
" you ask ? ) .
With one hand on the mouse I can quickly zip through Morningstar data , and use my free hand ( on the pad ) to scroll through a document , then quickly zip back and forth , scrolling and zooming as necessary .
Right now that 's just using a mouse and it can be tiresome to move around with just that little pointer ( especially morningstar !
oh it would be nice to have a touch interface for that... ) Finally , I need to have a " document scroller " or whatever it is that I can resize and move around , as I find myself with documents that sometimes need to show different parts of their data on screen .
Basically I need to be able to " undock " documents so i can use them effectively ( like papers on an actual desktop ) and then redock them when I 'm done.That would be a beautiful interface that I do feel would save me some time and frustration .
I would buy that for my business .</tokentext>
<sentencetext>I disagree with an earlier poster who says this can't replace the desktop interface we know.He points out that it is inefficient because one has to move hands between keyboard and pad.It seems to me that this interface can be manipulated with just one hand.
that's how the mouse works now.
you take your hand off the mouse to work with the full functionality of the keyboard, why couldn't 10/GUI replace that?Better still, why not have both!
The pad can sense a mouse and act as a mouse pad.
If you need to use it as a pad move the mouse off, or perhaps use both the mouse AND the pad at the same time (one hand each).
I can see a lot of possibilities there.
It could clutter a desk, sure, but I'm sure we can solve that problem.Second, but probably more importantly, I can easily see this for the work I do, which I imagine is similar to many other people.I use my system (two monitors) for business.
I have data on one side of the screen and sometimes excel or word on the other screen.
In addition (here's where 10/GUI could be useful) I'll have a pdf open in the background which i need to quickly scroll through ("in adobe, quickly!?
" you ask?).
With one hand on the mouse I can quickly zip through Morningstar data, and use my free hand (on the pad) to scroll through a document, then quickly zip back and forth, scrolling and zooming as necessary.
Right now that's just using a mouse and it can be tiresome to move around with just that little pointer (especially morningstar!
oh it would be nice to have a touch interface for that...)Finally, I need to have a "document scroller" or whatever it is that I can resize and move around, as I find myself with documents that sometimes need to show different parts of their data on screen.
Basically I need to be able to "undock" documents so i can use them effectively (like papers on an actual desktop) and then redock them when I'm done.That would be a beautiful interface that I do feel would save me some time and frustration.
I would buy that for my business.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29751617</id>
	<title>Re:All 10 fingers</title>
	<author>Anonymous</author>
	<datestamp>1255525500000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>So we should replace the mouse with a midi keyboard?</p></htmltext>
<tokenext>So we should replace the mouse with a midi keyboard ?</tokentext>
<sentencetext>So we should replace the mouse with a midi keyboard?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745705</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745775</id>
	<title>I see what's going on here:</title>
	<author>KrimZon</author>
	<datestamp>1255539360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Workspaces are an amazing new way to manage your windows an applications.</p><p>With conventional window managers, your windows are just grouped by application, or even not at all. Suppose you're writing an article, and you open up a web browser with some reference material. You open up your mail client and open a PDF attachment which a colleague thought might be helpful to you. Then you put on some music and start writing. But now you're switching back and forth through all the webpages you have open until you reach the one you want, past the mail client and the music player and the PDF back to the document you're writing. Things like this are a big problem, but thankfully, that's the old way.</p><p>With Workspaces, we offer you an awesome and new way to organize yourself. So you're ready to start writing that article again - you open the word processor. We're all familar with that, but what happens next is where the incredible new power of Workspaces is shown: press ctrl-alt-2 to switch to a second Workspace where you can open the browser of reference material. That's just amazing!</p><p>But that's not all. Next, you can press ctrl-alt-3 and open your mail client, and it opens in yet another workspace. We can open the colleague's email attachment and press ctrl-alt-shift-left to move it to the previous workspace, where we can arrange it side by side with the web browser window. Now what's awesome and incredible about that is you can flip between your word processor and the reference material with the keyboard shortcuts, without having to sort through windows ever. Amazing!</p><p>Oh, but before you start, you want your tunes again. Ctrl-alt-4, open your music player, ctrl-alt-1 back to the word processor. Awesome!</p><p>Workspaces. It really is just that simple.</p></htmltext>
<tokenext>Workspaces are an amazing new way to manage your windows an applications.With conventional window managers , your windows are just grouped by application , or even not at all .
Suppose you 're writing an article , and you open up a web browser with some reference material .
You open up your mail client and open a PDF attachment which a colleague thought might be helpful to you .
Then you put on some music and start writing .
But now you 're switching back and forth through all the webpages you have open until you reach the one you want , past the mail client and the music player and the PDF back to the document you 're writing .
Things like this are a big problem , but thankfully , that 's the old way.With Workspaces , we offer you an awesome and new way to organize yourself .
So you 're ready to start writing that article again - you open the word processor .
We 're all familar with that , but what happens next is where the incredible new power of Workspaces is shown : press ctrl-alt-2 to switch to a second Workspace where you can open the browser of reference material .
That 's just amazing ! But that 's not all .
Next , you can press ctrl-alt-3 and open your mail client , and it opens in yet another workspace .
We can open the colleague 's email attachment and press ctrl-alt-shift-left to move it to the previous workspace , where we can arrange it side by side with the web browser window .
Now what 's awesome and incredible about that is you can flip between your word processor and the reference material with the keyboard shortcuts , without having to sort through windows ever .
Amazing ! Oh , but before you start , you want your tunes again .
Ctrl-alt-4 , open your music player , ctrl-alt-1 back to the word processor .
Awesome ! Workspaces. It really is just that simple .</tokentext>
<sentencetext>Workspaces are an amazing new way to manage your windows an applications.With conventional window managers, your windows are just grouped by application, or even not at all.
Suppose you're writing an article, and you open up a web browser with some reference material.
You open up your mail client and open a PDF attachment which a colleague thought might be helpful to you.
Then you put on some music and start writing.
But now you're switching back and forth through all the webpages you have open until you reach the one you want, past the mail client and the music player and the PDF back to the document you're writing.
Things like this are a big problem, but thankfully, that's the old way.With Workspaces, we offer you an awesome and new way to organize yourself.
So you're ready to start writing that article again - you open the word processor.
We're all familar with that, but what happens next is where the incredible new power of Workspaces is shown: press ctrl-alt-2 to switch to a second Workspace where you can open the browser of reference material.
That's just amazing!But that's not all.
Next, you can press ctrl-alt-3 and open your mail client, and it opens in yet another workspace.
We can open the colleague's email attachment and press ctrl-alt-shift-left to move it to the previous workspace, where we can arrange it side by side with the web browser window.
Now what's awesome and incredible about that is you can flip between your word processor and the reference material with the keyboard shortcuts, without having to sort through windows ever.
Amazing!Oh, but before you start, you want your tunes again.
Ctrl-alt-4, open your music player, ctrl-alt-1 back to the word processor.
Awesome!Workspaces. It really is just that simple.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747719</id>
	<title>Re:Not for desktop pc's, but</title>
	<author>Anonymous</author>
	<datestamp>1255547940000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p>By your logic then, mice should never have existed, because they don't work best with everything.</p><p>[new tech] won't work with FPS games, thus this is stupid and should not be.</p><p>Under that logic, mice don't work with the game Asteroids best, so mice should not have been researched ever.</p><p>And the people that think your very non-insightful and obviously misplaced comment should be modded insightful need to go back to the non technical websites where they clearly would be happier with nothing but marketing articles for things with commercial potential instead of being for geeks.</p></htmltext>
<tokenext>By your logic then , mice should never have existed , because they do n't work best with everything .
[ new tech ] wo n't work with FPS games , thus this is stupid and should not be.Under that logic , mice do n't work with the game Asteroids best , so mice should not have been researched ever.And the people that think your very non-insightful and obviously misplaced comment should be modded insightful need to go back to the non technical websites where they clearly would be happier with nothing but marketing articles for things with commercial potential instead of being for geeks .</tokentext>
<sentencetext>By your logic then, mice should never have existed, because they don't work best with everything.
[new tech] won't work with FPS games, thus this is stupid and should not be.Under that logic, mice don't work with the game Asteroids best, so mice should not have been researched ever.And the people that think your very non-insightful and obviously misplaced comment should be modded insightful need to go back to the non technical websites where they clearly would be happier with nothing but marketing articles for things with commercial potential instead of being for geeks.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746779</id>
	<title>Tiling Window Manager?</title>
	<author>Vyse of Arcadia</author>
	<datestamp>1255543740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The first thing that popped into my head as an alternative to the standard window paradigm was a tiling window manager, like XMonad. Seems an awful lot more efficient than a linear window manager. And why not multiple desktops too, while we're at it? <br>
<br>
I don't see why we can't have something like this very soon, and the pad below keyboard arrangement doesn't bother me at all. After all, that's how modern laptops are setup, albeit with a much smaller touch pad.</htmltext>
<tokenext>The first thing that popped into my head as an alternative to the standard window paradigm was a tiling window manager , like XMonad .
Seems an awful lot more efficient than a linear window manager .
And why not multiple desktops too , while we 're at it ?
I do n't see why we ca n't have something like this very soon , and the pad below keyboard arrangement does n't bother me at all .
After all , that 's how modern laptops are setup , albeit with a much smaller touch pad .</tokentext>
<sentencetext>The first thing that popped into my head as an alternative to the standard window paradigm was a tiling window manager, like XMonad.
Seems an awful lot more efficient than a linear window manager.
And why not multiple desktops too, while we're at it?
I don't see why we can't have something like this very soon, and the pad below keyboard arrangement doesn't bother me at all.
After all, that's how modern laptops are setup, albeit with a much smaller touch pad.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744977</id>
	<title>A humble submission...</title>
	<author>Anonymous</author>
	<datestamp>1255536120000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Your post advocates a</p><p>(x) technical ( ) legislative ( ) market-based ( ) vigilante</p><p>approach to increasing the interaction between man and machine. Your idea will not work. Here is why it won't work. (One or more of the following may apply to your particular idea, and it may have other flaws which used to vary from state to state before a bad federal law was passed.)</p><p>(x) Users will not put up with it<br>(x) Poor ergonomics<br>( ) No one will build drivers for your device unless they own the patent<br>( ) We already tried new interaction paradigms with Dvorak<br>( ) The police will not put up with it<br>(x) Cut and paste doesn't work the way users expect<br>(x) Lack of tactile feedback</p><p>Specifically, your plan fails to account for</p><p>(x) Elbows resting on mouse surface while typing on the keyboard<br>(x) Handicapped or paralyzed users<br>(x) Sticky fluids on the device<br>( ) Asshats<br>(x) Susceptibility to data entry errors caused by cats<br>(x) Microsoft<br>(x) Extensor fatigue in fingers<br>(x) Won't work with VT100<br>(x) There is no add-on for World of Warcraft</p><p>and the following philosophical objections may also apply:</p><p>(x) Ideas similar to yours are easy to come up with, yet none have ever<br>been shown practical<br>( ) I won't accept anything less than a GitS cyberbrain<br>( ) The name of the device sucks<br>( ) Not everyone wants to learn how to play the piano<br>(x) Tablet devices have already failed in the marketplace<br>( ) Killing them that way is not slow and painful enough</p><p>Furthermore, this is what I think about you:</p><p>(x) Sorry dude, but I don't think it would work.<br>( ) This is a stupid idea, and you're a stupid person for suggesting it.<br>( ) Nice try, assh0le! I'm going to find out where you live and burn your<br>house down!</p></htmltext>
<tokenext>Your post advocates a ( x ) technical ( ) legislative ( ) market-based ( ) vigilanteapproach to increasing the interaction between man and machine .
Your idea will not work .
Here is why it wo n't work .
( One or more of the following may apply to your particular idea , and it may have other flaws which used to vary from state to state before a bad federal law was passed .
) ( x ) Users will not put up with it ( x ) Poor ergonomics ( ) No one will build drivers for your device unless they own the patent ( ) We already tried new interaction paradigms with Dvorak ( ) The police will not put up with it ( x ) Cut and paste does n't work the way users expect ( x ) Lack of tactile feedbackSpecifically , your plan fails to account for ( x ) Elbows resting on mouse surface while typing on the keyboard ( x ) Handicapped or paralyzed users ( x ) Sticky fluids on the device ( ) Asshats ( x ) Susceptibility to data entry errors caused by cats ( x ) Microsoft ( x ) Extensor fatigue in fingers ( x ) Wo n't work with VT100 ( x ) There is no add-on for World of Warcraftand the following philosophical objections may also apply : ( x ) Ideas similar to yours are easy to come up with , yet none have everbeen shown practical ( ) I wo n't accept anything less than a GitS cyberbrain ( ) The name of the device sucks ( ) Not everyone wants to learn how to play the piano ( x ) Tablet devices have already failed in the marketplace ( ) Killing them that way is not slow and painful enoughFurthermore , this is what I think about you : ( x ) Sorry dude , but I do n't think it would work .
( ) This is a stupid idea , and you 're a stupid person for suggesting it .
( ) Nice try , assh0le !
I 'm going to find out where you live and burn yourhouse down !</tokentext>
<sentencetext>Your post advocates a(x) technical ( ) legislative ( ) market-based ( ) vigilanteapproach to increasing the interaction between man and machine.
Your idea will not work.
Here is why it won't work.
(One or more of the following may apply to your particular idea, and it may have other flaws which used to vary from state to state before a bad federal law was passed.
)(x) Users will not put up with it(x) Poor ergonomics( ) No one will build drivers for your device unless they own the patent( ) We already tried new interaction paradigms with Dvorak( ) The police will not put up with it(x) Cut and paste doesn't work the way users expect(x) Lack of tactile feedbackSpecifically, your plan fails to account for(x) Elbows resting on mouse surface while typing on the keyboard(x) Handicapped or paralyzed users(x) Sticky fluids on the device( ) Asshats(x) Susceptibility to data entry errors caused by cats(x) Microsoft(x) Extensor fatigue in fingers(x) Won't work with VT100(x) There is no add-on for World of Warcraftand the following philosophical objections may also apply:(x) Ideas similar to yours are easy to come up with, yet none have everbeen shown practical( ) I won't accept anything less than a GitS cyberbrain( ) The name of the device sucks( ) Not everyone wants to learn how to play the piano(x) Tablet devices have already failed in the marketplace( ) Killing them that way is not slow and painful enoughFurthermore, this is what I think about you:(x) Sorry dude, but I don't think it would work.
( ) This is a stupid idea, and you're a stupid person for suggesting it.
( ) Nice try, assh0le!
I'm going to find out where you live and burn yourhouse down!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744643</id>
	<title>This problem has been solved on my desktop</title>
	<author>Kelsin5</author>
	<datestamp>1255534800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>On linux, I use a windows manager that lets me bind keys for "goto firefox" or "goto emacs". Or I use virtual desktops basically for the same thing. On my mac I can use Quicksilver for the same task. Some pre-defined, determined key combination that brings me directly where I want to go. Any task not in my day to day works with expose, or alt tab, etc. Often Quicksilver solves this task quicker than these methods anyway.

No zooming over a list, or stack, or grid, or anything. The keyboard alone can already solve these tasks with the mouse providing extra support when needed.

While the video was cool, I don't think it solves any issues that can't already be solved in a much easier fashion.</htmltext>
<tokenext>On linux , I use a windows manager that lets me bind keys for " goto firefox " or " goto emacs " .
Or I use virtual desktops basically for the same thing .
On my mac I can use Quicksilver for the same task .
Some pre-defined , determined key combination that brings me directly where I want to go .
Any task not in my day to day works with expose , or alt tab , etc .
Often Quicksilver solves this task quicker than these methods anyway .
No zooming over a list , or stack , or grid , or anything .
The keyboard alone can already solve these tasks with the mouse providing extra support when needed .
While the video was cool , I do n't think it solves any issues that ca n't already be solved in a much easier fashion .</tokentext>
<sentencetext>On linux, I use a windows manager that lets me bind keys for "goto firefox" or "goto emacs".
Or I use virtual desktops basically for the same thing.
On my mac I can use Quicksilver for the same task.
Some pre-defined, determined key combination that brings me directly where I want to go.
Any task not in my day to day works with expose, or alt tab, etc.
Often Quicksilver solves this task quicker than these methods anyway.
No zooming over a list, or stack, or grid, or anything.
The keyboard alone can already solve these tasks with the mouse providing extra support when needed.
While the video was cool, I don't think it solves any issues that can't already be solved in a much easier fashion.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744657</id>
	<title>going in circles</title>
	<author>Anonymous</author>
	<datestamp>1255534860000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>Apple got its multitouch technology by buying a company called FingerWorks.  FingerWorks' primary product was just like what 10/GUI describes: a multitouch surface that could either replace they keyboard or the mouse(pad).  It largely failed in the market.</p><p>People use the keyboard and mouse because they really work well.  If people did want more DOF, it would be easy to add more sensors to a standard mouse, for example to record twisting, pushing, and other pressures, but even that isn't catching on.</p><p>Another idea that keeps bubbling up is the idea of pressure sensitive keyboards; they also keep failing because the resulting interactions just become too complex and add little benefit.</p><p>The real flaw in all these devices is the assumption that the limiting factor in communicating with machines is they "bandwidth" of they keyboard and mouse.  It really isn't.  Generally, people can think no faster than they can type and mouse, and speeding up the keyboard or mouse any further is pointless.</p></htmltext>
<tokenext>Apple got its multitouch technology by buying a company called FingerWorks .
FingerWorks ' primary product was just like what 10/GUI describes : a multitouch surface that could either replace they keyboard or the mouse ( pad ) .
It largely failed in the market.People use the keyboard and mouse because they really work well .
If people did want more DOF , it would be easy to add more sensors to a standard mouse , for example to record twisting , pushing , and other pressures , but even that is n't catching on.Another idea that keeps bubbling up is the idea of pressure sensitive keyboards ; they also keep failing because the resulting interactions just become too complex and add little benefit.The real flaw in all these devices is the assumption that the limiting factor in communicating with machines is they " bandwidth " of they keyboard and mouse .
It really is n't .
Generally , people can think no faster than they can type and mouse , and speeding up the keyboard or mouse any further is pointless .</tokentext>
<sentencetext>Apple got its multitouch technology by buying a company called FingerWorks.
FingerWorks' primary product was just like what 10/GUI describes: a multitouch surface that could either replace they keyboard or the mouse(pad).
It largely failed in the market.People use the keyboard and mouse because they really work well.
If people did want more DOF, it would be easy to add more sensors to a standard mouse, for example to record twisting, pushing, and other pressures, but even that isn't catching on.Another idea that keeps bubbling up is the idea of pressure sensitive keyboards; they also keep failing because the resulting interactions just become too complex and add little benefit.The real flaw in all these devices is the assumption that the limiting factor in communicating with machines is they "bandwidth" of they keyboard and mouse.
It really isn't.
Generally, people can think no faster than they can type and mouse, and speeding up the keyboard or mouse any further is pointless.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29752087</id>
	<title>Window management was never the problem</title>
	<author>dirkdodgers</author>
	<datestamp>1255528740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Window management is a solved problem.</p><p>I see their video with this contorted user interface for accessing what are just standard applications, and I know they've missed the boat.</p><p>If they had spent all the time they put into the window manager, into researching powerful uses of multi-touch to carry out the functions of common business APPS, then they might have something.</p><p>As it stands this is just another window manager to toss in the dustbin of failed window manager history. I mean seriously, the window manager reverts back to Alt+Tab or Expose style operation for more than 5 windows anyhow. I would never consider using this over Expose.</p></htmltext>
<tokenext>Window management is a solved problem.I see their video with this contorted user interface for accessing what are just standard applications , and I know they 've missed the boat.If they had spent all the time they put into the window manager , into researching powerful uses of multi-touch to carry out the functions of common business APPS , then they might have something.As it stands this is just another window manager to toss in the dustbin of failed window manager history .
I mean seriously , the window manager reverts back to Alt + Tab or Expose style operation for more than 5 windows anyhow .
I would never consider using this over Expose .</tokentext>
<sentencetext>Window management is a solved problem.I see their video with this contorted user interface for accessing what are just standard applications, and I know they've missed the boat.If they had spent all the time they put into the window manager, into researching powerful uses of multi-touch to carry out the functions of common business APPS, then they might have something.As it stands this is just another window manager to toss in the dustbin of failed window manager history.
I mean seriously, the window manager reverts back to Alt+Tab or Expose style operation for more than 5 windows anyhow.
I would never consider using this over Expose.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744419</id>
	<title>Change</title>
	<author>Anonymous</author>
	<datestamp>1255533900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I am a proponent of change, when it makes sense. I love the interactions here and I would greatly enjoy this, for about two days. Then the luster would wear away and this would become an inconvenience.</p></htmltext>
<tokenext>I am a proponent of change , when it makes sense .
I love the interactions here and I would greatly enjoy this , for about two days .
Then the luster would wear away and this would become an inconvenience .</tokentext>
<sentencetext>I am a proponent of change, when it makes sense.
I love the interactions here and I would greatly enjoy this, for about two days.
Then the luster would wear away and this would become an inconvenience.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29752311</id>
	<title>Same ole demo stuff</title>
	<author>Griffyn</author>
	<datestamp>1255530240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>They wow you with eye candy and showing how easy it is to move windows around, and draw random lines, and zoom in on photographs.  Who is spending all their time doing these tasks?

Show me the same interface with someone doing real work, like coding/writing documents, or touching up artwork, or working with spreadsheets - the stuff we spend 99.9\% of our time doing.  Methinks the new GUI would show many many weaknesses.</htmltext>
<tokenext>They wow you with eye candy and showing how easy it is to move windows around , and draw random lines , and zoom in on photographs .
Who is spending all their time doing these tasks ?
Show me the same interface with someone doing real work , like coding/writing documents , or touching up artwork , or working with spreadsheets - the stuff we spend 99.9 \ % of our time doing .
Methinks the new GUI would show many many weaknesses .</tokentext>
<sentencetext>They wow you with eye candy and showing how easy it is to move windows around, and draw random lines, and zoom in on photographs.
Who is spending all their time doing these tasks?
Show me the same interface with someone doing real work, like coding/writing documents, or touching up artwork, or working with spreadsheets - the stuff we spend 99.9\% of our time doing.
Methinks the new GUI would show many many weaknesses.</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744155
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744727
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745491
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29754897
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744155
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744727
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746141
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_47</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744479
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745705
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29751617
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_52</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745119
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744371
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746919
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747781
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744653
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29753807
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745889
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_53</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744657
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745723
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29767271
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744177
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744653
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747663
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744653
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748483
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744653
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748227
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_50</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747685
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747603
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744181
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745537
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744417
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29753813
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744181
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745143
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745239
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744493
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744325
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748447
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744659
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29751799
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744325
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29755213
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744657
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745511
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747383
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_48</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744653
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746655
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746127
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_54</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744181
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744809
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29751679
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744933
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744949
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744953
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747277
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744181
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29750511
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747719
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744371
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29751695
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745705
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29749673
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744657
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746173
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_51</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744325
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29749535
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744905
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744657
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747395
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744181
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745957
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744659
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745993
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746969
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744155
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744727
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29750929
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744657
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745943
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744337
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744643
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747927
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_49</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744155
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29750397
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747199
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745583
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744967
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29750613
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744459
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_138207_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745705
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748779
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744573
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744449
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744653
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748483
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748227
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747663
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29753807
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746655
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744801
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744643
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747927
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744325
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29749535
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748447
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29755213
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29758153
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744311
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29743965
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745239
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746127
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747603
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747719
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744177
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744953
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747781
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747277
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744181
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744809
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29751679
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745957
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29750511
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745537
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745143
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744479
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744155
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744727
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745491
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29754897
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29750929
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746141
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29750397
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747383
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744949
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746969
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745119
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747685
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744337
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744493
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744933
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745153
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744459
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744905
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744417
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29753813
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745583
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745889
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747199
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744321
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29759883
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744967
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29750613
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744371
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29751695
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746919
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745705
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29749673
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29748779
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29751617
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744767
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29753221
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744657
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745723
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29767271
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745943
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29746173
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745511
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29747395
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744715
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745111
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745223
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744659
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745993
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29751799
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29745095
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29755527
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_138207.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_138207.29744591
</commentlist>
</conversation>
