New Threads:
Bear posted a new thread - Backup/Restore preferred feature name over
Dump/Reload
http://lists.osafoundation.org/pipermail/design/2007-February/
006472.html
+ Mike suggested that we use Backup and Restore to describe the
ability to create a complete backup of their Chandler data in a
manner that is cross-platform and schema-version independent.
+ Andi replied that we do have a separate Backup and Restore that
behaves slightly differently so that name is already used.
Bear posted a follow-up email to clarify his previous post on
renaming dump/reload - Backup/Restore and Dump/Reload - clarification
http://lists.osafoundation.org/pipermail/design/2007-February/
006475.html
+ We currently have Backup/Restore functionality available from the
File menu. It backs up the repository but you need the same version
of Chandler to restore it.
+ Dump and reload is a new feature to take the current repository and
export it using EEIM so that it's schema-version independent.
+ Bear is thinking that he can blend both the current backup/restore
and the new code for dump and reload but we haven't done this yet so
it's premature to get rid of the term backup/restore.
Mimi sent an update to the dashboard spec for recurring events. Mimi
has since updated the spec but a summary of major highlights.
http://lists.osafoundation.org/pipermail/design/2007-February/
006464.html
+ Changing the triage status applies to individual occurrences.
+ Stamping as a task applies will give the user the choice to apply
to a single occurrence, the entire series or all occurrences. We do
need to fix some bugs to make this work so for Preview we might only
have stamping as s task apply to a single occurrence if the other is
too difficult.
+ Read/Unread/Needs reply always applies to the entire series.
+ Reminders set in the detail view can apply to any subset of the
series. Reminders created in the detail view cannot be applied to
recurring events. We may have to live with this for Preview.
+ Send, Update, and the Addressing fields will always apply to the
entire event series. However, only 'edited' instances will be popped
to the top of the NOW section in the Dashboard view.
BKirsch sent out some questions about the Verbiage in Email Spec .7
as it pertains to outgoing messages.
http://lists.osafoundation.org/pipermail/design/2007-February/
006482.html
+ Mimi clarified the correct verbage for all the kind combinations -
SENDER> sent you a <KIND-COMBINATION> from Chandler at <DATE SENT>
+ We use the Chandler from NOT the email from.
+ The <TITLE> is the same as the title that appears in the dashboard.
+ <NOTES> refers to the body attribute.
+ The verbage for recurring events replaces what should appear in
place of "from/on <DATE/TIME> - this is a nice to have for Preview.
Jeffrey forwarded a reply to Andre's post to the design list. Andre
came across a bug where Anytime recurring events duplicated in
Chandler on restore settings.
http://lists.osafoundation.org/pipermail/design/2007-February/
006484.html
+ Since anytime events are now the default, we are still working out
a few bugs to get them to render correctly in Cosmo. Those have been
logged in bugzilla.
Andre posted on the Cosmo Home Collection Browser
http://lists.osafoundation.org/pipermail/design/2007-February/
006490.html
+ He has used this feature before and has noticed it missing since we
released Cosmo 0.6.
+ Travis clarified that the feature still exists and is called the
account browser. You can display it using the advanced settings tab.
+ With some clarification Andre located the feature and gave some
feedback re: the enhancements we made.
+ BCM asked if he was using the " view as HTML option" for calendars
and events since we were thinking of removing it. Apparently Andre
finds this very useful.
BCM sent out some feedback on the Cosmo "add to my calendars" feature
http://lists.osafoundation.org/pipermail/design/2007-February/
006503.html
+ He suggested having the ability to specify a name when we add a
subscription rather than changing the name afterwards.
+ He also commented - now that we have the calendar up and running,
overlays would be really useful to have.
BCM sent some further dogfood feedback on getting my google calendar
into osaf.us. Some highlights....
http://lists.osafoundation.org/pipermail/design/2007-March/006508.html
+ It's awkward to get his google calendar onto osaf.us since there is
no way to directly import events into Cosmo. He subscribed to Cosmo
collection using chandler and imported the events there. There wasn't
much progress feedback on the Cosmo side.
+ Switching weeks in Cosmo seems kind of slow.
+ We don't quite support the custom recurrence scenarios that BCM is
using. Specifically, the Cosmo UI doesn't show we have a custom
recurrence rule like Chandler.
+ He made note of some other performance issues.
+ Thinks we need to rethink the "view as HTML" feature.
Jeffrey posted that there is some Confusion about auto-triaging when
sharing. Both he and Stearns are working on pieces of this and have
different interpretations.
http://lists.osafoundation.org/pipermail/design/2007-March/006509.html
+ Mimi clarified that sharing and edit/update changes to an item
affect the section TriageStatus of that item but if you made a change
to the item's date/time, then auto-triaging based on date/time should
take effect.
BCM send some more Cosmo UI dogfood feedback.
http://lists.osafoundation.org/pipermail/design/2007-March/006511.html
+ It's hard to see all the important information on the lozenge
(start/end time, tz, summary) for 1/2 hr events.
+ Not a fan of the square look for event lozenges.
+ Having the detail view in constant edit mode is slightly confusing.
An idea would be to show as static text and fields become editable as
you click them.
+ Would prefer date/time picker widgets rather than text fields.
+ Made another request for more custom recurrence.
We held a Design Session - Conflict Management UI. Mimi was updating
the spec based on our discussion and wanted to do a reality check on
what we agreed upon.
http://lists.osafoundation.org/pipermail/design/2007-March/006512.html
+ Resurrecting items from the trash will put them back in all
collections, not just the one in which we deleted the item from.
+ We will be able to detect conflicts on global changes to the series
and on changes to individual instances in the series.
+ We won't be able to detect conflicts for this and future and rule
changes.
+ Detached series of occurrences don't have conflict management.
Sheila posted some Questions about name that appears in detail view
bi-line to clear up some confusing about https://
bugzilla.osafoundation.org/show_bug.cgi?id=8209
http://lists.osafoundation.org/pipermail/design/2007-March/006514.html
+ The name that appears in the byline comes from several sources
(depending on what is configured)
+ sharing account user name
+ email address
+ If we have created or edited events, tasks and notes we use the
account name from the default sharing account. If we haven't setup
any sharing accounts, we only display the date information in the
byline.
+ For draft message items we create and edit, in place of the name we
insert...
+ Email address associated with 1st Outgoing email account user has
successfully filled out; if there are no Outgoing email accounts...
+ Email address associated with 1st Incoming email account user has
successfully filled out; if there are no Incoming email accounts;
+ User name associated with 1st Sharing account; otherwise
+ We display only the date information.
+ Note: If you receive a Draft item via server sharing, Chandler
does not change the Send as / Edited by field to your email address
unless you actually click into the Draft item and make an edit.
Mimi responded to Andre's post - Installer detecting if Chandler is
running. Andre suggested that we provide the ability for the
installer to detect if Chandler is already running and either close
it for prompt the user.
http://lists.osafoundation.org/pipermail/design/2007-March/006519.html
+ Mimi has included this with our list of dump and reload scenarios.
Other Stuff:
Sheila sent out the notes from the Preview Meeting - Monday Feb 26th
http://lists.osafoundation.org/pipermail/design/2007-February/
006486.html
Sheila sent out the notes for the Weekly PPD Meeting
http://lists.osafoundation.org/pipermail/design/2007-February/
006494.html
+ Philippe replied to Sheila's notes with a summary of the Chandler
milestones and associated success criteria. Tracking these checklists
will help us mitigate the risks for Preview and get a better handle
on where we are.
+ It's agreed that this will not necessary give us a better estimate
of finish date.
+ We also should be tracking end-user criteria for fixing bugs as
well as end-user workflows since this progress information is more
useful to design, QA, Cosmo and also the Ops team
Philippe sent out a link to a CNET article on Serios
http://lists.osafoundation.org/pipermail/design/2007-February/
006496.html
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
