Skip to main content

Home/ Chandler Project/ Group items tagged to-do

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Graham Perrin

The Chandler Project Blog » Blog Archive » OSAF's Next Steps - 0 views

blog.chandlerproject.org/...osafs-next-steps

004250

shared by Graham Perrin on 22 Dec 08 - Cached
  • Chandler succeeds at meeting the needs of users who are tracking ‘knowledge work’
  • Chandler is not oriented around calendaring per se or around a complicated task and project landscape with many dependencies
  • we want Chandler to be more viral. We want Chandler to be easy to explain to others. We want Chandler to be found in contexts where people are already spending time. We want Chandler to be
  • ...17 more annotations...
  • even more useful as that user pulls in other people to collaborate
  • We want happy users be successful evangelists for Chandler
  • web widgets that might be deployed in different contexts — iGoogle, Facebook, on an iPhone, etc.
  • widgets should be compelling to a new user who does not use the desktop, in addition to providing features that complement the desktop. Eventually, the widgets can be building blocks
  • misperception in the press
  • Being a CalDAV reference implementation is not a priority.
  • the Microsoft product with the most overlap with our design objectives is probably OneNote
  • web widgets (in the browser, on mobile devices and on the desktop)
  • not trying to be a GTD specific tool
  • Chandler’s philosophy is different enough from GTD that it would be misleading to call Chandler a GTD tool
  • Our best articulation of our core value to date is: Chandler is a way to manage and collaborate on ideas using: A List View built around the idea of the Triage Workflow A Calendar View Chandler Hub Sharing Service
  • the user problem we are serving is an emerging market
  • there isn’t a shared, public vocabulary to describe what we’re doing
  • Better product messaging so that people understand what ‘user problem’ we’re trying to solve and how we’re trying to solve it.
  • more ways to get data in and out
  • we will not be implementing CalDAV scheduling
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      CalDAV scheduling is just one aspect of CalDAV; see http://caldav.calconnect.org/standards.html
  • We’re not looking to be a cheaper alternative to Outlook/Exchange. This means we’re not investing in support for free/busy-style scheduling. We’re not looking to be the ‘everyman’s’ version of Microsoft Project or Bug and Ticket-Tracking systems. This means we’re not investing in support for complex task and project management, e.g. task dependencies, tracking percent done, time estimates, robust support for assigning tasks, etc. We’re also not going to be implementing the GTD methodology.
  • Graham Perrin on 22 Dec 08
     
    February 6th, 2008 at 11:17 pm
Graham Perrin

Chandler Wiki : Browser Design - 0 views

chandlerproject.org/...BrowserDesign

004250 hierarchy

shared by Graham Perrin on 25 Jan 09 - Cached
  • 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 Perrin on 25 Jan 09
       
      Graham: review!
  • stop-motion semi-lattice building
    • Graham Perrin
      Graham Perrin on 25 Jan 09
       
      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

Apple Human Interface Guidelines: Keyboard Shortcuts Quick Reference - 0 views

developer.apple.com/...chapter_950_section_1.html

shared by Graham Perrin on 25 Jan 09 - Cached
  • Which key sequences are reserved by Mac OS X
  • Users rely on these shortcuts to perform the specified actions no matter which application is currently running (these include shortcuts reserved for accessibility purposes). Do not override these shortcuts
  • Which key sequences are recommended for common application tasks
  • ...5 more annotations...
  • Users expect these shortcuts to mean the same thing from application to application. Provide these shortcuts if your application performs the associated tasks. You should avoid using these shortcuts for other purposes
  • Extend selection to the end of the current word, then to the end of the next word.
  • Extend selection to the beginning of the current word, then to the beginning of the previous word.
  • Extend selection to the beginning of the current paragraph, then to the beginning of the next paragraph.
    • Graham Perrin
      Graham Perrin on 25 Jan 09
       
      … then to the beginning of the previous paragraph (For up arrow, not the _next_ paragraph.)
  • Extend selection to the end of the current paragraph, then to the end of the next paragraph
Graham Perrin

ISC Operations Status Page - 0 views

status.isc.org

Open Source Applications Foundation Internet Systems Consortium Chandler Chandler Hub

shared by Graham Perrin on 25 Aug 09 - Cached
  • 2009-08-21 - Our Redwood City (SQL1) data center has had a power outage. (all times PDT) Most mission critical systems are up. If you know of something that's down, please send an email to hands @ isc . org . 7:45 pm - Power goes out - routing unavailable 8:40 pm - R1.SQL1 and firewalls back up - most equipment down 8:50pm - farside is back up - power to servers being restored as UPSs charge up 10:00pm - most machines are back up The work on our Redwood City data center is complete for now. Apart from the outstanding new router hardware issue, and some minor tidy-ups, the upgrades are now complete. We are currently working with our router vendor to diagnose the issues we had with our core router and will attempt cutting over to this again in future when these are resolved. A new F-Root node has recently been installed in Philipsburg, on the island of Sint Maarten, Netherlands Antilles. If you are present at OCIX or going to be connected please setup peering with us there if you are not already doing so. You can use our web form for this. A new F-Root node has recently been installed in Frankfurt connected to the DE-CIX, so please setup peering with us there if you are not already doing so. You can use our web form for this. ISC's F-Root node in Munchen, Germany is currently partially down due to hardware failure. ISC is working on getting the node back up as soon as possible.
  • Graham Perrin on 25 Aug 09
     
    Internet Systems Consortium operations status
Graham Perrin

The Chandler Project Blog » Blog Archive » How do you use the Chandler Das... - 0 views

blog.chandlerproject.org/...you-use-the-chandler-dashboard

Chandler Desktop Dashboard reality 004250 collection item view wish event

shared by Graham Perrin on 25 Dec 08 - Cached
  • the Dashboard purely as a place to collect new notes, an “intake” area
  • collections must be initially kept out of the Dashboard
  • everything that could possibly be worked on right now needs to be in one place. I use the Dashboard to answer the question, ‘what should I work on next’. Every Collection is in the Dashboard
  • ...6 more annotations...
  • 30 going at a time
  • a cross-collection view of all their data where the could process items regardless of what collections
  • what’s new across all of your collections without having to click on individual collections one-by-one
  • Dashboard collection in Chandler
  • ground for experimentation
  • no way to view items that are in the Dashboard but not in any other collections
    • Graham Perrin
      Graham Perrin on 24 May 09
       
      I did wish for this in the early days, but in practice I don't require this type of view.
  • Graham Perrin on 25 Dec 08
     
    Interesting use cases.
Graham Perrin

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

bugzilla.gnome.org/show_bug.cgi

2009 2009-12 2009-12-07 CalDAV

shared by Graham Perrin on 08 Dec 09 - No Cached
  • 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

The Chandler Project Blog » Blog Archive » What is Chandler supposed to be... - 1 views

blog.chandlerproject.org/...dler-supposed-to-be-for-anyway

shared by Graham Perrin on 24 May 09 - Cached
  • wider range of tools
  • workflows are knit together via a wide variety of interoperation techniques
  • Chandler is meant to live in the middle of all these tools
  • ...26 more annotations...
  • pull all the disparate bits and pieces of information
  • into a contextualized, personal and shared ’source of truth’
  • the user interface we have today
  • contains vestiges of the ‘old’ way of thinking
  • proceed to lighten-up the app so that it’s a more accurate reflection of what Chandler is meant to do
  • focus on the quick item entry bar
  • the way to create new items in Chandler
  • see the messages you sent/received from Chandler
  • less of a “Mail Application”
  • credibility as a useful product
  • huge amount of effort and $$ we need to expend to be acceptable as a complete email solution
  • trust is important
  • move my group’s calendaring over
  • my own TODOs
  • Hopefully contact/address book stuff is next
  • Mail, iCal, Address Book
  • all separate, all highly functional
  • no clutter
  • the roles of the programs aren’t confused
  • interfaces aren’t cluttered up but there’s a heck of a lot of functionality
  • deceptively simple
  • Enterprise CRM’s are too complex and can only be used effectively when connected
  • fundamental link up between people and events, complex tasks and so on
  • I may be using ‘workflow’ differently
  • a loose framework of usage patterns
  • workflow-centric designs that bridge silos
Graham Perrin

VTODO with DUE date in Apple iCal : arnaudq's blog - 0 views

blogs.sun.com/...vtodo_with_due_date_in

VTODO task to-do to do CalDAV

shared by Graham Perrin on 02 Jun 09 - Cached
  • clients will consider the TRIGGER to be relative to the DTSTART property
  • meaningless (some time in 2004)
  • DTSTART property has a DATETIME
  • ...2 more annotations...
  • DUE property has a DATE
  • invalid per the new calsify spec
Graham Perrin

The Chandler Project Blog » Blog Archive » Next Steps for the Task Stamp - 0 views

blog.chandlerproject.org/...next-steps-for-the-task-stamp

Chandler item event message note task to-do VTODO triage star stamp label 004250

shared by Graham Perrin on 24 May 09 - Cached
  • don’t understand the point of marking some of my Notes as Tasks
  • proposal for extending the range of Item Kinds in Chandler
  • re-instate Tasks
  • ...10 more annotations...
  • extremely basic notion of Contacts
  • Reference Kind
  • don’t propose this instead of the Now/ Later/ Done system, but adjunct to
  • enter deadlines
  • see my tasks organized by those deadlines
  • and not necessarily a “to do” item
  • compilation of reference information
  • a configurable Chandler would be the most scalable solution
  • NOTES or REFERENCE feature would be useful
  • keep track of “reference material” that you want to keep around forever, just in case
Graham Perrin

Chandler Wiki : Top Usability Issues - 0 views

chandlerproject.org/...TopUsabilityIssues

004250

shared by Graham Perrin on 16 Jan 09 - Cached
  • Remove and Delete mental model
  • Data integrity issues (aka repo getting corrupted)
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      AFAIR a bug was fixed. Reference?
    • Graham Perrin
      Graham Perrin on 18 Jan 09
  • Spheres (way to group collections)
  • ...9 more annotations...
  • Focus Switching from one view to another should retain focus on the existing record [already reported] even if it would not appear in the new view.
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      To me, this behaviour feels extraordinarily weird. I need to understand the rationale.
  • drag items from the detail pane
    • Graham Perrin
      Graham Perrin on 16 Jan 09
  • anything that requires the use of Alt-keys
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      Choice of accelerator keys must be careful.
  • and doesn't offer a drag-and-drop alternative, is a problem
  • We need another button
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      I use: command-F to find, /f command-L for Lucene, /l
  • information between 'sync with self' PCs
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      I have half an eye on http://www.dotmobile.us/
  • corrupted way too often
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      Is this not fixed?
    • Graham Perrin
      Graham Perrin on 18 Jan 09
  • starting day of the week
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      Is this not done? (Related to locale, or choice of language.)
  • Define and clearly communicate what plugins (esp. third-party) can and cannot do
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      +1
Graham Perrin

Brain Breach » Blog Archive » Four Reasons Why Not to Use Chandler 1.0 - 0 views

brainbreach.com/reasons-not-to-use-chandler-10

critique

shared by Graham Perrin on 14 Jan 09 - Cached
  • Chandler is supposed to follow the GTD paradigm
    • Graham Perrin
      Graham Perrin on 14 Jan 09
       
      On the subject of GTD (not the single focus of Chandler), see also: http://www.diigo.com/04mh2 http://www.diigo.com/04mh3 http://www.diigo.com/04mh4
  • link a to-do to a contact to a calendar entry
    • Graham Perrin
      Graham Perrin on 14 Jan 09
       
      https://bugzilla.osafoundation.org/show_bug.cgi?id=5235#c12 I foresee Chandler Desktop interoperating with (not duplicating) the OS-managed address book data.
  • Memory Muncher
    • Graham Perrin
      Graham Perrin on 14 Jan 09
    • Graham Perrin
      Graham Perrin on 14 Jan 09
    • Graham Perrin
      Graham Perrin on 14 Jan 09
       
      Concerning a much earlier design decision, to not use ZODB: http://www.diigo.com/04mhd
    • Graham Perrin
      Graham Perrin on 14 Jan 09
    • Graham Perrin
      Graham Perrin on 18 Jan 09
Graham Perrin

The Chandler Project Blog » Blog Archive » Chandler and GTD? - 0 views

blog.chandlerproject.org/...chandler-and-gtd

004250 GTD goal action knowledge

shared by Graham Perrin on 14 Jan 09 - Cached
  • GTD is not our single focus
  • Supporting knowledge work is. (Blog post coming soon.)
  • Chandler will continue to improve for GTD practitioners
  • ...6 more annotations...
  • We also welcome and will actively help volunteers who want to write a GTD plug-in
  • Chandler shouldn’t be construed as an implementation of the GTD methodology or any other methodology
  • how to turn Goals into Next Actions
  • appreciate that there is a difference between the two
  • the GTD label actually scares people away.
  • people who knew about Chandler’s past association with GTD assumed they needed to subscribe to a particular way of doing things in order to succeed with the product
Graham Perrin

Chandler Wiki : Nutshell Cartoons - 0 views

chandlerproject.org/...NutshellCartoons

004250

shared by Graham Perrin on 22 Dec 08 - Cached
  • Information is the substance of their work and more information is the output of their work: Research, proposals, priorities, direction and decisions?
  • knowledge is gained and shared
  • how people actually work
  • ...17 more annotations...
  • (too) many interesting things
  • There's something wrong with the way data
  • doesn't flow between the tools we use to manage, process, organize our information
  • software should be modeled around information
  • fundamentally non-linear, non-binary nature of information work
  • processing and re-processing information to help you stay focused on the task(s) at hand
  • everything you can't and shouldn't be doing right now
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      These things are the ones that tend to throw in a 'pot' for later action.
  • many of the messages we send are really still drafts
  • too much copying and pasting
  • organized around your data and the semantics
  • not around which feature you used to create them
  • or over which transport protocol
  • Not around which file format
  • new Kinds of Items
  • designed to let you re-define what it means to be a PIM
  • personal definition of "Personal Information"
  • Extend the existing schema of Attributes
Graham Perrin

Chandler Wiki : Is Search The Panacea - 0 views

chandlerproject.org/...IsSearchThePanacea

shared by Graham Perrin on 22 Dec 08 - Cached
  • In our euphoria over the success and surprising usefulness and usable-ness of search and tagging, are we passing by a chance to not only make information accessible and useful but fundamentally alter the way we use information to make decisions.
  • we did not come all this way to end in Search, the biggest leap in information technology is yet to come
  • Search doesn't solve many of the biggest problems we face in our still nascent yet rapidly growing information-centric, information overloaded age
  • ...2 more annotations...
  • how do we grok, wrap our heads around all this data? (NOT just succeed in finding stuff in it.)
  • Search is not a solution to information management. It's one piece of the puzzle.
Graham Perrin

Chandler Getting Started Guide - Chapter 6: Triage Workflow and Stamping - 0 views

chandlerproject.org/...6-TriageWorkflow.html

shared by Graham Perrin on 22 Dec 08 - Cached
  • Today, many people do this by flagging emails or maintaining a task list. The problem is
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      This is a 'Getting Started Guide'. Keep it positive :) Talk of problems, behavioural patterns and visions should be elsewhere (the wiki is fine); simply refer from the Guide to the wiki.
  • have been added to the User Interface
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      Comments such as this belong in 'What's new' flyers, or in release notes. People who are truly using this Guide to get started are unlikely to have an interest in project history or design changes.
  • has been improved: better native
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      Whilst I'm getting started, I don't want to read that things were worse.
Graham Perrin

Chandler Wiki : The Element Of Time - 0 views

chandlerproject.org/...TheElementOfTime

004250

shared by Graham Perrin on 23 Dec 08 - Cached
  • Attaching semantics to items
  • organizing data, needs to be a separate workflow
  • separate UI affordances
  • ...3 more annotations...
  • adding structure to data
  • Getting to the root of the problem with user scenarios
  • The question remains: How do people get an eagle-eye view of their data?
Graham Perrin

The Chandler Project Blog » Blog Archive » What makes a Task a Task? - 0 views

blog.chandlerproject.org/...what-makes-a-task-a-task

Chandler item event message note task to-do VTODO triage star stamp label 004250

shared by Graham Perrin on 24 May 09 - Cached
  • Star isn’t so much a replacement for Tasks
  • trouble figuring out when to call something a Task
  • distinction between a task or todo
  • ...8 more annotations...
  • substance of the task
  • increasingly blurred
  • what’s a thought *about* a task
  • what’s a task
  • inspired by user feedback
  • starred items (furtively used as tasks)
  • users who regarded *everything* they put into Chandler as a task, thereby rendering a specialized “Task Label” superfluous
  • Modeling “Task-ness” well is critical to both workflow and usability in Chandler so rest assured that we will continue to work through it!
  • Graham Perrin on 24 May 09
     
    Tria
Graham Perrin

The Chandler Project Blog » Blog Archive » Andre Tries Out the New "Indepe... - 0 views

blog.chandlerproject.org/...he-new-independent-detail-view

Chandler GTD bucket item project list note task to-do VTODO 004250

shared by Graham Perrin on 14 Jan 09 - Cached
  • Andre keeps two items open all the time in separate windows:
  • The first is something he calls a “Bucket” item
  • The second is a GTD Projects List. Andre consults this list repeatedly throughout the day
  • ...1 more annotation...
  • saves me the trouble of having to leave the Chandler item I’m working with, find the GTD Projects List item, and then find my way back to the original item.
1 - 20 of 28 Next ›
Showing 20▼ items per page