Skip to main content

Home/ Chandler Project/ Group items tagged Chandler

Rss Feed Group items tagged

Graham Perrin

Chandler Wiki : FAQ - 0 views

  • Q Can I use Chandler for Email?
  • For Preview
    • Graham Perrin
       
      This paragraph, at least these words, should be updated with respect to 1.0.2.
    • Graham Perrin
       
      Re http://www.diigo.com/annotated/d62b6b8ed21cf763e92d3b3b6a88f86a the expression 'Preview' was in use around April 2007.
  • Chandler Preview
    • Graham Perrin
       
      Update to reflect the 1.0.2 situation.
  • ...11 more annotations...
  • sends and receives email
    • Graham Perrin
       
      … and uses IMAP, but does not place sent messages in the Sent mailbox of the IMAP server.
  • sent from other Chandler users
    • Graham Perrin
       
      This fundamental point should be HIGHLIGHTED (not diminished in parentheses).
  • downloads messages via 3 IMAP folders
    • Graham Perrin
       
      I see evidence of Chandler 1.0.2 working with POP, though I don't use it in that way.
  • Add messages from your email client into special Chandler IMAP folders
    • Graham Perrin
       
      Messages moved by your IMAP client to Chandler Desktop-specific mailboxes
  • to download them into Chandler where you can manage them as Chandler notes and events
    • Graham Perrin
       
      … will be copied by Chandler Desktop whenever you sync Chandler Desktop.
    • Graham Perrin
       
      Subsequent management within Chandler Desktop will not be communicated back to the IMAP server.
    • Graham Perrin
       
      After a message has been copied by Chandler Desktop, then in your IMAP client you may wish to archive (or set aside) the earlier copy, to avoid confusion.
  • What still needs to be done
  • Sync IMAP Flags and Read/Unread status
  • Unlike "regular" email, you can edit and re-send Chandler emails
  • current target screen size - 1024x768 pixels
  • should still be usable at 800x600 pixels
  • the application
    • Graham Perrin
       
      the Hub
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 : Get Started - 0 views

  • Collaborate on Notes and Events over Email
    • Graham Perrin
       
      IMHO the e-mail capabilities of Chandler 1.0.2 require special explanation. Some explanations are offered within the FAQ, http://www.diigo.com/annotated/faf93764c6f6f5eb9a29268ad4b472de
    • Graham Perrin
       
      The number and nature of the special explanations, criteria and limitations of e-mail in Chandler Desktop make me think that 'Email' its sub-headings, as currently presented in 'Get Started', should not appear in Get Started.
    • Graham Perrin
       
      I suggest leaving references, from the Get Started page, to pages that are dedicated to: (1) an overview of e-mail in Chandler Hub and Chandler Desktop, and of limited communications with IMAP and POP servers; (2) using Chandler Desktop to configure an IMAP server, and understanding the workflows (in particular, the aspects that are one-way, periodic (Chandler Desktop sync) and incremental (the effect of adding messages to a Chandler-specific mailbox that was previously synced)); (3) e-mail in Chandler Hub; (4) e-mail in Chandler Deskop.
    • Graham Perrin
       
      Critically: the overview should contain no instructions on use; it should present, in pictures and in few words as possible, the current workflow and vision, plus maybe no more than one vision of the future.
Graham Perrin

Chandler Wiki : Mailing Lists - 0 views

  •  
    I wish to offer feedback and suggestions relating to design/UI of Chandler Hub and Chandler Desktop. To me, it's not clear which of the two lists - chandler-users or chandler-dev - should be addressed.
Graham Perrin

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

  • Sign up for a Chandler Hub Account
    • Graham Perrin
       
      Placement of the list of clients beneath this heading will confuse readers; they may imagine that what's presented below are means of signing up for Chandler Hub.
  • Step One
    • Graham Perrin
       
      The page is missing named steps beyond 'One'.
  • Publish from Apple iCal 3.x
    • Graham Perrin
       
      The description that follows relates to CalDAV which is not limited to (one-way) publication.
  • ...3 more annotations...
  • Collections you've subscribed to
    • Graham Perrin
       
      We should be more explicit about subscriptions. I guess that this statement refers to your Chandler Desktop subscriptions to the Chandler collections of other users of Chandler.
    • Graham Perrin
       
      Consider: some users of Apple iCal perceived collections long before Chandler introduced the expression.
    • Graham Perrin
       
      Consider: users of Apple iCal were familiar with subscriptions long before Chandler Desktop introduced the expression.
  • Sunbird Version 0.3
    • Graham Perrin
       
      Mozilla Sunbird has reached version 0.9.
  • view-only subscribing to other people's shared calendars
Graham Perrin

Chandler Get Started Guide - Chapter 2: Setting Up Accounts - Email Accounts - 0 views

  • drag and drop the email messages that you want to import into Chandler into one of the folders
  • file incoming email into one of those folders
  • Depending on which Chandler folder the email is in, when it gets retrieved and imported as a Chandler item, it will be stamped as a calendar event, email message, or task
  • ...3 more annotations...
  • Every time Chandler syncs with the email server
  • it checks for any new messages in one of the Chandler folders
  • even though it remains in the folder it is only imported once into Chandler
    • Graham Perrin
       
      So: does Chandler Desktop use IMAP message IDs to determine whether a message has been previously copied?
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 » Thunderbird Plugin For Chandler - 0 views

  • plug-in would allow Thunderbird users to interface directly with the Chandler Hub
  • Is the idea of a plug-in to Thunderbird useful to the Chandler User base?
  • Will a plug-in help attract new users?
  •  
    On one hand: I'd prefer to see Chandler-oriented extensions to iCal and/or Mail in Mac OS X. On the other hand, extending key applications in that way could raise unrealistic expectations of what should be seen in (for example) Calendar in iPhone OS 3.0.
  •  
    http://n2.nabble.com/-tp2951656p2951656.html suggests a Chandler triage application for iPhone OS. I'd like to see comparable widgets for Dashboard in Mac OS X. I assume that such things could be at least partially portable to other platforms.
Graham Perrin

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

  • 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

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

  • Chandler is supposed to follow the GTD paradigm
    • Graham Perrin
       
      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
       
      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
    • Graham Perrin
       
      Concerning a much earlier design decision, to not use ZODB: http://www.diigo.com/04mhd
    • Graham Perrin
    • Graham Perrin
Graham Perrin

menus.py - 0 views

  • GoToPrevWeek
    • Graham Perrin
       
      Suggestion: GoToPrev
  • GoToNextWeek
    • Graham Perrin
       
      Suggestion: GoToNext
  • Alt+Right
    • Graham Perrin
  • ...3 more annotations...
  • Alt+Left
    • Graham Perrin
  • Ctrl+G
    • Graham Perrin
       
      Suggestion, for harmony with iCal 3.0.6 (1273): Ctrl+Shift+T
    • Graham Perrin
       
      Ctrl+G is more commonly associated with find aGain
  • Ctrl+T
    • Graham Perrin
       
      A good choice.
Graham Perrin

The Chandler Project Blog » Blog Archive » Mobile Chandler? - 0 views

  • sync Chandler data onto any device that can sync with or subscribe to calendars via .iCalendar or CalDAV
  • Specifically, that means you can: Publish your collections to Chandler Hub; Subscribe to them with Apple iCal or Google Calendar; Use either Apple iSync or Google Mobile to get your Chandler data onto your mobile device.
  • https://support.markspace.com/index.php?m=knowledgebase&a=viewarticle&kbarticleid=230
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

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

  • 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

Personal votes in OSAF Bugzilla - 0 views

  • 11696 Crash when any file is dragged into Chandler window if you have 2nd display
    • Graham Perrin
       
      As I most often work with a second display, for me this https://bugzilla.osafoundation.org/show_bug.cgi?id=11696 is close to a blocker.
  • 11918 Support 'spheres' or groups of collections
    • Graham Perrin
       
      https://bugzilla.osafoundation.org/show_bug.cgi?id=11918 may deserve priority thought/attention from any user who works with many collections.
  • 12474 alt-arrow key combinations must navigate text only; MUST NOT navigate other aspects of Chandler Desktop for Mac OS X
    • Graham Perrin
       
      https://bugzilla.osafoundation.org/show_bug.cgi?id=12474 seriously retards my productivity and causes confusion, with potential loss/misplacement of data.
  •  
    View, confirm and edit the votes that you wish to cast. Log in required.
Graham Perrin

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

  • 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
       
      I did wish for this in the early days, but in practice I don't require this type of view.
  •  
    Interesting use cases.
Graham Perrin

Chandler Wiki : Zero Point One Email 20060508 - 0 views

  • Pull down emails that have special headers
    • Graham Perrin
       
      I don't understand this point.
  • one-time import of an Inbox
  • Proposed Plan
  • ...21 more annotations...
  • Email support for collaboration workflows
  • DnD from select email clients
  • One-time download of new mail with special Chandler headers
    • Graham Perrin
       
      Is this implemented in 1.0.2?
  • One-time download of new mail from select IMAP folders
    • Graham Perrin
       
      My sense is that this is implemented in 1.0.2.
  • Set up IMAP server
  • allow users to move email from their existing email account to the desktop
    • Graham Perrin
       
      In 1.0.2 I suspect that e-mail is copied (not (copied then deleted) moved).
  • provided they are on the same machine
    • Graham Perrin
       
      Can we more clearly define 'same machine'?
    • Graham Perrin
       
      I see no requirement for IMAP client and Chandler Desktop to be on the same computer. IMAP client at computer A communicates a user-initiated move of a message to one of three Chandler Desktop-specific IMAP mailboxes. Chandler Desktop at computer B performs a one-time download from those three mailboxes.
  • early adopter, metrotechnicals as experimental email users
  • One-time download of new mail from IMAP
  • Basic message composition
  • Required features for supporting collaboration workflows
  • Reply, reply all, forward
  • Send and receive
  • rich text editing
  • draft, queued, sent, read, unread, needs reply, replied to, forwarded
  • email status column
  • Email threading support
  • overall clustering solution
  • stamping communications workflows
  • Features not targeted for 1.0
  • Drag and drop emails and attachments from other email clients
Graham Perrin

Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Tra... - 0 views

  •  
    A most remarkable omission from the reviews on Amazon (and presumably, from the book) is: discussion of standards, such as those relating to CalDAV. OSAF/Chandler Project members made significant contributions to the drafting and setting of standards. Happily, we don't hear companies such as Apple or Google criticising Chandler Project history whilst embracing/enjoying CalDAV. I suspect that - however well written the book may be - a *focus* on a space in time (however short or long) has overlooked the broader value of the Project.
  •  
    I'll rate and review this book, probably some time around Christmas.
  •  
    "Our civilization runs on software. Yet the art of creating it continues to be a dark mystery, even to the experts, and the greater our ambitions, the more spectacularly we seem to fail. … [this book] sets out to understand why, through the story of one software project -- Mitch Kapor's Chandler, an ambitious, open-source effort…
Graham Perrin

The New Chandler Project (rearchitecture) - Chandler2 documentation - 0 views

1 - 20 of 115 Next › Last »
Showing 20 items per page