New Threads:
Dan posted a new thread - Confusion after a recurrence series is
"split" by making a modification and choosing "all future events"
http://lists.osafoundation.org/pipermail/design/2007-January/006172.html
+ He points out that when you make a change to a recurring event that
applies ot "all and future", it splits the series in 2 and subsequent
changes to one series won't apply to the other. He gave a use case in
which this could result in confusing behavior.
+ Mimi replied asking if we could treat this the same way as we
currently treat modifications to individual events. All and future
changes would continue to apply to all and future even if we have
made all and future changes to a later occurrence.
+ Jeffrey responded that this is difficult and splitting the
recurring series was a simplification. Changes would also have
implications on Cosmo as well.
John started a thread on Search. He had just checked in the first
draft of the search feature for Preview and had a number of
suggestions for enhancements.
http://lists.osafoundation.org/pipermail/design/2007-January/006175.html
+ One the main issues centered around our use of the search field for
a dual purpose - both searching and for quick item entry and the
discoverability of each.
+ There as also much discussion on the appropriate default for the
search field.
+ He also had a list of search features that still had not been
implemented so we could prioritize.
+ Mimi responded..
+ The ability to display a drop-down with commands when the user
types / is still yet to be implemented and will help users but some
feel it's still a barrier to discoverability.
+ We will also have hint text in the search field which will help.
+ The search results should show for the selected collection and app
area only.
+ A number of other issues were discussed in detail...
+ For Preview, the default for the search field will be to create new
items. Even if we don't have the hint drop-down working. We will have
search accessible through Cmd/Ctrl-F and via a menu item that will
make it more accessible.
+ For now we will table the issue with the adjustable sidebar.
+ Search results in the sidebar will be shortened in the format
"Search R...(10)
+ We started separate threads to deal with the relevance, triage
table view and how CLIs work.
Mimi forwarded a bugzilla discussion to the list - [Bug 7944]
Deleting collections and items should move items to the trash
http://lists.osafoundation.org/pipermail/design/2007-January/006183.html
+ The issue is around whether or not we should move items to the
Trash, even if they have been explicitly put into user-defined
collections. Our plan is to simply put them all in the trash and
users can undelete anything specifically. We assume this won't be a
common use case
+ This discussion continued an another thread - Deleting collections
and the items in them.
http://lists.osafoundation.org/pipermail/design/2007-January/006184.html
+ Jeffrey has a different perspective, deleting collections can
happen quite frequently. He gave an example of downloading a sports
team schedule and moving what games you are interested in to a
personal calendar. We then delete the original.
+ Mimi clarified that we already support this workflow. This calendar
will most likely be a not-mine collection in which case it's contents
would move to the Trash except for items that have been added to
other collections.
+ There are use cases that support the user wanting to delete all the
items (including those from the user-defined collections)
+ Decision: Compromise is to prompt the user with a second dialog
when they delete a collection that has items in user-defined
collections.
Sheila sent out an email about the weekly - Preview Countdown Meeting
(giant non-code deliverables meeting)
http://lists.osafoundation.org/pipermail/design/2007-January/006197.html
In the thread Re: Design Digest, Vol 39, Issue 26, Andi continued the
discussion around the search feature.
+ He added a Find menu item under Edit to help the user discover the
search feature.
+ It also works with Command-F - puts the user into search mode in
the text field.
+ We changed the /search command to /find to be consistent with the
menu item.
http://lists.osafoundation.org/pipermail/design/2007-January/006204.html
Katie has several tasks involving reworking the menu items. She
posted an email (confirming the demise of "Use Sections") confirming
that she is to remove the "Use Sections" menu item per the lengthier
search thread.
http://lists.osafoundation.org/pipermail/design/2007-February/
006211.html
One of several search threads were started by Mimi. Saving Search
Collections addresses why we deferred the ability to save search
results until post-Preview.
http://lists.osafoundation.org/pipermail/design/2007-February/
006215.html
+ Due to various requirements and complexities, Mimi doesn't see a
phasing proposal that would enable us to implement something in the
Preview time frame. After some back and forth, we decided on a
compromise.
+ Some of this already works today and we can liken it to the user
creating a new collection and dragging all the search results into it.
Another splinter discussion from the search thread was about using a
Separate CLI palette
http://lists.osafoundation.org/pipermail/design/2007-February/
006220.html
+ The controversy is around how people will perceive the field in the
toolbar - for search or command line entry.
+ Mimi proposed changing the field to be non-round on the mac if that
makes it less confusing.
+ John still felt that using a single field for a dual purpose is
problematic and confusing
+ It was decided that although a more elegant solution is the ideal,
what we have now is good enough for Preview plausible promise.
Yet another search splinter thread on Relevance
http://lists.osafoundation.org/pipermail/design/2007-February/
006222.html
+ Jeffrey suggested that the current relevance doesn't work that well
and sorting by triage status is probably more useful.
+ Mimi agreed that this would clear up some confusion around the
views. We would no longer require a specific search view and could
simply display items by day view, week view and table view.
The final search thread was about the Adjustable-width sidebar.
+ We have discussed the adjustable sidebar a number of times. Mimi is
concerned about the design work required to get this right before
Preview. We haven't done the work to think about out all the
workflows and getting the mini calendar to look that way it does
today was alot of work. We understand that we would like to fine a
solution for the long-term and concatenating the sidebar name is the
short-term proposal.
http://lists.osafoundation.org/pipermail/design/2007-February/
006224.html
Bear had forwarded an article to Mimi - Jon Udell article on
subscribing to Google Calendar from Outlook
http://lists.osafoundation.org/pipermail/design/2007-February/
006230.html
+ A few observations. Chandler provides a unified way to share (same
step) as opposed to Google and Outlook that present 2 different ways
to publish/share.
+ Google also presents the "subscribe with other clients" option as a
list of technologies which isn't very helpful to most users.
+ Mimi pointed out that we just refer to it as sharing and don't
present it as sharing vs webdav. Morgen pointed out that in the short-
term we need to have users pick chandler vs webdav sharing because we
are using 2 different technologies under the hood. Maybe in time we
can unify this but it's easiest for Preview since we are changing the
sharing format.
Other Stuff:
We held a design session on Jan 29th to review the auto-triage
functionality and handle any unresolved issues
http://lists.osafoundation.org/pipermail/design/2007-January/
006171.html.
+ The team came away with a set of next actions for finishing the
auto-triage functionality. This included making some simplifying
assumptions and a list of use cases for when items ARE and AREN'T
auto-triaged. Mimi has this all summarized in a follow-up email.
http://lists.osafoundation.org/pipermail/design/2007-January/006179.html
Philippe sent out a link to Accomplice - another GTD type product.
http://lists.osafoundation.org/pipermail/design/2007-January/006173.html
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
