A touch screen table would solve that problem. In a perfect world we would have desks whose entire surface is a multi-touch screen, not as a replacement but additionally to "regular" monitors to allow exactly these kinds of interfaces.
Not really--you'd still be using large-arm motions on a large surface, holding up your arms so you wouldn't generate false touches. Even palm detection won't help, as you'd still need the large-scope motions to tie things together.
A possible solution: You need additional tablets. There are swipe gestures to transfer parts to your tablet for further interaction. When you are ready, you swipe the result back on the table/large monitor to compose the end result.
In my experience (multiple hours of touch screen use per day, sometimes >40hrs/week for weeks on end), "gorilla arm" is a total myth. Yes, if you switched to a touch screen without changing any other aspect of your workspace you might have issues with the screen being too far away or too high, but that would just be silly.
This looks really awesome. For a long time, I've thought that multi-touch has been very under used, it's nice to see people thinking outside of the desktop OS paradigm. I would imagine this would be quite useful with a Wacom tablet as well - any thoughts on that?
I've never reviewed articles before, but one thought from looking at your video is that it might be nice to be able to group things in a more concrete way, for example, if you are picking out different themes from the article. I was immediately reminded of BumpTop. I think that a part that is not necessarily focused on in the video is more rigorous organization of the snippets that you take out of the article.
It's a kind of belated consolation that people are finally waking up to the potential of transclusion, structured notetaking and active reading in assisting and boosting human intelligence, decades after the onset of the still unfulfilled visions of forefathers such as Ted Nelson and Douglas Engelbart; and it's definitely great to see skillful people working on the vastly unpopular field of general-purpose production software of the literary kind. But this is just the thing that ideally shouldn't be productized and shut into the walled garden of an iPad application, unable to flexibly integrate into a user's broader systems of knowledge and memory. Hopefully the technology will have much more extensive implementations beyond the application.
We should have had this kind of thing as a standard part of our common user-facing software by now; in all software related to reading and writing. All implemented in free software, open protocols and standards, in a distributed manner, not tied to one company or organization. In 2012, I should have been able to practically link a paragraph of my comment here to a line on a local PDF file, another paragraph on that file to a particular portion of a web video, and string a group of such links and transclusions together, comment further on them, keep them under version control, and share them with others, without being tied to a single service or application. This stuff should be infrastructure.
And this is what personal computers were supposed to be all about, before the original naive and optimistic vision of enhancing human intelligence and distributed production and sharing gave way to the current situation where personal computers are used mainly to mindlessly consume centrally produced crap. I'm still looking forward to and willing to work towards an updated variant of that vision, but it's going to be an uphill battle.
I have to wonder if something like this, tied to Google Glasses, might not make a great interface for using the things we do everyday to classify our world for ourselves, into tagged and meaningful links to be reused by others.
I assume you mean recent and active projects; there's nothing recent I can remember that attempts to do the kind of thing I tried to describe in the second paragraph of my comment. (Which is why I intend to start working on my own modest, desperate attempt at it in the following months.)
However, there are various projects, some of them historical, that have attempted to tackle it in limited contexts, or implemented parts of it, or have envisioned it in holistic systems that are now outdated. Almost all of the somewhat interesting ones I've come across can unfortunately be classified as one of the following: 1) Productized, narrowly focused yet-another-app 2) Academic or overly specialized in-house or personal project with no real effort at widespread usability 3) Unmaintained and outdated 4) Essentially vaporware
With that said, here are a few links of interest, with the forefathers noted first:
I'm in the preliminary research phase, and it's too early to tell. But I'm investigating the feasibility of using the Open Annotation data model (draft: http://openannotation.org/spec/core/), which they are also basing their work on, so the possibility is open.
Thanks for the link; I've been out of touch with his writing for some time. It's good to be reminded.
As for help, I'm going to need much of it once things materialize. It's going to be free (as in freedom) software, and contributions will be essential; but I don't intend to release anything until the initial architecture is settled and I have a working, dogfoodable version 0.1. And if I fail to create the necessary living conditions for focusing on the project, that can take a while.
I hope you don't mind me contacting you when that celebrated time comes. And if anyone is interested in updates or would like to discuss related matters, feel free to say hello at the email at the address in my profile. (Some folks already have; thank you.)
As a professional writer, I don't find this very useful. This software doesn't solve any actual problems I have ever had in journalism, book writing, book editing, fiction writing, or blogging. It is not any easier to do all of this in this way than it is with existing tools, except in the end look at what we're left with in your new application... a complete and total disorganized mess. I don't even want to touch that document after you've pulled it apart and screwed it all up like that. There is no substitute for a rewrite.
It seems like this was designed by a software developer who imagined potential problems that writers have, while desperately looking for a cool new way to use multi-touch.
So let me tell you about the actual problems I have as a professional writer. Maybe some/most/all of them are unique to me -- I don't really know.
1. Consistent access to the same documents across multiple devices, without storing them on any one specific device. I have solved this problem with SpiderOak, and by adjusting my file formats and toolsets across all devices.
2. Touchpad keyboards aren't big enough, or accurate enough for me. It is very difficult to write at the speed of thought on a touchscreen device. I can type much faster on a tactile keyboard, and I can always type faster than I can handwrite, even in shorthand.
3. Font hell. When you go to publish something from a word processor or PDF generator, you must have a license for all of the fonts you use. If you want to use open source fonts, that's fine -- maybe even preferable -- but then you have to use a clever font replacement scheme (which doesn't work for me), or embed the fonts in the document. Embedding fonts takes up a huge amount of space, and there is always one you forget (the page numbers in the footer, the title, even places that don't seem to have any text).
4. Character set encoding hell. Special characters don't translate well across multiple applications. Especially if you are writing in Word and pasting into blog software.
As a writer, I want to write. I don't want to learn a new interface. I do not want to use a multi-touch screen because the fastest form of written communication I've ever experienced is already available to me. Not every old paradigm is bad; not every old design is begging for improvement.
I want to have very little hassle when it comes to editing, publishing, and backup/version control. Can you solve that problem for me? Like, make LyX or LibreOffice save to easily accessible yet secure private cloud storage with rollback capabilities, output directly to CreateSpace, Lulu, and other publishing services without having to embed fonts or screw with formatting and templating?
I like it, but in all honesty - I don't see how multi-touch brings any advantage compared to a keyboard+mouse for this application.
The workflow is a bit different yes, but there is barely anything in there that really takes advantage of multi-touch gestures more than zoom, and there are many great zoom implementations available when using a mouse.
Regardless this could be quite useful, my biggest gripe is exporting your work, you should be able to export it to a PDF or something so that anyone can read or print it while still retaining comments, links etc. in a good, intuitive, way. That will make or break it in my eyes (granted I've only glanced at it so far) and I didn't see anything about that on the site/videos.
Not saying that it is badly suitable for multi-touch but I just have a hard time seeing myself working with my hands like that for a long session. Mouse + keyboard is vastly superior in terms of ergonomics and if I will be writing long comments a real keyboard is a must.
On a tablet? Sure, but feels like the UI requires a larger screen than a tablet.
My thoughts exactly. In fact, watching the presentation gave me the impressions that the touch ui was actually slightly awkward to work with, compared to using a mouse.
That's not a problem, as the application it self is quite interesting. So I think they should focus on that and then let the ui be secondary. When using it on a tablet, touch-ui is used, when on a laptop/desktop machine, the mouse/keyboard ui is used.
This looks amazing. It's nice to see a different take on a UI for working with bigger documents. I must say I'm not a huge fan of touch interfaces but something like this could port well to a kinect type interface. Project the screen onto a wall and add some voice recognition and kinect and you could have fun working on big texts while standing and moving around the room. You could write a book in a room without a chair or desk.
This is great. When reviewing/editing/revising technical manuscripts (journal articles, technical reports, dissertations etc) this would be extremely handy, and cut out the constant scrolling to check and recheck definitions and parts of the document with others. Referring back to the materials and methods section is an obvious use-case.
Would be nice to see the layout of comments/notes etc on the RHS be more structured (snapped to a grid?) though. Shouldn't have to zoom in and out on these.
Now if this was combined with one of those Wacom 24 or 27" touch screen displays ... :)
Seems really cool but I can't ever see using a giant touchscreen all day like that. Imaging the fatigue that would ensue and the Repetitive Use Injuries (RSI) that would occur.
I really like the concept though. I would really like to see something that used similar features in a coding IDE.
30 comments
[ 0.13 ms ] story [ 69.1 ms ] threadBut how do you avoid the "gorilla arm" problem with large touch-screen monitors?
"Swept Frequency Capacitive Sensing" http://www.youtube.com/watch?v=E4tYpXVTjxA
Basically the idea is to make devices aware of the physical context of user interactions.
I've never reviewed articles before, but one thought from looking at your video is that it might be nice to be able to group things in a more concrete way, for example, if you are picking out different themes from the article. I was immediately reminded of BumpTop. I think that a part that is not necessarily focused on in the video is more rigorous organization of the snippets that you take out of the article.
We should have had this kind of thing as a standard part of our common user-facing software by now; in all software related to reading and writing. All implemented in free software, open protocols and standards, in a distributed manner, not tied to one company or organization. In 2012, I should have been able to practically link a paragraph of my comment here to a line on a local PDF file, another paragraph on that file to a particular portion of a web video, and string a group of such links and transclusions together, comment further on them, keep them under version control, and share them with others, without being tied to a single service or application. This stuff should be infrastructure.
And this is what personal computers were supposed to be all about, before the original naive and optimistic vision of enhancing human intelligence and distributed production and sharing gave way to the current situation where personal computers are used mainly to mindlessly consume centrally produced crap. I'm still looking forward to and willing to work towards an updated variant of that vision, but it's going to be an uphill battle.
However, there are various projects, some of them historical, that have attempted to tackle it in limited contexts, or implemented parts of it, or have envisioned it in holistic systems that are now outdated. Almost all of the somewhat interesting ones I've come across can unfortunately be classified as one of the following: 1) Productized, narrowly focused yet-another-app 2) Academic or overly specialized in-house or personal project with no real effort at widespread usability 3) Unmaintained and outdated 4) Essentially vaporware
With that said, here are a few links of interest, with the forefathers noted first:
* Xanadu: http://en.wikipedia.org/wiki/Project_Xanadu
* NLS: https://en.wikipedia.org/wiki/NLS_%28computer_system%29
* Relations: http://relations-rcp.sourceforge.net/
* Zettelkasten: http://zettelkasten.danielluedecke.de/en/index.php
* semantic-notes: https://github.com/jsomers/semantic-notes
* Synapsen: http://www.verzetteln.de/synapsen/shots_e.html
* flashbake: https://github.com/commandline/flashbake
* ConnectedText: http://www.connectedtext.com/
* The Literary Machine: http://sommestad.com/lm.htm
* Leo: http://webpages.charter.net/edreamleo/front.html
* Smart Notebooks (currently seeking funding on Kickstarter): http://www.kickstarter.com/projects/1947703258/smart-noteboo...
* Bibkosh: http://www.bibkosh.com
* gitmarks: https://github.com/hmason/gitmarks
* Lifestreams: http://cs-www.cs.yale.edu/homes/freeman/lifestreams.html , http://www.wired.com/wired/archive/5.02/fflifestreams.html
* Locker: https://github.com/quartzjer/Locker
* Telehash: http://telehash.org/
* Singly: https://www.singly.com/
* pan.do/ra: https://pan.do/ra#about
* Papers: http://www.mekentosj.com/papers/
Some related reading:
* http://www.rheingold.com/texts/tft/1.html
* http://takingnotenow.blogspot.co.uk/
* http://www.visi.com/~snowfall/notebook.html
* http://web.archive.org/web/20100422130439/http://gilest.org/...
* pirateking ↗ Thank you very much for this list. andrewflnr ↗ This will supply research material for a long time. Thank you. wallflower ↗ Lifestreams was co-opted by Apple for their Time Machine interface. I think Apple settled with David Gelernter. SudarshanP ↗ Will your work somehow integrate/interface with the work these guys are doing: http://hypothes.is mgunes ↗ I'm in the preliminary research phase, and it's too early to tell. But I'm investigating the feasibility of using the Open Annotation data model (draft: http://openannotation.org/spec/core/), which they are also basing their work on, so the possibility is open. drothlis ↗ * Smallest federated wiki: http://wardcunningham.github.com mgunes ↗ Thanks; I forgot about it somehow. Previous HN discussion: http://news.ycombinator.com/item?id=4199260 melloclello ↗ Stanislav Datskovskiy (http://www.loper-os.org/?p=8) is a particular favourite writer of mine, on this kind of topic. mgunes ↗ Thanks for the link; I've been out of touch with his writing for some time. It's good to be reminded.
Here is a video: http://www.youtube.com/watch?v=cNrAS979MfA
Also, would you like any help?
As for help, I'm going to need much of it once things materialize. It's going to be free (as in freedom) software, and contributions will be essential; but I don't intend to release anything until the initial architecture is settled and I have a working, dogfoodable version 0.1. And if I fail to create the necessary living conditions for focusing on the project, that can take a while.
I hope you don't mind me contacting you when that celebrated time comes. And if anyone is interested in updates or would like to discuss related matters, feel free to say hello at the email at the address in my profile. (Some folks already have; thank you.)
It seems like this was designed by a software developer who imagined potential problems that writers have, while desperately looking for a cool new way to use multi-touch.
So let me tell you about the actual problems I have as a professional writer. Maybe some/most/all of them are unique to me -- I don't really know.
1. Consistent access to the same documents across multiple devices, without storing them on any one specific device. I have solved this problem with SpiderOak, and by adjusting my file formats and toolsets across all devices.
2. Touchpad keyboards aren't big enough, or accurate enough for me. It is very difficult to write at the speed of thought on a touchscreen device. I can type much faster on a tactile keyboard, and I can always type faster than I can handwrite, even in shorthand.
3. Font hell. When you go to publish something from a word processor or PDF generator, you must have a license for all of the fonts you use. If you want to use open source fonts, that's fine -- maybe even preferable -- but then you have to use a clever font replacement scheme (which doesn't work for me), or embed the fonts in the document. Embedding fonts takes up a huge amount of space, and there is always one you forget (the page numbers in the footer, the title, even places that don't seem to have any text).
4. Character set encoding hell. Special characters don't translate well across multiple applications. Especially if you are writing in Word and pasting into blog software.
As a writer, I want to write. I don't want to learn a new interface. I do not want to use a multi-touch screen because the fastest form of written communication I've ever experienced is already available to me. Not every old paradigm is bad; not every old design is begging for improvement.
I want to have very little hassle when it comes to editing, publishing, and backup/version control. Can you solve that problem for me? Like, make LyX or LibreOffice save to easily accessible yet secure private cloud storage with rollback capabilities, output directly to CreateSpace, Lulu, and other publishing services without having to embed fonts or screw with formatting and templating?
The workflow is a bit different yes, but there is barely anything in there that really takes advantage of multi-touch gestures more than zoom, and there are many great zoom implementations available when using a mouse.
Regardless this could be quite useful, my biggest gripe is exporting your work, you should be able to export it to a PDF or something so that anyone can read or print it while still retaining comments, links etc. in a good, intuitive, way. That will make or break it in my eyes (granted I've only glanced at it so far) and I didn't see anything about that on the site/videos.
Not saying that it is badly suitable for multi-touch but I just have a hard time seeing myself working with my hands like that for a long session. Mouse + keyboard is vastly superior in terms of ergonomics and if I will be writing long comments a real keyboard is a must.
On a tablet? Sure, but feels like the UI requires a larger screen than a tablet.
That's not a problem, as the application it self is quite interesting. So I think they should focus on that and then let the ui be secondary. When using it on a tablet, touch-ui is used, when on a laptop/desktop machine, the mouse/keyboard ui is used.
Would be nice to see the layout of comments/notes etc on the RHS be more structured (snapped to a grid?) though. Shouldn't have to zoom in and out on these.
Now if this was combined with one of those Wacom 24 or 27" touch screen displays ... :)
I really like the concept though. I would really like to see something that used similar features in a coding IDE.