openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hans Zybura" <hzyb...@zybura.com>
Subject RE: Issues with file associations for some users...
Date Wed, 18 Dec 2013 10:16:15 GMT


> -----Original Message-----
> From: jan i [mailto:jani@apache.org]
> Sent: Wednesday, December 18, 2013 9:39 AM
> To: dev
> Subject: Re: Issues with file associations for some users...
> 
> On 18 December 2013 02:09, Kay Schenk <kay.schenk@gmail.com> wrote:
> 
> > On Tue, Dec 17, 2013 at 4:43 PM, Rob Weir <robweir@apache.org> wrote:
> >
> > > On Tue, Dec 17, 2013 at 6:30 PM, Kay Schenk <kay.schenk@gmail.com>
> > wrote:
> > > > We have posted Installation Instructions for OpenOffice for some
> years.
> > > >
> > > > However, some users seem to still have issues with the file types
that
> > > AOO
> > > > will assign to itself after installation despite the fact that users
> > are
> > > > given the opportunity to change this. Please see:
> > > >
> > > >
> http://www.openoffice.org/download/common/instructions.html#fileassoc

<citation from instructions page link above>
7. Select a setup type (we recommend Complete) and click Next.

The File Type window is displayed.
</citation>

I just tried a fresh install on one of my test vm's (win7-32 ultimate) where
previously only LO 4.21 (updated from LO 3.x) was installed, no Microsoft
Office, no earlier version of OOo/AOO. I've used the German installer
'Apache_OpenOffice_4.0.1_Win_x86_install_de.exe', downloaded from
sourceforge about 3 months ago.

I left setup type to the pre-selected type complete (I don't remember what
it said in German).

Contrary to the description cited above, there was no File Type window
displayed at all, i.e. there was no chance to choose file type associations
during install.


> > > >
> > > > We could use some help with alternate wording or presentation of
this
> > > > topic. We welcome your suggestions. Thanks.
> > > >
> > >
> > > Presumably the user who had the problem (and reported it to the
private
> > > list):
> > >
> > > 1) Did not read the install instructions
> > >
> > > 2) Did not pay attention to the install wizard panel where
associations
> > > were set
> > >
> > > 3) Perhaps is not familiar with what file associations are and that
> > > they can be changed by applications or by the user.
> > >
> > > Looking at Google Analytics it looks like the
> > > /download/common/instructions.html page is viewed around 700 times
> per
> > > day.  Since we have around 170K downloads per day, it is clear that
> > > very few people consult that page.
> > >
> > >
> > > I wonder this is a topic for a future post-install survey?  Questions
> > like:
> > >
> > > Are you aware of the MD5 hashes and detached signatures?  Did you use
> > them?
> > >
> > > Are you aware of the install instructions on the website?  Did you
read
> > > them?
> > >
> > > Are you aware of the release notes?  Did you read them?
> > >
> > > Did you have any install-related questions while installing?
> > >
> > > Stuff like that.  Try to figure out what users actually do when
> > > installing AOO.  We like to think they read all the material we
> > > create.  But I bet most of them just "click and pray".
> > >
> >
> > Yeah, I was  aware of the divide in downloads vs instruction views quite
> > some time ago. :/  Since I've only installed on Linux and know how to do
> > that successfully for my needs, it would be nice if we could improve
and/or
> > clarify the experience for other platforms -- but I don't know what they
> > experience.
> >
> > "click and pray" is probably very descriptive. Assuming some are not
likely
> > to ever use the Install Instructions, is there anything we can do during
> > the install process to assist them in NOT getting unexpected results?
> > That's the crux of the matter.
> >
> > For instance, can 2) above in your list be modified to make them more
> aware
> > of what this means and what will happen? (I don't see anything like this
on
> > Linux install).
> >
> 
> I believe users only consult these instruction if "click and pray" fails.
> If we want to make users aware of hash etc, we should write it on the
> initial splash screen. I know that is no guarantee the people actually
read
> it, but at least it guarantees they have seen it.
> 
> rgds
> jan I.
> 
> 
> >
> >
> >
> >
> > >
> > > Regards,
> > >
> > > -Rob
> > >
> > > >
> > > >
> > > > --
> > > >
> > >
> >
----------------------------------------------------------------------------
---------------
> ------
> > > > MzK
> > > >
> > > > "Cats do not have to be shown how to have a good time,
> > > >  for they are unfailing ingenious in that respect."
> > > >                                        -- James Mason
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> > > For additional commands, e-mail: dev-help@openoffice.apache.org
> > >
> > >
> >
> >
> > --
> >
> >
----------------------------------------------------------------------------
---------------
> ------
> > MzK
> >
> > "Cats do not have to be shown how to have a good time,
> >  for they are unfailing ingenious in that respect."
> >                                        -- James Mason
> >


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Mime
View raw message