Slashdot Mirror


Douglas Engelbart's HyperScope 1.0 Launched

ReadWriteWeb writes, "HyperScope 1.0 is a new Web app based on Douglas Engelbart's 1968 NLS/Augment (oNLine System). Engelbart and team have been working on Hyperscope since March of this year in a project funded by the National Science Foundation. Its aim is to rebuild portions of Engelbart's NLS, on the Web, using current Web technologies such as Ajax and DHTML. In effect it gives an advanced browsing experience, including classic hypertext features like indirect links and transclusions of remote pieces of other documents. HyperScope has been completely built with open source JavaScript toolkit Dojo — meaning that everything is done on the client-side."

82 comments

  1. is this really a good idea? by Desolator144 · · Score: 3, Interesting

    If it takes you 10x longer to design the content and the person viewing the page can find what they want 10x faster then is it really a net gain? (no pun intended) It still is a good way to organize information and beats the crap out of the way some webpage makers do it. It sure would save surfing/researching time but is that a good tradeoff for a massive slowdown in content creation speed because of the page maker having to add all the meta data type stuff?

    --
    now stop reading and go play Dance Dance Revolution!
    1. Re:is this really a good idea? by PhrostyMcByte · · Score: 5, Interesting
      If it takes you 10x longer to design the content and the person viewing the page can find what they want 10x faster then is it really a net gain?
      Maybe it won't make sense if only a single person is viewing it, but with hundreds, the gain could be very useful. Not just to the readers, but the writer too - if 100 people view the doc and 75% of them are able to understand it better thanks to this, that's much less questions the writer will have to waste time answering.
    2. Re:is this really a good idea? by Qzukk · · Score: 2, Insightful

      If it takes you 10x longer to design the content and the person viewing the page can find what they want 10x faster then is it really a net gain?

      What if two people find what they want 10x faster? (Other than what would really happen: companies would switch from 10 words on an ad-filled page to 5 words each?) There are generally more content consumers than creators, both in the general sense as well as in the case of just about any field.

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    3. Re:is this really a good idea? by RuBLed · · Score: 2, Interesting

      and it seems to be not compatible with Opera [the browser I'm using now] so I tried loading it in IE7 RC1 and only got it to work after around 4 or 5 "permission to run active x controls" (you know, that yellow information toolbar)

      So then I browsed the demo, hmmm.. the interface looks fresh and promising, but for compatability reasons, it is much easier (and faster) to browse a document thru html links or by printing them. Although I believe this HyperScope concept (or something similar) is bound to be popular to certain kinds of documents (especially long documents).

      but.. I'd miss the 25-page articles with all the subliminal ads. :)

    4. Re:is this really a good idea? by PhunkySchtuff · · Score: 1

      If it takes you 10x longer to design it, and users can find what they're after 2x faster, and there are 5 users, then yes - there is a nett gain.
      Development/design is generally done once, but reading and digesting the information happens over and over again, by many many different people.

  2. Wiki? by ScruffyNerf · · Score: 1

    IMHO it seems that this would be a good add-in for community reference materials like wiki's.

    Unfortunately the spammers will probably hook into this first... or the 'Web 2.0' crowd.

    1. Re:Wiki? by ballermann · · Score: 3, Informative

      Eugene Kim [1] (why didn't the poster give him credit? It's mostly his work, but I guess Doug is just a tid bit more popular) presented the system at WikiSym2006 [2] and did indeed show how to integrate this as additional view into a Wiki (I think he used his PurpleWiki [3])

      [1] http://www.eekim.com/blog/
      [2] http://wikisym.org/ws2006/
      [3] http://www.blueoxen.com/tools/purplewiki/

      --

      Need a Wiki? Check out DokuWiki

  3. How does it compare to Xanadu? by Beryllium+Sphere(tm) · · Score: 1

    Community orientation, granular targeting, indirect linking and of course transclusion were all part of the Xanadu vision. How's this different, except for the notable distinction of actually existing?

    1. Re:How does it compare to Xanadu? by fm6 · · Score: 1

      All the buzzwords are completely different!

    2. Re:How does it compare to Xanadu? by Eideewt · · Score: 2, Insightful

      Existing seems to be HyperScope's big advantage.

    3. Re:How does it compare to Xanadu? by Myself · · Score: 1

      Ahh, glad I looked for mentions of Project Xanadu before posting! Yes, this sounds like a rehash of the same ideas.

      Existing is good.

    4. Re:How does it compare to Xanadu? by Mateo_LeFou · · Score: 1

      Also it doesn't seem to go in for micropayments everywhere.

      --
      My turnips listen for the soft cry of your love
    5. Re:How does it compare to Xanadu? by BradNeuberg · · Score: 1

      This is also a reimplementation of the original hypertext system, the one that invented hyperlinks in the 60s, named Augment/NLS, so it predates Ted Nelson's Xanadu and his book Computer Lib. Just to note Ted Nelson actually invented the word "hyperlink" and "hypertext", but Douglas Engelbart had a working hypertext system first; he just called them 'addresses' and 'links'. HyperScope is a clone of parts of Augment for the contemporary web.

  4. Actual link by generic-man · · Score: 5, Informative

    Actual site: http://hyperscope.org/

    Blog blog blog blog blog, blog blogpost blog blog...

    --
    For more information, click here.
    1. Re:Actual link by tehcyder · · Score: 1
      Blog blog blog blog blog, blog blogpost blog blog...
      Your ideas are intriguing to me and I wish to subscribe to your newsletter.
      --
      To have a right to do a thing is not at all the same as to be right in doing it
  5. One first use... by Anonymous Coward · · Score: 0

    ...it just seems like a hierarchal tree of data. You can expand/contract content to go into more detail. I guess I'm missing the point.

  6. AHA! caution: massive insight inside by Desolator144 · · Score: 5, Funny

    I figured out how to make this super popular! With all these capabilities, they should just take that tiny extra step and have disaster scenarios like a monster slowly eating the info on the page and you have to stop him or a black hole at the bottom of the page sucking up all the text and scrolling you down faster and faster as it grows. That would be cool and would really spice up boring web documents. I think it would even encourage kids to read long research papers more :-)

    --
    now stop reading and go play Dance Dance Revolution!
  7. So let me get this straight.... by supasam · · Score: 3, Interesting

    The demo I looked at on the page seemed to be to be an html doc, with the difference being that instead of clicking the words, you would awkwardly click the column to the left to the line in which the thing you want to link resides? I must be missing something cause I don't see how this might be any easier. True I didn't actually read the paper I was clicking through which happened to be on this topic, but how many web pages do I really actually read anyways? A little help?

    --


    Suck a lemon?
    1. Re:So let me get this straight.... by RuBLed · · Score: 3, Informative

      If I'm right, it is just one file and to put it simply, it is just like reading an html document with the usual anchor tags, where "sections" (div?) appear and disappear as you read the document. If I'm still right, it would create an illusion that you are reading several pages but in reality, you only made that part of the page visible by clicking on the appropriate "links" or "arrows". The article says everything is client-side so I assume the document is all there.

    2. Re:So let me get this straight.... by Anonymous Coward · · Score: 1, Insightful

      So it's basically the same as the "New Discussion System" which is currently being tested right here on Slashdot?

    3. Re:So let me get this straight.... by TrappedByMyself · · Score: 3, Informative

      Yeah, I really don't get it either. The little buttons appear even if there is no useful action to take. If the text is expanded, or whatever its doing, you can still click the little page icon. Doing so, it jumps to some other location, then jumps back to somewhere close to where you were, could be the same line, could be a few lines off. If you hit a few lines off, the technology has successfully disoriented you and has given you no way to get back to where you were before.

      I guess if the team's goal was to create something which is even more of a navigation nightmare than Flash, well, then, They're Winner!

      --

      Help me take back Slashdot. When did 'News for Nerds' become 'FUD and Conspiracy Theories for Extremist Nutjobs'?
    4. Re:So let me get this straight.... by supasam · · Score: 2, Interesting

      Indeed, it took me a couple (few) clicks to realize that not only was I still on the same page, but that the page I was on wasn't as long as I thought it was. If they'd have demo'ed something huge like the Sams FreeBSD 6 unleashed book (weighing in at about 877 pages including the index) or something like that, maybe there could have been something to it. I don't see this being all that useful to me as of yet.

      --


      Suck a lemon?
    5. Re:So let me get this straight.... by HiThere · · Score: 1

      Except that the Slashdot version works better, and is more intuitive without instruction.

      Zigzag looked more promissing, but seems to have been dead since 2001, and moribund since 1999. As I read it, Zigzag appears to be based around a resizeable vector of doubly-linked lists that were conceptualized as being orthogonal. Could have been *very* interesting, but probably also quite confusing to navigate.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  8. There's hope. by exp(pi*sqrt(163)) · · Score: 4, Funny

    Version 1.0 conceived in 1968, implemented in 2006. There's home for Duke Nukem Forever then.

    --
    Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
    1. Re:There's hope. by bobby1234 · · Score: 1

      but no HOPE for you.... sorry but nice typo

  9. People are strange... by pianoben · · Score: 1, Insightful

    I'm surprised that the man who spearheaded the development of the mouse would produce such an unnavigable system; you can't even scroll down with the arrow keys! Of course, in his vision, you're using a mouse and a 5-key chording keyboard; no third hand seems to be available for said arrow keys. But to not enable the scroll wheel, either?! No, thanks...

    1. Re:People are strange... by civilizedINTENSITY · · Score: 1

      Well my scroll wheel is sure working. So are my arrow keys. Did you try the original website's demo? It looks like HTML merged with an Outliner.

  10. Moo by Chacham · · Score: 2, Interesting
    here

    For example, every paragraph in a HyperScope document has a location number, an address corresponding to the paragraph's location in a document. For example, the second paragraph in the top-level of a document has the location number 2. To link to this paragraph, you can use the address:

        http://foo/bar.opml#2

    To jump directly to the second paragraph while viewing a document, you can click on the Jump button, type 2, and press Apply.


    Isn't this just an anchor tag on drugs? Just make it part of HTML 5.
    1. Re:Moo by Lars+Arvestad · · Score: 3, Insightful
      Isn't this just an anchor tag on drugs? Just make it part of HTML 5.
      I would actually like to see something like this in HTML. I have always found it a bit weak that you have to explicitly put anchors in your document to be able to jump there. Of course, I have not been clever enough to suggest an improvement or even voice my disapproval.

      Some way of saying "fifth P element of this document" or "H1 element with text 'The Main Point'" should all be pretty easy to implement for a client program.

      --
      Reality or nothing.
    2. Re:Moo by hey! · · Score: 3, Insightful

      http://foo/bar.opml#2

      I think it has to do with how the reference is generated.

      OPML is an XML standard for creating outlines. You use your favorite OPML outliner, dump it on the web, and suddenly you have a web version of the outline. OPML was not designed as a web standard; once you put an OPML document on the web, it immediately becomes obvious that every node in the outline ought to have some kind of address you can link to.

      I'm not terribly thrilled by this approach, but something like it is necessary. I'd rather extend OPML so that every node has a UUID, as well as an optional human readable idea. That way you could cite the node as http://foo.bar.opml#dbcb7190-3d9b-11db-a98b-080020 0c9a66, even if the author did not think it worthy of a human generated ID. The advantage of this system would be that citations would be stable, even if users reorganize the outline. Which is kind of the point of outlining.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    3. Re:Moo by Chacham · · Score: 2, Interesting

      I have always found it a bit weak that you have to explicitly put anchors in your document to be able to jump there.

      Then get a tool to put the tags in for you. Don't mess with the standard that allows the granularity of actually defining it.

    4. Re:Moo by Chacham · · Score: 1

      OPML was not designed as a web standard

      Neither was HTML.

      rather extend OPML so that every node has a UUID, as well as an optional human readable idea. That way you could cite the node as http://foo.bar.opml/#dbcb7190-3d9b-11db-a98b-08002 0 0c9a66, even if the author did not think it worthy of a human generated ID.

      Then just add character or paragraph count. Using current regex expressions, it really should be that hard to implement.

      The advantage of this system would be that citations would be stable, even if users reorganize the outline. Which is kind of the point of outlining.

      A simple hash could do that.

      --

      I see an idea here, but a poor implementation.

      BTW, thanx for your comments.

    5. Re:Moo by hey! · · Score: 1

      Using current regex expressions, it really should be that hard to implement.

      Not if a paragraph was edited.

      A simple hash could do that.

      Not if the paragraph was edited. hash("I like hashes because their good for identifying paragraphs") hash ("I like hashes because they're good for identifying paragraphs")

      Of course you could use some kind of serial genrator, but what if you cut paragraph from one outline and put it into another? UUIDs are just as easy to use and much better. You can move a paragraph from one site to another without it losing its identity.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    6. Re:Moo by kthejoker · · Score: 1

      Exactly, just write your page in XML and then transform it appropriately with XSL.

      if (element in anchorList) {add anchor before element}

      is a fairly simple conditional to apply.

      Or add it to your processor as a function. But parents is right, granularity is the key to all good HTML specs.

    7. Re:Moo by Chacham · · Score: 1

      You can move a paragraph from one site to another without it losing its identity.

      But you said earlier "That way you could cite the node as http://foo.bar.opml/#dbcb7190-3d9b-11db-a98b-08002 0 0c9a66, even if the author did not think it worthy of a human generated ID."

      Well, if the author didn't give it an id, and the id was autogenerated, and then the author changed some of the text, what good is the id? Would not the author be required to decide if the change was major or minor, having a minor change keep the same UID, but a major change gettinga new one? (Much like ISBN numbers work.)

      Which means that the author cannot truly be divorced from the context of serialization, so it is he that would have to give the ids. Or, if they are truly to be autogenerated, even a minor change would require a new id. Imagine a minor change and a move at the same time, how could anyone decide if it is the same or not, and then there's context.

      I admit i like the idea, but i don't see it as being feasable without rules that make it too complicated to be useful.

    8. Re:Moo by KermodeBear · · Score: 1
      Then just add character or paragraph count. Using current regex expressions, it really should be that hard to implement.
      This reminds me of one of my all time favorite programmer quotations, by Jamie Zawinski:
      Some people, when confronted with a problem, think "I know, I'll use regular expressions." Now they have two problems.
      --
      Love sees no species.
    9. Re:Moo by Lars+Arvestad · · Score: 1
      Yeah, sure, but what if it is not my document? If it is a document I own, I wouldn't even bother with using anything other than my favourite authoring tool and put the anchors that I need where I want them. That is probably easier than figuring out what part of the document I want to link to. And if I use some auto-generated anchor using XML+XSL as someone suggested will just cause the pain of figuring our how a new edit would affect the auto-generated anchor-ids.

      The point here is that I want to link to any part of any document.

      --
      Reality or nothing.
    10. Re:Moo by Anonymous Coward · · Score: 0

      > Some way of saying "fifth P element of this document" or "H1 element with text 'The Main Point'" should all be pretty easy to implement for a client program.

      Get browsers to implement xpath and xquery as targets and you're there. The URL spec knows nothing about HTML, and doesn't care what you put after the #

    11. Re:Moo by zacronos · · Score: 1

      That only works if you are linking to webpages you create or can edit. If I'm linking to someone else's massive webpage with no anchor tags, it would be nice to be able to have the link automatically take them to the paragraph/sentence/image I want (just like an anchor tag allows, but without the anchor being explicitly coded). The alternative is to give the link, and say "scroll down to the 5th paragraph in the section on asshats, next-to-last sentence".

      GP's suggestion wouldn't have to change the way named anchors work -- they're still a good thing. But it would be nice if there were also a way to link to arbitrary locations in a webpage.

    12. Re:Moo by Chacham · · Score: 1

      This comment: If it is a document I own, I wouldn't even bother with using anything other than my favourite authoring tool and put the anchors that I need where I want them.

      Previous comment: I have always found it a bit weak that you have to explicitly put anchors in your document to be able to jump there.

      What i commented on, and what you are replying to seem to be different things.

    13. Re:Moo by Chacham · · Score: 1

      And you just reminded me of something i heard during an oral test. It went something like this.

      The tester asked a question, the student gave an elaborate answer. After he finished, the tester said "That's an excellent answer, but for the wrong question."

    14. Re:Moo by Lars+Arvestad · · Score: 1
      Good point. What I had in mind in my first post was: ... explicitly put anchors in a document ... rather than ... in your document...

      Sorry for the confusion.

      --
      Reality or nothing.
    15. Re:Moo by Chacham · · Score: 1

      Ah OK, at least i understand the sentiment now. :)

    16. Re:Moo by hey! · · Score: 1

      You are assuming that all documents are essentially unstructured.

      For truly unstructured documents, such as short story or a blog post, you are right.

      However, there are other kinds of documents, particularly outline structured ones, where nodes in the text do play an indentifiable function. For example, I could say section 1.5.2.1 of our outline, and its descendents, list all the known regulatory requirements our project has to comply with. Or section 2.1 provides a summary of our product position versus the main competitors in our space. etc. Naturally, in these cases if you decide to insert or delete sections, reorganize your outline, all references are off. If you want to include part of one outline in toto as part of another, this doesn't work either.

      In these cases, you want something more structured than a blog post but less structured than a program. There's a whole universe of tasks which are done which demand more structure than a plain old document, but for which creating a special software system is impractical. This is often a place where a wiki sort of works. But I've had zealous editors screw up wikis something fierce, leaving dangling wiki words all over the place. The wiki is kind of close, but not quite there; it confuses presentation with identity.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    17. Re:Moo by Chacham · · Score: 1

      I hear the point, i just don't see this as a breakthrough or anything, and certainly not something thayt isn't mostly alreayd done.

    18. Re:Moo by tehcyder · · Score: 1
      I have not been clever enough to suggest an improvement or even voice my disapproval.
      You must be new here.
      --
      To have a right to do a thing is not at all the same as to be right in doing it
  11. Now I'll never get to sleep by MarkusQ · · Score: 5, Funny

    Great, now I'll never get to sleep.

    First FreeDos 1.0, and now this. If I go to bed now, I'm sure to miss the story I'm really waiting for; just think of it, Babbage's Analytical Engine, completed at last! Will it work the way he thought?

    The suspense is killing me.

    --MarkusQ

    1. Re:Now I'll never get to sleep by James+Youngman · · Score: 1

      yes

    2. Re:Now I'll never get to sleep by velorg · · Score: 2, Informative

      Where you been sleeping, man?
      That hardware (=crucial, number-crunching part of the Mill) was finally implemented waaaay back in 2000 or thereabouts, and is now on display AND running (crank-powered) in The Science Museum in London, UK. Scientific American had a feature on it around then,too. Sorry, no urls.
      Along the way, the two "implementers" discovered several "mechanical" errors in Babbage's original drawings, which would have prevented the Engine from fuctioning even had it been built; so they corrected them, and the concept proved viable after all.

  12. virtual machine by drDugan · · Score: 2, Interesting

    hot damn! browsers really will be a virtual machine.

    I give us about 4.9 years until self-aware computers emerge

  13. the real story by Anonymous Coward · · Score: 0

    Why are U.S. taxpayers (via an NSF grant) paying for this?

  14. Enough with the snide remarks.... by FlyingGuy · · Score: 3, Insightful

    Ohh wait this IS> /. after all...

    Now here's something we hope you'll really like!

    Its seems to me that its time for a major shakeup in HTML. While CSS and other things make bold attempts at making the WWW usefull for something other then very basic page display it does seem rather lacking.

    Page inclusion based on simple tests! The machinations one has to go through to make what seems like an obvious feature like if(X=Y,this.html,that.html) actualy happen require scripting and all sorts of PHP like occurances, java, javascript and what have you.

    CSS gets ever more complex to simply accomplish a text area on the rendered page.

    So now the idea HyperScope gets trotted out from a dust filled closet. I can't really see how that is going to help matters rather then just muddy the waters even more.

    Isn't it really time for a MAJOR overhaul of HTML and the HTTP protocol? HTML as it was created was sufficient for the basic exchange of information, formatting was limited and things worked fairly well. Microsoft came along and realized that this could be taken MUCH farther and started doing things their own way, which was good for them, not so good for everyone else and was properly derided for doing so in a uncooperative way. But was it really? I agree that MS did what they did out of pure self interest, but did they suggest these things to various committies only to have them shot down because it was MS centric only? I don't know the answer.

    I for one think its time to just scratch HTML as it currently exists and scratch CSS right along with it, and come up with something that actualy works smoothly and works as designed!

    Basic fundemental layout strategies like Areas, Menus, Images, scrolling, layers and all the primitives sould be part and parsle of an HTML-Like specifcation, not an add-on cludge like CSS. The specification for this should rightly be decided upon by the major browser venders and fully supported by all the web server vendors. It should be code modules written to the specification that are freely available to anyone who wants to link them into their rendering engine. Further more, they should be written in ANSI C and all supporting libraries are included also written in ANSI C.

    --
    Hey KID! Yeah you, get the fuck off my lawn!
    1. Re:Enough with the snide remarks.... by Anonymous Coward · · Score: 0

      If it ain't broke, don't fix it.

    2. Re:Enough with the snide remarks.... by FlyingGuy · · Score: 1

      Ahh yes, but it IS broken, thats the problem

      --
      Hey KID! Yeah you, get the fuck off my lawn!
    3. Re:Enough with the snide remarks.... by Anonymous Coward · · Score: 0, Flamebait

      Where on earth did you get the stoopid idea that microsoft came up with page formatting?? Haven't you ever seen a textbook printed before 1980? Don't you know that microsoft didn't invent the web browser?? Did you crawl out from under a rock somewhere in redmond? Why don't you pull your head out of bill's ass for a sec, HTML was not invented for basic information transfer. That was what you call the "internet" upon which the "web" runs. HTML is an ADVANCED textual formatting system, you dope! EVERYONE POINT AND LAUGH AT THE STUPID IDIOT!!!

      HAHAHAHAHAHAHHAHAHAHAHAHHAHA

      HAHAHHAHAHAHAHSNORTHAHAHAHAHAH
      DOUCHEBAG!!!
      HE HEHAHEHAHEHAHAHAHAHEHEHEHAHAHAHAHAH

    4. Re:Enough with the snide remarks.... by wralias · · Score: 1
      I for one think its time to just scratch HTML as it currently exists and scratch CSS right along with it, and come up with something that actualy works smoothly and works as designed!

      I'll grant you that, yes, there are some limitations and frustrations with CSS. But to scrap it entirely is nonsense - why start over from scratch, when CSS 2 and 3 are actually steps in the right direction? The newer specifications for CSS contain much more power and control over layout and style. The problem is not with CSS 1, it's mostly with getting browser makers to implement a bug-free and consistent engine for CSS (think IE).

      Basic fundemental layout strategies like Areas, Menus, Images, scrolling, layers and all the primitives sould be part and parsle of an HTML-Like specifcation, not an add-on cludge like CSS.

      According to you. According to some others, HTML should get farther away from that crud (think XHTML). And if you ask me, I think they are right. I'd rather have HTML become more objective. I shouldn't have to remove pre-defined styles from HTML elements with CSS (like one has to with unordered lists, which have margins, padding, layout, and list-styles by default).

      If you are passionate and want to have a say in the direction of HTML / CSS, you could join the w3. It's a joke, but hey...

    5. Re:Enough with the snide remarks.... by FlyingGuy · · Score: 1

      Imagine this...



      Document.Background = white

      Document.Styles = /styles/PageStyles.stl

      DefArea('TopHeader',(0,0),100px,Document.Width)

      DefMenu('MainMenu','/menus/main',TopHeader)

      TopHeader.ApplyStyle = Document.HeaderStyle

      MainMenu.ApplyStyle = Document.MainMenuStyle


      Or something like that.

      --
      Hey KID! Yeah you, get the fuck off my lawn!
    6. Re:Enough with the snide remarks.... by Anonymous Coward · · Score: 0

      That looks like hell, you dumb arse'ole.
      Lets change everything because I don't understand how it all works! Changing stuff makes it better!! I sucked bill gates off last night!!

      BLARGRGARGBLARG!!!!

    7. Re:Enough with the snide remarks.... by Harry+Coin · · Score: 1

      Capital idea! Somebody rewrite decades worth of technology for me, but design it better this time! Also, make sure that all competing software companies cooperate on fully supporting it. Also, ensure that it mixes presentation information with content. Plus, was Microsoft really doing the wrong thing by extending HTML?

      In addition, please hurry, because I am a very busy person and I don't like waiting.

      --
      That's pre 7-11 thinking....
  15. 4.9 years?!!!? by headkase · · Score: 1

    :0
    As a computer, I find your faith in technology amusing.
    ;)

    --
    Shh.
  16. The 1968 Demo by mrdrivel · · Score: 4, Interesting

    In 1968 Douglas Engelbart gave a presentation of the NLS/Augment system in San Francisco. It's quite amazing. It uses a three button mouse and pointer (called a bug). It also uses several buttons operated by the non-mouse hand in a chorded fashion to select and copy text.

    Video conferencing, group collaboration, the hierarchical presentation and hiding of data, spatial representation of data, hyperlinking are all shown in the demo.

    There is a Quicktime of it here: http://www.invisiblerevolution.net/video-68-large. html

    I first saw this in one of my computer science classes at Berkeley; we were all surprised at how much of what we think of as recent technology (last 10 years or so) actually existed in 1968.

    NOTE: The video is rather long. The impatient (read: Slashdotters) might want to fast forward through parts.

  17. typical by Anonymous Coward · · Score: 0

    Typical Slashdot trashing every idea that comes out... while there's no comparsion here, I can't help but be reminded of the original iPod announcement and how it was received: http://apple.slashdot.org/article.pl?sid=01/10/23/ 1816257 : "No wireless. Less space than a nomad. Lame."

    It's a pretty cool research project that brings to life work that was developed nearly 40 years ago, and is at best an early proof of concept of their original work. Take it for what it is rather than jumping on the trash it because you can bandwagon.

    1. Re:typical by Anonymous Coward · · Score: 0

      I know, why don't we openly accept any ideas that come our way? Lets just welcome them all in with open arms! No idea can be a bad one if everybody just goes ahead and loves it, right?/

  18. silly made-up word by DreadfulGrape · · Score: 1

    Dictionary.com says

    "No results found for transclusion. "

    --
    sig has been sent away for a few small repairs...
  19. What I want to see is his presentation template... by jpellino · · Score: 1

    He gave a talk maybe 10 years ago here in CT, and his presentation was built on a template that essentially had a border of thumbnails around the outside like the ads on a restaurant placemat, starting at 12:00 and proceeding clockwise - each thumbnail either telltaled or swelled (like the OSX dock - can't recall) the cool thing was you had random access to your presentation, and you could jump to any slide from a single screen... you could build it from scratch, but I;m betting it was automated somehow.

    --
    "Win treats sysadmins better than users. Mac treats users better than sysadmins. Linux treats everyone like sysadmins."
  20. It appears to be a web based outliner by hey! · · Score: 3, Informative

    Based on approximately 30 seconds clicking through links.

    If so it's not a bad idea. If my impression is correct, then think for a moment about this idea:

            hyperscope : wiki :: outliner : word processor

    There is no document you can produce in an outliner that cannot be produced in a word processor, whereas there are practically infinite documents you can create in a word processor. Which is what makes an outliner useful. Classification is such a basic and useful mental pattern, putting an amorphous blob of thoughs into the form of an electronic outline goes a lot of the way to organizing it into something coherent.

    My experience with wikis is that if you have one really mentally disorganized person with time on his hands, he can quickly turn important parts of the wiki into mush.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  21. Re:More Moo by Sir+Runcible+Spoon · · Score: 1

    I always wanted to link to arbitary points in other people's documents, perhaps to a paragraph containing a particular piece of text. So I guess it would be xpath expressions in links that we need.

  22. Yes, I know by MarkusQ · · Score: 1

    Yes, I know.

    My post was a test of a new form of communication that we've been trying out over here (called a "joke" or "jest"). It aims to amuse, but at the occasional cost of some technical accuracy.

    Hope that helps.

    --MarkusQ

  23. Duke Nukem Nothing! by WED+Fan · · Score: 1

    Wow, 1968? 38 years from concept to implementation? And idiots were giving the FreeDOS folks a hard time for their release schedule. :)

    --
    Politics is the art of looking for trouble, finding it everywhere, diagnosing it incorrectly and applying the wrong fix.
  24. Why don't do the right thing anyway? by master_p · · Score: 1

    The right thing would be to forget about HTML alltogether and make a distributed platform where the browser IS the virtual machine, programs are lazilly downloaded like web pages and the GUI is a library, rather than a set of specs specified by a commitee.

    Simple informational web pages are a subset of an application anyway.

    1. Re:Why don't do the right thing anyway? by FlyingGuy · · Score: 1

      I like your notion...

      But how do you keep something like this from becomming a large bandwidth burden? Would it be every interactive site then has to be downloaded as an entire program? What you seem to be describing was MS's vision of ActiveX wouldn't you agree?

      This became something that has caused probelms, security holes, etc.

      The most tedious and problematic things like menu's that dont quite look correct from browser to browser unless some of the most increadably convoluted CSS is applied should be, IMHO, be spec'd, coded up and linked into the browser rendering engine, to provide a consistent browser and platform independent expirience.

      --
      Hey KID! Yeah you, get the fuck off my lawn!
    2. Re:Why don't do the right thing anyway? by master_p · · Score: 1

      Bandwidth would not be a problem...first of all, the programs will only have to be downloaded once, or if they are updated. Secondly, the program will be downloaded lazilly, in compressed/tokenized form.

      As for security, the code will be executed in a sandbox, like javascript.

    3. Re:Why don't do the right thing anyway? by FlyingGuy · · Score: 1

      Master_P,

      So a defined menu system drop down, fly-out, combinations of those forms, downloaded once. It would encompas a raw menu system that could then be styled by a web page.

      Style would entail things like tabs with rounded corners, square corners, color, depth, parent ( local to an equivilent of a DIV ) and such?

      Lets start a project!

      --
      Hey KID! Yeah you, get the fuck off my lawn!
    4. Re:Why don't do the right thing anyway? by master_p · · Score: 1

      I would definitely be interested in a project, but from your comment it seems your understanding is different than mine.

      First and foremost, I am talking about a totally new platform, not based on existing standards and web browsers.

      My idea of 'platform' entails a virtual machine, a programming language, a 'browser' window, and a set of libraries.

      The virtual machine would be distributed, i.e. it is responsible for:

      a) interpreting the bytecode and caching its native representation both as a client and as a server.

      b) client tasks: lazy download of a program, i.e. parts of the program are downloaded only when requested; then they are cached. Each part of a program is versioned and when a new instance of the app is run, the virtual machine checks if there is an update and downloads it.

      c) server tasks: connections, running applications, timeouts etc.

      d) security, encryption, I/O with the local platform.

      The programming language I have in mind would be:

      a) functional

      b) with syntax that allows arbitrary domain-specific-languages to be built

      c) statically typed, with type inference and functions as first class values

      d) closures and continuations

      e) subtypes and multi-methods

      f) allow destructive update, i.e. assignment only at user-defined places

      g) be distributed right from the start; the concept of running different code in different sites, either statically or dynamically declared would be part of the language.

      The language would be totally 32-bit unicode, because we leave in an international society and there are still issues with fonts etc. Today's computers have enough space to accomodate 32-bit strings; saving a few bytes here and a few bytes there does offer any significant advantages, and compression algorithms can take care of empty bytes.

      The browser window will look like a web browser, but its purpose would be to host the applications' GUI. It would have an 'application address' combo box where the user can type in the address of an application in the form of a URL-like string. The string would not be a URL, because URLs are very complex beasts, but a very simplified pathway string to a resource. the browser would not have a back/forward button, because those are application-specific concepts.

      Finally, the libraries would cover a large spectrum of functionality: gui, database, utilities, collections etc, all of them runnable either in the client or server.

      Libraries would be 'imported' as URL-like declarations, and the virtual machine would be responsible for downloading, installing and upgrading the libraries, transparently. Library vendors need only publish their library in their site, and the library would be distributed automatically to those that request it.

      If you are still interested (which I doubt it, given the scope and depth of work), we can set up an online discussion to clear things up even further, exchange ideas, and set up a development plan.

  25. good alternative by eegreg · · Score: 1

    tiddlywiki is better and more powerful through the use of plugins http://www.tiddlywiki.com/

  26. More on HyperScope OPML From The Coder by BradNeuberg · · Score: 3, Interesting

    Hi there; I'm the software architect and implementor of HyperScope, and thought I'd provide some more info on the OPML capabilities of what you can do with it.

    HyperScope is like OPML and HTML hyperlinks on steroids. There are so many different kinds of addressing your nodes that its not even funny. You can do direct addressing using hiearchical placement, even if there are no anchors:

    mydoc.opml#2A

    Where 2A is the second node (2), followed by it's first child (A). Node numbering always alternates between letters and numbers for readability; so you might have 2A3B. These are generated automatically and will work across all OPML documents, not just ones that have been marked up with the optional HyperScope namespaced attributes.

    You can target node IDs, which are unique values that never change for a node even if it is moved around; these always start with a 0:

    mydoc.opml#0626

    Node IDs are optional, and placed on an OPML outline node using the hs: namespace:

    <outline text="foobar" hs:nid="0626"/>

    Node IDs are optional, and are created on document creation or editing, while the node hierachical numbers above work for any OPML file.

    You can target based on label, using the optional hs:label attribute:

    <outline text="foobar" hs:label="mylabel">

    This would be the following address:

    mydoc.opml#mylabel

    Now, here's some cool stuff; once you've hit your target address using direct addressing, you can start to use relative addresses to move relative to the one you just targeted. For example, once I've gone to 'mylabel', I could jump down in the node hierarchy then to the next 2 nodes using the following:

    mydoc.opml#mylabel.d2n

    Which is .d for down and .2n for next two. You can jump through the hierarchy using many of these, including successor (.s) for going to the next sibling of the current node, independent of children; predecessor (.p) for the same, but for the previous sibling; back (.b), which will take you to the previous node that is right before you, independent of hierarchy; next (.n) for the same but forward; up (.u) to move up an ancestor; down (.d) to move down; tail (.t) to move to the last child sibling on my level; head (.h) to move to the first child sibling on my level; and more.

    Once you've done these, you can start doing some other fun stuff. I can now do an indirect link, which is .l (that's a lower case L):

    mydoc.opml#mylabel.d2nl

    The 'l' is magical; it says: "once you've found the final node after dereferencing the other addresses, look inside the contents of this node, and take the first address you find then follow it."

    For example, if the node that lies at mylabel.d2n has the following contents (that's an encoded HTML hyperlink in there):

    <outline text='Make sure to see the document: &lt;a href=&quot;http://foobar.com/important.opml#2&quot ;Important&lt;/&lt;/&gt;

    then adding that .l will cause HyperScope to extract
    http://foobar.com/important.opml#2, and follow it and dereference it, which will cause the browser to jump to important.opml, then jump to node #2.

    So indirect links let you create a layer of indirection between you and a set of links. You could imagine combining this with the node labels to create a kind of link database; just create a file that you always use that has named nodes for important links that you want to go to, then use indirect links against these. This is exactly what Engelbart does; I've sat and watched him and studied how he uses the system. You can see modern screencasts of that system and his work practices at these blog posts of mine: http://codinginparadise.org/weblog/2006/03/new-scr eencast-of-douglas-engelbarts.html and

  27. Re:More Moo by Fred_A · · Score: 1

    I suppose this could be done with some sort of JavaScript trickery (a kind of linkTo(URL, RegexKindOfThing)).

    It requires some cogitation and a bit of coffee though. A general purpose function for this would indeed be a very nice tool. It should be part of the Dojo toolkit or something like that...

    --

    May contain traces of nut.
    Made from the freshest electrons.
  28. Re:More Moo by Sir+Runcible+Spoon · · Score: 1

    I was thinking of this as requiring an extension to HTML. Doing it using existing JavaScript technology would be tricky as it would mean running JavaScript inside the target page. Even if you find a way to do this, you cannot be sure that someone at Mozilla or Microsoft woun't see it as a security problem and close the hole.

    I don't think it would be possible with AJAX unless the target document is on the same server, this is a restriction of XMLHttpRequest. (This where I would like to link to the "Security Alert" near the bottom).

    That said, it might be possible to do this using a frameset. You link to a frameset on yout own server with the extra info passed as arguments. The frameset parses the arguments, loads the target page into a frame, then it scans the page for the text and then scrolls the frame.

    Alternatively you could serve the target page via your own server inserting an anchor.