Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

On 04/07/11 07:06, Ian Lynch wrote:
On 3 July 2011 21:38, Robert Derman<>  wrote:

Ian Lynch wrote:

On 2 July 2011 23:22, Robert Derman<>  wrote

Keith Curtis wrote:

The problem with building a reader is that it would be about the same
as LibreOffice. OpenDocument is very different from PDF. For those who
install LO, they probably can't install the reader either

Perhaps separating the modules of LO so that users could download and
install only the parts that they actually want, for instance I NEVER use
spreadsheets and probably never would use any part of the LO package
than Writer.  There is a small chance that I might use the database, but
rest of it never.

The snag as I understand it is that there is a lot of code shared between
components so separating them is not easy and would not result in as big a
saving in "size" as one would think. I use Writer but I tend to use Google
spreadsheets as I need to share them collaboratively. I use Inkscape
than Draw simply because I like it better. I doubt I would ever use Base.
Perhaps Impress on occasions. But I think Impress and Draw share a lot of
code so its probably not going to save much having one without the other.

I believe there is quite a bit of redundant code in OOo so would a better
starting point not be to get rid of as much of this as possible?

As I understand this is being done by the LO developers and much more
effectively than OOo ever did.  As I understand doing a general clean-up of
the code was never a priority with Sun management, although it probably
should have been.

Good to know.

What I am wondering is if there aren't a lot of users like me who only ever
use Writer and are not likely to ever use any of the other modules.


  In any case, I think that it might be a good idea to do a survey of LO
users and find out how many only use one of the modules, and if so which
one.  If such a survey shows that a substantial number say 40% of users only
use Writer, then it might be a good idea to work to be able to offer a
Writer only package.  I know that if a Writer only package were available
from LibreOffice, that is what I would download and use.

what if a Writer only package only save 30% of the code size, was quite a
lot of work to achieve and then you were left with two sets of code to
maintain? Would it be worth it? Don't get me wrong, I'd like to see
independent components. I'd also like to see at least Writer on Smartphones
and Tablets and I'd like to see a good web implementation of Writer. All
about the resources and priorities in the end.

To produce such a package I expect,  would mean stripping out ALL code not
used specifically by Writer.

Sorry to come in late on this thread, but there is an android ODF reader:

It seems to have rather come to a halt, but there may be code there which could be massaged into a reader (?)

I'm in no way a developer, and have little experience with the reader, other than finding it can't open encrypted files. I suggested this to the developer, but he indicated he wasn't actually working on the project currently.



Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.