Hi Christian,
Thank you for your feedback, I appreciate it.
I agree that text description of the issue cannot be replaced
and is of great value.
Your point on time consumption of watching compared to explanation
+screenshot
is also very instructive for my reflection on increasing efficiency
(if possible)
in the development process.
The searchability is also a very important aspect of these
informations, of course.
Thank you also for the technical feedback,
can I ask you from which country you experienced this issue ?
Thank you
Sebastien
On Sep 10, 2009, at 8:16 AM, Christian Lohmaier wrote:
Hi Sebastien, *,
On Wed, Sep 9, 2009 at 7:51 PM, Sebastien
Plisson<sebastien.plis...@free.fr> wrote:
I thought it could be great to describe issues by just recording a
short
screencast
Well, "no"
A screencast forces you to spend the time watching it, the real issue
probably only comes at 3 minutes into the screencast, so this time is
forced on the QA and dev persons (and not only only one person, but
multiple).
So while a screencast is a good help to further describe and
demonstrate a problem, it is in no way a replacement for a good
description and a screenshot.
Especially when then people write issues with "see the screencast"
with no other explanation, we will have a big mess.
So again: Screencast are fine in /addition/, but not as replacement.
For more information, bookmarklet, etc you can check it at
http://www.screenjelly.com
What do you think ?
I had a look to the "how to install OOo on mac" screencast you linked
from your blog and was very, very disappointed.
First of all the screencast wouldn't even start. It showed the
buffering circle thing but didn't start off.
By chanc I tried it with one of your public screencasts, the same
problem.
It did work without problem however, when switching to fullscreen
mode. (i.e. in fullscreen mode the screencast showed playing). Use the
very same screencast in the regular mode and all you get is the
"buffering" symbol without any action.
So that for the technical part.
And then to the part I tried to point out in the first part of the
post: To get to the contents you need to watch. And that costs time.
The disappointment id even bigger when you don't get what the title
suggests.
The "how to install OOo on Mac" doesn't show how you install OOo on
Mac. It shows going to the OOo-homepage and clicking on the download
link. Before OOo is downloaded, the screencast recording is stopped.
You don't even see the opening of the dmg.
I'm not sure whether it is possible to easily edit the screencast with
that software, but many users probably won't anyway, and staring at a
progress meter is not very satisfying.
Please don't get me wrong, I myself did create screencasts already as
well (with pyvnc2swf) to illustrate something, and it can help to
illustrate stuff hard to put into words. But please don't forget the
words. You cannot search for contents shown within a screencast, you
can only search for the words in the description. Keep that in mind
and it will be a great help, otherwise not.
ciao
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: mac-unsubscr...@porting.openoffice.org
For additional commands, e-mail: mac-h...@porting.openoffice.org
