Graham Perrin wrote: > > John Beardmore wrote: >> … a boolean star or not star isn't that good for prioritising. >> >> … I wish for the minimum that can do the job nicely. … >> >> … Scheduled items are things which you don't have to thing about - you >> just follow the program. >> >> Unscheduled items are where you go when you want to schedule some >> productive activity in some unallocated time slot. >> >> … If I was working with postit notes, I''d probably make a calendar out of >> the scheduled tasks, and sort the unsceduled ones by >> >> class of activity >> >> strategic importance >> >> and >> >> ungency >> >> where strategic importance and urgency are NOT the same things. >> >> (At busy times some urgent tasks (close deadlines) have to be dropped. >> Strategically important issues must be pursued, even if they have no >> deadlines.) >> >> … To me, we seem to be heading for something where the use interface isn't >> intuitive, and I don't find my organisational needs being fully met. I'll >> comment more when I've got more familiar with Chandler and maybe found >> time read the documentation. >> >>> When you seek a store/collection of >>> unscheduled unimportant items, what's the purpose? >> To organise, understand, prioritise and ultimately schedule them. … > > Thanks to John. I agree 100% that the UI should be intuitive.
Hi Graham, Sorry to be so long getting back on this. Pressure of work is stopping me experimenting with Chandler, but I am now using it as my main diary, and it's great in so many ways. > <http://www.diigo.com/063mi> and <http://www.diigo.com/063mj> present > highlights from documentation for Chandler 2. This work in progress is > developer-oriented but in the context of recent discussions, three things > leap out at me: > >> Chandler is also a platform for building a PIM … > >> … additional triage states can be defined in plugins. I suppose in a sense, some general mechanism for extending and dumping objects within Chandler would be nice. I could then add attributes like job number, and export items at the end of each month to generate some kind of time sheet. >> Generally, triage can be thought of as a timeline … > > In Chandler as we know it, that timeline is shown vertically. For obvious > reasons, NOW is uppermost. I'm not sure that is obvious. To me, now is between present and future, so which ever way you chronologically sort a list, NOW won't be at the top. > If from the Chandler platform someone builds an alternative (but > complementary) PIM, to show the timeline in a different way: how might we > shake things up, and let them settle, to suit our individual/organisational > needs? > > Key words: collections, triage, timeline. And Dashboard, although we don't > see that in Chandler Hub. > > To me, an obvious alternative would be to have a timeline horizontally. More > on this in a separate topic. OK. Cheers, J/. -- John Beardmore, MSc EDM (Open), B.A. Chem (Oxon), CMIOSH, AIEMA, MEI Managing Director, T4 Sustainability Limited. http://www.T4sLtd.co.uk/ Energy Audit, Carbon Management, Design Advice, Sustainable Energy Consultancy and Installation, Carbon Trust Standard Registered Assessor Phone: 0845 4561332 Mobile: 07785 563116 Skype: t4sustainability _______________________________________________ chandler-users@osafoundation.org mailing list unsubscribe here: http://lists.osafoundation.org/mailman/listinfo/chandler-users Chandler wiki: http://chandlerproject.org/wikihome
