Mike's dashboard

hi Peter, thanks for your reply. I do have a url - but the content is a little confidential. When I get a minute, I can create a copy and change the content to be safe :)

The main challenge i see is the zooming in and out at speed.

I think there is probably a lot of trial and error involved in getting it right.

Maybe there is some path analysis that can be done to advise users that they may have a motion sickness problem with their prezi? – Mike, on October 04, 2009 08:52

well you already have a problem with the synchronisation, there is no real sync - you simply create a new copy each time you click 'Sync' - a quick win would be to tidy it up. You don't have to worry about merging or anything like that - or even differences (atleast not for now). Let me explain.

You could just save a timestamped version on every save (a bit like a wordpress blog). The default view is the latest (but with the option of looking at the history).

It gets a little trickier with the sync of the desktop... here is a possible solution.

Easiest is perhaps to create a timeline per source (i.e. desktop and web). This way you could maintain versions separately , and when they sync, you can address the difficult bits.

An Example...

When I create a prezi online it becomes Prezi-Web/0410200909:35:31), if I make some changes to the online version and save (10 minutes later) , the system creates a copy Prezi-Web/0410200909:45:00.

This would work exactly the same on the desktop - same process, just different version tagging , perhaps Prezi-Desktop/04102009.

Syncing them is a little complicated, but you can make a pretty good job of it, I'm sure... will think some more soon :)

i love prezi - but the motion sickness can be a problem. I know 2 very prominent trainers who have stopped using prezi because their audience have complained about the queesiness they experienced (and it wasnt the content!).

I want to keep using prezi and I think there is some changes that must be possible to make the movements less dizzying. Also, I think helping us (the users) with some best usage guidelines to minimize dizziness would also be good.

doh!

My bad - it thought it would either save on exiting the field or keep the value in the field and then a form level save button.

This solution works, but it may not be conventional (who is conventional anyway!).

Mike