A bunch of my design mail is getting put in another folder. Sorry,
there are a few items in this week's summary that should have been
for last week.
Also, there are actually several conversations going on in the Cosmo
Login-related workflows update thread. The bits in the design list
summaries haven't been very clear. I will summarize this thread
independently so it makes more sense.
New Threads:
Priscilla proposed we defer free-busy work targeted for Cosmo 0.6 to
post Preview.
http://lists.osafoundation.org/pipermail/design/2006-November/
005674.html
Sheila replied to a thread on the Cosmo with a proposal to defer the
work to handle free-busy in the Cosmo UI until post Preview. The dev
team had this on the plan for 0.6 and since it scoped out as a couple
of weeks, the PPD team brought up the notion of cutting it.
+ From a user standpoint, our casual collaborator doesn't really need
this feature for Preview.
+ The developers felt otherwise and didn't think the cost was that
high. Cosmo can generate free-busy tickets whether or not they are
used by Chandler or the Cosmo UI.
+ Users can then click on these free-busy URLs and we need to handle
them somehow.
+ Priscilla suggested a dialog saying the feature is not supported.
+ Conclusion: We decided that for now we would use the dialog that
Priscilla suggested. As a side project we can work on figuring out
our free-busy interop story and also get a better handle on the
Chandler free-busy bugs and determine if we can deal with all the
issues for Preview. Once we do that, we can use the time allotted for
the free-busy estimates to do some free-busy work as it applies to
interop goals.
http://lists.osafoundation.org/pipermail/design/2006-November/
005689.html
Philippe forwarded some important instructions for users upgrading to
the latest Alpha4 checkpoint of Chandler. Due to a problem found with
our hosted service migration from cosmo-demo to osaf.us, we needed to
fix a bug in Chandler that breaks compatibility with old data. This
means that users have to start with a fresh Chandler repository and
fresh shared data. The only way you can backup your existing data and
move it over is to export all your calendars, re-import and re-share
all the collections.
http://lists.osafoundation.org/pipermail/design/2006-November/
005681.html
Priscilla, Mimi and the Cosmo team met to review and discus the list
of UI elements we want to have in the Cosmo UI for Preview. She also
attached the notes.
http://lists.osafoundation.org/pipermail/design/2006-November/
005682.html
Priscilla sent out a brief message with an update of where we are on
our screenshot design for the Cosmo Preview UI. They should be out soon.
http://lists.osafoundation.org/pipermail/design/2006-November/
005703.html
Sheila forwarded a list of the top 10 perceived performance problems
(from a dogfooder perspective). We want to here from others if there
are any we are forgetting.
http://lists.osafoundation.org/pipermail/design/2006-November/
005734.html
Mimi sent out a new proposal for the magic URL, login and subscribe
workflows we are going to handle in Cosmo 0.6. Now that we are going
to handle more than just events for Preview in the Cosmo UI, Mimi and
Priscilla wanted to rework the screenshots we had done for 0.6 in
anticipation of these new features. They scheduled a design review
with the Cosmo team.
http://lists.osafoundation.org/pipermail/design/2006-November/
005738.html
Priscilla also sent out some proposals for the Cosmo Preview UI, as
well as the post-Preview possibilities. We are aiming for something
simple in Preview but the developers wanted a bit more information
about our future design ideas.
http://lists.osafoundation.org/pipermail/design/2006-November/
005741.html
Continued Discussions:
Matthew had some further comments on the bare minimum for the Preview
casual collaborator Cosmo UI.
+ Matthew had some questions about the use of the cancel button in
the detail view. He thought the use of the word Cancel meant we were
stopping an operation and we should consider "revert" instead since
the behavior we want is to revert the changes I have made.
+ Priscilla commented that it seemed more intuitive to just click
away and get prompted asking if you want to save the changes.
+ Mimi replied that Google Calendar uses Cancel, so does Yahoo
calendar and hotmail calendar. Mimi thinks that people might be too
afraid to click away, something more explicit will let them know
their changes won't be saved.
+ Priscilla said that the better behavior is to have all the changes
saved like Chandler - when you actually edit a field and tab out.
+ After some initial analysis by Matthew, this is probably too
ambitious for Preview.
+ Mimi explained her position but doesn't feel strongly about the
"Cancel" button, if we consider any of the proposals.
+ Conclusion: Still waiting for resolution on this one.
http://lists.osafoundation.org/pipermail/design/2006-November/
005687.html
There was further discussion about the In Out collection logic
proposal refinements. This is pretty detailed and gets into some
implementation details. I think it's best we summarize in a separate
email since it's a lengthy discussion.
http://lists.osafoundation.org/pipermail/design/2006-November/
005686.html
The lengthy Cosmo Login-related workflows update thread took yet
another fork and started to get into the implementation details.
Matthew suggested the discussion move to the cosmo dev list.
http://lists.osafoundation.org/pipermail/design/2006-November/
005704.html
Jeremy did reply to a some questions Priscilla had put to the list
about timezones - mainly how do we figure out a user's default
timezone. We just use the timezone that the computer is set to.
The other discussion in the Cosmo Login-related workflows update
thread about the admin and file browser UIs continued. As of now
there is still disagreement about where to put this link and we will
be working towards a resolution ASAP.
http://lists.osafoundation.org/pipermail/design/2006-November/
005726.html
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
