Forwarding bug to the list.
What would it mean to keep the 'order' of collections in sync between
Hub and Desktop?
What's the order if the user has multiple sharing accounts and/or
only a subset of Hub collections synced on their Desktop client?
(Hopefully this will *not* be the common case.)
Can we order collections as 'best we can' and skip over missing
collections? See example below.
Hub 1
*D*
*3*
*A*
B - Not synced on Desktop
Hub 2
_2_
_1_
4 - Not synced on Desktop
Desktop
*D* - Shared on Hub 1
*3* - Shared on Hub 1
_2_ - Shared on Hub 2
*A* - Shared on Hub 1
_1_ - Shared on Hub 2
C - Not shared
Mimi
Begin forwarded message:
From: [EMAIL PROTECTED]
Date: November 5, 2007 11:52:44 AM PST
To: [EMAIL PROTECTED]
Subject: [Bug 11244] Keep order of collections in sync between Hub
and Desktop
https://bugzilla.osafoundation.org/show_bug.cgi?id=11244
Dan Steinicke <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------
------
AssignedTo|[EMAIL PROTECTED] |
[EMAIL PROTECTED]
Target Milestone|--- |0.7.future
--- Comment #1 from Dan Steinicke <[EMAIL PROTECTED]>
2007-11-05 11:52:42 PST ---
Bug council targets 0.7.future.
Per bug council discussion:
Mimi this needs to be discussed on the list as there is no current
Cosmo api
for this, and other issues such as what the order would be if
Chandler is
subscribed to multiple servers.
--
Configure bugmail: https://bugzilla.osafoundation.org/userprefs.cgi?
tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You reported the bug.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
