eric b wrote: > FYI, OOo4Kdis runs honestly on Celeron 500 + 128 MB or RAM ( using > Puppy Linux distribution ), or on XO ( Sugar / 900 MHz / 521 MB or > RAM). > > The drawback : no Java, nor Base, but who cares, if we got a reader ? > Yep, played with it on a Celeron 400 / 256 Megs here, and actually snappy, once retrieved from the slow disk. ;)
> >If K-office does it better then OOo has a problem. If K-office gets > >established in the mobile space I doubt OOo will then get in at all. > > > > IMHO, the fact Nokia has been choosen by Nokia, is because of the QT > dependency ( QT wass TrollTech and is now Nokia ) > KOffice choosen by Nokia, I assume - yep, that has surely helped. But from what I could glean from the code base, the KOffice folks managed separation between cores and UI much better than OOo did, which would be a huge head start for such a project. Both project renaissance & OOo4Kids provide big opportunities to put effort into exactly that - making OOo less monolithic, and easier to reuse parts of it / re-deploy it under completely new UIs. I only hope those opportunities will not be missed. Cheers, -- Thorsten
pgpmKm4ue9iku.pgp
Description: PGP signature
