Skip to main content

Home/ Chandler Project/ Group items tagged date

Rss Feed Group items tagged

Graham Perrin

The Chandler Project Blog » Blog Archive » Scoble Follow-up: The Brain Beh... - 0 views

  • refining our heuristics
  • What is ‘most important’ is subjective
  • Message items always display From/To
  • ...5 more annotations...
  • Who column always displays ‘Edited by’ when an item has been modified by a fellow subscriber
  • depending on whether the message is Inbound or Outbound
  • event dates usually trump all other dates
  • alarm date
  • display something even if it’s the wrong thing some of the time
Graham Perrin

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

  • 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

Chandler Wiki : Running Chandler From Source Releases - 0 views

Graham Perrin

Vista - End of the Dream? * The Register - 0 views

  • I downloaded a copy of Chandler the other day, just to see how things were shaping up. As soon as I launched version
    • Graham Perrin
       
      Reading the April 2007 date of this story alongside http://blog.chandlerproject.org/2007/04/18/preview-update/ and http://blog.chandlerproject.org/2007/09/11/preview/ it's clear that the version (probably a checkpoint) tested by Dave Jewell predated the 'preview' by around five months.
  • Chandler is still an awful long way off from that magic 1.0 release
    • Graham Perrin
       
      The OSAF vision of Chandler originated around 2001. In 2007: the preview milestone version was certainly (but not disappointingly) some way away from the release. Chandler 1.0 was released in August 2008.
  •  
    Some discussion of the Chandler Project.
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
  • 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
       
      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.
  •  
    February 6th, 2008 at 11:17 pm
Graham Perrin

Chandler Wiki : Product Tour - 0 views

  • without having to go to the Calendar
  • Turn Reminders into Events
    • Graham Perrin
       
      Bug 12827: Reminder turned into event: adding an alarmed item to the calendar should schedule the event on the date of (not before) the alarm https://bugzilla.osafoundation.org/show_bug.cgi?id=12827
Graham Perrin

Chandler Wiki : Web Home - 0 views

  • all development on Chandler is volunteer
  • most volunteer effort is focused on Chandler 2
  • focus your efforts on Chandler 2 and Chandler Server
  • ...3 more annotations...
  • Bugtracker - not set up yet
    • Graham Perrin
       
      At https://bugzilla.osafoundation.org/ will we see an additional product for Chandler 2? Or will there be a separate tracker?
  • good stuff in the wiki, but
  • don't assume information in a wiki page is up to date
Graham Perrin

The Chandler Project Blog » Blog Archive » Sync *all* of your Chandler dat... - 0 views

  • show up in other iCalendar or CalDAV calendar applications
  • Chandler notes
  • Chandler notes
  • ...3 more annotations...
  • as Tasks (VTODOS)
  • NOW and LATER triage status will both be interpreted as “Not-Done”
  • Anytime events will look the same as All-day events
    • Graham Perrin
       
      See also http://n2.nabble.com/-tp2938080p2946160.html concerning events that have a start date and time, but no duration.
Graham Perrin

[chandler] Index of / - ViewVC - 0 views

1 - 10 of 10
Showing 20 items per page