New Threads:
Phil Jones, another Google Summer of Code intern, sent out a summary
of the project he is working on - Google SoC Project: Quick Entry
Refinements
http://lists.osafoundation.org/pipermail/design/2007-June/007382.html
+ Phil has a couple of tasks he is starting out with
+ Adding a switch to the Quick Entry menu item in Chandler which
will bring the focus to the Quick Entry box in the top right of the
toolbar.
+ He will also be expanding the Quick Entry feature so that
additional commands can be added more easily.
+ Phil was interested in getting some technical feedback on the
preferred methods for providing plug-in feedback.
+ Jeffrey responded and explained the way we current develop parcels.
It seems our instructions page is a bit out of date.
+ Philippe added that another one of our summer interns is revising
the plug-in code so we will be updating all the various instructions.
Mimi started a new thread - Quest to rationalize copy across Chandler
Project
http://lists.osafoundation.org/pipermail/design/2007-June/007389.html
+ Mimi took a pass a creating a messaging properties to rationalize
all the user messages and text in Cosmo.
Jeffrey summarized a bugzilla discussion for the design list -
Calendar UI discussion
http://lists.osafoundation.org/pipermail/design/2007-June/007396.html
+ The discussion relates to bug https://bugzilla.osafoundation.org/
show_bug.cgi?id=9513 which has been deferred to future. It's about
the ordering of items on the calendar canvas and some lozenges
getting hidden.
+ Jeffrey talked about some of the things we could consider doing in
the future to address this issue ie: alpha blending, changing
indentation levels.
Mimi started a new thread on Registering deletes and removes as
pending changes...
http://lists.osafoundation.org/pipermail/design/2007-June/007397.html
+ Basically in attempting to track down a bug on the office calendar,
we discovered that we are ignoring deletes and removes from shared
collections when there are local edits. This means if someone deletes
or removes and item that gets edited, it simply appears again and you
don't get notified as part of the pending changes.
+ There is a proposal to fix this problem for non-recurring events
but Mimi wanted to know what was involved to get this to work
properly with recurrence and all the associated use cases.
Continued Discussions:
Mimi responded to Vera's Design proposal for progress reporting in
chandler for your evaluation
http://lists.osafoundation.org/pipermail/design/2007-June/007383.html
+ Mimi and Vera agreed to some modifications/enhancements for Vera's
proposal.
+ We will not only track the number of items that came into NOW last
week, we will also include the number that came into LATER.
+ We will also track the number of items in the NOW section that are
still there from the week before - this gives us some sense of how
quickly people are working on their current items. This also
translates to the LATER items as well - get a sense of how long some
items remain in LATER.
+ We will also track how many items became DONE as well.
+ Vera also added a follow-up that she is planning on integrating the
report output into a parcel
Andi responded to an old thread - Deleting collections only vs.
collections and items
http://lists.osafoundation.org/pipermail/design/2007-June/007391.html
+ Andre had sent a message to the users list talking asking about
what circumstances the user is presented with the 2 options to delete
the collection and delete the collection and items. He thought this
had something to do with whether or not it was in the dashboard.
+ Andre had suggested we add an additional option for "Deleting
collection and deleting items in this collection from
all the places where they appear (are included)"
+ Mimi pointed out that we can also satisfy Andre's use case with
multi-select and delete.
+ We are not sure if this will work for Preview or not.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
