Mimi Yin wrote: > The theory was, the reason* why information management sucks is due to = a > lack of integration. *Integration in terms of data types and > integrations in terms of workflow.=20 >=20 > *In the meantime, the world around us has changed. Instead of a trend > towards more 'integrated' solutions, people are adopting a wider range > of tools and workflows are knit together via a wide variety of > interoperation techniques.*
I am not so sure I'd buy that as a whole. Interoperation, yes, that is important. But I do think there is a place for an application that *integrates* the *interoperation* features. You can see integration in the hardware side as well. Where 10 years ago or so people carried pagers, cell phones and palm devices, they now carry just a smartphone/PDA. > integrates.* Chandler is no longer about replacing* your email client, > enterprise email, calendaring and content management systems, wiki, > project manager, IM, news reader... This seems like mischaracterization of why things are the way they are and where we are planning to go with email. Doing full featured email client is a lot of work, and we simply have not done the work (yet?) to become one. It would not take a huge amount of work to become usable email client for casual email users (say 0-10 emails a day with no spam to speak of). I very strongly believe that email must be a core area of any serious PIM, or it is not interoperable nor integrated. What we have now feels like a terrible kludge to me. > *That being said, the UI we have today is misleading.* It contains > vestiges of the 'old' way of thinking about integration which has the > potential to scare new users away, both because there is a gut-level > sense that the app is big and complicated and that you can't get starte= d > without moving your entire world into Chandler. Now this I partly rhyme with, although not exactly for the same reason as you do. > *1a. Remove the Reply, Reply All, Forward buttons from the Toolbar*; an= d=20 > *1b. Add a Reply/Forward menu item to the Item menu* I would be ok to move email specific buttons to detail view for items stamped as email. I don't think you can lose the Reply All button, though= =2E > *2. Remove the the 'New' button from the Toolbar* and really focus on > the quick item entry bar as *the* way to create new items in Chandler. I am somewhat neutral about this at the moment. > *3. Rename the Mail application area Messages* so that it's more of a > 'Message Center', a place where you can see the messages you > sent/received from Chandler (not un-like Inboxes for social networking > sites like Facebook or Linked In), and less of a *"Mail Application".* I have a slightly negative feel towards this. If we had an IM client together with email, then perhaps Messages would make sense. But I don't see that as the case today. > In a previous message, I suggested that we address the *'Where do I put= > my projects'* problem by renaming the Tasks, Projects and Collections, > Workspaces. I'd like to hold off on that idea for now and see how the > suggested 'paring down' above plays out with new users. I have somewhat negative feel about this. Tasks are well understood in PIMs. Personally I don't have any problems with collections at the moment= =2E Have you thought about them as contexts? Like our sample collections are more about contexts (Home, Work, Fun). --=20 Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
