Skip to main content

Diigo Home
Home/ Groups/ CalDAV
Graham Perrin

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

  • 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
  • we will not be implementing CalDAV scheduling
    • Graham Perrin
       
      CalDAV scheduling is just one aspect of CalDAV; see http://caldav.calconnect.org/standards.html
  • 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:



    1. A List View built around the idea of the Triage Workflow
    2. A Calendar View
    3. 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
    • 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.
  • 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)
  • Graham Perrin
     
    February 6th, 2008 at 11:17 pm
Graham Perrin

CalDAV with Leopard iCal - Zimbra :: Wiki - 0 views

  • iCal supports CalDAV principal concept, and the URL to use is simply
  • You must not append anything after the servername when using iCal
  • Using the supplied username and password it can discover the user's calendar
Graham Perrin

Forum for iCal4OL & Print4OL / iCal4OL 2.7.0 with integrated CalDAV-Server (!!) for Outloo... - 0 views

  • CALDAV SERVER is integrated to SHARE your Outlook Calendar (and Tasks) with clients
    • Graham Perrin
       
      AFAICT this is iCal4OL providing CalDAV service (available to clients only whilst your computer is connected to the Internet, with firewall exceptions et cetera) - not communicating your Outlook data with a higher-availability CalDAV server elsewhere.
  • Is Outlook fast enough for this? No
Graham Perrin

Apple Sync Services, Truth Database; CalDAV; Google Calendar, Calaboration - 0 views

  • Tasks created in Google Mail are not presentable as To Do Items
  • http://developer.apple.com/macosx/syncservices.html
    • Graham Perrin
       
      Integrating Sync Services into Your Application
  • http://developer.apple.com/documentation/Cocoa/Conceptual/SyncServices/Articles/SyncOverview.html#//apple_ref/doc/uid/TP40001151-139942
    • Graham Perrin
       
      Sync Services Programming Guide: Sync Services Overview
Graham Perrin

use iTunes to prefer a calendar for events created on iPhone and iPod touch - 0 views

  • http://support.apple.com/kb/HT1419
    • Graham Perrin
       
      iPod touch: How to sync contacts and calendars
  • http://support.apple.com/kb/HT1957
    • Graham Perrin
       
      MobileMe, iPhone/iPod touch: Differences between Push and manually syncing calendars and contacts
  • http://developer.apple.com/macosx/syncservices.html
    • Graham Perrin
       
      Integrating Sync Services into Your Application
  • ...6 more annotations...
  • an iPhone may use both MobileMe (wirelessly) and a computer (typically wired)
  • Clients of Sync Engine may be many
  • If you have two or more Mac OS X computers:
  • a Truth Database and Sync Engine on each computer
  • If in addition you subscribe to MobileMe:
  • your MobileMe account is a client of multiple Sync Engines
Graham Perrin

Integrating Sync Services into Your Application - 0 views

  • Sync Services provides a powerful and extensible mechanism that enables
    data to move seamlessly between multiple Macs, devices such as mobiles
    phones and PDAs, and network services. This ability has long been a part
    of Mac OS X , through iSync and .Mac, which could manage contacts,
    calendar items, and bookmarks. Now in Mac OS X v10.4 Tiger, any Mac OS X application
    can tap into this functionality to sync any kind of data reliably,
    frequently, and easily.
Graham Perrin

YOUnite Use Case: Apple's MobileMe - 0 views

  • Graham Perrin
     
    PDF
Graham Perrin

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

1 - 20 of 24 Next ›
Showing 20 items per page
Join this group