If it does that addresses the migration problem, but not the problem
of a single Chandler user who wishes to sync multiple machines (the
problem Foxmarks addresses).

Pieter

On 5/11/07, Mimi Yin <[EMAIL PROTECTED]> wrote:
Morgen? If you use Reload to migrate, will your shared OOTB
collections rationalize themselves with the OOTB collections in the
new version of Chandler?

Mimi

On May 11, 2007, at 12:24 PM, Pieter Hartsook wrote:

> I published my Dashboard collection. Then upgraded Chandler to a new
> version where I had to blow away my data.
>
> I used restore published shares and saw my Dashboard collection on the
> qacosmo server, so restored that.
>
> So now I have an OOTB Dashboard collection that is not shared and a
> new Dashboard collection that is. Of course the shared Dashboard
> collection items appear in the OOTB Dashboard collection as well.
>
> It seems to me, if I restore apublished Dashboard collection from
> Chandler Hub it  ought to replace the OOTB Dashboard that only
> contains the Welcome to Chandler item.
>
> This would not only let me update as I move to new Chandler versions,
> but the use case where I have several Chandler Desktops running on
> various machines and want to keep them all in sync.
>
> Just wondering what others think.
>
> Pieter
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design


_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design

Reply via email to