Skip to main content

Home/ Chandler Project/ Group items tagged browse

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
  • brains ARE really really good at seeing relationships
  • visual information mapping hasn't already taken over the world
  • that break the tree
  • browse the same data via many different trees
  • 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
  • easily walk from one tree to another
  • 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
  • "watch" in "slow-motion" or user manipulated motion
  • 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

Chandler Wiki : How The Cookie Crumbles Part I - 0 views

  • hierarchies has been the designated one size fits all solution to all our organizational needs
  • we break our semantically pure hierarchies by overstretching their bounds
  • we end up with messy hierarchies that are unusable and unmaintainable
  • ...4 more annotations...
  • Stuff I need access to DOES NOT HAPPEN TO EQUAL the stuff at the top of the tree
  • Case study: Katie's OmniOutliner
  • http://www.shirky.com/writings/ontology_overrated.html
  • The following are images taken from: http://www.shirky.com/writings/ontology_overrated.html
Graham Perrin

Gnome Evolution bug 359755 - Support for CalDAV collections - 0 views

  • GNOME Bugzilla
  • Bug 359755
  • Support for CalDAV collections
  • ...42 more annotations...
  • Product: Evolution
  • FIXED
  • enhancement
  • The definition of 'calendar-home-set' is that it returns the URL of the collection which contains the user's calendars. Not the URLs of the calendars themselves.
  • then do a Depth: 1 PROPFIND on that URL to retrieve the actual calendars
  • you will request the resourcetype & supported-calendar-component-set
  • know which ones are calendars
  • whether they support VEVENT/VTASK/VJOURNAL
  • public calendars
  • calendars for a given user offered by other users
  • the dust isn't fully settled on parts of this
  • a few tricks
  • Trick #1
  • PROPFIND request for current-user-principal
  • Also planned
  • query a 'well known URL'
  • find the right port
  • PROPFIND the /.well-known/caldav/ URL
  • Once you've *got* the principal-URL
  • PROPFIND for the group-membership
  • possibly do this repeatedly
  • Once *that's* fully expanded to a list of principal-URLs
  • query the calendar-home-set for them
  • Depth: 1 PROPFIND on those to find their calendars
  • possible simplification
  • combine two steps
  • expand-property report is defined in RFC 3253 (WebDAV Versioning)
  • DAV::expand-property REPORT
  • can't think of a way to get the actual collections
  • maybe there is some trick
  • I guess at this point
  • current-user-principal in the first instance
  • PROPFIND Depth: 1 on the calendar-home-set
  • gets you the user's direct calendars
  • differentiating
  • my approach would be
  • on demand
  • e.g. 'display delegated calendar'
  • principal-URL for the currently authenticated user
  • recursively PROPFIND
  • expand their group-membership into a tree
  • In DAViCal the public.php is specifically for looking at calendars which have been declared to need no authentication
Graham Perrin

Chandler Wiki : Scoble Follow Up Screen Shots - 0 views

1 - 4 of 4
Showing 20 items per page