Skip to main content

Home/ Chandler Project/ Group items tagged list

Rss Feed Group items tagged

Graham Perrin

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

  • 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.
Graham Perrin

Mailing list archives - 0 views

  • 2. Mailing list systems... All the comment on whether to have user group mailing lists on Gname or Nibble or MyLittleMailingListServer sometimes seems a bit beside the point of the forum for users for chandler. <commence flame>
Graham Perrin

The Chandler Project Blog » Blog Archive » More Blogging and Fewer Mailing... - 0 views

  • Chandler-dev is now the working list for all things pertaining to the Chandler Project
  • planning, design and bug prioritization
  • Chandler-users will remain the best place for users to ask questions and report issues
Graham Perrin

A Quick Look at Chandler | Linux Journal - 0 views

  • think about your things first, get them scribbled down and then organize them
  • no problem, for example, putting an existing note into multiple lists and/or multiple types of lists
  • what if the people I want to share things with don't run/don't want to run Chandler?
  • ...1 more annotation...
  • URLs for things you share. One is for read-only access and the other for read/write
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

Hosted @ISC | Internet Systems Consortium - 0 views

shared by Graham Perrin on 25 Aug 09 - No Cached
  • ISC's main data centers
  • available to qualified public benefit projects
  •  
    OSAF — Open Source Applications Foundation — appears under Racked Guests. I guess that Chandler Hub and other Chandler Project activities/services fall under that umbrella.
  •  
    OSAF is listed as a racked guest.
Graham Perrin

[chandler-users] IMAP linkage doesn't seem to work - 0 views

Graham Perrin

[chandler-users] Chandler Losing All Data - 0 views

  • no choice to Save
    • Graham Perrin
       
      The absence of (non-requirement for) a Save command should be explained in terms that are user-friendly.
    • Graham Perrin
  • re-open a previously used file
    • Graham Perrin
       
      The value of the automated and manual routines outlined at http://n2.nabble.com/-td2109816.html should presented in a user-friendly way.
    • Graham Perrin
  • different metaphor being used here with this program, one unlike any i've ever encountered before in using other programs. But what is it?
    • Graham Perrin
       
      Without paying attention to database technologies, the easiest comparison might be with iTunes. Concerning the Save command, in the File menu: iTunes has no need for this, the application simply works. To users, the absence of a Save command is unremarkable.
  • ...1 more annotation...
  • I was able to restore them one time by using Time Machine on my Mac
    • Graham Perrin
       
      I wonder which file(s) Michael chose to restore.
Graham Perrin

[Sum] Re: [Chandler-dev] What's our Web Strategy? Web Widgets, The Server and The Curr... - 0 views

  • continue to support items in multiple collections in a first class way on the server, which in turn means that the web UI and future web widgets will handle this case elegantly as well :D
Graham Perrin

[Chandler-dev] What's our Web Strategy? Web Widgets, The Server and The Current Web UI - 0 views

  • rely on desktop users to reconcile edits to items in multiple collections
  • a more sophisticated solution to our security issues that allows the server to understand about items in multiple collections
Graham Perrin

[Chandler-dev] What's our Web Strategy? Web Widgets, The Server and The Current Web UI - 0 views

  • Less important behaviors to 'get right' across Chandler access points
  • items living in multiple collections
Graham Perrin

[chandler-users] Collections: Calendar view: presenting and setting aside overlays [was... - 0 views

  • collection icon resembles any/all of the following: * a mobile phone * a clipboard * an envelope, in flight, dropping downwards Anyone: please, what _is_ that icon?
    • Graham Perrin
       
      The icon with four interpretations from one person is in fact a fifth thing: a 'tag'!
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

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 Getting Started Guide - Chapter 6: Triage Workflow and Stamping - 0 views

  • Today, many people do this by flagging emails or maintaining a task list. The problem is
    • Graham Perrin
       
      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
       
      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
       
      Whilst I'm getting started, I don't want to read that things were worse.
Graham Perrin

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

  • 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
1 - 20 of 23 Next ›
Showing 20 items per page