6 Matching Annotations
  1. Aug 2019
    1. After the success of MORE, he went on to develop a scripting language whose syntax (for both code and data) was an outline. Kind of like Lisp with open/close triangles instead of parens! It had one of the most comprehensive implementation of Apple Events client and server support of any Mac application, and was really useful for automating other Mac apps, earlier and in many ways better than AppleScript.

      Yes, lisp!

      This is my thinking as well i.e. if you could (a) keep parentheses but render them differently. But not going over board in basic view so it's still editable like text. AND also have a more graphical view.

    2. After the success of MORE, he went on to develop a scripting language whose syntax (for both code and data) was an outline.

      Lisp! ;P

    3. More was great because it had a well designed user interface and feature set with fluid "fahrvergnügen" that made it really easy to use with the keyboard as well as the mouse. It could also render your outlines as all kinds of nicely formatted and stylized charts and presentations. And it had a lot of powerful features you usually don't see in today's generic outliners.

      fahrvergnügen German for "driving-pleasure. Yes! ALSO This is kind of central, in two ways.

      A. you need to have good story for mouse only and keyboard only B. you need to have multi-modal rendering

    4. Engelbart also showed how to embed lists and outlines in maps:https://www.youtube.com/watch?v=yJDv-zdhzMY&t=15m39s

      Now this is interesting. Instead of normal map here they've had to use this simple sketch/graph. Just arrows etc. BUT There maybe an actual value in that kind of simplicity!

      Question worth asking here is why we have to see all the detail on the map always? Google may have different incentives than just showing you only essential data.

  2. Apr 2019
  3. Feb 2017