Since I skipped over some lengthy threads that will be summarized
separately, I decided to do two weeks instead of one in a single
summary.
New Threads:
BKirsch sent out a proposal that we don't Change collections when
Replying and Forwarding
http://lists.osafoundation.org/pipermail/design/2007-March/006534.html
+ Currently when the user hits reply or forward the out collection is
selected and the focus put in the mail message. He is proposing that
we don't do this for Preview since it's counter intuitive to the way
current email apps work.
+ We decided on the following....
+ If the user tries to create items (or reply/fwd) in the trash
collection - they get a warning popup.
+ If you are in the IN collection
+ Don't switch context, as in don't leave the IN collection
+ De-select the message item the user is replying to / forwarding
+ Display the Reply/Forward in the Detail view
+ Add the Reply/Forward to the OUT collection (which will mean it
will get picked up by the Dashboard collection as well?)
+ All other collections:
+ Don't switch context
+ Add the Reply/Forward item to the selected collection and
automatically select it.
+ Display the Reply/Forward in the Detail view.
+ Add the Reply/Forward to the OUT collection (which will mean it
will get picked up by the Dashboard collection as well?)
Jared posted a mail about Non-code deliverables for service: error pages
http://lists.osafoundation.org/pipermail/design/2007-March/006547.html
+ When Chandler Hub users encouter an unexpected error, they see a
raw tomcat error. Jared is suggesting that we display and alternate
page with a user friendly message and a look & feel consistent with
our other chandlerproject.org pages.
+ Sheila is going to add this to the non-code deliverables list.
Priscilla responded to BCM's email on feedback for getting my google
calendar into osaf.us.
http://lists.osafoundation.org/pipermail/design/2007-March/006548.html
+ Priscilla has compiled BCM's feedback into bugzilla and prioritized
them based on Preview and Future goals. Some of the items will be put
out for discussion on the design list.
Mimi put out a request for detailed use cases for Duplicate, Cut,
Copy and Paste in Chandler.
http://lists.osafoundation.org/pipermail/design/2007-March/006549.html
+ Mimi put together a list of workflow examples for each one but
wanted some additional more specific use cases for when people want
to use duplicat, cut, copy and paste.
BCM sent some more Cosmo feedback on subscribing to cosmo feeds.
http://lists.osafoundation.org/pipermail/design/2007-March/006550.html
+ Basically BCM summarized his steps to subscribe to feeds and
indicated that a hyperlink from the "chose feed reader" dialog would
enhance and shorten his workflow.
+ There were a couple other suggestions to make this workflow easier
but having a link from the dialog directly seems to be the easiest.
Grant checked in a new feature to import and export VTODOs - The
user, the Chandler and the ICalendar VTODO
http://lists.osafoundation.org/pipermail/design/2007-March/006565.html
+ You simply use the import/export menu the same way you do for .ics
files.
Travis is about to resume implementing the "Forgot Password"
workflow and summarized how this will work for the design list.
http://lists.osafoundation.org/pipermail/design/2007-March/006572.html
Grant send an email about the "importance" attribute we currently
support on ContentItem - The importance of Importance?
http://lists.osafoundation.org/pipermail/design/2007-March/006574.html
+ We are not using this attribute anywhere other than test code so he
was thinking of removing it entirely.
+ Nobody seemed to have an objection to that.
Based on replies to Mimi's summary of end-user documentation - End-
user documentation, anyone?, Mimi pulled together some of the
questions and comments into a FAQ.
http://lists.osafoundation.org/pipermail/design/2007-March/006577.html
+ Sheila is about to send out a last call for all the end-user docs
for Preview.
BKirsch sent out an Edit / Update workflow question.
http://lists.osafoundation.org/pipermail/design/2007-March/006578.html
+ Brian wanted to confirm that in the case of updated to an email
conversation, the from, to and cc fields will not change providing
the user does not add or remove any of the participants.
+ Mimi clarified that if the sender is not already mentioned in one
of the Chandler addressing fields (to, cc, bcc), then if someone
comes along and updates the item, the previous sender is added to the
cc field so they don't get left out of the thread.
Mimi started a thread for discussing more fun with items in multiple
collections.
http://lists.osafoundation.org/pipermail/design/2007-March/006582.html
+ The Cosmo folks have been working on supporting items in multiple
collections and we have run into a bunch of issues with Chandler, the
sharing work and getting everything to work end to end ok. This is
very lengthy thread and it makes sense to summarize separately since
some of the issues are still yet unresolved.
BKirsch sent out a list of questions about the Email Spec.
http://lists.osafoundation.org/pipermail/design/2007-March/006600.html
+ He wanted to know if the sender of the message was also supposed to
receive a a copy in his/her inbox.
+ What happens when another user received the edit/update via sharing
- the sender info will not be in the Chandler from, to, or cc fields
+ Mimi clarified - When editing sent items, the previous sender or
updater should be automatically added to the cc field of the message.
This is the Chandler cc and not just the email cc. If the sender of
the message wants a copy, they can do this explicitly.
+ There was another question raised about whether or not changing the
addressing fields raises conflicts or not.
+ If 2 users change the same field, it is captured as a conflict.
Morgen was going to take a look at some Brian's code to see what's
going on.
Mimi posted on - Using the Account Browser to restore a lost Chandler
repository.
http://lists.osafoundation.org/pipermail/design/2007-March/006605.html
+ Mimi detailed her observations/issues when trying to restore
collections onto Chandler Desktop on Vista using the account browser.
+ Among other things, Mimi noted the confusion with the /username/
freebusy URLs and it was hard to figure out exactly how to get a ticket.
+ Some of the confusion in the naming that Mimi brought up will go
away once the new sharing format is in place. People won't be going
to get the Cosmo bookmarkable URL from the account browser as often.
+ It's unclear if we are going to make significant changes until that
is all in place. There are a couple of bugs logged for improvements.
+ Mimi and Priscilla are logging appropriate enhancements/bugs into
bugzilla to be reviewed by the bug council.
Grant took an IRC discussion to the list - Clarification on error
icons. The proper behavior is as follows....
http://lists.osafoundation.org/pipermail/design/2007-March/006609.html
+ If a conflict arises on an item do we display an error icon next to
the collection in the sidebar AND in the communication status column.
+ If there is a sync error we display an error icon next to the
sidebar collection AND in the communication status column.
+ If there is some sharing error that is not associated with a
particular item we display an error icon next to the sidebar. NO icon
appears in the communication status column for every item in that
collection.
+ If there is a mail error during download we will display an error
icon next to the In collection in the sidebar.
+ If there is an error sending mail an error icon appears next to the
Out collection and in the communication status column for that
specific item.
Mimi looked at the current state of the view selector - Changing
views in Chandler.
http://lists.osafoundation.org/pipermail/design/2007-March/006626.html
+ There are a number of bugs (which have been logged) that we need to
fix in order to get this right. There are a bunch of issues surfacing
that make it hard to get this working correctly, particularly with
recurring events.
+ Mimi is suggesting we consider pulling this feature from Preview.
The thread Ted started for Towards a solution for Items in multiple
collections? is related to the discuss about more fun with items in
multiple collections.
http://lists.osafoundation.org/pipermail/design/2007-March/006628.html
+ As with the later, this thread is really long and deserves it's own
summary.
Priscilla posted the detailed write-up for yet another interview with
a casual collaborator - Another Interview: A Casual Collaborator
perspective of Cosmo 0.6
http://lists.osafoundation.org/pipermail/design/2007-March/006633.html
+ The user encountered several bugs that has been logged.
Mimi posted a question about - [Bug 8249] Disallow creation of new
messages in "In" collection.
http://lists.osafoundation.org/pipermail/design/2007-March/006650.html
+ She was wondering if it was difficult to just allow users to create
new items in the IN collection, as an inclusion. We would disallow it
for the trash collection as planned.
+ If the user hits reply, reply all, fwd the agreed upon desired
behaviors is as follows.
+ IN collection
+ Don't switch context, as in don't leave the IN collection
+ De-select the message item the user is replying to / forwarding
+ Display the Reply/Forward in the Detail view
+ Add the Reply/Forward to the OUT collection (which will mean it
will get picked up by the Dashboard collection as well?)
+ All other collections:
+ Don't switch context
+ Add the Reply/Forward item to the selected collection and
automatically select it.
+ Display the Reply/Forward in the Detail view.
+ Add the Reply/Forward to the OUT collection (which will mean it
will get picked up by the Dashboard collection as well?)
Still some leftover discussion about - dialog.CenterOnSCreen()
http://lists.osafoundation.org/pipermail/design/2007-March/006660.html
+ Heikki is still advocating that we not use any Center methods for
dialogs.
+ BKirsch was having a problem centering the account preferences
dialog without using CenterOnScreen - we need to test this on all
platforms.
Mimi forwarded a Chandler-dev discussion to the design list since it
started to talk about user workflows - ContentItem sharing (Was Re:
[Chandler-dev] What attributes get shared over EIM)
http://lists.osafoundation.org/pipermail/design/2007-March/006681.html
+ The discussion was about needing to share the needs reply status.
Mimi presented a workflow for when 2 people would want to do this. It
isn't essential for Preview but we could definitely identify some use
cases. Mimi was wondering is we could make this optional.
Continued Discussions:
More discussion on the Questions about name that appears in detail
view bi-line.
http://lists.osafoundation.org/pipermail/design/2007-March/006546.html
+ Further comments by Mimi - we probably don't need to have "created
by xxx on yyy" if you don't share or send any email. It might simply
be visual clutter. It's good enough to only display the date info. We
could replace xxx by simple "me" rather than using the fullname.
+ Philippe sent a detailed description, based on the desired user
behavior, of how the various attributes <lastModifiedDate>,
<displayDate>
+ There was a great deal of back and forth in the discussion and it's
too lengthy to summarize. We will summarize this thread on it's own
separately.
Meetings and other stuff:
Priscilla sent out the notes for the Preview Countdown meeting Monday
Mar 5th.
http://lists.osafoundation.org/pipermail/design/2007-March/006533.html
Philippe sent out all the details for the Internship positions
available with OSAF this summer
http://lists.osafoundation.org/pipermail/design/2007-March/006568.html
Sheila sent out the notes from the Cosmo 0.7 planning meeting.
http://lists.osafoundation.org/pipermail/design/2007-March/006579.html
Priscilla conducted a post Cosmo 0.6 user interview and sent out all
her notes - Interview: A Casual Collaborator perspective of Cosmo 0.6
http://lists.osafoundation.org/pipermail/design/2007-March/006581.html
+ The next steps are to log some of these issues in bugzilla and take
some of the feedback to the list for specific discussion.
+ There was some back and forth between Mimi and Priscilla to discuss
the issues that were captured.
Mimi is running Chandler on Vista and sent out a screenshot -
Chandler lookin' hot on Vista
http://lists.osafoundation.org/pipermail/design/2007-March/006632.html
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
