Date: Mon, 7 Jun 2010 12:54:33 -0400 From: Alejandro Imass <ait@p2ee.org> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: office apps Message-ID: <AANLkTil2gpibF2N2Bir_eewMBQXru5L8Wln0EbqrUszw@mail.gmail.com> In-Reply-To: <20100607164035.GC2102@libertas.local.camdensoftware.com> References: <20100606203416.GF46089@libertas.local.camdensoftware.com> <20100607112150.6824a94f@icy.localdomain> <20100607164035.GC2102@libertas.local.camdensoftware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 7, 2010 at 12:40 PM, Chip Camden <sterling@camdensoftware.com> wrote: > On Jun 07 2010 11:21, Anh Ky Huynh wrote: >> On Sun, 6 Jun 2010 13:34:16 -0700 >> Chip Camden <sterling@camdensoftware.com> wrote: >> >> > This might not be the right list for this question -- if so, please >> > slap me over to the right one. >> > >> > Does anyone have a recommendation for a lighter-weight office suite? >> > OOo is such a pig. =A0It takes a good minute to start it up and open a >> > spreadsheet. >> >> There are some tips to speed up your Ooo. But if your Ooo took minute to= start, I guess that your system has a low hardware? > > I wouldn't have thought that an Intel Core i3 M350 (2.27Ghz) with 4GB wou= ld be > considered "lo (sic) hardware". =A0Everything else runs very quickly, eve= n > Windows 7 in VirtualBox. =A0OOo is the only time I find myself waiting > impatiently. >> Well, now that I recall I had a similar issue with the Android SDK under Linux, and it's related to your problem because OO uses gjc (the GNU Java implementation) as a pre-requisite and Eclipse was using _that_ instead of the Sun jdk I had installed. Well the issue is that Eclipse _took FOREVER_ to start, much like what you are describiong right now with OO (albeit I use FBSD with OO in older hw w/ no problems). Anyway, chack to see if you may have a broken Java implementation, and check to see if it's possible to get OO to work with Sun's JRE 6, and give that a go and see. I have a gut feeling your problem is related to a broken Java VM somewhere in your machine.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTil2gpibF2N2Bir_eewMBQXru5L8Wln0EbqrUszw>