Skip to main content

Home/ Chandler Project/ Group items tagged review

Rss Feed Group items tagged

Graham Perrin

Chandler Wiki : Browser Design - 0 views

  • computer file systems
  • book stores and supermarket aisles
  • hierarchical org charts
  • ...57 more annotations...
  • Trees abound in
  • trees prevail
  • they clearly limit us
  • Semi-lattices are non-polar, where do you start, where do you end?
  • Reality and the human brain's ability to grok it are far more complex than a tree
  • dumbing down isn't always a bad thing
  • you don't really understand something unless you can explain it in 5 words
  • Let's improve on the software
  • too strict, too dry, too simplistic
  • browse the same data via many different trees
  • visual information mapping hasn't already taken over the world
  • that break the tree
  • brains ARE really really good at seeing relationships
  • linear doublethink
    • Graham Perrin
       
      Graham: review!
  • stop-motion semi-lattice building
    • Graham Perrin
       
      Graham: review!
  • extremely adept at looking at the same data and reorganizing it into different trees in rapid succession
  • in one file cabinet, on one bookshelf, in one way
  • forcing us to look at our data
  • semi-lattii
  • Challenge: Find balance between trees
  • distorts the truth
  • expressive but often not communicative
  • same data in as many different kinds of trees as they want
  • start at any point in the tree
  • same data, different perspectives
  • rotate the tree
  • visual cues that seemed to burst forth with meaning begin to feel meaningless, random, disorienting
  • "watch" in "slow-motion" or user manipulated motion
  • future Chandler may have a richer graphical interface
  • different tree organizations of the same data
  • Overlaying the visualizations
  • composite semi-lattice
  • richness of semi-lattii
  • feed it to users in a way they can easily understand: trees
  • All parameters set in the browser are reflected in the Search bar
  • Saved rules
  • better than limiting users to a single tree
  • better than overwhleming users with a semi-lattice
  • "dumbing down" the data for the user
  • avoid UI shock via information overload
  • present users with the full-force and complexity of their information in a way that is understandable
  • possible, even within the confines of the 2-dimensional
  • easily walk from one tree to another
  • breaking away from hierarchy and how people used to hierarchies of folder are coping
  • http://weblog.edventure.com/blog/_archives/2004/4/19/36468.html
  • the freedom and amorphous-ness of a search-centric navigation paradigm
  • a little built in structure
  • Dashboard view / triage workflow as a point of entry
  • search to get within range
  • navigate using contextual clues to find the exact item
  • fixed hierarchies present a workflow bottlenck
  • we know what topic to file something under, but we don't know where that topic belongs in the hierarchy
  • pilers never bother to file
  • something new comes along to screw up the hierarchy
  • unwieldy taxonomies with duplication and confusion
  • Sometimes we don't know what we're looking for until we see it in context
  • brain's ability to use environmental clues to remember things
Graham Perrin

Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Tra... - 0 views

  •  
    A most remarkable omission from the reviews on Amazon (and presumably, from the book) is: discussion of standards, such as those relating to CalDAV. OSAF/Chandler Project members made significant contributions to the drafting and setting of standards. Happily, we don't hear companies such as Apple or Google criticising Chandler Project history whilst embracing/enjoying CalDAV. I suspect that - however well written the book may be - a *focus* on a space in time (however short or long) has overlooked the broader value of the Project.
  •  
    I'll rate and review this book, probably some time around Christmas.
  •  
    "Our civilization runs on software. Yet the art of creating it continues to be a dark mystery, even to the experts, and the greater our ambitions, the more spectacularly we seem to fail. … [this book] sets out to understand why, through the story of one software project -- Mitch Kapor's Chandler, an ambitious, open-source effort…
Graham Perrin

Chandler Wiki : FAQ - 0 views

  • Q Can I use Chandler for Email?
  • For Preview
    • Graham Perrin
       
      This paragraph, at least these words, should be updated with respect to 1.0.2.
    • Graham Perrin
       
      Re http://www.diigo.com/annotated/d62b6b8ed21cf763e92d3b3b6a88f86a the expression 'Preview' was in use around April 2007.
  • Chandler Preview
    • Graham Perrin
       
      Update to reflect the 1.0.2 situation.
  • ...11 more annotations...
  • sends and receives email
    • Graham Perrin
       
      … and uses IMAP, but does not place sent messages in the Sent mailbox of the IMAP server.
  • sent from other Chandler users
    • Graham Perrin
       
      This fundamental point should be HIGHLIGHTED (not diminished in parentheses).
  • downloads messages via 3 IMAP folders
    • Graham Perrin
       
      I see evidence of Chandler 1.0.2 working with POP, though I don't use it in that way.
  • Add messages from your email client into special Chandler IMAP folders
    • Graham Perrin
       
      Messages moved by your IMAP client to Chandler Desktop-specific mailboxes
  • to download them into Chandler where you can manage them as Chandler notes and events
    • Graham Perrin
       
      … will be copied by Chandler Desktop whenever you sync Chandler Desktop.
    • Graham Perrin
       
      Subsequent management within Chandler Desktop will not be communicated back to the IMAP server.
    • Graham Perrin
       
      After a message has been copied by Chandler Desktop, then in your IMAP client you may wish to archive (or set aside) the earlier copy, to avoid confusion.
  • What still needs to be done
  • Sync IMAP Flags and Read/Unread status
  • Unlike "regular" email, you can edit and re-send Chandler emails
  • current target screen size - 1024x768 pixels
  • should still be usable at 800x600 pixels
  • the application
    • Graham Perrin
       
      the Hub
1 - 3 of 3
Showing 20 items per page