Calendar spec: minor use case clarification
The use case of "subscribe to calendar... uses another client other
than Chandler" won't be handled in entirety, and I *think* that this is
a use case that is more handled by the server than by the client
(Morgen can correct me). I believe this could be reworded something
like this:
"A user subscribes to any read-write or read-only calendar hosted in
a Cosmo server in the correct format"
Lisa
On Jun 3, 2005, at 6:23 AM, Sheila Mooney wrote:
All,
I thought I would forward a couple of the 0.6 specs that are now ready
for a wider review. They do not yet contain the implementation details
but the UI behaviors are fairly well documented after several
iterations.
Detail view spec:
http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_6/Detailview
-0.6.htm
Calendar spec:
http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_6/Calendar
-0.6.htm
Feedback and comments are welcome.
Thanks,
Sheila
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
