Regarding the clip from Mimi's note, "I suggested that we hold off on this functionality for now as it complicates the mental model for QE widgets and it's not clear if QE is really a 'drive-by / casual collaborator' kind of workflow"
I think this workflow would require the view-collection web widget along with the QE widget. I don't see an obvious casual collaborator workflow for QE alone. My enthusiasm for the QE widget derives from the GTD collection workflow. (For non-GTDers, I mean the "get the idea out of your head and into a trusted place for later processing and organizing" workflow, that is, not Chandler collections.) The QE widget would mean less emailing to oneself, which typically then requires a bit of a somewhat tedious routine of unstamping as mail, stamping as something else (or not), drag and drop to one or more collections, removing from Dashboard perhaps, etc.). -Andre On Fri, 22 Feb 2008 15:12:45 -0800, "Mimi Yin" <[EMAIL PROTECTED]> said: > Met with Jeffrey about the Quick Entry (QE) widget for iGoogle. Here > are our notes below: > > WORKFLOW > 1. Go to Chandler Hub - Click on QE widget in gallery > 2. Click on iGoogle link - takes you to Google > - Do you want to add this widget to your iGoogle page > - Log into Google (if you aren't already) > - Yes > 3. Goes to your iGoogle homepage - where the Chandler QE widget has > been instantiated > 4. Log into Chandler Hub in the widget. > > OPEN ISSUES > - Persistence of username/password is an issue - You really want to > be able to stay logged in across iGoogle sessions, otherwise the QE > experience will be substantially hampered > > - We can store it in cookies in Firefox, but cookies isn't ideal > because you might have this weird case where somebody else logs into > their iGoogle homepage on your computer, but is logged in as you in > their Chandler widget. Freaky! > - Safari won't support storing the Chandler Hub username/password in > cookies. > > Solution? So I'm wondering if we can just offer users an option to > store their username password in their iGoogle account. > - There is a potential security hole (which Jeffrey thinks can be > patched up) where Google will pass your Chandler Hub username/ > password to your browser and then if you click on a link from within > the QE widget?, your username/password will be logged as the > 'referring URL'. > > Jeffrey and Travis had created the option for users to configure the > QE widget with a collection ticket-URL. I suggested that we hold off > on this functionality for now as it complicates the mental model for > QE widgets and it's not clear if QE is really a 'drive-by / casual > collaborator' kind of workflow. > > INTERACTION > - Grey out Send button > - Add a 'Clear' button which is greyed out at first, activates as > soon as you type into the text field and then turns to 'Undo' if you > hit 'Clear'. > - 'Undo' then turns to 'Clear'. > - Add grey hint text to the text field that shows people that the 1st > line will be used as the Title and the rest will be put into the > Notes field. > > STYLING > - Tooltips? > - Custom arrow for pulldown > - Get rid of yellow outline > - Specify fonts, sizes and color > > NEXT ACTIONS: > Mimi to go mock stuff up! > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
