Hi Christian, > sorry for the delay, this sat in my outbox unnoticed.. never mind :) happens to all of us :)
I'll try to summarize your response: > Unpredictable behaviour of users > 1. OOo is big, so higher chances of being downloaded for someone else > 2. Browser languages are not always equal to the desired OOo language > Hard to know, depends also on which country you are targeting. In most of Europe bandwidth is not so much of a problem for most (>80% has cable/(a)dsl/...) [1] On the other hand you assume that the alternative download page should become harder to use than the current one. That is just something to fight for then ;) It is like the store, is 'this something what you are looking for?', and if you can make it in such a way that 80% answers it with yes (which may also be a friend who downloads OOo for Windows for another friend who runs OOo for Windows, you saved those a whole lot of effort). For the other 20% you can create an as accessible page as the current one, which isn't such a bad page after all (of course I never should say so ;) ) > Java is hard to detect, and may still not be necessary > 3. Java may simply be disabled as a plugin, but available on the machine > 4. Java is not an absolute requirement > 7. Not all servers may carry the with JRE versions (not sure whether I > got this correctly) > 8. If user has no JRE, it might be because it conflicts with his/her > system > Very valid comments. You convinced me of dropping JRE detection. It may come down to Sun's marketing wishes here... because I would like to steer the majority to only ONE option, making download a no brainer. What should we recommend, without having to explain too much? No JRE, and if they complain Base is not working, tell them to download JRE? Or with JRE, and if they care about bandwidth, and the other tools on their computer, they should have been more careful? > 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. > User friendlyness > 9. Have no space to inform them about almost ready versions > 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? 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. g., Maarten [1] http://epp.eurostat.ec.europa.eu/pls/portal/docs/PAGE/PGP_PRD_CAT_PREREL/PGE_CAT_PREREL_YEAR_2007/PGE_CAT_PREREL_YEAR_2007_MONTH_12/4-03122007-EN-BP.PDF --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
