Yes, I should have illustrated with a workflow example: That means, when sending items out, we want a way to make the item available on Cosmo via the Cosmo UI so that non-Chandler users can use the Cosmo UI to make Edits and send Updates. For example: Sheila sends out the weekly PPD meeting agenda proposal Monday morning. Priss, a Chandler user edits and updates the agenda in Chandler. Mimi, a non-Chandler user receives the agenda in Apple mail and clicks on a link to edit and update the agenda in Cosmo UI. You can think of it as: Upload this item to Cosmo so others can see it, edit it, update it. Sort of similar to how you might upload Photos to a photo-sharing service such as Flickr so that others can see view it, add comments, maybe even fix red-eye and make other changes.... As opposed to sharing photos with others using the same Photo Management app (e.g. iPhoto, Picasa, etc). I think the technical complication arises when we try to streamline the workflows so that sharing via uploading to a server/web app AND sharing via email AND sharing via desktop client all happen in a single end-user workflow, we're calling Item Sharing where you Stamp to Address and item and then click Send. Mimi On Oct 5, 2006, at 1:41 PM, Morgen Sagen wrote:
|
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
