For Preview, there will be a single Dump and Reload option for end-
users. Is the backup functionality where users pick their own file
location included in Dump and Reload? My understanding of DnR was
that Chandler would automatically dump the repo somewhere.
I understand how this is a general crossing platforms issues: Is
there a way to 'detect' what platforms the user is crossing? My
concern is that most people don't think of PPC to Intel as a platform
switch.
It seems like the best way for people to deal with this problem is to
publish everything to Cosmo. Save their settings as an .ini file and
then email themselves the .ini file and Restore settings. Does this
take care of all the Dump and Reload issues as well? What if this was
good enough for Preview?
Mimi: More in-line...
On Feb 23, 2007, at 10:11 PM, Andi Vajda wrote:
On Thu, 22 Feb 2007, Mimi Yin wrote:
Another hurdle: We need to communicate to the user the highly
unintuitive idea that in order to Restore their data on the new
Intel Mac, they must first blow away their old PPC repository,
otherwise, Chandler on the new Intel Mac won't start up at all.)
Not true anymore. With my fix to bug 8186, I put up and dialog
informing them about Backup and Restore. Their chandler should
start, but with that error dialog, and then a fresh repository.
Well this is what my comment was about on 8186. I was rooting around
for a more concrete way to explain this problem to users and ran into
problems making it sound easy ;o)
Not to sound panicked or anything, but...Is there a way to do Dump
and Reload for PPC-Intel Mac from the new Intel Mac?
I don't know about "Dump and Reload" but "Backup and Restore" of a
PPC repositoruy on an Intel mac can only work if the PPC bits are
run on Intel which is possible when stubbing out PyLucene (which is
not supported under Rosetta, the PPC emulation on Intel). That
PyLucene stub is here [1].
Is that a possibility for Preview? Other Mac apps make this
transition without having to do anything special...which makes any
hiccups in Chandler even more confusing...By contrast, most people
don't have expectations around being able to port apps and data from
Windows to Mac.
I'm not saying this is a must for Preview...but I'm wondering if
there are ways for us to make this transition easier that we haven't
considered for whatever reason.
Currently our only 'solution' to this problem is a dialog: https://
bugzilla.osafoundation.org/show_bug.cgi?id=8186
That 'solution' is better than the crash and may be as good as it
gets since we have no control over how and when users copy their
stuff around from one machine to the next.
I think PPC to Intel Mac is a special case tho, for the reasons
outlined above.
Any ideas? How important is it for us to get this workflow right?
I should also say that this problem is not specific to PPC ->
Intel. Any such transfer to a different machine is problematic. A
Windows user switching to a Mac would encounter the very same problem.
Berkeley DB environments are not portable, even machine to machine.
The only way to port a repository from one machine to another is
via Backup and Restore. (and via Dump and Reload, once it's
implemented, but then you're not porting your repository, only the
latest version of a subset of the the user's data is getting dumped).
Besides carefully documenting this 'feature', I don't know what
else to suggest.
Andi..
[1] http://svn.osafoundation.org/chandler/trunk/external/PyLucene/
dummy/
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
