Hi all,
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?
This was one of my first ideas, too. [That's why I asked about the use of JRE in a previous post. ;-) ]
Well, I have learned that Base uses Java, but I do not use Base. And most people I know do not use Base (or Access). So, my impression is, that OOo should come without Java.
Then, of course, I have grown up with R (http://cran.R-project.org). This program has > 1,000 packages, and many packages depend on other packages. When you install one package, this will install automatically all dependent packages. No need for user interaction.
So why not split OOo into a module/package-based product. When one user chooses to use a (rare) component that needs an additional package, download automatically only that package. This would be indeed nice.
I wholeheartedly recommend splitting Base from the main OOo. There are not many Base users. And if you would make upgrading OOo (w/o Base) easily to OOo+Base, then this is the *correct solution*. [This is of course one approach that needs some time to implement.]
Sincerely, Leonard --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
