Hi *,
and happy new year :-)
On Dec 21, 2007 4:04 PM, :murb: [maarten brouwers] <[EMAIL PROTECTED]> wrote:
>
> > Complicated business
> > 5. You can go into enourmous detail with detecting, but how far do you
> > want to go (RPM/DEB discussion)
> > 6. The problem would be too hard if we want to tackle multiple languages
> > at the same time, and we should tackle that, since otherwise they
> > might simply leave
> >
> The current idea is that the 'download button' is not always a direct
> one-click download, but in case of linux may for example present the user
> with a new page, explaining the different options, including maybe even a
> recommendation of just trying to start Synaptic.
OK, then all this fuzz was based on the assumpiion, that it should
really be a one-click solution, as has been stressed multiple times.
If it is not a one click solution but a step-by-step solution with a
reduced set of options to choose from, based on the autodetection,
then I'm far less reserved.
> > User friendlyness
> > 9. Have no space to inform them about almost ready versions
Nah, you got that wrong. That was referring to localized versions that
might not be available at the same time as the english one. And when
talking about a really-one-click download you cannot use language
detection at all. In fact, with the current system you cannot do
language detection in any case - it is just too unreliable.
You could do a simultaneous launch of the "big" languages (in term of
big/fast QA) that aim to release at the same time, but that would be
bad, since then you would offer some languages right at the beginning,
but others only from some "hidden" place, and when you want to offer
all languages, then you have the problem of keeping track of what is
the current versions.
Even with the "big" QAs, there is often the situation that one OS is
not approved at the same time as others - so the point is that you can
only provide english OOo and that language detection is a bad thing.
But given that we're not talking about a one-click solution anymore,
this ain't a problem.
> > 10. The majority don't want default selections, except maybe for OS.
>
> Do we now inform them about upcoming versions? Or is that something you
> would like to do?
The notification is within OOo (check for updates), so for existing
users, this is not a problem. They choose whether they want to be
informed of new versions or not. The problem is for new users (that
don't want the english version) see above.
> I do however believe that the majority will benefit from a quick, advising
> link. I see this argument more of an argument for making sure that the
> 'alternative' download page should get proper attention as well.
No. It was advocating against a one-click solution. But as this is now
no longer the thing that is wanted, I'm fine with it and sketch the
following navigation theme:
Notes: I expect a "get OOo via P2P/Bittorrent[1] or on CD" link(s) and
a "get OOo in your native language" or a similar button to be visible
all the time during the download selection. The main download page
only offers english OOo
Whether the following is realized using one single, big page or
realized using redirects is an implementation detail
So user clicks download:
This step is optional:
site checks whether browser language is english or something different
if browser is set to language other than english:
prominent "You might be interested in a localized version of
OOo, please see 'landing page with localized versions'" button/link
site checks the operating system of the browser
Note: in all cases a "get OOo for other platforms" link/button
should be available
if windows
offer only button/links for with JRE and without JRE
optionally check for JRE-plugin. If available, default to the
without JRE download (highlight color or similar)
if linux
offer only buttons for DEB/RPM Add hint wrt getting/installing a JRE.
(Novice users should install a JRE via the distribution's
package management, not manually)
if Mac
Not sure whether to offer download links or immediately
redirect to the Mac--download pages
add a hint that the builds need X11 installed (link to
instructions on how to install X11 on Mac)
optionally check for version (10.4 and newer vs older
versions) (if that is not possible, add a hint that 10.3 needs a
legacy build
optionally detect Architecture PPC/Intel and default to that arch
show buttons for Intel and PPC (and dependig on OS detection
add a "get OOo for Mac OSX 10.3" one)
if Solaris
optionally detect sparc/x86
only show links for the arch or both (solaris user will
probably know...)
else (other OS or unsure)
add link/button to manual selection page
show link to porting projects optionally add direct links for
FreeBSD and LInuxPPC
if the user chooses manual selection (get OOo for other platform) the
user is redirected to a page with a flat table that lists all the
english downloads for the main platforms (and a link button to the
localized landing page of course) and a link to the porting page.
[1] I'd prefer if those links were beneath the traditional download
buttonsm but I can live with only having a separate page for that
Would that fit more or less your ideas?
ciao
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
