Skip to main content

Home/ CalDAV/ Contents contributed and discussions participated by Graham Perrin

Contents contributed and discussions participated by Graham Perrin

Graham Perrin

Chandler Wiki : Using Other Apps With Chandler Hub - 0 views

Graham Perrin

How to add group-shared highlights to a page that is already shared with the group? | D... - 0 views

  • Please check it.
    • Graham Perrin
       
      This sticky note added using Firefox 3.0.4 on Mac OS X, and shared with the CalDAV group (no-one other than me there, at the moment :)
  • 1. add highlights to a page (not a home page) 2. share the page, and annotations, with a group 3. add some more highlights — for the benefit of the group. How do I achieve step 3?
Graham Perrin

[CalendarServer-dev] [CalendarServer-changes] [3245] CalendarServer/tags/release/Calend... - 0 views

  • we'll probably have an increasingly stable trunk again as the year winds down, and perhaps it'll make sense to tag a 2.0 (or maybe a preview?) in the new year
    • Graham Perrin
       
      2009.
Graham Perrin

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

  • Being a CalDAV reference implementation is not a priority.
  • we will not be implementing CalDAV scheduling
    • Graham Perrin
       
      CalDAV scheduling is just one aspect of CalDAV; see http://caldav.calconnect.org/standards.html
  • misperception in the press
  • ...17 more annotations...
  • the Microsoft product with the most overlap with our design objectives is probably OneNote
  • 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
  • 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
  • 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
  • the user problem we are serving is an emerging market
  • there isn’t a shared, public vocabulary to describe what we’re doing
  • 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
  • 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
  • web widgets (in the browser, on mobile devices and on the desktop)
  • 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.
  •  
    February 6th, 2008 at 11:17 pm
‹ Previous 21 - 25 of 25
Showing 20 items per page